You could search the logs, with something like sudo zegrep -n 'wpa_supplicant|NetworkManager' /var/log/*
to see what's going on.
After looking at the posted log, here's how I analyzed it.
Analysis of var_log.txt (http://pastebin.com/Y9s3UJMN
), 230 lines
like:
/var/log/syslog:7607:Dec 18 14:57:52 trav-HP-Pavilion-dv6000-RG360UA-ABA NetworkManager[870]: <info> (wlan0): device state change: need-auth -> prepare (reason 'none') [60 40 0]
Too much clutter, and possibly too little information. Let's reduce
the clutter, and see what's left. The tool I use for this is the GNU
Emacs editor, but you can use any editor on a copy of the file, as did
I.
All the lines start with "/var/log/syslog:
" - no useful information
here, delete.
Next is the line number (due to the -n option). Note that there
are gaps in the sequence of line numbers. The omitted lines
(7622-7625, and other short gaps) are lines that don't contain
"NetworkManager
" or "wpa_supplicant
", but they might contain
interesting information. This is something for you to look
at. Let's keep the line numbers, for now.
Then there's the date, time, hostname (what kind of hostname is
"trav-HP-Pavilion-dv6000-RG360UA-ABA
"? Replace (in the log) it with
"trav
", with no information lost, and 31 characters of clutter saved
per line), and the processname that made the log entry. We only
grepped for "NetworkManager
" or "wpa_supplicant
", so that's all we
got. Notice that the PIDs (the Process IDs, in []) remain the same,
[870]
for NetworkManager
, and [916]
for wpa_supplicant
. This means
that NetworkManager and wpa_supplicant did NOT restart during this log
fragment. They each think they are functioning "normally".
Finally, we get to the message that was logged. NetworkManager tags
its messages with "info" or "warn", wpa_supplicant doesn't.
Then, looking at the messages in the first block of consecutive line
numbers, 7607 to 7621:
<info> (wlan0): device state change: need-auth -> prepare (reason 'none')
<info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
<info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
<info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
<info> (wlan0): device state change: prepare -> config (reason 'none')
<info> Activation (wlan0/wireless): connection 'Auto Verizon DROIDX 19
<info> Config: added 'ssid' value 'Verizon DROIDX 1980'
<info> Config: added 'scan_ssid' value '1'
<info> Config: added 'key_mgmt' value 'WPA-PSK'
<info> Config: added 'psk' value '<omitted>'
<info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
<info> Config: set interface ap_scan to 1
<info> (wlan0): supplicant interface state: inactive -> scanning
Trying to authenticate with 40:fc:89:29:82:fb (SSID='Verizon DROIDX 19
<info> (wlan0): supplicant interface state: scanning -> authenticating
We see NetworkManager doing Stage 1 and Stage 2 (of 5) of Activation,
then calling on wpa_supplicant to try to authenticate using the SSID
"Verizon DROIDX 1980", MAC address 40:fc:89:29:82:fb.
Then, at Dec 18 14:58:02 and every 8 seconds thereafter,
wpa-supplicant logs:
Trying to authenticate with 40:fc:89:29:82:fb (SSID='Verizon DROIDX 1980' freq=2462 MHz)
Then, at Dec 18 14:58:38, NetworkManager does a 'user-requested'
disconnect.
Looking at these log entries was a waste of time - starting over at
line 7654 "Activation (wlan0) starting connection 'Verizon DROID2
6182'", but this time, there's some different information:
<info> Activation (wlan0) starting connection 'Verizon DROID2 6182'
<info> (wlan0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
<info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
<info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
<info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
<info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
<info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
<info> (wlan0): device state change: prepare -> config (reason 'none') [40 50 0]
<info> Activation (wlan0/wireless): access point 'Verizon DROID2 6182' has security, but secrets are required.
<info> (wlan0): device state change: config -> need-auth (reason 'none') [50 60 0]
<info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Then at 14:59:27, we see another wireless restart, still WPA-PSK,
known "secrets", but with added 'auth_alg' value 'OPEN'. Different frequency.
get_secret_flags: assertion `is_secret_prop (setting, secret_name, error)' failed
<info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
<info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
<info> (wlan0): device state change: need-auth -> prepare (reason 'none') [60 40 0]
<info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
<info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
<info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
<info> (wlan0): device state change: prepare -> config (reason 'none') [40 50 0]
<info> Activation (wlan0/wireless): connection 'Verizon DROID2 6182' has security, and secrets exist. No new secrets needed.
<info> Config: added 'ssid' value 'Verizon DROID2 6182'
<info> Config: added 'scan_ssid' value '1'
<info> Config: added 'key_mgmt' value 'WPA-PSK'
<info> Config: added 'auth_alg' value 'OPEN'
<info> Config: added 'psk' value '<omitted>'
<info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
<info> Config: set interface ap_scan to 1
<info> (wlan0): supplicant interface state: disconnected -> scanning
Trying to authenticate with f8:7b:7a:4f:8f:56 (SSID='Verizon DROID2 6182' freq=2437 MHz)
Ends up with wpa_supplicant trying a different MAC and SSID, and
retrying. At Dec 18 15:00:27 NetworkManager timed out:
<warn> Activation (wlan0/wireless): association took too long.
<info> (wlan0): device state change: config -> need-auth (reason 'none') [50 60 0]
<warn> Activation (wlan0/wireless): asking for new secrets
<info> (wlan0): supplicant interface state: authenticating -> disconnected
<warn> Couldn't disconnect supplicant interface: This interface is not connected.
get_secret_flags: assertion `is_secret_prop (setting, secret_name, error)' failed
<info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
<info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
<info> (wlan0): device state change: need-auth -> prepare (reason 'none') [60 40 0]
<info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
<info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
<info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
<info> (wlan0): device state change: prepare -> config (reason 'none') [40 50 0]
<info> Activation (wlan0/wireless): connection 'Verizon DROID2 6182' has security, and secrets exist. No new secrets needed.
<info> Config: added 'ssid' value 'Verizon DROID2 6182'
<info> Config: added 'scan_ssid' value '1'
<info> Config: added 'key_mgmt' value 'WPA-PSK'
<info> Config: added 'auth_alg' value 'OPEN'
<info> Config: added 'psk' value '<omitted>'
<info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
<info> Config: set interface ap_scan to 1
<info> (wlan0): supplicant interface state: disconnected -> scanning
Trying to authenticate with f8:7b:7a:4f:8f:56 (SSID='Verizon DROID2 6182' freq=2437 MHz)
<info> (wlan0): supplicant interface state: scanning -> authenticating
then more "Trying to authenticate", restarts, ending up at 15:01:36,
"asking for new secrets", and warning "Couldn't disconnect supplicant
interface: This interface is not connected." and "No agents were
available for this request." which hints at the (lack of) progress of
the connection/authentication attempt. NetworkManager gives up on
'Verizon DROID2 6182', marking it invalid.
At Dec 18 15:01:43, NetworkManager auto-activates Verizon DROIDX
1980, but it falls to a 'user-requested' disconnect at 15:02:22.
At 15:02:26 NetworkManager auto-activates Verizon DROIDX 1980 again,
until 15:02:40, when "deactivating device (reason
'connection-removed') [38]" happens.
The questions I have at this point are:
Is there any interesting information in lines 7622-7625, and other
short gaps?
Why use "40:fc:89:29:82:fb (SSID='Verizon DROIDX 1980' freq=2462 MHz)"
and "f8:7b:7a:4f:8f:56 (SSID='Verizon DROID2 6182' freq=2437 MHz)"?
Which one is right?
Are you really, really, really sure that you have the WPA
pre-shared-key entered correctly? If it's a hex string, try replacing
[a-f] with [A-F] or the other way.
Waltinator
sudo modprobe iwl3945 dmesg | grep iwl lspci -nn | grep -i wireless
what does this do i dont want to do anything i dont know. Could that help my problem?
– TRAV Dec 18 '11 at 22:41