connection to wireless AP was unreliable in room having multiple XOs
|Reported by:||mikus||Owned by:||riccardo|
|Component:||wireless||Version:||Development build as of this date|
|Keywords:||cjbfor9.1.0||Cc:||mikus@…, dsd, carrano, ashish|
|Deployments affected:||Action Needed:||diagnose|
G1G1. 756, with libertas updated to 110.22.p18. Instead of "locking in" on a wireless router in the room, my XO seemed to "hunt" around after I had clicked on that AP's icon in Neighborhood view -- and often my XO decided to give up on the AP, and run only mesh.
Sometimes, when the XO did change to 'connected' for the AP, when I tried using Browse it sooner or later told me a name could not be found (due in fact to the connection to the outside no longer existing).
I experienced unreliability with the AP at more than one XO. What was particularly confusing was that while the wireless router was set on Channel 6, I saw the palette entry for the "wireless AP" icon in one XO's Frame saying Channel 1, whereas I saw the palette entry for the "wireless AP" icon in another XO's Frame saying Channel 11. [Neither of these "so called" connections actually worked.]
[I was wondering whether the presence of more XOs in the room, some of them trying to transmit/listen on mesh channel 1, managed to confuse my XO.]
Am enclosing an olpc-log dump taken shortly after reboot, when my XO did *not* manage to connect to the AP.
Change History (8)
Changed 9 years ago by mikus
comment:1 Changed 9 years ago by mstone
- Action Needed changed from never set to diagnose
- Cc dsd carrano added
- Component changed from not assigned to wireless
- Owner set to dwmw2
comment:2 follow-ups: ↓ 3 ↓ 5 Changed 9 years ago by kimquirk
- Milestone changed from Not Triaged to 8.2.1
- Owner changed from dwmw2 to riccardo
comment:6 Changed 8 years ago by mstone-xmlrpc
- Keywords cjbfor9.1.0 added
- Milestone changed from 8.2.1 to 9.1.0