All of lore.kernel.org
 help / color / mirror / Atom feed
From: Brian <bnc@astronomicalresearchaustralia.org>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] Link drops out
Date: Sat, 29 Nov 2008 22:34:59 +1000	[thread overview]
Message-ID: <493136F3.9060506@astronomicalresearchaustralia.org> (raw)
In-Reply-To: <492A5FC2.4050202@astronomicalresearchaustralia.org>

All,
This has happened twice now and I am not sure what to collect to get
more info for you.

1) I fire up a wireless link from this machine to the router.
This is running 2.6.28.rc6.

Nov 29 10:08:41 L2 SuSEfirewall2: Error: iptables-batch failed,
re-running using iptables
Nov 29 10:08:41 L2 SuSEfirewall2: Firewall rules successfully set
Nov 29 10:08:46 L2 kernel: [   66.931665] TKIP decrypt: data(len=56) 00
20 01 a0 00 00 00 00 aa aa 03 00 00 00 08 06 00 01 08 00 06 04 00 01 00
1b 11 e9 b1 88 c0 a8 01 05 00 00 00 00 00 00 c0 a8 01 01 82 c8 9c 22 09
19 a8 11 df a5 57 23


2) When I first fire it up the link is extremely quick but then seems to
get progressively slower.

3) It takes a few hours but eventually the link drops.
This is what dmesg says.
00 00 00 00 c0 a8 01 01 90 58 70 ed e9 e1 db a1 af bb 19 5a
Nov 29 19:08:38 L2 kernel: [32458.714789] TKIP decrypt: iv16=0002
iv32=00000000
Nov 29 19:08:39 L2 kernel: [32459.714665] TKIP decrypt: data(len=56) 00
20 03 60 00 00 00 00 aa aa 03 00 00 00 08 06 00 01 08 00 06 04 00 01 00
1b 11 e9 b1 88 c0 a8 01 05 00 00 00 00 00 00 c0 a8 01 01 90 58 70 ed e9
e1 db a1 af bb 19 5a
Nov 29 19:08:39 L2 kernel: [32459.714741] TKIP decrypt: iv16=0003
iv32=00000000
Nov 29 19:08:42 L2 kernel: [32462.130305] wlan0: deauthenticated (Reason: 9)
Nov 29 19:08:43 L2 kernel: [32463.130065] wlan0: direct probe to AP
00:1c:f0:fb:6d:92 try 1
Nov 29 19:08:43 L2 kernel: [32463.134532] wlan0 direct probe responded
Nov 29 19:08:43 L2 kernel: [32463.134543] wlan0: authenticate with AP
00:1c:f0:fb:6d:92
Nov 29 19:08:43 L2 kernel: [32463.136485] wlan0: authenticated
Nov 29 19:08:43 L2 kernel: [32463.136496] wlan0: associate with AP
00:1c:f0:fb:6d:92
Nov 29 19:08:43 L2 kernel: [32463.139944] wlan0: RX ReassocResp from
00:1c:f0:fb:6d:92 (capab=0x431 status=0 aid=2)
Nov 29 19:08:43 L2 kernel: [32463.139954] wlan0: associated
[32459.714665] TKIP decrypt: data(len=56) 00 20 03 60 00 00 00 00 aa aa
03 00 00 00 08 06 00 01 08 00 06 04 00 01 00 1b 11 e9 b1 88 c0 a8 01 05
00 00 00 00 00 00 c0 a8 01 01 90 58 70 ed e9 e1 db a1 af bb 19 5a


So the link stayed up almost exactly 9 hours.


4) Both times is has happened after I have started another machine with
a wireless connection. Not sure this is relevant though.


5) I have tried restarting wlan0, wpa_suppicant, network restart, but
the only way I can get going again is to reboot.

6) I have the -dd flags turned on when wpa_supplicant starts and it goes
to a file. This shows(see below) that the problem appears to be the fact
that the ssid field is blank. Eventually both my APs get added to a
black list, then taken out and the cycle starts again.
I do not understand why the ssid comes up blank.
Where do you look for the contents of the blacklist?

