Relay agent

boris@hal2000.law.columbia.edu Sat, 18 May 1996 00:25 UTC

Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa01198; 17 May 96 20:25 EDT
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa01194; 17 May 96 20:25 EDT
Received: from reef.bucknell.edu by CNRI.Reston.VA.US id aa19004; 17 May 96 20:25 EDT
Received: from localhost by reef.bucknell.edu with SMTP (5.65/IDA-1.2.8) id AA12882; Fri, 17 May 1996 20:23:00 -0400
Date: Fri, 17 May 1996 20:23:00 -0400
Message-Id: <9605172258.AA10552@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: Relay agent
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas
X-Comment: Discussion of DHCP for IPv4

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