Re: DHCP Spoofing
William Burns <wdburns@cstar.ac.com> Fri, 01 November 1996 17:58 UTC
Received: from cnri by ietf.org id aa18679; 1 Nov 96 12:58 EST
Received: from marge.bucknell.edu by CNRI.Reston.VA.US id aa15479;
1 Nov 96 12:58 EST
Received: from reef.bucknell.edu by mail.bucknell.edu;
(5.65v3.2/1.1.8.2/17Jul96-0109PM)
id AA31652; Fri, 1 Nov 1996 12:51:22 -0500
Date: Fri, 1 Nov 1996 12:51:22 -0500
Message-Id: <9611011649.AA04381@junior.tp.ac>
Errors-To: droms@bucknell.edu
Reply-To: dhcp-v4@bucknell.edu
Originator: dhcp-v4@bucknell.edu
Sender: dhcp-v4@bucknell.edu
Precedence: bulk
From: William Burns <wdburns@cstar.ac.com>
To: Multiple recipients of list <dhcp-v4@bucknell.edu>
Subject: Re: DHCP Spoofing
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas
X-Comment: Discussion of DHCP for IPv4
Mime-Version: 1.0
X-Mailer: ELM [version 2.4 PL24]
For the ascend ISDN router/bridges, that's a setting you can set so that the ascend box will reply with a "temporary" DHCP assignment for host machines hooked up to it....I think you can also set the lease time so that you can force the client machine to renew its license once the ISDN line is up and stable. (i.e. give an address to pacify Win95 during the ISDN connection and dialup phases). At least that's how I understood it... > > I just ran into a router feature called "DHCP Spoofing". It was > in an ascend pipeline 50 router. Anyone know what DHCP spoofing is? > > -John Wobus > -- William Burns wdburns@tp.ac.com Mac/Unix Network Administrator Andersen Consulting 847.714.2098 Technology Park Network Services, Alternative Technology Group
- DHCP Spoofing John M. Wobus
- Re: DHCP Spoofing William Burns
- Re: DHCP Spoofing John M. Wobus