From owner-freebsd-hackers Fri Sep 12 07:09:52 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id HAA05460 for hackers-outgoing; Fri, 12 Sep 1997 07:09:52 -0700 (PDT) Received: from earth.mat.net (root@earth.mat.net [206.246.122.2]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id HAA05453 for ; Fri, 12 Sep 1997 07:09:47 -0700 (PDT) Received: from Journey2.mat.net (journey2.mat.net [206.246.122.116]) by earth.mat.net (8.8.7/8.6.12) with SMTP id KAA23938; Fri, 12 Sep 1997 10:09:34 -0400 (EDT) Date: Fri, 12 Sep 1997 10:09:38 -0400 (EDT) From: Chuck Robey X-Sender: chuckr@Journey2.mat.net To: Brian Mitchell cc: FreeBSD-Hackers Subject: Re: network programming. In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk 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 > > > > ----------------------------+----------------------------------------------- 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! ----------------------------+-----------------------------------------------