Can't connect to my home network

Hello all. I'm trying to use Linux a little more even though I don't mind WinVista. So I downloaded Ubuntu 8.04 and am using Wubi to run it within my Windows Vista. I have the 64bit version fo Ubuntu. This is the second time I've tried Linux. I tried Suse about a year ago and hated it so now I'm trying this as it seems more use friendly.
I am an absolute NEWBIE so be VERY gentle. Here's the problem I'm having so far.
I am using an HPdv9700t, Intel Core 2 duo 2.0 Ghz, Nvidia 8600M GS, 4GB ram (see my sig). I have the Intel PRO Wireless 4965AGN. When I go to the wireless network it is able find my home network, but it will not connect to it. I have it set to WEP 128Bit with a security key. When Iput the security key in it searches for the network but is unable to connect. I know it's working because i can leech off my neighbors unsecured network (which I'm doing now, but don't tell them). For some reason it's not connecting to mine though. I don't know if has to do with Linux or not. I can connect just fine in Vista, and my brother in law's Macbook Pro connects just fine as well.
My wireless router is Linksys WRT54GL, it's supposed to work for Windows & Linux.
Any help would be much appreciated.

 

If you open a terminal and run:

$ iwlist scan

What is the output?

(BTW, the $ sign in "$ iwlist scan" should not be typed. The $ sign just indicates that what follows is a command to be typed at a shell prompt. I feel I need to mention this since you say you are a newbie.)

 

Could he have mac-filtering enabled?

 

This is what I get:

lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

wmaster0 Interface doesn't support scanning.

wlan0 No scan results


Mac Filtering? What is it, and is that the problem?

 

Yeah, I thought about that because whenever I bring a new machine onto my network I momentarily forget about that. But if I understood properly the OP the laptop connects fine when running Vista. The MAC address is the same no matter which OS is running so that would eliminate the possibility of an issue with MAC-filtering.

 

Ooops... I think you need to do

Code:

$ sudo iwlist scan

so that it will run as root. If iwlist is not run as root, it does not give you an error message but produces no scan results. I've just tried on my machine and got the same results you got despite the fact that I am connected. I tried with sudo and got something sensible so sudo is needed. (Bad design, IMHO: iwlist should report that the user does not have privileges to probe the interfaces rather than return no results.)

Don't worry about the MAC address. That's probably not your problem. You're able to connect with that very same laptop when running Vista, right?

 

Alright I did the second scan, here are the results:

lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

wmaster0 Interface doesn't support scanning.

wlan0 Scan completed :
Cell 01 - Address: 00:1D:7E:BB:A5:50
ESSID:"Home Network"
Mode:Master
Channel:6
Frequency:2.437 GHz (Channel 6)
Quality=89/100 Signal level=-43 dBm Noise level=-127 dBm
Encryption key n
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
24 Mb/s; 36 Mb/s; 54 Mb/s; 6 Mb/s; 9 Mb/s
12 Mb/s; 48 Mb/s
Extra:tsf=0000019b9b42f7c0

 

That's your network?

 

Right click the gnome network manager icon in the system tray and set up manually, then try to connect. I'm not in gnome now, but I think it's under either new connection, or edit connections

 

Yes, that is me. I don't know why it won't connect to it though. It just does the little circling thing in the upper taskbar and say its trying to connect.

 

Please confirm: you are able to connect with this laptop when running Vista, right? I just want to make sure that I understood properly because if the answer to the above is yes, then that eliminates the possibility of a problem with MAC-filtering.

