From owner-freebsd-hackers  Fri Sep 12 02:46:24 1997
Return-Path: <owner-freebsd-hackers>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id CAA21551
          for hackers-outgoing; Fri, 12 Sep 1997 02:46:24 -0700 (PDT)
Received: from shell.firehouse.net (brian@shell.firehouse.net [209.42.203.45])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id CAA21546
          for <FreeBSD-Hackers@FreeBSD.ORG>; Fri, 12 Sep 1997 02:46:20 -0700 (PDT)
Received: from localhost (brian@localhost)
	by shell.firehouse.net (8.8.5/8.8.5) with SMTP id FAA16736;
	Fri, 12 Sep 1997 05:46:04 -0400 (EDT)
Date: Fri, 12 Sep 1997 05:46:01 -0400 (EDT)
From: Brian Mitchell <brian@firehouse.net>
To: Chuck Robey <chuckr@Glue.umd.edu>
cc: FreeBSD-Hackers <FreeBSD-Hackers@FreeBSD.ORG>
Subject: Re: network programming.
In-Reply-To: <Pine.BSF.3.96.970911190130.2260C-100000@Journey2.mat.net>
Message-ID: <Pine.BSI.3.95.970912054532.16712A-100000@shell.firehouse.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

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