Wireshark

  • Riverbed Technology
  • WinPcap
the world's foremost network protocol analyzer
  • Wireshark
    • About
    • Download
    • Blog
  • Get Help
    • Ask a Question
    • FAQs
    • Documentation
    • Mailing Lists
    • Online Tools
    • Wiki
    • Bug Tracker
  • Develop
    • Get Involved
    • Developer's Guide
    • Browse the Code
    • Latest Builds

Wireshark-users: Re: [Wireshark-users] Understanding what I'm seeing

Date Index Thread Index Other Months All Mailing Lists
Date Prev Date Next Thread Prev Thread Next


From: <juan.wortley@xxxxxxx>
Date: Wed, 10 Oct 2007 11:29:02 -0500

Hi,

Be sure you do not have a firewall in your PC. Check it in Network Connections->Properties.
 

>-----Original Message-----
>From: wireshark-users-bounces@xxxxxxxxxxxxx 
>[mailto:wireshark-users-bounces@xxxxxxxxxxxxx] On Behalf Of 
>ext Luis EG Ontanon
>Sent: MiƩrcoles, 10 de Octubre de 2007 01:25 p.m.
>To: Community support list for Wireshark
>Subject: Re: [Wireshark-users] Understanding what I'm seeing
>
>If your network card is known to work in "promiscuous mode" 
>the problem is probably that the mirror port is not working propperly.
>
>If CDP is enabled and you see CDP packets whose source 
>interface is declared to be the one you are connected, the 
>mirroring is not working properly, it is working as a normal 
>port not as a SPAN one.
>
>
>
>On 10/10/07, Chad Webb <Chad.Webb@xxxxxxxx> wrote:
>> I do have "promiscous mode" checked within the Options screen
>>
>> Luis EG Ontanon said the following on 10/10/2007 10:22 AM:
>> > The symptoms are those of not capturing in promiscuous mode, I.e. 
>> > you see only broadcast packets and those directed to your machine 
>> > (which in this case do not exist).
>> >
>> > Set the "Capture n promiscuous mode" flag in the capture dialog.
>> >
>> > On 10/10/07, Giles Coochey <gcoochey@xxxxxxxxxxx> wrote:
>> >>> Obviously the port monitoring is incorrect. Cisco does a 
>great job 
>> >>> of being inconsistent across their product line (but don't tell 
>> >>> that to
>> >> the
>> >>> layer 3 guys - most insist Cisco can do no wrong as an article of
>> >> faith).
>> >>
>> >> Are you sure that the port monitoring is wrong for a 3560?
>> >>
>> >> Maybe I'm missing something.
>> >>
>> >> Giles
>> >> _______________________________________________
>> >> Wireshark-users mailing list
>> >> Wireshark-users@xxxxxxxxxxxxx
>> >> http://www.wireshark.org/mailman/listinfo/wireshark-users
>> >>
>> >
>> >
>>
>> --
>> Chad S. Webb
>> Systems Administrator
>> General Dynamics Information Technology NOAA\NESDIS\NCDDC 
>Bldg 1100 Rm 
>> 117 Stennis Space Center, MS 39529
>> Voice: 228.688.3808
>> Email: Chad.Webb@xxxxxxxx; chad.webb@xxxxxxxx www.gdit.com 
>> _______________________________________________
>> Wireshark-users mailing list
>> Wireshark-users@xxxxxxxxxxxxx
>> http://www.wireshark.org/mailman/listinfo/wireshark-users
>>
>
>
>--
>This information is top security. When you have read it, 
>destroy yourself.
>-- Marshall McLuhan
>_______________________________________________
>Wireshark-users mailing list
>Wireshark-users@xxxxxxxxxxxxx
>http://www.wireshark.org/mailman/listinfo/wireshark-users
>

  • References:
    • [Wireshark-users] Understanding what I'm seeing
      • From: Chad Webb
    • Re: [Wireshark-users] Understanding what I'm seeing
      • From: Randy . Grein
    • Re: [Wireshark-users] Understanding what I'm seeing
      • From: Giles Coochey
    • Re: [Wireshark-users] Understanding what I'm seeing
      • From: Luis EG Ontanon
    • Re: [Wireshark-users] Understanding what I'm seeing
      • From: Chad Webb
    • Re: [Wireshark-users] Understanding what I'm seeing
      • From: Luis EG Ontanon
  • Prev by Date: Re: [Wireshark-users] Understanding what I'm seeing
  • Next by Date: Re: [Wireshark-users] Understanding what I'm seeing
  • Previous by thread: Re: [Wireshark-users] Understanding what I'm seeing
  • Next by thread: Re: [Wireshark-users] Understanding what I'm seeing
  • Index(es):
    • Date
    • Thread

Wireshark and the "fin" logo are registered trademarks of the Wireshark Foundation