--On Thursday, March 27, 2003 03:31:45 PM +0100 David Fokkema <[EMAIL PROTECTED]> wrote:
I run dhcpdump and get this output at the time when my IP changes (192.168.1.192 is the 'old' address, 192.168.1.2 is the dhcpd):
TIME: 14:06:30.215030 IP: 192.168.1.192.68 (0:10:a4:f5:63:d6) > 192.168.1.2.67 (0:30:48:10:49:75) OP: 1 (BOOTPREQUEST) HTYPE: 1 (Ethernet) HLEN: 6 HOPS: 0 XID: affc4578 SECS: 216 FLAGS: 0 CIADDR: 192.168.1.192 YIADDR: 0.0.0.0 SIADDR: 0.0.0.0 GIADDR: 0.0.0.0 CHADDR: 00:10:a4:f5:63:d6:00:00:00:00:00:00:00:00:00:00 SNAME: . FNAME: . OPTION: 53 ( 1) DHCP message type 3 (DHCPREQUEST) OPTION: 51 ( 4) IP address leasetime 600 (10m) OPTION: 55 ( 7) Parameter Request List 1 (Subnet mask) 28 (Broadcast address) 2 (Time offset) 3 (Routers) 15 (Domainname) 6 (DNS server) 12 (Host name)
After this my network link goes down and comes up again with the new address.
Any ideas what would cause the dhcpd to give me a new address instead of assigning the same again?
Are you sure there is not even a DHCPNAK received? And I'm puzzled, since tcpdump|dhcpdump should show you the OFFER, REQUEST and ACK for the new address...
I assume that these packages are exchanged right after eth0 comes up again. Unfortunately tcpdump dies when the interface goes down and the connection is back up (with a new address) already when I can start tcpdump again. :-/
Harry
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
