Opened 6 years ago

Last modified 6 years ago

#8189 new defect

connection to wireless AP was unreliable in room having multiple XOs

Reported by: mikus Owned by: riccardo
Priority: high Milestone: 9.1.0-cancelled
Component: wireless Version: Development build as of this date
Keywords: cjbfor9.1.0 Cc: mikus@…, dsd, carrano, ashish
Blocked By: Blocking:
Deployments affected: Action Needed: diagnose
Verified: no

Description

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.

Attachments (1)

logs.CSN74804910.2008-08-27.15-41-54.tar.bz2 (47.8 KB) - added by mikus 6 years ago.
log taken after XO gave up trying to connect to wireless AP

Download all attachments as: .zip

Change History (7)

Changed 6 years ago by mikus

log taken after XO gave up trying to connect to wireless AP

comment:1 Changed 6 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

Thanks for the nice report, Mikus!

comment:2 follow-ups: Changed 6 years ago by kimquirk

  • Milestone changed from Not Triaged to 8.2.1
  • Owner changed from dwmw2 to riccardo

How many XOs? We know that we have trouble with any RF transmission if there are 10 or more XOs in a closed space. If there are lots of other RF devices, it might be difficult to connect at less than 10.

We connected 32 laptops to an AP and school server at 1CC; and we can get only 10 XOs in simple mesh mode.

comment:3 in reply to: ↑ 2 Changed 6 years ago by mikus

Replying to kimquirk:

How many XOs? We know that we have trouble with any RF transmission if there are 10 or more XOs in a closed space.

There usually were four or less active XOs in the room. HOWEVER, this was a rf-rich environment -- at all times there were more than a dozen APs showing in Neighborhood view. [Although there were two or so APs in the room, which we thought would be given preference because of signal strength, sometimes after being booted an XO would ask for a key -- meaning it was trying "automatically" to connect to an outside-of-the-room AP.]

The frustrating thing was that when I would click in Neighborhood View on the circle of the channel-6 non-locked AP in the room, that circle would blink for a while, then go back to not trying to connect. I ended up connecting my XO via wired ethernet - because that was more reliable.

comment:4 Changed 6 years ago by ashish

  • Cc ashish added

comment:5 in reply to: ↑ 2 Changed 6 years ago by riccardo

Replying to kimquirk:

I'm quite sure I (riccardo lucchese) shouldn't be the owner of this bug ;P
Perhaps Ricardo Carrano ?

Recently I became the owner of more wireless related bugs; please let me know whom I should reassign them.

comment:6 Changed 6 years ago by mstone-xmlrpc

  • Keywords cjbfor9.1.0 added
  • Milestone changed from 8.2.1 to 9.1.0

Pushing out to 9.1.0, per edmcnierney's request.

Note: See TracTickets for help on using tickets.