Re[2]: Default Gateways

bclark@ccmailpc.ctron.com Wed, 28 February 1996 21:11 UTC

Date: Wed, 28 Feb 96 15:39:27 EST
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: bclark@ccmailpc.ctron.com
Encoding: 2387 Text
Message-Id: <9601288255.AA825550768@ccmailpc.ctron.com>
To: "Edie E. Gunter" <edie@watson.ibm.com>, dhcp-v4@bucknell.edu
Subject: Re[2]: Default Gateways

     All we are trying to do is allow tell the DHCP client that its IP 
     address should be the same one it uses as its default gateway address. 
     That way, when the DHCP client needs to transmit to a different 
     subnet, it can use itself as the gateway, rather then sending the 
     packet to a router for the relay. Of course in a switched network 
     sometimes routers don't exist and multiple subnets exist in the same 
     network and that is where the problem is occurring.
     
     DCHP allows you to send default gateways, but the 0.0.0.0 is not 
     working on an MS-NT DHCP server, which, in the TCP/IP world, is 
     suppose to mean local host. So either the RFC is not written 
     correctly, or MS has not implement it correctly, or it hasn't been 
     addressed in the DHCP RFC. I can't say which is the case.
     
     You can manually create default routes at each windows 95 or NT box by 
     typing: route add 0.0.0.0 MASK 0.0.0.0 [the DHCP client's IP]. This, of 
     course, defeats the purpose of DHCP though and doesn't work once the lease 
     expires.
     
     Any other questions, please let me know,
     
     Bret
______________________________ Reply Separator _________________________________
Subject: Re: Default Gateways
Author:  "Edie E. Gunter" <edie@watson.ibm.com> at !INTERNET
Date:    2/28/96 2:29 PM


>      In summary, we have customers using flat networks, different subnets, 
>      no routers, and are experiencing communication problems because DHCP 
>      (under NT) doesn't support default gateways.
     
Hi,
     
I saw your post to the dhcp-v4 working group, and I'm trying to 
understand how DHCP is getting in the way.  Are you saying that 
the NT DHCP server does not allow you configure some particular 
DHCP option you need?  Or is there a DHCP client in your network 
that is unable to process the option received from that server? 
Does "doesn't support default gateways" mean there is a DHCP 
option problem?  (If so, which option?)
     
Or is the problem elsewhere?  Like, perhaps the server doesn't 
let you serve multiple subnets on the same physical network 
because of a lack of a way to specify this in the server 
configuration tools?
     
I'm baffled, and since I'm currently working with MS DHCP 
clients, I'm concerned.
     
Edie