RE: Wired vs wireless - comm trace needed -- MIDRANGE-L

Subject: RE: Wired vs wireless - comm trace needed
From: "Jeff Crosby" <jlcrosby@xxxxxxxxxxxxxxxx>
Date: Tue, 12 Jun 2007 10:10:02 -0400
List-archive: <http://archive.midrange.com/midrange-l>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

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!

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

RE: Wired vs wireless - comm trace needed , Mike Krebs
Re: Wired vs wireless - comm trace needed , Roger Vicker, CCP

This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.