Date: Fri, 12 Sep 1997 08:57:07 -0400 (EDT) From: Jamie Bowden <jamie@itribe.net> To: "Eric A. Davis" <edavis@nas.nasa.gov> Cc: Chuck Robey <chuckr@glue.umd.edu>, FreeBSD-Hackers <FreeBSD-Hackers@freebsd.org> Subject: Re: network programming. Message-ID: <199709121249.IAA17231@gatekeeper.itribe.net> In-Reply-To: <199709112327.QAA10762@shark.nas.nasa.gov>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 11 Sep 1997, Eric A. Davis wrote: > > You want tcpdump located at /usr/sbin/tcpdump. > > > On Thu, 11 Sep 1997 19:06:26 -0400 (EDT) Chuck Robey wrote > >I have to do my very first network programming, a UDP client+server, and I > >was wondering if anyone knows of how I could go about intercepting > >something sent to a UDP socket, so I could use it for troubleshooting? I > >don't want to receive it (else the client would never get it), just to > >monitor what's going on. This is my home machine, and I (obviously) have > >root here. > > > >I don't want the application written for me, just a tool I could use to > >capture what's going on between my buggy server and my buggy client. > > > >Thanks for any hints, guys. > > > >----------------------------+----------------------------------------------- > >Chuck Robey | Interests include any kind of voice or data > > -- > Eric Allen Davis Network Engineer If tcpdump does all traffic on an interface, shouldn't it be renamed to reflect that capability? Not having used tcpdump, based on the name, I would have thought it was for monitoring tcp traffic, and wouldn't do udp. Jamie Bowden System Administrator, iTRiBE.net Abusenet: The Misinformation Superhighway
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199709121249.IAA17231>