Re: Sniffing a DHCP Boot
"Michael J. Lewis" <hosmjl@chevron.com> Wed, 10 April 1996 17:49 UTC
Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa22932;
10 Apr 96 13:49 EDT
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa22928;
10 Apr 96 13:49 EDT
Received: from reef.bucknell.edu by CNRI.Reston.VA.US id aa12160;
10 Apr 96 13:49 EDT
Received: from localhost by reef.bucknell.edu with SMTP
(5.65/IDA-1.2.8) id AA21296; Wed, 10 Apr 1996 12:58:36 -0400
Date: Wed, 10 Apr 1996 12:58:36 -0400
Message-Id: <316BE736.4477@chevron.com>
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: "Michael J. Lewis" <hosmjl@chevron.com>
To: Multiple recipients of list <dhcp-v4@bucknell.edu>
Subject: Re: 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: Mozilla 2.0 (Win95; I)
On the software side, Microsoft's Network Monitor does a decent job of decoding DHCP. It has some faults, namely it does not recognize the type of packet if the packet type is not the first option after the magic cookie; it does translate ASCII options like domain name into ASCII on the decode; it does not display secondary and/or tertiary addresses for DNS and WINS servers, and its provides some judgmental (and erroneous) proannouncements on packets. Most of these faults, though, are mere nusances. On the plus side, Microsoft recognizes DHCP packets as DHCP (since they don't support BOOTP anyway)
- 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