Laptop not scanning for mesh; can't connect to the XO on an AP
|Reported by:||kimquirk||Owned by:||dcbw|
|Deployments affected:||Action Needed:|
I connected one XO to my local WEP enabled AP. It is sitting on channel 6. When I look at iwconfig, the mesh is also sitting on channel 6.
Then when I boot up a second XO, it sits on mesh channel 1 and doesn't seem to scan around for that mesh that would let it connect to XO1 with the AP. I seems like it is connect with a mesh on channel 1 even though there is nothing else on channel 1. Either it doesn't see the mesh advertisements on channel 6, or it isn't scanning.
I think it isn't scanning because I typed iwconfig many times over the course of a few minutes and it is always on channel 1. When I did that in the past, I could see it sit on channel 2, then channel 3, etc. This took a long time to get through all the channels, but it would eventually connect to my XO on the AP of channel 6. So I think this is a regression bug.
Change History (7)
comment:4 Changed 8 years ago by kimquirk
- Cc zack jg added
- Milestone changed from Untriaged to Trial-3
comment:6 Changed 7 years ago by kimquirk
- Resolution set to wontfix
- Status changed from new to closed
- Verified set