Re: Sniffing a DHCP Boot

Evan Wetstone <evanw@sabine.us.dell.com> Wed, 10 April 1996 14:12 UTC

Date: Wed, 10 Apr 1996 10:07:52 -0400
Message-Id: <199604101310.IAA09588@sabine.us.dell.com>
Errors-To: droms@bucknell.edu
Reply-To: dhcp-v4@bucknell.edu
Originator: dhcp-v4@bucknell.edu
Precedence: bulk
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Evan Wetstone <evanw@sabine.us.dell.com>
To: Multiple recipients of list <dhcp-v4@bucknell.edu>
Subject: Re: Sniffing a DHCP Boot

Bill Fox writes:
> 
> 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?

DHCP is supported by the Sniffer, it just gets called BootP due to the 
same port numbers (67 and 68) being used.  If you look at the detail of
the captured packets, you'll see that while it calls it a BootP packet,
the decode also correctly identifes DHCPDiscover, DHCPOffer, etc.

-- 
Evan Wetstone                                                evanw@dell.com

	 	    The Network Works.  No Excuses.

Sniffing a DHCP Boot Bill Fox
Re: Sniffing a DHCP Boot KEY
Re: Sniffing a DHCP Boot Evan Wetstone
Re: Sniffing a DHCP Boot Evan Wetstone
Re: Sniffing a DHCP Boot Greg E Hersh
Re: Sniffing a DHCP Boot Michael J. Lewis