B.a.t.m.a.n.

[Monthadar Al Jaberi]

On Mon, May 14, 2012 at 3:02 PM, Ivo Vachkov <ivo.vachkov at gmail.com> wrote:
> Hello all,
>
> On Mon, May 14, 2012 at 1:52 PM, Monthadar Al Jaberi <monthadar at gmail.com>
> wrote:
>>
>> On Sun, May 13, 2012 at 2:49 PM, Ivan Voras <ivoras at gmail.com> wrote:
>> > On 13 May 2012 06:46, Ivo Vachkov <ivo.vachkov at gmail.com> wrote:
>> >> Please define "working"? Porting? Kernel-level implementation?
>> >> BSD-licensed
>> >> one?
>> >
>> > I'm just throwing the idea out, in case it catches the eye of someone
>> > who's looking for an interesting project. In the ideal world, I'd say
>> > BSD-licensed reimplementation, but I certainly won't get picky.
>> >
>> > It does have some documentation (e.g.
>> > http://tools.ietf.org/html/draft-wunderlich-openmesh-manet-routing-00
>> > , http://www.open-mesh.org/wiki/batman-adv/Doc-overview).
>
>
> Since it's not standardized, isn't it more logical to proceed with either
> user-space implementation or kernel implementation of something that has RFC
> assigned to the name (just asking, no troll/flame here)? Other than that I
> have some experience with BMX, Babel and OLSR. Also, i'm personally not
> convinced that kernel level implementation is the most appropriate choice
> for routing protocol (still i may be wrong).
>
>>
>> >> Are there any reasons to choose B.A.T.M.A.N. instead of bmx or babel?
>> >> ... or
>> >> OLSR? ... or HSLS?
>> >
>> > I've seen BATMAN work at a local Linux club meeting, and I was pretty
>> > much impressed by how easy it is to setup. I don't know about the
>> > other protocols you listed, but BATMAN is in the stock Linux kernel,
>> > making it a practical choice. I might be wrong but it seems to me that
>> > it, contrasted to 802.11s, requires no special support from the wifi
>> > driver side, making it easier to implement. Other than that, no, I
>
>
> As mentioned already 802.11s is link-layer technology (that from our
> experiments and research seems to be limited to some 30 devices), in
> contrast those are network layer (L3) protocols that operate on top of IP.
>
>>
>>
>>
>> I think it a better version of the Optimized Link State Routing
>> Protocol (OLSR) which is an IP routing algoritm, 802.11s is link level
>> routing, which needs a wifi driver that permits changing the mac
>> address.
>>
>> But there is no standard for it I think.
>
>
> OLSR: http://www.ietf.org/rfc/rfc3626.txt

Sorry, I meant BATMAN

>
>>
>> > know far too little about all of them to have a preference.
>> > _______________________________________________
>> > freebsd-net at freebsd.org mailing list
>> > http://lists.freebsd.org/mailman/listinfo/freebsd-net
>> > To unsubscribe, send any mail to "freebsd-net-unsubscribe at freebsd.org"
>>
>>
>>
>> --
>> Monthadar Al Jaberi
>
>
>
>
> --
> Ivo Vachkov



-- 
Monthadar Al Jaberi