RE: Default Gateways
Munil Shah <munils@microsoft.com> Thu, 29 February 1996 00:36 UTC
Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa06182;
28 Feb 96 19:36 EST
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa06178;
28 Feb 96 19:36 EST
Received: from coral.bucknell.edu by CNRI.Reston.VA.US id aa17422;
28 Feb 96 19:36 EST
Received: from charcoal-gw.eg.bucknell.edu by coral.bucknell.edu;
(5.65v3.0/1.1.8.2/29Aug94-0956AM)
id AA19945; Wed, 28 Feb 1996 19:16:20 -0500
Received: from reef.bucknell.edu by charcoal (5.x/SMI-SVR4)
id AA18167; Wed, 28 Feb 1996 19:03:21 -0500
Received: from red-05-imc.itg.microsoft.com by reef.bucknell.edu with SMTP
(5.65/IDA-1.2.8) id AA00901; Wed, 28 Feb 1996 19:03:18 -0500
Received: by red-05-imc.itg.microsoft.com with Microsoft Exchange (IMC 4.0.822)
id <01BB05F6.3BC8A700@red-05-imc.itg.microsoft.com>;
Wed, 28 Feb 1996 16:03:00 -0800
Message-Id: <c=US%a=_%p=msft%l=RED-75-MSG-960229000210Z-6040@red-05-imc.itg.microsoft.com>
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Munil Shah <munils@microsoft.com>
To: "dhcp-v4@bucknell.edu" <dhcp-v4@bucknell.edu>,
"'bclark@ccmailpc.ctron.com'" <bclark@ccmailpc.ctron.com>
Cc: Pradeep Bahl <pradeepb@microsoft.com>
Subject: RE: Default Gateways
Date: Wed, 28 Feb 1996 16:02:09 -0800
X-Mailer: Microsoft Exchange Server Internet Mail Connector Version 4.0.822
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
I dont think it is specified anywhere in the RFCs, how to support the kind of DHCP server behaviour you need below. Microsoft's DHCP server does support default gateway option as described in RFCs. As I suggested earlier, you can do something like this for reserved ip addresses. But for automatic addresses, it will require some special intelligence(code) on the DHCP server side to give out the default gateway address same as client's IP address. Are you suggesting that there are other(non-microsoft) dhcp servers that support this? Thanks, -Munil >---------- >From: bclark@ccmailpc.ctron.com[SMTP:bclark@ccmailpc.ctron.com] >Sent: Wednesday, February 28, 1996 7:59 AM >To: Munil Shah; dhcp-v4@bucknell.edu >Cc: Pradeep Bahl >Subject: Re: Default Gateways > > > We sell a large number of our switching products and many of our > customers are seeing that switching is allowing them to remove >routing > from their networks. This, in effect, flattens the network to one > large network. > > While routing does a good job for keeping traffic localized, >routers > in general are a bottleneck for networks that regularly > intercommunicate with each other. Switches eliminate this >bottleneck > because they provide traffic management without creating a >bottleneck. > > Without getting into the cons and pros of routers and switches, we > > have several very large customers with thousands of host >computers. > They have gone with a switch environment and are removing their > routers from their network. > > Since the routers have been removed from the network, it is up to >the > host to perform its own gateway functions. Class a and class b >subnets > are not so much an issue as class c subnets are. > > Many of our customers use an intermix of class c subnet structures >to > help manage their workgroups. With only 255 host available in each > > class c subnet, multiple subnets are obviously needed. Because the > > network is flat they need to have every DHCP client use itself as >a > default gateway so that they can talk to other clients. > > 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. > > Regards, > Bret Clark > Product Management > Cabletron Systems >
- Re: Default Gateways bclark
- Re[2]: Default Gateways bclark
- RE: Default Gateways Munil Shah
- Re: Default Gateways Richard Letts