[Commotion-discuss] Picostation mesh with APs

[Adam Longwill]

As Josh stated, I too have noticed this behavior and I chalk it up to
radio-sharing between the AP interface and the mesh interface. But I'm not
certain of that. The nodes that have done this most were a group of 4
Rockets meshing over ethernet over a Ubiquiti PoE switch. I have not really
noticed the problem with our omni-directional nodes along the one street
we've installed on. Of course, I am unable to turn off either of those
Interfaces to test because they're constantly in use!

I am afraid what Josh is describing is just what is to be expected out of a
mesh network. But please correct me if I am wrong.

Adam

On Tue, Mar 3, 2015 at 9:02 AM, Josh Harle <josh.harle at gmail.com> wrote:

> Hi All,
>
> I've been installing 20 picostation M2HPs in a town to try to set up a
> mesh network, partially based on the "Building Pop-up Mesh Networks
> <https://commotionwireless.net/blog/2013/10/30/building-popup-mesh-networks/>"
> article.
>
> I've found that when I have a handful of mesh nodes, if more than just one
> of them has an access point interface enabled, the ETX goes from about 1 to
> somewhere between 5 and 7!
>
> I've been talking to Adam Longwill about this, who has found similar
> behaviour.  I don't understand how to mitigate this.  Isn't it expected
> behaviour to have all nodes as APs too?  How do I get area coverage with
> WiFi client access?
>
> It seems to impact performance so much to have more than one AP turned on
> in the network that the only thing I can think of is to have one
> Picostation for mesh, connected to one souly for AP on another channel.
>
> I would be hugely greatful for advice on this: I'm in a remote Aussie town
> for just a couple of days trying to troubleshoot this.
>
> Kind Regards,
>
> Dr Josh Harle
> ____________________
> http://joshharle.com
> http://tacticalspace.org
> ph: +61 (0)491 155 985
>
> _______________________________________________
> Commotion-discuss mailing list
> Commotion-discuss at lists.chambana.net
> https://lists.chambana.net/mailman/listinfo/commotion-discuss
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.chambana.net/pipermail/commotion-discuss/attachments/20150303/d91e5a38/attachment.html>