Hi Thomas
I didn't want to bridge the mesh interface for two reasons:
1. I wanted to minimise any broadcast traffic across the mesh.
2. The mesh is self forming and flexible, and I don't know in advance what
machines will be connected. Nodes exist in a pool of about 200 IP
addresses, and any or all of them can be connected at any one time. To
get routing to work I would have had to run OSPF or RIP2 across the whole
network, but OLSR just handles it through the HNA concept, and the routing
issues just go away. I know is a "mesh" protocol on top of a mesh protocol
but the overhead from OLSR is so low it makes no difference at all.
On 17 January 2013 14:48, Thomas Pedersen <[email protected]> wrote:
> Hi Ross,
>
> On Tue, Jan 15, 2013 at 5:49 PM, Ross Wakelin <[email protected]> wrote:
>>
>> Just to let you know..
>>
>> I have been using 11s and authsae for the last couple of months. I have been
>> manually patching the make files to get a working build from trunk
>> Attitude Adjustment.
>> I use tplink wdr-4300 devices, with the mesh on the 802.11a band, and I can
>> successfully get authenticated meshes set up. Link speed regularly ticks
>> along
>> at about 100Mb/s indicated, with bursts up over 300Mb/s when the load goes
>> up.
>> The mesh is used to support VoIP and video cameras, with a typical mesh
>> having
>> six to eight nodes, with a couple of those being pure, in the middle,
>> relay nodes.
>> The mesh architecture has one internet gateway, and each mesh node
>> supports a class C network behind it, so for example the mesh node
>> 10.3.2.12 has the network 10.2.12.0/24 behind it. Each node is a
>> "mesh gateway" but I couldn't get the o11s gateway/portal stuff to
>> work, so I run OLSR across the top of the mesh to handle the routing.
>
> Cool! Glad to hear someone is actually using this :)
>
> About the mesh gateway: did you try simply bridging the mesh "gateway"
> interface with the exit interface? AFAIK this should work.
>
> Thomas
> _______________________________________________
> Devel mailing list
> [email protected]
> http://lists.open80211s.org/cgi-bin/mailman/listinfo/devel
_______________________________________________
Devel mailing list
[email protected]
http://lists.open80211s.org/cgi-bin/mailman/listinfo/devel
