Re: Relay agent
boris@hal2000.law.columbia.edu Mon, 20 May 1996 19:23 UTC
Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa23268;
20 May 96 15:23 EDT
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa23264;
20 May 96 15:23 EDT
Received: from reef.bucknell.edu by CNRI.Reston.VA.US id aa12082;
20 May 96 15:23 EDT
Received: from localhost by reef.bucknell.edu with SMTP
(5.65/IDA-1.2.8) id AA27333; Mon, 20 May 1996 15:18:12 -0400
Date: Mon, 20 May 1996 15:18:12 -0400
Message-Id: <9605201845.AA11988@hal2000.law.columbia.edu>
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: boris@hal2000.law.columbia.edu
To: Multiple recipients of list <dhcp-v4@bucknell.edu>
Subject: Re: Relay agent
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas
X-Comment: Discussion of DHCP for IPv4
Thanks for response.
We are using pretty old Novell's TCPIP1.NLM version TCP/IP V1.01 ALPHA 2+
Should we run bootpforwarding only on the router? It makes a certain
inconvinience. The matter is that we are migrating to new network environment
and also from bootp to dhcp. dhcp server is in experimental stage. So right
now we are running two servers bootp and dhcp at the same time with duplicated
database. Another thing is that the old software on existing router doesn't
support multiple forwarding, so we decided to run relay agent on another host.
We gonna get rid of old stuff soon but need support users during the
migration.
Probably, we can run routing on the relay host. But I was wondering why this
stuff happens and is there any other solution.
- Boris
>
> Packet drivers have no knowledgeof IP; what TCPIP stack are you using?
>
> boris@hal2000.law.columbia.edu wrote....
> >
> >
> > Has anyone experienced the following problem with CMU dhcp server and dos
> > Packet Driver (NE2000) :
> >
> > I use a bootp relay agent for forwarding bootp requests to the dhcp server
> > which is on another subnet. The relay agent is not on the router but a host
> > behind the router (using Novell's bootpforwarding).
> > The problem is that PCs using Packet Driver get the gateway IP wrong - instead
> > of the IP of the router which dhcp server is supposed to provide (gw tag) they
> > get IP of the relay agent
> > Other clients get it correct.
> >
> > Any solution for that?
> >
> > ==================================
> > Boris Niyazov
> > IT Department
> > Columbia Law School
> >
>
> Richard Letts
> -------------------------------------------------------------------------------
> Network Manager mail: R.J.Letts@salford.ac.uk
> University of Salford phone: +44 161 745 5252
> Great Britain fax: +44 161 745 5888
>
- Relay agent boris
- Re: Relay agent Richard Letts
- Re: Relay agent boris
- Re: Relay agent Richard Letts