Also, if no one else is using your network right now, you might want to reboot the router and try connecting again. Just in case. (On most routers I've owned, rebooting was best accomplished by unplugging it for about 12 secs and replugging.) This way you know your router is in a clean state.

 

Yes I have been using it all day in Vista, it just refuses to work in Ubuntu for some reason. I'll will try rebooting my router as well.

 

Have you rebooted the machine and tried again?

 

It has been working on Vista all day long. I just tried rebooting the router and still having the same problem.

I've rebooted several times, cold and warm boots. I had to cold boot it just to be able to get the wireless to start working.

 

The next thing I would do is to check what the logs are saying:

Code:

$ grep NetworkManager /var/log/syslog

If for some reason this fails you might need to add "sudo" before "grep". (I don't need "sudo" on my machine because I gave myself the rights to inspect logs.)

 

This is going to be long. You'll see "Actiontec" that is my neighbors network I'm leeching off of.

Jul 12 17:43:56 daddy-laptop NetworkManager: <info> Activation (wlan0) New wireless user key requested for network 'Home Network'.
Jul 12 17:43:56 daddy-laptop NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Jul 12 17:43:56 daddy-laptop NetworkManager: <info> Activation (wlan0) New wireless user key for network 'Home Network' received.
Jul 12 17:43:56 daddy-laptop NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Jul 12 17:43:56 daddy-laptop NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Jul 12 17:43:56 daddy-laptop NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
Jul 12 17:43:56 daddy-laptop NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Jul 12 17:43:56 daddy-laptop NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Jul 12 17:43:56 daddy-laptop NetworkManager: <info> Activation (wlan0/wireless): access point 'Home Network' is encrypted, and a key exists. No new key needed.
Jul 12 17:43:57 daddy-laptop NetworkManager: <info> retry to connect to global supplicant socket (try=1)
Jul 12 17:43:57 daddy-laptop NetworkManager: <info> SUP: sending command 'INTERFACE_ADD wlan0^I^Iwext^I/var/run/wpa_supplicant0^I'
Jul 12 17:43:57 daddy-laptop NetworkManager: <info> SUP: response was 'OK'
Jul 12 17:43:57 daddy-laptop NetworkManager: <info> SUP: sending command 'AP_SCAN 1'
Jul 12 17:43:57 daddy-laptop NetworkManager: <info> SUP: response was 'OK'
Jul 12 17:43:57 daddy-laptop NetworkManager: <info> SUP: sending command 'ADD_NETWORK'
Jul 12 17:43:57 daddy-laptop NetworkManager: <info> SUP: response was '0'
Jul 12 17:43:57 daddy-laptop NetworkManager: <info> SUP: sending command 'SET_NETWORK 0 ssid 486f6d65204e6574776f726b'
Jul 12 17:43:57 daddy-laptop NetworkManager: <info> SUP: response was 'OK'
Jul 12 17:43:57 daddy-laptop NetworkManager: <info> SUP: sending command 'SET_NETWORK 0 key_mgmt NONE'
Jul 12 17:43:57 daddy-laptop NetworkManager: <info> SUP: response was 'OK'
Jul 12 17:43:57 daddy-laptop NetworkManager: <info> SUP: sending command 'SET_NETWORK 0 wep_key0 <key>'
Jul 12 17:43:57 daddy-laptop NetworkManager: <info> SUP: response was 'OK'
Jul 12 17:43:57 daddy-laptop NetworkManager: <info> SUP: sending command 'SET_NETWORK 0 wep_tx_keyidx 0'
Jul 12 17:43:57 daddy-laptop NetworkManager: <info> SUP: response was 'OK'
Jul 12 17:43:57 daddy-laptop NetworkManager: <info> SUP: sending command 'ENABLE_NETWORK 0'
Jul 12 17:43:57 daddy-laptop NetworkManager: <info> SUP: response was 'OK'
Jul 12 17:43:57 daddy-laptop NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Jul 12 17:43:59 daddy-laptop NetworkManager: <info> Supplicant state changed: 1
Jul 12 17:43:59 daddy-laptop NetworkManager: <info> Activation (wlan0/wireless) Stage 2 of 5 (Device Configure) successful. Connected to access point 'Home Network'.
Jul 12 17:43:59 daddy-laptop NetworkManager: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) scheduled.
Jul 12 17:43:59 daddy-laptop NetworkManager: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) started...
Jul 12 17:44:01 daddy-laptop NetworkManager: <info> Activation (wlan0) Beginning DHCP transaction.
Jul 12 17:44:01 daddy-laptop NetworkManager: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) complete.
Jul 12 17:44:01 daddy-laptop NetworkManager: <info> DHCP daemon state is now 12 (successfully started) for interface wlan0
Jul 12 17:44:02 daddy-laptop NetworkManager: <info> DHCP daemon state is now 1 (starting) for interface wlan0
Jul 12 17:44:04 daddy-laptop NetworkManager: <info> Old device 'wlan0' activating, won't change.
Jul 12 17:44:46 daddy-laptop NetworkManager: <info> DHCP daemon state is now 9 (fail) for interface wlan0
Jul 12 17:44:46 daddy-laptop NetworkManager: <info> Activation (wlan0) Stage 4 of 5 (IP Configure Timeout) scheduled...
Jul 12 17:44:46 daddy-laptop NetworkManager: <info> Activation (wlan0) Stage 4 of 5 (IP Configure Timeout) started...
Jul 12 17:44:46 daddy-laptop NetworkManager: <debug> [1215906286.998172] real_act_stage4_ip_config_timeout(): Activation (wlan0/wireless): could not get IP configuration info for 'Home Network', asking for new key.
Jul 12 17:44:47 daddy-laptop NetworkManager: <info> DHCP daemon state is now 14 (normal exit) for interface wlan0
Jul 12 17:44:47 daddy-laptop NetworkManager: <info> Activation (wlan0) New wireless user key requested for network 'Home Network'.
Jul 12 17:44:47 daddy-laptop NetworkManager: <info> Activation (wlan0) Stage 4 of 5 (IP Configure Timeout) complete.
Jul 12 17:45:23 daddy-laptop NetworkManager: <info> Activation (wlan0) New wireless user key for network 'Home Network' received.
Jul 12 17:45:23 daddy-laptop NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Jul 12 17:45:23 daddy-laptop NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Jul 12 17:45:23 daddy-laptop NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
Jul 12 17:45:23 daddy-laptop NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Jul 12 17:45:23 daddy-laptop NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Jul 12 17:45:23 daddy-laptop NetworkManager: <info> Activation (wlan0/wireless): access point 'Home Network' is encrypted, and a key exists. No new key needed.
Jul 12 17:45:24 daddy-laptop NetworkManager: <info> retry to connect to global supplicant socket (try=1)
Jul 12 17:45:24 daddy-laptop NetworkManager: <info> SUP: sending command 'INTERFACE_ADD wlan0^I^Iwext^I/var/run/wpa_supplicant0^I'
Jul 12 17:45:24 daddy-laptop NetworkManager: <info> SUP: response was 'OK'
Jul 12 17:45:25 daddy-laptop NetworkManager: <info> SUP: sending command 'AP_SCAN 1'
Jul 12 17:45:25 daddy-laptop NetworkManager: <info> SUP: response was 'OK'
Jul 12 17:45:25 daddy-laptop NetworkManager: <info> SUP: sending command 'ADD_NETWORK'
Jul 12 17:45:25 daddy-laptop NetworkManager: <info> SUP: response was '0'
Jul 12 17:45:25 daddy-laptop NetworkManager: <info> SUP: sending command 'SET_NETWORK 0 ssid 486f6d65204e6574776f726b'
Jul 12 17:45:25 daddy-laptop NetworkManager: <info> SUP: response was 'OK'
Jul 12 17:45:25 daddy-laptop NetworkManager: <info> SUP: sending command 'SET_NETWORK 0 key_mgmt NONE'
Jul 12 17:45:25 daddy-laptop NetworkManager: <info> SUP: response was 'OK'
Jul 12 17:45:25 daddy-laptop NetworkManager: <info> SUP: sending command 'SET_NETWORK 0 auth_alg SHARED'
Jul 12 17:45:25 daddy-laptop NetworkManager: <info> SUP: response was 'OK'
Jul 12 17:45:25 daddy-laptop NetworkManager: <info> SUP: sending command 'SET_NETWORK 0 wep_key0 <key>'
Jul 12 17:45:25 daddy-laptop NetworkManager: <info> SUP: response was 'OK'
Jul 12 17:45:25 daddy-laptop NetworkManager: <info> SUP: sending command 'SET_NETWORK 0 wep_tx_keyidx 0'
Jul 12 17:45:25 daddy-laptop NetworkManager: <info> SUP: response was 'OK'
Jul 12 17:45:25 daddy-laptop NetworkManager: <info> SUP: sending command 'ENABLE_NETWORK 0'
Jul 12 17:45:25 daddy-laptop NetworkManager: <info> SUP: response was 'OK'
Jul 12 17:45:25 daddy-laptop NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Jul 12 17:45:32 daddy-laptop NetworkManager: <info> Old device 'wlan0' activating, won't change.
Jul 12 17:45:44 daddy-laptop NetworkManager: <info> Old device 'wlan0' activating, won't change.
Jul 12 17:45:56 daddy-laptop NetworkManager: <info> Old device 'wlan0' activating, won't change.
Jul 12 17:46:07 daddy-laptop NetworkManager: <info> Old device 'wlan0' activating, won't change.
Jul 12 17:46:19 daddy-laptop NetworkManager: <info> Old device 'wlan0' activating, won't change.
Jul 12 17:46:30 daddy-laptop NetworkManager: <info> Old device 'wlan0' activating, won't change.
Jul 12 17:46:42 daddy-laptop NetworkManager: <info> Old device 'wlan0' activating, won't change.
Jul 12 17:46:54 daddy-laptop NetworkManager: <info> Old device 'wlan0' activating, won't change.
Jul 12 17:47:05 daddy-laptop NetworkManager: <info> Old device 'wlan0' activating, won't change.
Jul 12 17:47:17 daddy-laptop NetworkManager: <info> Old device 'wlan0' activating, won't change.
Jul 12 17:47:20 daddy-laptop NetworkManager: <debug> [1215906440.933624] nm_device_802_11_wireless_get_activation_ap(): Forcing AP 'ACTIONTEC'
Jul 12 17:47:20 daddy-laptop NetworkManager: <info> User Switch: /org/freedesktop/NetworkManager/Devices/wlan0 / ACTIONTEC
Jul 12 17:47:20 daddy-laptop NetworkManager: <info> Deactivating device wlan0.
Jul 12 17:47:20 daddy-laptop NetworkManager: <info> Activation (wlan0): cancelling...
Jul 12 17:47:20 daddy-laptop NetworkManager: <info> Activation (wlan0) cancellation handler scheduled...
Jul 12 17:47:20 daddy-laptop NetworkManager: <info> Activation (wlan0): waiting for device to cancel activation.
Jul 12 17:47:20 daddy-laptop NetworkManager: <info> Activation (wlan0) cancellation handled.
Jul 12 17:47:20 daddy-laptop NetworkManager: <info> Activation (wlan0): cancelled.
Jul 12 17:47:21 daddy-laptop NetworkManager: nm_utils_supplicant_request_with_check: assertion `ctrl != NULL' failed
Jul 12 17:47:21 daddy-laptop NetworkManager: <WARN> nm_device_802_11_wireless_scan(): (wlan0): could not trigger wireless scan
Jul 12 17:47:21 daddy-laptop NetworkManager: <info> Device wlan0 activation scheduled...
Jul 12 17:47:21 daddy-laptop NetworkManager: <info> Activation (wlan0) started...
Jul 12 17:47:21 daddy-laptop NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Jul 12 17:47:21 daddy-laptop NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Jul 12 17:47:21 daddy-laptop NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
Jul 12 17:47:21 daddy-laptop NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Jul 12 17:47:21 daddy-laptop NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Jul 12 17:47:21 daddy-laptop NetworkManager: <info> Activation (wlan0/wireless): access point 'ACTIONTEC' is unencrypted, no key needed.
Jul 12 17:47:22 daddy-laptop NetworkManager: <info> retry to connect to global supplicant socket (try=1)
Jul 12 17:47:22 daddy-laptop NetworkManager: <info> SUP: sending command 'INTERFACE_ADD wlan0^I^Iwext^I/var/run/wpa_supplicant0^I'
Jul 12 17:47:22 daddy-laptop NetworkManager: <info> SUP: response was 'OK'
Jul 12 17:47:23 daddy-laptop NetworkManager: <info> SUP: sending command 'AP_SCAN 1'
Jul 12 17:47:23 daddy-laptop NetworkManager: <info> SUP: response was 'OK'
Jul 12 17:47:23 daddy-laptop NetworkManager: <info> SUP: sending command 'ADD_NETWORK'
Jul 12 17:47:23 daddy-laptop NetworkManager: <info> SUP: response was '0'
Jul 12 17:47:23 daddy-laptop NetworkManager: <info> SUP: sending command 'SET_NETWORK 0 ssid 414354494f4e544543'
Jul 12 17:47:23 daddy-laptop NetworkManager: <info> SUP: response was 'OK'
Jul 12 17:47:23 daddy-laptop NetworkManager: <info> SUP: sending command 'SET_NETWORK 0 key_mgmt NONE'
Jul 12 17:47:23 daddy-laptop NetworkManager: <info> SUP: response was 'OK'
Jul 12 17:47:23 daddy-laptop NetworkManager: <info> SUP: sending command 'ENABLE_NETWORK 0'
Jul 12 17:47:23 daddy-laptop NetworkManager: <info> SUP: response was 'OK'
Jul 12 17:47:23 daddy-laptop NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Jul 12 17:47:23 daddy-laptop NetworkManager: <debug> [1215906443.118391] nm_device_802_11_wireless_update_bssid(): Roamed from BSSID 00:0F:B3:57 A:BB to 00:1D:7E:BB:A5:50 on wireless network 'ACTIONTEC'
Jul 12 17:47:23 daddy-laptop NetworkManager: <debug> [1215906443.121448] nm_dbus_signal_filter(): NetworkManagerInfo triggered update of wireless network 'ACTIONTEC'
Jul 12 17:47:23 daddy-laptop NetworkManager: <info> Old device 'wlan0' activating, won't change.
Jul 12 17:47:24 daddy-laptop NetworkManager: <info> Supplicant state changed: 1
Jul 12 17:47:24 daddy-laptop NetworkManager: <info> Activation (wlan0/wireless) Stage 2 of 5 (Device Configure) successful. Connected to access point 'ACTIONTEC'.
Jul 12 17:47:24 daddy-laptop NetworkManager: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) scheduled.
Jul 12 17:47:24 daddy-laptop NetworkManager: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) started...
Jul 12 17:47:26 daddy-laptop NetworkManager: <info> Activation (wlan0) Beginning DHCP transaction.
Jul 12 17:47:26 daddy-laptop NetworkManager: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) complete.
Jul 12 17:47:26 daddy-laptop NetworkManager: <debug> [1215906446.917922] nm_device_802_11_wireless_update_bssid(): Roamed from BSSID 00:1D:7E:BB:A5:50 to 00:0F:B3:57 A:BB on wireless network 'ACTIONTEC'
Jul 12 17:47:26 daddy-laptop NetworkManager: <info> DHCP daemon state is now 12 (successfully started) for interface wlan0
Jul 12 17:47:26 daddy-laptop NetworkManager: <debug> [1215906446.921119] nm_dbus_signal_filter(): NetworkManagerInfo triggered update of wireless network 'ACTIONTEC'
Jul 12 17:47:26 daddy-laptop NetworkManager: <info> Old device 'wlan0' activating, won't change.
Jul 12 17:47:28 daddy-laptop NetworkManager: <info> DHCP daemon state is now 1 (starting) for interface wlan0
Jul 12 17:47:29 daddy-laptop NetworkManager: <info> Old device 'wlan0' activating, won't change.
Jul 12 17:47:30 daddy-laptop NetworkManager: <info> DHCP daemon state is now 2 (bound) for interface wlan0
Jul 12 17:47:30 daddy-laptop NetworkManager: <info> Activation (wlan0) Stage 4 of 5 (IP Configure Get) scheduled...
Jul 12 17:47:30 daddy-laptop NetworkManager: <info> Activation (wlan0) Stage 4 of 5 (IP Configure Get) started...
Jul 12 17:47:30 daddy-laptop NetworkManager: <info> Retrieved the following IP4 configuration from the DHCP daemon:
Jul 12 17:47:30 daddy-laptop NetworkManager: <info> address 192.168.0.3
Jul 12 17:47:30 daddy-laptop NetworkManager: <info> netmask 255.255.255.0
Jul 12 17:47:30 daddy-laptop NetworkManager: <info> broadcast 192.168.0.255
Jul 12 17:47:30 daddy-laptop NetworkManager: <info> gateway 192.168.0.1
Jul 12 17:47:30 daddy-laptop NetworkManager: <info> nameserver 192.168.0.1
Jul 12 17:47:30 daddy-laptop NetworkManager: <info> nameserver 205.171.3.65
Jul 12 17:47:30 daddy-laptop NetworkManager: <info> hostname 'daddy-laptop'
Jul 12 17:47:30 daddy-laptop NetworkManager: <info> domain name 'domain.actdsltmp'
Jul 12 17:47:30 daddy-laptop NetworkManager: <info> Activation (wlan0) Stage 5 of 5 (IP Configure Commit) scheduled...
Jul 12 17:47:30 daddy-laptop NetworkManager: <info> Activation (wlan0) Stage 4 of 5 (IP Configure Get) complete.
Jul 12 17:47:30 daddy-laptop NetworkManager: <info> Activation (wlan0) Stage 5 of 5 (IP Configure Commit) started...
Jul 12 17:47:31 daddy-laptop NetworkManager: <info> Clearing nscd hosts cache.
Jul 12 17:47:31 daddy-laptop NetworkManager: <WARN> nm_spawn_process(): nm_spawn_process('/usr/sbin/nscd -i hosts'): could not spawn process. (Failed to execute child process "/usr/sbin/nscd" (No such file or directory))
Jul 12 17:47:31 daddy-laptop NetworkManager: <info> Activation (wlan0) successful, device activated.
Jul 12 17:47:31 daddy-laptop NetworkManager: <info> Activation (wlan0) Finish handler scheduled.
Jul 12 17:47:31 daddy-laptop NetworkManager: <info> Activation (wlan0) Stage 5 of 5 (IP Configure Commit) complete.
Jul 12 17:47:31 daddy-laptop NetworkManager: <debug> [1215906451.295940] nm_dbus_signal_filter(): NetworkManagerInfo triggered update of wireless network 'ACTIONTEC'
Jul 12 18:56:59 daddy-laptop NetworkManager: <debug> [1215910619.224283] nm_device_802_11_wireless_get_activation_ap(): Forcing AP 'Home Network'
Jul 12 18:56:59 daddy-laptop NetworkManager: <info> User Switch: /org/freedesktop/NetworkManager/Devices/wlan0 / Home Network
Jul 12 18:56:59 daddy-laptop NetworkManager: <info> Deactivating device wlan0.
Jul 12 18:57:00 daddy-laptop NetworkManager: <info> Device wlan0 activation scheduled...
Jul 12 18:57:00 daddy-laptop NetworkManager: <info> Activation (wlan0) started...
Jul 12 18:57:00 daddy-laptop NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Jul 12 18:57:00 daddy-laptop NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Jul 12 18:57:00 daddy-laptop NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
Jul 12 18:57:00 daddy-laptop NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Jul 12 18:57:00 daddy-laptop NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Jul 12 18:57:00 daddy-laptop NetworkManager: <info> Activation (wlan0/wireless): access point 'Home Network' is encrypted, but NO valid key exists. New key needed.
Jul 12 18:57:00 daddy-laptop NetworkManager: <info> Activation (wlan0) New wireless user key requested for network 'Home Network'.
Jul 12 18:57:00 daddy-laptop NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Jul 12 18:57:00 daddy-laptop NetworkManager: <info> Activation (wlan0) New wireless user key for network 'Home Network' received.
Jul 12 18:57:00 daddy-laptop NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Jul 12 18:57:00 daddy-laptop NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Jul 12 18:57:00 daddy-laptop NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
Jul 12 18:57:00 daddy-laptop NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Jul 12 18:57:00 daddy-laptop NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Jul 12 18:57:00 daddy-laptop NetworkManager: <info> Activation (wlan0/wireless): access point 'Home Network' is encrypted, and a key exists. No new key needed.
Jul 12 18:57:01 daddy-laptop NetworkManager: <info> retry to connect to global supplicant socket (try=1)
Jul 12 18:57:02 daddy-laptop NetworkManager: <info> SUP: sending command 'INTERFACE_ADD wlan0^I^Iwext^I/var/run/wpa_supplicant0^I'
Jul 12 18:57:02 daddy-laptop NetworkManager: <info> SUP: response was 'OK'
Jul 12 18:57:02 daddy-laptop NetworkManager: <info> SUP: sending command 'AP_SCAN 1'
Jul 12 18:57:02 daddy-laptop NetworkManager: <info> SUP: response was 'OK'
Jul 12 18:57:02 daddy-laptop NetworkManager: <info> SUP: sending command 'ADD_NETWORK'
Jul 12 18:57:02 daddy-laptop NetworkManager: <info> SUP: response was '0'
Jul 12 18:57:02 daddy-laptop NetworkManager: <info> SUP: sending command 'SET_NETWORK 0 ssid 486f6d65204e6574776f726b'
Jul 12 18:57:02 daddy-laptop NetworkManager: <info> SUP: response was 'OK'
Jul 12 18:57:02 daddy-laptop NetworkManager: <info> SUP: sending command 'SET_NETWORK 0 key_mgmt NONE'
Jul 12 18:57:02 daddy-laptop NetworkManager: <info> SUP: response was 'OK'
Jul 12 18:57:02 daddy-laptop NetworkManager: <info> SUP: sending command 'SET_NETWORK 0 wep_key0 <key>'
Jul 12 18:57:02 daddy-laptop NetworkManager: <info> SUP: response was 'OK'
Jul 12 18:57:02 daddy-laptop NetworkManager: <info> SUP: sending command 'SET_NETWORK 0 wep_tx_keyidx 0'
Jul 12 18:57:02 daddy-laptop NetworkManager: <info> SUP: response was 'OK'
Jul 12 18:57:02 daddy-laptop NetworkManager: <info> SUP: sending command 'ENABLE_NETWORK 0'
Jul 12 18:57:02 daddy-laptop NetworkManager: <info> SUP: response was 'OK'
Jul 12 18:57:02 daddy-laptop NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Jul 12 18:57:02 daddy-laptop NetworkManager: <debug> [1215910622.328910] nm_device_802_11_wireless_update_bssid(): Roamed from BSSID 00:1D:7E:BB:A5:50 to 00:0F:B3:57 A:BB on wireless network 'Home Network'
Jul 12 18:57:02 daddy-laptop NetworkManager: <debug> [1215910622.331850] nm_dbus_signal_filter(): NetworkManagerInfo triggered update of wireless network 'Home Network'
Jul 12 18:57:02 daddy-laptop NetworkManager: <info> Old device 'wlan0' activating, won't change.
Jul 12 18:57:04 daddy-laptop NetworkManager: <info> Supplicant state changed: 1
Jul 12 18:57:04 daddy-laptop NetworkManager: <info> Activation (wlan0/wireless) Stage 2 of 5 (Device Configure) successful. Connected to access point 'Home Network'.
Jul 12 18:57:04 daddy-laptop NetworkManager: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) scheduled.
Jul 12 18:57:04 daddy-laptop NetworkManager: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) started...
Jul 12 18:57:06 daddy-laptop NetworkManager: <info> Activation (wlan0) Beginning DHCP transaction.
Jul 12 18:57:06 daddy-laptop NetworkManager: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) complete.
Jul 12 18:57:06 daddy-laptop NetworkManager: <debug> [1215910626.862356] nm_device_802_11_wireless_update_bssid(): Roamed from BSSID 00:0F:B3:57 A:BB to 00:1D:7E:BB:A5:50 on wireless network 'Home Network'
Jul 12 18:57:06 daddy-laptop NetworkManager: <info> DHCP daemon state is now 12 (successfully started) for interface wlan0
Jul 12 18:57:06 daddy-laptop NetworkManager: <debug> [1215910626.868152] nm_dbus_signal_filter(): NetworkManagerInfo triggered update of wireless network 'Home Network'
Jul 12 18:57:06 daddy-laptop NetworkManager: <info> Old device 'wlan0' activating, won't change.
Jul 12 18:57:07 daddy-laptop NetworkManager: <info> DHCP daemon state is now 1 (starting) for interface wlan0
Jul 12 18:57:09 daddy-laptop NetworkManager: <info> Old device 'wlan0' activating, won't change.
Jul 12 18:57:48 daddy-laptop NetworkManager: <info> DHCP daemon state is now 9 (fail) for interface wlan0
Jul 12 18:57:48 daddy-laptop NetworkManager: <info> Activation (wlan0) Stage 4 of 5 (IP Configure Timeout) scheduled...
Jul 12 18:57:48 daddy-laptop NetworkManager: <info> Activation (wlan0) Stage 4 of 5 (IP Configure Timeout) started...
Jul 12 18:57:48 daddy-laptop NetworkManager: <debug> [1215910668.824633] real_act_stage4_ip_config_timeout(): Activation (wlan0/wireless): could not get IP configuration info for 'Home Network', asking for new key.
Jul 12 18:57:48 daddy-laptop NetworkManager: <info> DHCP daemon state is now 14 (normal exit) for interface wlan0
Jul 12 18:57:49 daddy-laptop NetworkManager: <info> Activation (wlan0) New wireless user key requested for network 'Home Network'.
Jul 12 18:57:49 daddy-laptop NetworkManager: <info> Activation (wlan0) Stage 4 of 5 (IP Configure Timeout) complete.
Jul 12 18:58:21 daddy-laptop NetworkManager: <info> Activation (wlan0) New wireless user key for network 'Home Network' received.
Jul 12 18:58:21 daddy-laptop NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Jul 12 18:58:21 daddy-laptop NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Jul 12 18:58:21 daddy-laptop NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
Jul 12 18:58:21 daddy-laptop NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Jul 12 18:58:21 daddy-laptop NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Jul 12 18:58:21 daddy-laptop NetworkManager: <info> Activation (wlan0/wireless): access point 'Home Network' is encrypted, and a key exists. No new key needed.
Jul 12 18:58:23 daddy-laptop NetworkManager: <info> retry to connect to global supplicant socket (try=1)
Jul 12 18:58:23 daddy-laptop NetworkManager: <info> SUP: sending command 'INTERFACE_ADD wlan0^I^Iwext^I/var/run/wpa_supplicant0^I'
Jul 12 18:58:23 daddy-laptop NetworkManager: <info> SUP: response was 'OK'
Jul 12 18:58:23 daddy-laptop NetworkManager: <info> SUP: sending command 'AP_SCAN 1'
Jul 12 18:58:23 daddy-laptop NetworkManager: <info> SUP: response was 'OK'
Jul 12 18:58:23 daddy-laptop NetworkManager: <info> SUP: sending command 'ADD_NETWORK'
Jul 12 18:58:23 daddy-laptop NetworkManager: <info> SUP: response was '0'
Jul 12 18:58:23 daddy-laptop NetworkManager: <info> SUP: sending command 'SET_NETWORK 0 ssid 486f6d65204e6574776f726b'
Jul 12 18:58:23 daddy-laptop NetworkManager: <info> SUP: response was 'OK'
Jul 12 18:58:23 daddy-laptop NetworkManager: <info> SUP: sending command 'SET_NETWORK 0 key_mgmt NONE'
Jul 12 18:58:23 daddy-laptop NetworkManager: <info> SUP: response was 'OK'
Jul 12 18:58:23 daddy-laptop NetworkManager: <info> SUP: sending command 'SET_NETWORK 0 wep_key0 <key>'
Jul 12 18:58:23 daddy-laptop NetworkManager: <info> SUP: response was 'OK'
Jul 12 18:58:23 daddy-laptop NetworkManager: <info> SUP: sending command 'SET_NETWORK 0 wep_tx_keyidx 0'
Jul 12 18:58:23 daddy-laptop NetworkManager: <info> SUP: response was 'OK'
Jul 12 18:58:23 daddy-laptop NetworkManager: <info> SUP: sending command 'ENABLE_NETWORK 0'
Jul 12 18:58:23 daddy-laptop NetworkManager: <info> SUP: response was 'OK'
Jul 12 18:58:23 daddy-laptop NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Jul 12 18:58:26 daddy-laptop NetworkManager: <info> Supplicant state changed: 1
Jul 12 18:58:26 daddy-laptop NetworkManager: <info> Activation (wlan0/wireless) Stage 2 of 5 (Device Configure) successful. Connected to access point 'Home Network'.
Jul 12 18:58:26 daddy-laptop NetworkManager: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) scheduled.
Jul 12 18:58:26 daddy-laptop NetworkManager: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) started...
Jul 12 18:58:27 daddy-laptop NetworkManager: <info> Activation (wlan0) Beginning DHCP transaction.
Jul 12 18:58:27 daddy-laptop NetworkManager: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) complete.
Jul 12 18:58:27 daddy-laptop NetworkManager: <info> DHCP daemon state is now 12 (successfully started) for interface wlan0
Jul 12 18:58:28 daddy-laptop NetworkManager: <info> DHCP daemon state is now 1 (starting) for interface wlan0
Jul 12 18:58:31 daddy-laptop NetworkManager: <info> Old device 'wlan0' activating, won't change.
Jul 12 18:59:09 daddy-laptop NetworkManager: <info> DHCP daemon state is now 9 (fail) for interface wlan0
Jul 12 18:59:09 daddy-laptop NetworkManager: <info> Activation (wlan0) Stage 4 of 5 (IP Configure Timeout) scheduled...
Jul 12 18:59:09 daddy-laptop NetworkManager: <info> Activation (wlan0) Stage 4 of 5 (IP Configure Timeout) started...
Jul 12 18:59:09 daddy-laptop NetworkManager: <debug> [1215910749.190805] real_act_stage4_ip_config_timeout(): Activation (wlan0/wireless): could not get IP configuration info for 'Home Network', asking for new key.
Jul 12 18:59:09 daddy-laptop NetworkManager: <info> DHCP daemon state is now 14 (normal exit) for interface wlan0
Jul 12 18:59:09 daddy-laptop NetworkManager: <info> Activation (wlan0) New wireless user key requested for network 'Home Network'.
Jul 12 18:59:09 daddy-laptop NetworkManager: <info> Activation (wlan0) Stage 4 of 5 (IP Configure Timeout) complete.
Jul 12 19:01:04 daddy-laptop NetworkManager: <info> Activation (wlan0) New wireless user key for network 'Home Network' received.
Jul 12 19:01:04 daddy-laptop NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Jul 12 19:01:04 daddy-laptop NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Jul 12 19:01:04 daddy-laptop NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
Jul 12 19:01:04 daddy-laptop NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Jul 12 19:01:04 daddy-laptop NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Jul 12 19:01:04 daddy-laptop NetworkManager: <info> Activation (wlan0/wireless): access point 'Home Network' is encrypted, and a key exists. No new key needed.
Jul 12 19:01:05 daddy-laptop NetworkManager: <info> retry to connect to global supplicant socket (try=1)
Jul 12 19:01:06 daddy-laptop NetworkManager: <info> SUP: sending command 'INTERFACE_ADD wlan0^I^Iwext^I/var/run/wpa_supplicant0^I'
Jul 12 19:01:06 daddy-laptop NetworkManager: <info> SUP: response was 'OK'
Jul 12 19:01:06 daddy-laptop NetworkManager: <info> SUP: sending command 'AP_SCAN 1'
Jul 12 19:01:06 daddy-laptop NetworkManager: <info> SUP: response was 'OK'
Jul 12 19:01:06 daddy-laptop NetworkManager: <info> SUP: sending command 'ADD_NETWORK'
Jul 12 19:01:06 daddy-laptop NetworkManager: <info> SUP: response was '0'
Jul 12 19:01:06 daddy-laptop NetworkManager: <info> SUP: sending command 'SET_NETWORK 0 ssid 486f6d65204e6574776f726b'
Jul 12 19:01:06 daddy-laptop NetworkManager: <info> SUP: response was 'OK'
Jul 12 19:01:06 daddy-laptop NetworkManager: <info> SUP: sending command 'SET_NETWORK 0 key_mgmt NONE'
Jul 12 19:01:06 daddy-laptop NetworkManager: <info> SUP: response was 'OK'
Jul 12 19:01:06 daddy-laptop NetworkManager: <info> SUP: sending command 'SET_NETWORK 0 wep_key0 <key>'
Jul 12 19:01:06 daddy-laptop NetworkManager: <info> SUP: response was 'OK'
Jul 12 19:01:06 daddy-laptop NetworkManager: <info> SUP: sending command 'SET_NETWORK 0 wep_tx_keyidx 0'
Jul 12 19:01:06 daddy-laptop NetworkManager: <info> SUP: response was 'OK'
Jul 12 19:01:06 daddy-laptop NetworkManager: <info> SUP: sending command 'ENABLE_NETWORK 0'
Jul 12 19:01:06 daddy-laptop NetworkManager: <info> SUP: response was 'OK'
Jul 12 19:01:06 daddy-laptop NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Jul 12 19:01:15 daddy-laptop NetworkManager: <info> Supplicant state changed: 1
Jul 12 19:01:15 daddy-laptop NetworkManager: <info> Activation (wlan0/wireless) Stage 2 of 5 (Device Configure) successful. Connected to access point 'Home Network'.
Jul 12 19:01:15 daddy-laptop NetworkManager: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) scheduled.
Jul 12 19:01:15 daddy-laptop NetworkManager: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) started...
Jul 12 19:01:15 daddy-laptop NetworkManager: <info> Old device 'wlan0' activating, won't change.
Jul 12 19:01:16 daddy-laptop NetworkManager: <info> Activation (wlan0) Beginning DHCP transaction.
Jul 12 19:01:16 daddy-laptop NetworkManager: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) complete.
Jul 12 19:01:16 daddy-laptop NetworkManager: <info> DHCP daemon state is now 12 (successfully started) for interface wlan0
Jul 12 19:01:17 daddy-laptop NetworkManager: <info> DHCP daemon state is now 1 (starting) for interface wlan0
Jul 12 19:01:20 daddy-laptop NetworkManager: <info> Old device 'wlan0' activating, won't change.
Jul 12 19:01:27 daddy-laptop NetworkManager: <debug> [1215910887.334106] nm_device_802_11_wireless_get_activation_ap(): Forcing AP 'ACTIONTEC'
Jul 12 19:01:27 daddy-laptop NetworkManager: <info> User Switch: /org/freedesktop/NetworkManager/Devices/wlan0 / ACTIONTEC
Jul 12 19:01:27 daddy-laptop NetworkManager: <info> Deactivating device wlan0.
Jul 12 19:01:27 daddy-laptop NetworkManager: <info> Activation (wlan0): cancelling...
Jul 12 19:01:27 daddy-laptop NetworkManager: <info> Activation (wlan0) cancellation handler scheduled...
Jul 12 19:01:27 daddy-laptop NetworkManager: <info> Activation (wlan0): waiting for device to cancel activation.
Jul 12 19:01:28 daddy-laptop NetworkManager: <info> Activation (wlan0) cancellation handled.
Jul 12 19:01:28 daddy-laptop NetworkManager: <info> Activation (wlan0): cancelled.
Jul 12 19:01:28 daddy-laptop NetworkManager: <info> Device wlan0 activation scheduled...
Jul 12 19:01:28 daddy-laptop NetworkManager: <info> Activation (wlan0) started...
Jul 12 19:01:28 daddy-laptop NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Jul 12 19:01:28 daddy-laptop NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Jul 12 19:01:28 daddy-laptop NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
Jul 12 19:01:28 daddy-laptop NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Jul 12 19:01:28 daddy-laptop NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Jul 12 19:01:28 daddy-laptop NetworkManager: <info> Activation (wlan0/wireless): access point 'ACTIONTEC' is unencrypted, no key needed.
Jul 12 19:01:29 daddy-laptop NetworkManager: <info> SUP: sending command 'INTERFACE_ADD wlan0^I^Iwext^I/var/run/wpa_supplicant0^I'
Jul 12 19:01:29 daddy-laptop NetworkManager: <info> SUP: response was 'OK'
Jul 12 19:01:30 daddy-laptop NetworkManager: <info> SUP: sending command 'AP_SCAN 1'
Jul 12 19:01:30 daddy-laptop NetworkManager: <info> SUP: response was 'OK'
Jul 12 19:01:30 daddy-laptop NetworkManager: <info> SUP: sending command 'ADD_NETWORK'
Jul 12 19:01:30 daddy-laptop NetworkManager: <info> SUP: response was '0'
Jul 12 19:01:30 daddy-laptop NetworkManager: <info> SUP: sending command 'SET_NETWORK 0 ssid 414354494f4e544543'
Jul 12 19:01:30 daddy-laptop NetworkManager: <info> SUP: response was 'OK'
Jul 12 19:01:30 daddy-laptop NetworkManager: <info> SUP: sending command 'SET_NETWORK 0 key_mgmt NONE'
Jul 12 19:01:30 daddy-laptop NetworkManager: <info> SUP: response was 'OK'
Jul 12 19:01:30 daddy-laptop NetworkManager: <info> SUP: sending command 'ENABLE_NETWORK 0'
Jul 12 19:01:30 daddy-laptop NetworkManager: <info> SUP: response was 'OK'
Jul 12 19:01:30 daddy-laptop NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Jul 12 19:01:30 daddy-laptop NetworkManager: <debug> [1215910890.335588] nm_device_802_11_wireless_update_bssid(): Roamed from BSSID 00:0F:B3:57 A:BB to 00:1D:7E:BB:A5:50 on wireless network 'ACTIONTEC'
Jul 12 19:01:30 daddy-laptop NetworkManager: <debug> [1215910890.339555] nm_dbus_signal_filter(): NetworkManagerInfo triggered update of wireless network 'ACTIONTEC'
Jul 12 19:01:30 daddy-laptop NetworkManager: <info> Old device 'wlan0' activating, won't change.
Jul 12 19:01:36 daddy-laptop NetworkManager: <info> Old device 'wlan0' activating, won't change.
Jul 12 19:01:44 daddy-laptop NetworkManager: <info> Old device 'wlan0' activating, won't change.
Jul 12 19:01:51 daddy-laptop NetworkManager: <info> Old device 'wlan0' activating, won't change.
Jul 12 19:01:52 daddy-laptop NetworkManager: <debug> [1215910912.336168] nm_device_802_11_wireless_get_activation_ap(): Forcing AP 'ACTIONTEC'
Jul 12 19:01:52 daddy-laptop NetworkManager: <info> User Switch: /org/freedesktop/NetworkManager/Devices/wlan0 / ACTIONTEC
Jul 12 19:01:52 daddy-laptop NetworkManager: <info> Deactivating device wlan0.
Jul 12 19:01:52 daddy-laptop NetworkManager: <info> Activation (wlan0): cancelling...
Jul 12 19:01:52 daddy-laptop NetworkManager: <info> Activation (wlan0) cancellation handler scheduled...
Jul 12 19:01:52 daddy-laptop NetworkManager: <info> Activation (wlan0): waiting for device to cancel activation.
Jul 12 19:01:52 daddy-laptop NetworkManager: <info> Activation (wlan0) cancellation handled.
Jul 12 19:01:52 daddy-laptop NetworkManager: <info> Activation (wlan0): cancelled.
Jul 12 19:01:52 daddy-laptop NetworkManager: <info> Device wlan0 activation scheduled...
Jul 12 19:01:52 daddy-laptop NetworkManager: <info> Activation (wlan0) started...
Jul 12 19:01:52 daddy-laptop NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Jul 12 19:01:52 daddy-laptop NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Jul 12 19:01:52 daddy-laptop NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
Jul 12 19:01:52 daddy-laptop NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Jul 12 19:01:52 daddy-laptop NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Jul 12 19:01:52 daddy-laptop NetworkManager: <info> Activation (wlan0/wireless): access point 'ACTIONTEC' is unencrypted, no key needed.
Jul 12 19:01:53 daddy-laptop NetworkManager: <info> retry to connect to global supplicant socket (try=1)
Jul 12 19:01:54 daddy-laptop NetworkManager: <info> SUP: sending command 'INTERFACE_ADD wlan0^I^Iwext^I/var/run/wpa_supplicant0^I'
Jul 12 19:01:54 daddy-laptop NetworkManager: <info> SUP: response was 'OK'
Jul 12 19:01:54 daddy-laptop NetworkManager: <info> SUP: sending command 'AP_SCAN 1'
Jul 12 19:01:54 daddy-laptop NetworkManager: <info> SUP: response was 'OK'
Jul 12 19:01:54 daddy-laptop NetworkManager: <info> SUP: sending command 'ADD_NETWORK'
Jul 12 19:01:54 daddy-laptop NetworkManager: <info> SUP: response was '0'
Jul 12 19:01:54 daddy-laptop NetworkManager: <info> SUP: sending command 'SET_NETWORK 0 ssid 414354494f4e544543'
Jul 12 19:01:54 daddy-laptop NetworkManager: <info> SUP: response was 'OK'
Jul 12 19:01:54 daddy-laptop NetworkManager: <info> SUP: sending command 'SET_NETWORK 0 key_mgmt NONE'
Jul 12 19:01:54 daddy-laptop NetworkManager: <info> SUP: response was 'OK'
Jul 12 19:01:54 daddy-laptop NetworkManager: <info> SUP: sending command 'ENABLE_NETWORK 0'
Jul 12 19:01:54 daddy-laptop NetworkManager: <info> SUP: response was 'OK'
Jul 12 19:01:54 daddy-laptop NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Jul 12 19:01:56 daddy-laptop NetworkManager: <info> Old device 'wlan0' activating, won't change.
Jul 12 19:02:07 daddy-laptop NetworkManager: <info> Old device 'wlan0' activating, won't change.
Jul 12 19:02:15 daddy-laptop NetworkManager: <info> Old device 'wlan0' activating, won't change.
Jul 12 19:02:22 daddy-laptop NetworkManager: <info> Old device 'wlan0' activating, won't change.
Jul 12 19:02:28 daddy-laptop NetworkManager: <info> Old device 'wlan0' activating, won't change.
Jul 12 19:02:32 daddy-laptop NetworkManager: <debug> [1215910952.034996] nm_device_802_11_wireless_get_activation_ap(): Forcing AP 'ACTIONTEC'
Jul 12 19:02:32 daddy-laptop NetworkManager: <info> User Switch: /org/freedesktop/NetworkManager/Devices/wlan0 / ACTIONTEC
Jul 12 19:02:32 daddy-laptop NetworkManager: <info> Deactivating device wlan0.
Jul 12 19:02:32 daddy-laptop NetworkManager: <info> Activation (wlan0): cancelling...
Jul 12 19:02:32 daddy-laptop NetworkManager: <info> Activation (wlan0) cancellation handler scheduled...
Jul 12 19:02:32 daddy-laptop NetworkManager: <info> Activation (wlan0): waiting for device to cancel activation.
Jul 12 19:02:32 daddy-laptop NetworkManager: <info> Activation (wlan0) cancellation handled.
Jul 12 19:02:32 daddy-laptop NetworkManager: <info> Activation (wlan0): cancelled.
Jul 12 19:02:32 daddy-laptop NetworkManager: nm_utils_supplicant_request_with_check: assertion `ctrl != NULL' failed
Jul 12 19:02:32 daddy-laptop NetworkManager: <WARN> nm_device_802_11_wireless_scan(): (wlan0): could not trigger wireless scan
Jul 12 19:02:32 daddy-laptop NetworkManager: nm_utils_supplicant_request_with_check: assertion `ctrl != NULL' failed
Jul 12 19:02:32 daddy-laptop NetworkManager: <WARN> nm_device_802_11_wireless_scan(): (wlan0): could not trigger wireless scan
Jul 12 19:02:32 daddy-laptop NetworkManager: <info> Device wlan0 activation scheduled...
Jul 12 19:02:32 daddy-laptop NetworkManager: <info> Activation (wlan0) started...
Jul 12 19:02:32 daddy-laptop NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Jul 12 19:02:32 daddy-laptop NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Jul 12 19:02:32 daddy-laptop NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
Jul 12 19:02:32 daddy-laptop NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Jul 12 19:02:32 daddy-laptop NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Jul 12 19:02:32 daddy-laptop NetworkManager: <info> Activation (wlan0/wireless): access point 'ACTIONTEC' is unencrypted, no key needed.
Jul 12 19:02:33 daddy-laptop NetworkManager: <info> retry to connect to global supplicant socket (try=1)
Jul 12 19:02:33 daddy-laptop NetworkManager: <info> SUP: sending command 'INTERFACE_ADD wlan0^I^Iwext^I/var/run/wpa_supplicant0^I'
Jul 12 19:02:33 daddy-laptop NetworkManager: <info> SUP: response was 'OK'
Jul 12 19:02:34 daddy-laptop NetworkManager: <info> SUP: sending command 'AP_SCAN 1'
Jul 12 19:02:34 daddy-laptop NetworkManager: <info> SUP: response was 'OK'
Jul 12 19:02:34 daddy-laptop NetworkManager: <info> SUP: sending command 'ADD_NETWORK'
Jul 12 19:02:34 daddy-laptop NetworkManager: <info> SUP: response was '0'
Jul 12 19:02:34 daddy-laptop NetworkManager: <info> SUP: sending command 'SET_NETWORK 0 ssid 414354494f4e544543'
Jul 12 19:02:34 daddy-laptop NetworkManager: <info> SUP: response was 'OK'
Jul 12 19:02:34 daddy-laptop NetworkManager: <info> SUP: sending command 'SET_NETWORK 0 key_mgmt NONE'
Jul 12 19:02:34 daddy-laptop NetworkManager: <info> SUP: response was 'OK'
Jul 12 19:02:34 daddy-laptop NetworkManager: <info> SUP: sending command 'ENABLE_NETWORK 0'
Jul 12 19:02:34 daddy-laptop NetworkManager: <info> SUP: response was 'OK'
Jul 12 19:02:34 daddy-laptop NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Jul 12 19:02:35 daddy-laptop NetworkManager: <info> Old device 'wlan0' activating, won't change.
Jul 12 19:02:42 daddy-laptop NetworkManager: <info> Old device 'wlan0' activating, won't change.
Jul 12 19:02:48 daddy-laptop NetworkManager: <info> Old device 'wlan0' activating, won't change.
Jul 12 19:02:55 daddy-laptop NetworkManager: <info> Old device 'wlan0' activating, won't change.
Jul 12 19:03:01 daddy-laptop NetworkManager: <info> Old device 'wlan0' activating, won't change.
Jul 12 19:03:08 daddy-laptop NetworkManager: <debug> [1215910988.590757] nm_device_802_11_wireless_update_bssid(): Roamed from BSSID 00:1D:7E:BB:A5:50 to 00:0F:B3:57 A:BB on wireless network 'ACTIONTEC'
Jul 12 19:03:08 daddy-laptop NetworkManager: <info> Supplicant state changed: 1
Jul 12 19:03:08 daddy-laptop NetworkManager: <info> Activation (wlan0/wireless) Stage 2 of 5 (Device Configure) successful. Connected to access point 'ACTIONTEC'.
Jul 12 19:03:08 daddy-laptop NetworkManager: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) scheduled.
Jul 12 19:03:08 daddy-laptop NetworkManager: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) started...
Jul 12 19:03:08 daddy-laptop NetworkManager: <info> Old device 'wlan0' activating, won't change.
Jul 12 19:03:08 daddy-laptop NetworkManager: <debug> [1215910988.594685] nm_dbus_signal_filter(): NetworkManagerInfo triggered update of wireless network 'ACTIONTEC'
Jul 12 19:03:08 daddy-laptop NetworkManager: <info> Old device 'wlan0' activating, won't change.
Jul 12 19:03:09 daddy-laptop NetworkManager: <info> Activation (wlan0) Beginning DHCP transaction.
Jul 12 19:03:09 daddy-laptop NetworkManager: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) complete.
Jul 12 19:03:09 daddy-laptop NetworkManager: <info> DHCP daemon state is now 12 (successfully started) for interface wlan0
Jul 12 19:03:10 daddy-laptop NetworkManager: <info> DHCP daemon state is now 1 (starting) for interface wlan0
Jul 12 19:03:10 daddy-laptop NetworkManager: <info> DHCP daemon state is now 2 (bound) for interface wlan0
Jul 12 19:03:10 daddy-laptop NetworkManager: <info> Activation (wlan0) Stage 4 of 5 (IP Configure Get) scheduled...
Jul 12 19:03:10 daddy-laptop NetworkManager: <info> Activation (wlan0) Stage 4 of 5 (IP Configure Get) started...
Jul 12 19:03:11 daddy-laptop NetworkManager: <info> Retrieved the following IP4 configuration from the DHCP daemon:
Jul 12 19:03:11 daddy-laptop NetworkManager: <info> address 192.168.0.3
Jul 12 19:03:11 daddy-laptop NetworkManager: <info> netmask 255.255.255.0
Jul 12 19:03:11 daddy-laptop NetworkManager: <info> broadcast 192.168.0.255
Jul 12 19:03:11 daddy-laptop NetworkManager: <info> gateway 192.168.0.1
Jul 12 19:03:11 daddy-laptop NetworkManager: <info> nameserver 192.168.0.1
Jul 12 19:03:11 daddy-laptop NetworkManager: <info> nameserver 205.171.3.65
Jul 12 19:03:11 daddy-laptop NetworkManager: <info> hostname 'daddy-laptop'
Jul 12 19:03:11 daddy-laptop NetworkManager: <info> domain name 'domain.actdsltmp'
Jul 12 19:03:11 daddy-laptop NetworkManager: <info> Activation (wlan0) Stage 5 of 5 (IP Configure Commit) scheduled...
Jul 12 19:03:11 daddy-laptop NetworkManager: <info> Activation (wlan0) Stage 4 of 5 (IP Configure Get) complete.
Jul 12 19:03:11 daddy-laptop NetworkManager: <info> Activation (wlan0) Stage 5 of 5 (IP Configure Commit) started...
Jul 12 19:03:12 daddy-laptop NetworkManager: <info> Clearing nscd hosts cache.
Jul 12 19:03:12 daddy-laptop NetworkManager: <WARN> nm_spawn_process(): nm_spawn_process('/usr/sbin/nscd -i hosts'): could not spawn process. (Failed to execute child process "/usr/sbin/nscd" (No such file or directory))
Jul 12 19:03:12 daddy-laptop NetworkManager: <info> Activation (wlan0) successful, device activated.
Jul 12 19:03:12 daddy-laptop NetworkManager: <info> Activation (wlan0) Finish handler scheduled.
Jul 12 19:03:12 daddy-laptop NetworkManager: <info> Activation (wlan0) Stage 5 of 5 (IP Configure Commit) complete.
Jul 12 19:03:12 daddy-laptop NetworkManager: <debug> [1215910992.915193] nm_dbus_signal_filter(): NetworkManagerInfo triggered update of wireless network 'ACTIONTEC'
daddy@daddy-laptop:~$

 

Yeah... that's a lot of lines. From what I can tell, the encryption protocol is working fine but dhclient fails to get an IP address. The next thing I would do is look for lines like these:

Code:

Jul 12 17:12:06 bodhi NetworkManager: <info>  DHCP daemon state is now 1 (starting) for interface wlan0
Jul 12 17:12:06 bodhi dhclient: wmaster0: unknown hardware address type 801
Jul 12 17:12:08 bodhi dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 5
Jul 12 17:12:08 bodhi dhclient: DHCPOFFER of 192.168.0.198 from 192.168.0.1
Jul 12 17:12:08 bodhi dhclient: DHCPREQUEST of 192.168.0.198 on wlan0 to 255.255.255.255 port 67
Jul 12 17:12:08 bodhi dhclient: DHCPACK of 192.168.0.198 from 192.168.0.1

The lines above indicate a successful DHCP request so of course your lines will be different.

If you open your /var/log/system in an editor and search for this line (which I copied from your previous post):

Code:

Jul 12 17:44:02 daddy-laptop NetworkManager:  DHCP daemon state is now 1 (starting) for interface wlan0

Immediately after it, you should have a bunch of dhclient lines which will tell us what dhclient was trying to do and what errors it may have encountered.

 

I can't find any of those 'dhclient' lines in my log at all.

 

!?!? That's very strange.

Can you run these two commands to make sure dhclient is there?

Code:

$ which dhclient
$ dpkg -S /sbin/dhclient

Here's what I get:

Code:

$ which dhclient
/sbin/dhclient
$ dpkg -S /sbin/dhclient
dhcp3-client: /sbin/dhclient

 

For which dhclient i get:

/sbin/dhclient

Well, this is interesting. I ran 'dpkg -s /sbin/dhclient' and I get this:

Package `/sbin/dhclient' is not installed and no info is available.
Use dpkg --info (= dpkg-deb --info) to examine archive files,
and dpkg --contents (= dpkg-deb --contents) to list their contents.

