[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]
dhcrelay
- From: Adrian Buxton <abuxton internal ozemail com au>
- To: "'redhat-list redhat com'" <redhat-list redhat com>
- Subject: dhcrelay
- Date: Thu, 16 Sep 1999 15:25:45 +1000
Hi there
I'm wondering if anyone has made the dhcprelay program 'dhcrelay' run on a
redhat 6.0 system. It's running stock kernel and config.
I'm experiencing the following problem:
There are 2 networks, A & B.
eth0 is connected to network A. eth1 is connected to network B.
There is a dhcp server running on an NT box on Network A (nt isn't the
problem :)
There is a linux router passing traffic without a problem from network A to
B
There is a machine on network B trying to get IP information from the dhcp
server on network A.
The linux router can see both machines (ping test). dhcrelay was started
using the following syntax:
# dhcrelay <ip address of dhcp server on network A>
the following output is produced:
Listening on Socket/eth0/unattached
Sending on Socket/eth0/unattached
Listening on Socket/eth1/unattached
Sending on Socket/eth1/unattached
netstat -an --udp shows this line (amongst other things):
Proto Recv-Q Send-Q Local Address Foreign Address State
udp 0 0 0.0.0.0:67 0.0.0.0:*
Soo.. the daemon is listening on the correct port. With tcpdump you can see
when the machine on network B sends a dhcp request out it arrives on eth1,
but nothing ever leaves out eth0
Any ideas anyone?
Thanks
Adrian
[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]