Re: Wired vs wireless - comm trace needed

Jeff,

Just guessing here so if you already know/have tried just ignore me.

In order to use any sniffer your PC NIC has to be in the data path of
what you want to watch. If you are using a switch (hope so) then just
plugging in to the switch doesn't get you in the data path.

Most managed switches have what they call an RMON port configuration
which allows you to say that any traffic to/from PORT(s) X gets copied
to PORT Y, which is where you attach the PC with the sniffer.

Also, you could plug an old cheap hub between the AP and the network
then plug in the PC so you see everything going to/from the AP.

I haven't upgraded to WireShark yet but in Ethereal you can configure it
to capture only traffic to/from a specific IP or a MAC.

Finally, I seem to remember that some NICs (drivers?) didn't support a
needed mode for sniffing and all you would ever see is traffic to/from
your PC. Might want to find and check the compatibility list somewhere.

Roger Vicker, CCP

On 6/12/2007 9:10 AM, Jeff Crosby wrote:

Ethereal is now called "WireShark". Found that out _after_ I had downloaded
and installed Ethereal. <g>

Wireshark is what I've been trying to sniff with. It seems WinPCap (some
underlying thing in Windows to enable sniffing) is unable to handle
wireless. So all my attempts have been moot.

So now I will begin the journey into i5 comm tracing. Am I right that I
should be able to limit it to this particular IP address?

Open that Infocenter! Read those fine manuals! Try to stay awake while
doing so!