Is there some client I need to install? If so, which one? And where do I get it?

 

The flag is "-S" not "-s". In the Unix universe you should assume that everything is case-sensitive. "-S" is different than "-s". dhclient is different than DHCLIENT, DHclient, Dhclient and dhclienT. At any rate, it seems that dhclient is there so I'm confused as to why it is not run...

Alright, open /var/log/syslog in an editor and show me the lines between these two lines (copied from your grep output):

Code:

Jul 12 17:44:02 daddy-laptop NetworkManager:  DHCP daemon state is now 1 (starting) for interface wlan0 

and

Code:

Jul 12 17:44:46 daddy-laptop NetworkManager:  DHCP daemon state is now 9 (fail) for interface wlan0 

Use the timestamps for guidance (17:44:02 and 17:44:46).

 

This is all that came up:

Jul 12 17:44:02 daddy-laptop NetworkManager: DHCP daemon state is now 1 (starting) for interface wlan0
Jul 12 17:44:04 daddy-laptop NetworkManager: Old device 'wlan0' activating, won't change.
Jul 12 17:44:46 daddy-laptop NetworkManager: DHCP daemon state is now 9 (fail) for interface wlan0

I ran the other command CORRECTLY and got this:

dhcp3-client: /sbin/dhclient

 

Which editor did you use to inspect your /var/log/syslog?

