Date: Fri, 12 Sep 1997 10:11:46 -0400 (EDT) From: Chuck Robey <chuckr@glue.umd.edu> To: Brian Mitchell <brian@firehouse.net> Cc: FreeBSD-Hackers <FreeBSD-Hackers@FreeBSD.ORG> Subject: Re: network programming. Message-ID: <Pine.BSF.3.96.970912100955.17492D-100000@Journey2.mat.net> In-Reply-To: <Pine.BSI.3.95.970912054532.16712A-100000@shell.firehouse.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 12 Sep 1997, Brian Mitchell wrote: > On Thu, 11 Sep 1997, 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. > > man 3 pcap, man 4 bpf Sorry for the previous blank post. Using the pcap lib is a little much for someone who's struggling yet to get their first app working, so I'm using tcpdump, as SO many have suggested. Thanks to everyone for the suggestions, which were right on the money. > > > > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@eng.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic, both FreeBSD (301) 220-2114 | version 3.0 current -- and great FUN! ----------------------------+-----------------------------------------------
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.96.970912100955.17492D-100000>