![]() |
|
|
|||
|
dhcpcd anomaly
I have a computer with two interfaces, a wired and a wireless interface.
Both appear to function correctly, BUT: After about half an hour, the dhcpcd for the wireless interface will start querying the DHCP servers over and over again, twice every 3 seconds, and will continue to do so until dhcpcd is killed or restarted, after which it works correctly for half an hour again. A short log excerpt: May 7 00:16:41 tree dhcpd: DHCPREQUEST for 172.16.24.9 from 00:0b:cd:74:1a:bf via eth1 May 7 00:16:41 tree dhcpd: DHCPACK on 172.16.24.9 to 00:0b:cd:74:1a:bf via eth1 May 7 00:16:41 tree dhcpd: DHCPREQUEST for 172.16.24.9 from 00:0b:cd:74:1a:bf via eth1 May 7 00:16:41 tree dhcpd: DHCPACK on 172.16.24.9 to 00:0b:cd:74:1a:bf via eth1 May 7 00:16:44 tree dhcpd: DHCPREQUEST for 172.16.24.9 from 00:0b:cd:74:1a:bf via eth1 May 7 00:16:44 tree dhcpd: DHCPACK on 172.16.24.9 to 00:0b:cd:74:1a:bf via eth1 May 7 00:16:44 tree dhcpd: DHCPREQUEST for 172.16.24.9 from 00:0b:cd:74:1a:bf via eth1 May 7 00:16:44 tree dhcpd: DHCPACK on 172.16.24.9 to 00:0b:cd:74:1a:bf via eth1 May 7 00:16:47 tree dhcpd: DHCPREQUEST for 172.16.24.9 from 00:0b:cd:74:1a:bf via eth1 May 7 00:16:47 tree dhcpd: DHCPACK on 172.16.24.9 to 00:0b:cd:74:1a:bf via eth1 May 7 00:16:47 tree dhcpd: DHCPREQUEST for 172.16.24.9 from 00:0b:cd:74:1a:bf via eth1 May 7 00:16:47 tree dhcpd: DHCPACK on 172.16.24.9 to 00:0b:cd:74:1a:bf via eth1 # ps -fC dhcpcd | cat UID PID PPID C STIME TTY TIME CMD root 8206 1 0 May05 ? 00:00:00 /sbin/dhcpcd -h fairy -t 5 eth0 root 20189 1 0 00:22 ? 00:00:00 /sbin/dhcpcd -h fairy -t 15 -m 2000 wlan0 The only thing I can see is that dhcpcd sets the hostname where it shouldn't (gentoo doesn't allow for specifying a hostname per interface, or rather, it will tack on -h `hostname` regardless), but that shouldn't affect the renewal. The DHCP servers are set to ignore the hostname for gentoo hosts, due to this design flaw. This problem only occurs for the wlan0 interface, and not for eth0. Anyone seen this, and know what could cause this misbehaviour? Regards, -- *Art |
![]() |
|
| Thread Tools | Search this Thread |
| Display Modes | |
|
|