The only thing that I can tell is different about the network that we can't connect to is that there is a space in the essid. I don't know if this will cause a problem or not, but it doesn't seem like it should.
Any advice will be greatly appreciated.
Here is a snippet from the daemon.log file:
Code: Select all
CTRL-EVENT-CONNECTED - Connection to 00:22:6b:a7:69:be completed (reauth) [id=0 id_str=]
Jun 13 20:04:04 lapticus-compuman dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 13
Jun 13 20:04:08 lapticus-compuman NetworkManager: <info> (wlan0): DHCP transaction took too long, stopping it.
Jun 13 20:04:08 lapticus-compuman NetworkManager: <info> (wlan0): canceled DHCP transaction, dhcp client pid 23468
Jun 13 20:04:08 lapticus-compuman NetworkManager: <info> Activation (wlan0) Stage 4 of 5 (IP4 Configure Timeout) scheduled...
Jun 13 20:04:08 lapticus-compuman NetworkManager: <info> Activation (wlan0) Stage 4 of 5 (IP4 Configure Timeout) started...
Jun 13 20:04:08 lapticus-compuman NetworkManager: <info> (wlan0): device state change: 7 -> 9 (reason 5)
Jun 13 20:04:08 lapticus-compuman NetworkManager: <info> Activation (wlan0) failed for access point (XXXX XXXXX)
Jun 13 20:04:08 lapticus-compuman NetworkManager: <info> Marking connection 'XXXX XXXXXX' invalid.
Jun 13 20:04:08 lapticus-compuman NetworkManager: <info> Activation (wlan0) failed.
Jun 13 20:04:08 lapticus-compuman NetworkManager: <info> Activation (wlan0) Stage 4 of 5 (IP4 Configure Timeout) complete.
Jun 13 20:04:08 lapticus-compuman NetworkManager: <info> (wlan0): device state change: 9 -> 3 (reason 0)
Jun 13 20:04:08 lapticus-compuman NetworkManager: <info> (wlan0): deactivating device (reason: 0).
Jun 13 20:04:08 lapticus-compuman wpa_supplicant[856]: CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
Jun 13 20:04:19 lapticus-compuman NetworkManager: <info> Sleeping...