*** From dhcp-server -- To unsubscribe, see the end of this message. ***
Ted,
I checked to see if I really have a routing problem as you suggested.
For that purpose I first started dhcpd, let one client
(hostname "waters") discover a lease and then renew a lease.
At the same time a did a tcpdump.
Here's the output of dhcpd and tcpdump:
root@plymouth:/home/operator > /usr/sbin/dhcpd -d -f
Internet Software Consortium DHCP Server V2.0b1pl18
Copyright 1995, 1996, 1997, 1998, 1999 The Internet Software Consortium.
All rights reserved.
Please contribute if you find this software useful.
For info, please visit http://www.isc.org/dhcp-contrib.html
Listening on Socket/eth1/KP
Sending on Socket/eth1/KP
Listening on Socket/eth0/INFRASERV
Sending on Socket/eth0/INFRASERV
DHCPDISCOVER from 00:60:08:48:fe:85 via eth0
DHCPOFFER on 149.250.128.134 to 00:60:08:48:fe:85 via eth0
DHCPREQUEST for 149.250.128.134 from 00:60:08:48:fe:85 via eth0
DHCPACK on 149.250.128.134 to 00:60:08:48:fe:85 via eth0
-------------------------------------------------------------------
root@plymouth:/home/operator > tcpdump ether host 00:60:08:48:fe:85
tcpdump: listening on eth0
20:12:51.795900 0.0.0.0.bootpc > 255.255.255.255.bootps: xid:0x98549768
[|bootp]
20:12:51.835900 0.0.0.0.bootpc > 255.255.255.255.bootps: xid:0x211aeb50
[|bootp]
20:12:57.475900 waters.gendorf.hoechst.com.bootpc >
plymouth.gendorf.hoechst.com.bootps: xid:0x95226546 C:waters.gendorf.hoechst.com
[|bootp]
20:13:07.505900 waters.gendorf.hoechst.com.bootpc >
plymouth.gendorf.hoechst.com.bootps: xid:0x95226546 secs:2560
C:waters.gendorf.hoechst.com
[|bootp]
At 20:12:57 the client first tries to renew his lease,
the packet arrives correctly at the dhcp server's ("plymouth")
interface, but it ignores the packet at all (according to
dhcpd's log output).
The config works fine on a host with only one NIC and no aliases
(same kernel, same hardware, same dhcpd).
Would be happy about any ideas (even the wildest ones).
Thanks!
Stefan Gasteiger
Mail: [EMAIL PROTECTED]
Phone: +49 8679 7 5599
Fax: +49 8679 7 5050
> According to the log, the server didn't receive the DHCPREQUEST.
> This is probably a problem with the NT client not being able to route
> packets to the server. If you look at your trace, you'll see that
> the server saw all the broadcasts, but didn't see the unicast. My
> guess is that you have a routing problem, not a DHCP problem.
>
> _MelloN_
---
Sent through Global Message Exchange - http://www.gmx.net
------------------------------------------------------------------------------
To unsubscribe from this list, please visit http://www.fugue.com/dhcp/lists
If you are without web access, or if you are having trouble with the web page,
please send mail to [EMAIL PROTECTED] Please try to use the web
page first - it will take a long time for your request to be processed by hand.
------------------------------------------------------------------------------
