Date: Fri, 25 Jul 2008 08:16:16 -0400 From: "Bob McConnell" <rvm@CBORD.com> To: <freebsd-questions@freebsd.org> Subject: RE: [OT ? ] getting stats out of network capture Message-ID: <FF8482A96323694490C194BABEAC24A00306A17D@Email.cbord.com> In-Reply-To: <20080725123722.3f2263d0@ayiin> References: <20080725101242.64fdabc1@ayiin><40515BC3-EB63-4A74-9A4F-B91A6C1D1B4D@mac.com> <20080725123722.3f2263d0@ayiin>
next in thread | previous in thread | raw e-mail | index | archive | help
On Behalf Of Norberto Meijome >On Thu, 24 Jul 2008 17:42:04 -0700 >Chuck Swiger <cswiger@mac.com> wrote: >=20 >> Try something like this on the webserver or client machine: >>=20 >> # tcpdump -ttt -q -n -A tcp port 80 >=20 > Excellent, thanks Chuck. > I haven't got access to the server, and the client has to > run on a win32 ... so i'll figure out how to tcpdump on w32 > or howto in wireshark gui. On MS-Windows, the easiest option is to download and install Wireshark 1.0, which will also install Winpcap. It gives you the option of installing Winpcap as a system service, which enables it for all users, even the non-admin types. When you use it, if possible, always tie it to the NIC, not the NDIS layer. A lot of traffic is sidetracked before it gets to NDIS. In some cases where the NIC is not supported, we have found that the only traffic Wireshark can capture is what is left after every other process has received theirs. Bob McConnell
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?FF8482A96323694490C194BABEAC24A00306A17D>