[ath9k-devel] 2.6.28.1 with compat-wireless-2009-01-19 also gives No ProbeResp

[ath9k-devel] 2.6.28.1 with compat-wireless-2009-01-19 also gives No ProbeResp

[Joseph Cheek]

Hi Luis,

I upgraded wireless to compat-wireless-2009-01-19 and still get No
ProbeResp.  I'll change IEEE80211_MONITORING_INTERVAL to 100 * HZ and at
least I should be as good as I was before (hopefully).  Perhaps having
such a large monitoring timeout gives the driver a chance to receive a
beacon when transmission halts?  unsure.

as you can see, i got 69 seconds of connectivity before No ProbeResp.

Jan 21 00:16:41 harrisburg ath9k: 0.1

Jan 21 00:16:41 harrisburg ath9k 0000:00:07.0: PCI INT A -> Link[LNKC]
-> GSI 10 (level, low) -> IRQ 10

Jan 21 00:16:42 harrisburg phy1: Selected rate control algorithm
'ath9k_rate_control'

Jan 21 00:16:42 harrisburg Registered led device: ath9k-phy1:radio

Jan 21 00:16:42 harrisburg Registered led device: ath9k-phy1:assoc

Jan 21 00:16:42 harrisburg Registered led device: ath9k-phy1:tx

Jan 21 00:16:42 harrisburg Registered led device: ath9k-phy1:rx

Jan 21 00:16:42 harrisburg phy1: Atheros AR5416 MAC/BB Rev:2 AR2133 RF
Rev:81: mem=0xd8da0000, irq=10

Jan 21 00:16:42 harrisburg ADDRCONF(NETDEV_UP): wlan0: link is not ready

Jan 21 00:16:42 harrisburg wlan0: authenticate with AP d6290ce8

Jan 21 00:16:42 harrisburg wlan0: authenticated

Jan 21 00:16:42 harrisburg wlan0: associate with AP d6290ce8

Jan 21 00:16:42 harrisburg wlan0: RX AssocResp from d417c02a
(capab=0x421 status=0 aid=2)

Jan 21 00:16:42 harrisburg wlan0: associated

Jan 21 00:16:42 harrisburg ADDRCONF(NETDEV_CHANGE): wlan0: link becomes
ready
Jan 21 00:16:43 harrisburg dhcpcd[5443]: exiting

Jan 21 00:16:43 harrisburg dhcpcd[5445]: wlan0: dhcpcd 3.2.1 starting

Jan 21 00:16:43 harrisburg dhcpcd[5445]: wlan0: hardware address =
00:21:91:fa:ea:b8

Jan 21 00:16:43 harrisburg dhcpcd[5445]: wlan0: DUID =
00:01:00:01:0e:e0:b2:b7:00:0c:41:62:e6:4a

Jan 21 00:16:43 harrisburg dhcpcd[5445]: wlan0: broadcasting for a lease

Jan 21 00:16:44 harrisburg dhcpcd[5445]: wlan0: offered 192.168.1.194
from 192.168.1.1

Jan 21 00:16:44 harrisburg dhcpcd[5445]: wlan0: checking 192.168.1.194
is available on attached networks

Jan 21 00:16:45 harrisburg dhcpcd[5445]: wlan0: leased 192.168.1.194 for
86400 seconds

Jan 21 00:16:45 harrisburg dhcpcd[5445]: wlan0: adding IP address
192.168.1.194/24

Jan 21 00:16:45 harrisburg dhcpcd[5445]: wlan0: adding route to
192.168.1.0/24 metric 2004

Jan 21 00:16:45 harrisburg dhcpcd[5445]: wlan0: removing route to
192.168.1.0/24 metric 0

Jan 21 00:16:45 harrisburg dhcpcd[5445]: wlan0: adding default route via
192.168.1.1 metric 2004

Jan 21 00:16:45 harrisburg dhcpcd[5445]: wlan0: adding route to
169.254.0.0/16 metric 2004

Jan 21 00:16:45 harrisburg dhcpcd[5445]: wlan0: exiting

Jan 21 00:16:47 harrisburg sshd[5571]: Server listening on 0.0.0.0 port
22.
Jan 21 00:16:47 harrisburg sshd[5571]: Server listening on :: port 22.

Jan 21 00:16:53 harrisburg wlan0: no IPv6 routers present

Jan 21 00:17:02 harrisburg login[5068]: pam_unix(login:session): session
closed for user root

Jan 21 00:17:50 harrisburg wlan0: No ProbeResp from current AP d6290ce8
- assume out of range

thanks!

Joseph Cheek
_______________________________________________
ath9k-devel mailing list
ath9k-devel at lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel