Sniffing a DHCP Boot

Bill Fox <wbfox@goodyear.com> Wed, 10 April 1996 12:27 UTC

Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa13831; 10 Apr 96 8:27 EDT
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa13827; 10 Apr 96 8:27 EDT
Received: from reef.bucknell.edu by CNRI.Reston.VA.US id aa06596; 10 Apr 96 8:27 EDT
Received: from localhost by reef.bucknell.edu with SMTP (5.65/IDA-1.2.8) id AA00139; Wed, 10 Apr 1996 08:25:38 -0400
Date: Wed, 10 Apr 1996 08:25:38 -0400
Message-Id: <9604101143.AA28951@rdsrv2>
Errors-To: droms@bucknell.edu
Reply-To: dhcp-v4@bucknell.edu
Originator: dhcp-v4@bucknell.edu
X-Orig-Sender: dhcp-v4@bucknell.edu
Precedence: bulk
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Bill Fox <wbfox@goodyear.com>
To: Multiple recipients of list <dhcp-v4@bucknell.edu>
Subject: Sniffing a DHCP Boot
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas
X-Comment: Discussion of DHCP for IPv4
Mime-Version: 1.0
X-Mailer: Windows Eudora Version 1.4.4

We are testing DHCP as served by Windows NT, and just to NT clients
right now.  My Network General Sniffer did not see DHCP, so I asked 
their support group if DHCP is decoded.  The answer was, "We don't
think so."

In the trace file, which is taken from the client end, 
I see BOOTP packets, then an ARP for the IP address of the client
workstation, from the client workstation.

Do you folks have any experience with this?
--------------------------------------------------------
   The opinions expressed herein are my own and not 
 necessarily those of Goodyear Tire and Rubber Company
            Goodyear can have its own opinions
--------------------------------------------------------
Bill Fox                              wbfox@goodyear.com
Senior Network Engineer - d/450B      Phone 330.796.7495
Goodyear Tire and Rubber Company      FAX   330.796.1671
Akron, OH                  44316      Hope  in Christ
--------------------------------------------------------