On 11 November 2015 at 22:31, Kenneth Westerback <kwesterb...@gmail.com> wrote: > On 11 November 2015 at 21:52, Ted Unangst <t...@tedunangst.com> wrote: >> On my X1 carbon, I unplugged the ethernet cable and switched to wireless. I >> had a forgotten dhclient running for some time. >> >> ifconfig reports the following: >> >> ifconfig em0 >> em0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500 >> lladdr 54:ee:75:3c:17:cb >> priority: 0 >> media: Ethernet autoselect (none) >> status: no carrier >> >> dhclient however spammed me with messages like the following: >> >> Nov 11 13:07:53 carbolite dhclient[24723]: DHCPDISCOVER on em0 - interval 10 >> Nov 11 13:07:53 carbolite dhclient[24723]: send_packet: No buffer space >> available >> Nov 11 13:08:03 carbolite dhclient[24723]: DHCPDISCOVER on em0 - interval 1 >> Nov 11 13:08:03 carbolite dhclient[24723]: send_packet: No buffer space >> available >> Nov 11 13:08:04 carbolite dhclient[24723]: No acceptable DHCPOFFERS received. >> Nov 11 13:08:04 carbolite dhclient[24723]: No working leases in persistent >> database - sleeping. >> Nov 11 13:13:04 carbolite dhclient[24723]: DHCPDISCOVER on em0 - interval 3 >> Nov 11 13:13:04 carbolite dhclient[24723]: send_packet: No buffer space >> available >> Nov 11 13:13:07 carbolite dhclient[24723]: DHCPDISCOVER on em0 - interval 4 >> >> My expectation is that dhclient should observe a status of no carrier and >> cease attempts to continue blasting packets. >> > > A capture of 'route -n monitor' while unplugging the ethernet cable > would be helpful information. > > .... Ken
And compiling dhclient with DEBUG, and the resulting /var/log/daemon as well. Or more specifically unconditionally forcing the print out of the link state changes at line 346 of -current dhclient.c. .... Ken
