[Olsr-dev] Comments regarding the talk of Thomas Clausen at metalab

[Markus Kittenberger]

just for your information,..

since december harald and me, are developing olsr repeater like things,..

it startet with an failed approach of mine to just bridge an wireless adhoc
network with an ethernet,..

in jannuary i had an kernel patch (ipt_TEE), repeating all olsr traffic, and
a patch to the txtinfo (on the main router) plugin to feed the olsr repeater
with routes,..

it was only a proof of concept (using shell sripts on the repeater), but it
worked,..(and showed that it needs some more coding to make it efficient and
stable)

than the project staled a while till harald found the reason for the
bridging problems,.. than we created an working adhoc bridge,..

(in fact just a plain bridge of an adhoc network with an ethernet port, but
using mac and arp nating on the bridge, to get around the limitations of
adhoc mode (only 1 MAC))

since about one month we test them on some foneras (in our olsr mesh in
vienna),.. the performance is now good, and it will work with any routing
dameon/whatever,.. (just the foneras itself are a bit instable, but this
already seems to be better with never kamkaze versions,..)

similar approach will also work on routers with an 2.4 kernel, but needs a
kernel patch, while in kernel 2.6 its jsut a configuration option, but
anyhow it will need a special kernel, resulting in a special firmware
image,..

the bridging solution is more generic, making it suitable for many usages,
but will not provide the olsrd daemon with information of the physical layer
as an olsr repeater might do,.. (but this could be added)

So anyhow, maybe what you want is already available (-;

Markus

On Tue, Aug 19, 2008 at 8:50 AM, Henning Rogge <(spam-protected)> wrote:

> Am Dienstag 19 August 2008 08:43:02 schrieb Hannes Gredler:
> > jumping late into the thread:
> > i may be completely mistaken, but isn't generating 'consistent' routing
> > tables the job of a routing-protocol ? - what is the root-cause problem
> > that you are trying to solve here ?
>
> We are talking about connecting multiple routers over ethernet so they can
> behave as a SINGLE olsr node. This way MPR selection can be done much more
> efficient because you don't need MPRs to forward over the ethernet (it will
> happen transparently).
>
> Of course the routing tables of the ethernet connected devices must be
> synchronized to prevent local routingloop storms.
>
> Henning Rogge
>
> *************************************************
> Diplom Informatiker Henning Rogge
> Forschungsgesellschaft für
> Angewandte Naturwissenschaften e. V. (FGAN)
> Neuenahrer Str. 20, 53343 Wachtberg, Germany
> Tel.: 0049 (0)228 9435-961
> Fax: 0049 (0)228 9435-685
> E-Mail: (spam-protected)
> Web: www.fgan.de
> ************************************************
> Sitz der Gesellschaft: Bonn
> Registergericht: Amtsgericht Bonn VR 2530
> Vorstand: Dr. rer. nat. Ralf Dornhaus (Vors.), Prof. Dr. Joachim Ender
> (Stellv.)
>
> --
> Olsr-dev mailing list
> (spam-protected)
> http://lists.olsr.org/mailman/listinfo/olsr-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.olsr.org/pipermail/olsr-dev/attachments/20080820/8f594b5b/attachment.html>