dhcpcd-discuss

Hi, having a problem with renewing in 3.2.3. 

My setup is cable modem >> linksys 4 port router/switch >> computer

When it firsts grabs an address it's fine. Then 12 hours later it will drop off the internet. The first time it will get 192.168.1.100, then when it tries to renew it will ask for an addres, but receive 192.168.1.101. This is odd because with previous dhcpcd, the router would always send the same address 192.168.1.100. 

In my kernel logs I am getting this.

Jul 21 08:34:51 localhost dhcpcd[25994]: eth0: netlink: Cannot assign requested address.

And of couse I can force it to renew with dhcpcd -n and the same thing happens.

I tried connecting straight to the cable modem and renews work fine. 

Wasn't sure what is causing my router to send a different address. So did a tcpdump. And looks something like this from my point of view. 

1) Dhcpcd asks the router for a new address.
2) ARP who has 192.168.1.100 tell 192.168.1.1 
3) ARP reply 192.168.1.100 is at (my mac address)
4) 192.168.1.1 > 192.168.1.100: [|icmp] (thought this was a ping, but now not sure)
5) ARP who has 192.168.1.101
6) dhcpcd request to the router again for address
7) ARP who has 192.168.1.101 tell 0.0.0.0 (this happens 3 times)
8) ARP who 192.168.1.101 (along with pc mac) tell 192.168.1.101 (2 times)


Did some searching around and saw various stuff about 3.2.3 and DUID. Tried to disable it, but looks like only the mac is being sent anyway.

3.2.3 is the version currently in slackware 13RC1/current. So went back to 2.0.8 (which works) and did a tcpdump. It's a little different. 

1) dhcpcd asks the router for a new address
2) ARP who has 192.168.1.100 tell 192.168.1.1
3) ARP who has 192.168.1.100 tell 0.0.0. (this happens 5 times)
4) ARP reply 192.168.1.100 is at (my mac address)
5) ARP request who has 192.168.1.1 tell 192.168.1.100
6) ARP reply 192.168.1.1 is at (my routers mac)


I know 3.2.3 is old and you guys are already past version 4. And easy enough to just not use dhcp and request a static address from the router. But dying to know why the router is sending a different address. There is also some chatter in the tcpdump between 0.0.0.0 and 255.255.255.255. So can include the full tcpdump if needed.

Thanks.