Re: [ipw3945-devel] 2.6.29-wl-36116-g6a982a0: connection loss

[Johannes Berg <johannes@sipsolutions.net>]

[-- Attachment #1: Type: text/plain, Size: 3552 bytes --]

On Tue, 2009-03-31 at 10:15 -0700, reinette chatre wrote:
> Adding Kalle and the linux-wireless list ... if anybody responds who is
> not member of ipw3945 ml, please consider removing that ml from cc list.
> If anybody on ipw3945 are interested in this, please follow thread on
> linux-wireless.

> > [ 3009.365039] wlan0: direct probe to AP 00:14:6c:67:9c:32 try 1
> > [ 3009.368315] wlan0 direct probe responded
> > [ 3009.368321] wlan0: authenticate with AP 00:14:6c:67:9c:32
> > [ 3009.370298] wlan0: authenticated
> > [ 3009.370304] wlan0: associate with AP 00:14:6c:67:9c:32
> > [ 3009.568063] wlan0: associate with AP 00:14:6c:67:9c:32
> > [ 3009.575107] wlan0: RX AssocResp from 00:14:6c:67:9c:32 (capab=0x601 status=0 aid=10)
> > [ 3009.575114] wlan0: associated

There the connection is already not entirely reliable -- needed two
assoc messages to get through, despite retries.

> > [ 3009.581276] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
> > [ 3020.000031] wlan0: no IPv6 routers present
> > [ 3151.295473] wlan0: beacon loss from AP 00:14:6c:67:9c:32 - sending probe request
> > [ 4191.742593] wlan0: beacon loss from AP 00:14:6c:67:9c:32 - sending probe request
> > [ 4193.740066] wlan0: no probe response from AP 00:14:6c:67:9c:32 - disassociating

Here you have (look at the times!) the probe request once getting an
answer, and once not.

> > [ 4321.376160] wlan0: deauthenticated (Reason: 7)
> > [ 7337.805893] wlan0: direct probe to AP 00:14:6c:67:9c:32 try 1
> > [ 7337.810976] wlan0 direct probe responded
> > [ 7337.810983] wlan0: authenticate with AP 00:14:6c:67:9c:32
> > [ 7338.008060] wlan0: authenticate with AP 00:14:6c:67:9c:32
> > [ 7338.010087] wlan0: authenticated
> > [ 7338.010093] wlan0: associate with AP 00:14:6c:67:9c:32
> > [ 7338.018590] wlan0: RX ReassocResp from 00:14:6c:67:9c:32 (capab=0x201 status=0 aid=13)
> > [ 7338.018597] wlan0: associated

Here auth needs two tries.

> > [ 7572.146385] wlan0: beacon loss from AP 00:14:6c:67:9c:32 - sending probe request
> > [ 7702.189368] wlan0: beacon loss from AP 00:14:6c:67:9c:32 - sending probe request
> > [ 7962.173161] wlan0: beacon loss from AP 00:14:6c:67:9c:32 - sending probe request
> > [ 8092.216232] wlan0: beacon loss from AP 00:14:6c:67:9c:32 - sending probe request
> > [ 8094.216137] wlan0: no probe response from AP 00:14:6c:67:9c:32 - disassociating

Here you have three probe requests over quite some time sometimes
getting answers and at the last time not.

> > [ 8221.952208] wlan0: deauthenticated (Reason: 7)
> > [33012.904311] wlan0: direct probe to AP 00:14:6c:67:9c:32 try 1
> > [33012.907527] wlan0 direct probe responded
> > [33012.907533] wlan0: authenticate with AP 00:14:6c:67:9c:32
> > [33013.104059] wlan0: authenticate with AP 00:14:6c:67:9c:32
> > [33013.106102] wlan0: authenticated
> > [33013.106107] wlan0: associate with AP 00:14:6c:67:9c:32
> > [33013.114796] wlan0: RX ReassocResp from 00:14:6c:67:9c:32 (capab=0x201 status=0 aid=14)
> > [33013.114802] wlan0: associated
> > [33053.635621] wlan0: beacon loss from AP 00:14:6c:67:9c:32 - sending probe request
> > [33183.267415] wlan0: beacon loss from AP 00:14:6c:67:9c:32 - sending probe request

etc.

> Perhaps the new beacon filtering work [1] is changing more than it
> intended?

I think it only changed the messages here. Previously, that message
simply wouldn't have been there, instead you'd only have seen the "No
ProbeResp from current AP - assume out of range" thing.

johannes

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]