Thanks,
Brian

Wireless event: cmd=0x8b19 len=8
Received 438 bytes of scan results (1 BSSes)
Scan results: 1
Selecting BSS from priority group 0
Try to find WPA-enabled AP
0: 00:1c:f0:fb:6d:92 ssid='' wpa_ie_len=28 rsn_ie_len=0 caps=0x11
   skip - SSID mismatch
Try to find non-WPA AP
0: 00:1c:f0:fb:6d:92 ssid='' wpa_ie_len=28 rsn_ie_len=0 caps=0x11
   skip - SSID mismatch
No APs found - clear blacklist and try again
Removed BSSID 00:00:00:00:00:00 from blacklist (clear)
Removed BSSID 00:1c:f0:fb:6d:92 from blacklist (clear)
Selecting BSS from priority group 0
Try to find WPA-enabled AP
0: 00:1c:f0:fb:6d:92 ssid='' wpa_ie_len=28 rsn_ie_len=0 caps=0x11
   skip - SSID mismatch
Try to find non-WPA AP
0: 00:1c:f0:fb:6d:92 ssid='' wpa_ie_len=28 rsn_ie_len=0 caps=0x11
   skip - SSID mismatch
No suitable AP found.
Setting scan request: 5 sec 0 usec
State: DISCONNECTED -> SCANNING
Starting AP scan (broadcast SSID)
Scan requested (ret=0) - scan timeout 30 seconds
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
Wireless event: cmd=0x8b19 len=8
Received 438 bytes of scan results (1 BSSes)
Scan results: 1
Selecting BSS from priority group 0
Try to find WPA-enabled AP
0: 00:1c:f0:fb:6d:92 ssid='' wpa_ie_len=28 rsn_ie_len=0 caps=0x11
   skip - SSID mismatch
Try to find non-WPA AP
0: 00:1c:f0:fb:6d:92 ssid='' wpa_ie_len=28 rsn_ie_len=0 caps=0x11
   skip - SSID mismatch
No suitable AP found.
Setting scan request: 5 sec 0 usec
CTRL-EVENT-TERMINATING - signal 2 received
Removing interface wlan0
State: SCANNING -> DISCONNECTED
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
No keys have been configured - skip key clearing
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
wpa_driver_wext_set_wpa
wpa_driver_wext_set_drop_unencrypted
wpa_driver_wext_set_countermeasures
No keys have been configured - skip key clearing
Control interface directory not empty - leaving it behind
Cancelling scan request
Cancelling authentication timeout
WEXT: Operstate: linkmode=0, operstate=6

  reply	other threads:[~2008-11-29 12:34 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-19 17:41 [ath9k-devel] Constant AP dropout Tyler W. Mills
2008-11-19 17:54 ` Jouni Malinen
2008-11-19 17:58   ` Tyler W. Mills
2008-11-19 18:38     ` Tyler W. Mills
2008-11-19 22:34     ` [ath9k-devel] Constant AP dropout -LINKS Brian
2008-11-20  3:52       ` Luis R. Rodriguez
2008-11-21  0:04         ` [ath9k-devel] It Works! Brian
2008-11-21  1:39           ` Sujith
2008-11-21  4:52             ` [ath9k-devel] Issues Brian
2008-11-21  6:16               ` Sujith
2008-11-22  3:57                 ` Brian
2008-11-24  8:03                 ` [ath9k-devel] 2.6.28-rc6-wl Brian
2008-11-29 12:34                   ` Brian [this message]
2008-11-29 14:59                   ` [ath9k-devel] 2.6.28-rc6-wl update Brian
2008-11-30 13:13                     ` [ath9k-devel] 2.6.28-rc6-wl update2 Brian

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=493136F3.9060506@astronomicalresearchaustralia.org \
    --to=bnc@astronomicalresearchaustralia.org \
    --cc=ath9k-devel@lists.ath9k.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.