Re: Default Gateways.

"David B. Stewart" <dbstewa@metronet.com> Sun, 25 February 1996 05:42 UTC

Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa06670; 25 Feb 96 0:42 EST
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa06666; 25 Feb 96 0:42 EST
Received: from reef.bucknell.edu by CNRI.Reston.VA.US id aa01328; 25 Feb 96 0:42 EST
Received: from localhost by reef.bucknell.edu with SMTP (5.65/IDA-1.2.8) id AA11084; Sun, 25 Feb 1996 00:39:38 -0500
Date: Sun, 25 Feb 1996 00:39:38 -0500
Message-Id: <2.2.32.19960225052145.008ec64c@metronet.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: "David B. Stewart" <dbstewa@metronet.com>
To: Multiple recipients of list <dhcp-v4@bucknell.edu>
Subject: Re: Default Gateways.
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas
X-Comment: Discussion of DHCP for IPv4
X-Mailer: Windows Eudora Pro Version 2.2 (32)

Sorry for the overdue reply to this, but I've been on vacation and just now
catching up...

Bret's idea touches on a fringe that may require further consideration.
Using a  local host's address as its own default gateway seems to have a lot
of popularity in dial-up (check out "ipconfig /all" or "winipconfig" on a
Mickeysoft PC's PPP adapter).  It has also found use in avoiding renumbering
hassles as default gateway addresses change.  I saw no responses to Bret's
query beyond that attached.  Anyone else see a need?  Is Bret's issue a MS
NT limitation (scuttle of late sez MS seems rather free-willed with
implementations of some IP standards) or is this a simple case of DHCP v4
never did it that way and never will?

-dave

At 05:45 AM 2/16/96 -0500, you wrote:
>bclark@ccmailpc.ctron.com writes:
>> 
>> 
>>      Any suggestions on how I can make a dhcp client use its own IP address 
>>      as the default gateway using dhcp server on an NT box? I'm not on this 
>>      mailing list so please cc any replies back to my address.
>>      
>>      Regards,
>>      Bret Clark
>>      Cabletron Systems
>>      bclark@ctron.com
>> 
>It means that your client is a router and it is requesting an IP address from
>the DHCP server. BUT in the beginning of the DHCP RFC , it is clearly
>mentioned that DHCP is not intended for use in configuring routers...
> 
>regards:
>Rajesh Saluja
>email: rsaluja@wipinfo.soft.net
>
>