Yep, that's to be expected.

 

Aw crap! I was resizing a window Ubuntu and it got stuck in resize mode. I had to restart my notebook. I am in Vista right now and am using my Home Network so it's definately something going on in Ubuntu. I can redo the log if you need me to. By the way, thanks for all the help.

 

You're welcome. Your syslog should be intact so you don't need to "redo the log". It is definitely strange that you don't get any dhclient lines though between the two lines I mentioned above. I'm wondering if the procedure you use to inspect the /var/log/syslog file is problematic somehow. So I need to know what editor you use to inspect /var/log/syslog.

(NB: I'm off to bed now so this conversation will have to continue tomorrow. If anyone else in a different time zone or different sleeping habits wants to take the relay, be my guest.)

 

I have resolved my problem. I uninstalled WUBI/Ubuntu.

I then re-installed it and used "WEP 64/128 Bit Hex" and entered my security key...............and BAM! it connected. Thanks again for the help Emperor Lemur.

 

Yep, simple encryption protocol.....I use WPA2 with Mandriva, but some distro's I couldn't connect until I selected WEP xxx , but I didn't have something installed at that time during 'trials'

 

I'm glad it is fixed but this is weird. In theory fixing this problem should not have required to reinstall. However, if something went bad during the first installation, it can be difficult to walk someone else through the steps required to fix it.

It has only happened once I think that I screwed up an installation so badly that the best course of action was to reinstall rather than to try fixing it. (LVM+encryption without a /boot partition is not a good idea. That's the mistake I made.)

But yay, I'm glad you did not get turned off by this hiccup.

 

I almost did get turned off. I was thinking "this linux just isn't for me". But I decided to go ahead and re-install it again. When you install Wubi it gives the option of how much disc space to use. This time I used 15GB instead of 10GB. I tried using the different WEP options in the original installation but it didn't work. This time I just started from the top and worked my way down the options, and it was the second one down that worked for me.

Now I have Ubuntu Linux..........now what do I do? :confused2:
Guess that'll be my next topic of discussion.

 

One last thing to try is to use WPA encryption as WEP is extremely insecure.

 

True. Using WPA would be better.

 

yep....a lot of WEP sport cracking going on out there....WPA2 fixes them.