[wsfii-discuss] Playing around with AirOS + OLSRRe: WasabiNet mesh in St. Louis appeared on local TV news!

[L. Aaron Kaplan]

On Nov 21, 2010, at 5:51 AM, Ben West wrote:

> Hi Christian,
> 
> Thanks for your response.  Your descriptions make sense for operating an OLSR mesh, i.e. no default gateway, and all (except one) nodes operating as Station + Router.
> 
> Besides the NSM5 and Rocket M5 I'm testing with, I also have a pair of Bullet M5s which I could use to test a mesh of 2+ nodes.  Since i only anticipate my own devices (i.e. no users' hardware) participating in the 5GHz meshm, I'm building, I would like to see whether setting all repeater nodes in Bridge mode could work for me.

It will work. But please note that you are supporting a single layer 2 broadcast domain in this case.
This might be OK for you (I know ISPs where *everything* is bridged) - as long as your links have a high capacity and they are stable. In my experience things can get a bit tasty if you have too many broadcast storms.

In addition here is something which might be helpful for you: the new etx_ffeth metric:
You might want to tune your links with the  mode "mesh" or mode "ethernet" parameters and the etx_ffeth metric in olsrd.conf.
See files/olsrd.conf.default.lq for a good description.
The etx_ffeth metric is new in 0.6* and basically treats wired links as links with ETX metric 0.1 . Which makes them the prefered routes . So the idea is to stay on the cable as long as you can.
Note that etx_ffeth is not compatible with the previous etx_* metrics.

Best,
a.



> 
> On Fri, Nov 19, 2010 at 9:12 PM, equinox <equinox at chaos-at-home.org> wrote:
> Hi,
> 
> Ben West schrieb:
> [..]
> > I have the modded AirOS images running on a NSM5 and a Rocket M5.  Both
> > devices see each using standard ubnt functionality.
> >
> that was the plan ;).
> 
> > A question, at high level: how does the OLSR patch interact with the
> > existing modes in AIrOS for LAN and WLAN  routing?
> >
> not really, the only change i made is to allow to set no default
> gateway. By default the web interface enforces you to set a default
> gateway. But of course this can interfere with dynamic routing.
> 
> > E.g. for the "Network" tab, there is Bridge, Router, SOHO Router, and
> > for the "Wireless" tab there is Station and Access Point.
> >
> all of these should be basically the same. For olsr you normally would
> use router mode on alle nodes, AP mode on one node and Station at all
> the others.
> 
> > The screenshots from the wiki show one device (the Airgrid) as
> > Router/Access Point.  Are all other nodes set to the same modes, or do
> > some nodes need to be set at Stations/Bridge?
> 
> As with normal wireless setup there is one node configured as access
> point and all the others are configured as station. Using router mode
> (not bridge) is preferred in most cases (on both sides). But setting it
> to bridge is also supported because this may be usefull at times.
> Also you have to consider that unfortunately there is no ad-hoc mode in
> this version of the firmware. The main reason for that is that the
> kernel used by Airos is quite old (2.6.16 i think) and a quite new
> version of the driver would be needed to have stable ad-hoc mode. Also
> in our network we don't need ad-hoc mode by the nodes running AirOS. We
> use OpenWRT on Ubiquity hardware when we need ad-hoc.
> 
> regards,
>  christian
> 
> 
> _______________________________________________
> wsfii-discuss mailing list
> wsfii-discuss at lists.okfn.org
> http://lists.okfn.org/mailman/listinfo/wsfii-discuss
> 
> 
> 
> 
> -- 
> Ben West
> westbywest at gmail.com
> _______________________________________________
> wsfii-discuss mailing list
> wsfii-discuss at lists.okfn.org
> http://lists.okfn.org/mailman/listinfo/wsfii-discuss

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.okfn.org/pipermail/wsfii-discuss/attachments/20101123/d8357129/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: PGP.sig
Type: application/pgp-signature
Size: 194 bytes
Desc: This is a digitally signed message part
URL: <http://lists.okfn.org/pipermail/wsfii-discuss/attachments/20101123/d8357129/attachment.sig>