On Mon, Feb 10, 2014 at 01:41:51PM +1100, James Cameron wrote:
> Ingredients:
>
> 1. several XO-1, with mesh not disabled, with Q2F19,
At least two XO-1 are required.
> Recipe:
>
> 1. record the SSID of the access point, and customise the shell
> script accordingly,
>
> 2. record the MA
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, t
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 fi
Both. Using a tp ml3040I've given the xo's to Mr moody for further testing.
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. T
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 x
I completely agree that we have evidence that some routers (and android
hotspots) just work and that if you can figure out how to make this reliable
and even how to add this capability to other routers that currently fail
that would be the best solution.
However, as a parallel track we should
