On Mon, Feb 10, 2014 at 11:31:39AM +1100, James Cameron wrote:
On Sun, Feb 09, 2014 at 07:18:49PM -0500, Kevin Gordon Gmail wrote:
Tp link set as 3g router mode, with usb Sierra wireless usb modem,
set to channel 11, 80211g only, wpa2 pal security. Running stock
f/w.
Terry found that
On Tue, Feb 11, 2014 at 7:08 AM, James Cameron qu...@laptop.org wrote:
On Mon, Feb 10, 2014 at 11:31:39AM +1100, James Cameron wrote:
On Sun, Feb 09, 2014 at 07:18:49PM -0500, Kevin Gordon Gmail wrote:
Tp link set as 3g router mode, with usb Sierra wireless usb modem,
set to channel 11,
Potentially silly question. Once the xo-1 is successfully attached to an AP,
does the mesh beaconing on those three channels on that box then potentially
stop?
I had my twelve xo -1s successfully attach to an AP, and run internet reliably,
concurrently . Powering up a virgin non-ap attached
On Sun, Feb 09, 2014 at 06:33:52PM -0500, Kevin Gordon Gmail wrote:
Once the xo-1 is successfully attached to an AP, does the mesh
beaconing on those three channels on that box then potentially stop?
No.
This can be proven using a wireless device with monitor mode, tcpdump,
and wireshark.
Other notes that may be of interest..Tp link set as 3g router mode, with usb Sierra wireless usb modem, set to channel 11, 80211g only, wpa2 pal security. Running stock f/w.Pretty noisy in my house, could see 7 other ap's, but only one of which was also showing as channel 11.All xo1's at q2f19
On Sun, Feb 09, 2014 at 07:18:49PM -0500, Kevin Gordon Gmail wrote:
Tp link set as 3g router mode, with usb Sierra wireless usb modem,
set to channel 11, 80211g only, wpa2 pal security. Running stock
f/w.
Terry found that channel 1 was the most afflicted. I suspect, but I
haven't checked,
I've seen XO-1s randomly drop off the AP in Paraguay.
I *think* we solved it by disabling 802.11s (the mesh network). This can
be done at boot time by setting a parameter of the libertas kernel module.
Sorry for being vague, it's been a long time ago.
On 02/07/2014 10:10 AM, Adam Holt wrote:
