On Tue, Jul 27, 2010 at 6:33 PM, Phil Savoie psavoie1783@rogers.com wrote:
Beginning DHCP transaction. Jul 27 19:31:38 smurf3 dhclient: Internet Systems Consortium DHCP Client V3.0.5-RedHat Jul 27 19:31:38 smurf3 dhclient: Copyright 2004-2006 Internet Systems Consortium. Jul 27 19:31:38 smurf3 dhclient: All rights reserved. Jul 27 19:31:38 smurf3 dhclient: For info, please visit http://www.isc.org/sw/dhcp/ Jul 27 19:31:38 smurf3 dhclient: Jul 27 19:31:38 smurf3 NetworkManager: <info> dhclient started with pid 30770 Jul 27 19:31:38 smurf3 NetworkManager: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) complete. Jul 27 19:31:38 smurf3 NetworkManager: <info> DHCP: device wlan0 state changed normal exit -> preinit Jul 27 19:31:38 smurf3 dhclient: Listening on LPF/wlan0/c4:17:fe:bb:6a:df Jul 27 19:31:38 smurf3 dhclient: Sending on LPF/wlan0/c4:17:fe:bb:6a:df Jul 27 19:31:38 smurf3 dhclient: Sending on Socket/fallback Jul 27 19:31:38 smurf3 dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 4 Jul 27 19:31:42 smurf3 dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 11 Jul 27 19:31:53 smurf3 dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 14 Jul 27 19:32:07 smurf3 dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 20 Jul 27 19:32:23 smurf3 NetworkManager: <info> Device 'wlan0' DHCP transaction took too long (>45s), stopping it. Jul 27 19:32:23 smurf3 NetworkManager: <info> wlan0: canceled DHCP transaction, dhcp client pid 30770
It would seem that one possibility is that the AP is not running a DHCP server.
Another is that if the AP is running a DHCP server, it is restricting IP addresses to known clients.
kind regards/ldv