Subject: dhclient logging
To: None <port-i386@netbsd.org>
From: Simon Gerraty <sjg@juniper.net>
List: port-i386
Date: 08/16/2004 16:58:44
A while back I reported that dev/pci/if_wm.c 1.71 didn't work with my
thinkpad. An up to date -current kernel with 1.70 if_wm.c works ok,
and I _think_ it works ok with 1.75.
I say _think_ because on my net at home dhclient simply fails to get a
lease - until I boot with a kernel using 1.70 if_wm.c. Last time I
tried, manual ifconfig of wm0 didn't work either - unless I used 1.70
Here at work I can boot a kernel using 1.75 and it would appear that I
get a lease (after several failed attempts), but all I can find in
/var/log/messages is:
Aug 16 14:46:58 sjg-lt dhclient: DHCPDISCOVER on ath0 to 255.255.255.255 port 67
interval 21
Aug 16 14:46:58 sjg-lt dhclient: send_packet: No buffer space available
Aug 16 14:47:19 sjg-lt dhclient: DHCPDISCOVER on ath0 to 255.255.255.255 port 67
interval 7
Aug 16 14:47:19 sjg-lt dhclient: send_packet: No buffer space available
Aug 16 14:47:26 sjg-lt dhclient: DHCPDISCOVER on ath0 to 255.255.255.255 port 67
interval 1
Aug 16 14:47:26 sjg-lt dhclient: send_packet: No buffer space available
Aug 16 14:47:27 sjg-lt dhclient: No DHCPOFFERS received.
Aug 16 14:47:27 sjg-lt dhclient: No working leases in persistent database - slee
ping.
repeated over and over. On the console I did see it trying wm0 as
well but these were clearly not logged. Failure on ath0 is expected -
since I don't configure the WEP passwd if I see that wm0 is active.
Even if I log daemon.debug I don't get any log of successful lease
activity, but it still claims there are no working leases - yet it
brought wm0 up straight away...
Anyone know if (short of hacking the code), dhclient can be made to
log what its doing better?
Thanks
--sjg