Re: proxy relay agent
Rajesh Saluja <rsaluja@wipinfo.soft.net> Thu, 07 March 1996 14:31 UTC
Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa13167;
7 Mar 96 9:31 EST
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa13163;
7 Mar 96 9:31 EST
Received: from coral.bucknell.edu by CNRI.Reston.VA.US id aa06966;
7 Mar 96 9:31 EST
Received: from charcoal-gw.eg.bucknell.edu by coral.bucknell.edu;
(5.65v3.0/1.1.8.2/29Aug94-0956AM)
id AA23421; Thu, 7 Mar 1996 09:17:20 -0500
Received: from reef.bucknell.edu by charcoal (5.x/SMI-SVR4)
id AA20585; Thu, 7 Mar 1996 09:10:54 -0500
Received: from s.wipinfo.soft.net by reef.bucknell.edu with SMTP
(5.65/IDA-1.2.8) id AA10055; Thu, 7 Mar 1996 08:53:35 -0500
Received: by s.wipinfo.soft.net (4.1/SMI-4.1)
id AA07734; Thu, 7 Mar 96 19:45:07 IST
Received: from comm10 by rolex.rnd.blr (4.1/SMI-4.1)
id AA29468; Thu, 7 Mar 96 19:44:34+050
Received: (from rsaluja@localhost) by comm10 (8.6.12/8.6.9) id TAA03217 for
dhcp-v4@bucknell.edu; Thu, 7 Mar 1996 19:40:08 +0500
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Rajesh Saluja <rsaluja@wipinfo.soft.net>
Message-Id: <199603071440.TAA03217@comm10>
Subject: Re: proxy relay agent
To: DHCP MAILING LIST <dhcp-v4@bucknell.edu>
Date: Thu, 7 Mar 1996 19:40:07 +0500 (GMT+0500)
X-Mailer: ELM [version 2.4 PL24]
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sorry if you get a duplicate copy, since the previous mail bounced back. > What I was alluding to in the last mail was that if you want the > dial-in client to use DHCP to obtain its IP address then there is a > timing issue since IPCP may not be up by the time DHCP tries to get > the address. This is one of the reasons we use the proxy client > method. In the proxy client case the remote access server is doing > the DHCP work and, as you say, passes the IP address back to the > dial-in client using IPCP. I agree ... > It's up to the dial-in client to know how > to take that address and force it down into the IP stack, which is not > necessarily that easy (and I don't know whow it's done, the client > software folks handle that end). How it is difficult? It will easily be done through IPCP negotiation. In my opinion, during IPCP negotiation if the dial-in client does not have any IP address, let our proxy-client request DHCP server to give an IP address and hand it over to the dial-in client. What is the special processing required on dial-in client side? The only question that remains is whether the dial-in client's IPCP negotiation will wait until the proxy-client obtains the IP address from the DHCP server ( which can be even of the order of minutes). > -- Jonathan Best regards Rajesh saluja
- proxy relay agent Hiroto Shibuya
- Re: proxy relay agent Mike Carney - Sun BOS Software
- Re: proxy relay agent Hiroto Shibuya
- Re: proxy relay agent Jonathan Wenocur
- Re: proxy relay agent Jonathan Wenocur
- Re: proxy relay agent Rajesh Saluja
- Re: proxy relay agent Jonathan Wenocur
- Re: proxy relay agent Rajesh Saluja
- Re: proxy relay agent Rajesh Saluja
- Re: proxy relay agent Rajesh Saluja