[Babel-users] switching cerowrt to quagga-babeld issues

L. Aaron Kaplan aaron at lo-res.org
Mon Jul 2 12:16:27 EDT 2012


On Jul 2, 2012, at 5:36 PM, Dave Taht wrote:

> How goeth ipv6?
> 
>> 
>> The project may get more options, if we drive the prototype towards a finished deliverable.
> 
> I am very enthusiastic about babel's new authenticated mesh routing!
> 
> It is also my opinion that without a decent drop and packet mixing
> strategy that mesh networks will perform badly under load. I'm hoping
> that fq_codel does well, although it seems very likely that an
> aggregation aware and fq_codel-like strategy needs to move into the
> mac80211 layer, which is perhaps years worth of work.
Or have better cross-layer communication - see below....
> 
> What would a deliverable look like? What would interest people enough
> to get some good data, papers written, progress made, more
> users/developers and cash in the door?


I would like to point you towards a nice feature that Henning is currently implementing: DLEP - a (mostly routing protocol independent) framework for communicating settings and metrics between a radio and a routing daemon.
See https://datatracker.ietf.org/doc/draft-ietf-manet-dlep/

Abstract


   When routing devices rely on modems to effect communications over 
   wireless links, they need timely and accurate knowledge of the 
   characteristics of the link (speed, state, etc.) in order to make 
   forwarding decisions. In mobile or other environments where these 
   characteristics change frequently, manual configurations or the  
   inference of state through routing or transport protocols does not 
   allow the router to make the best decisions. A bidirectional, event-
   driven communication channel between the router and the modem is 
   necessary.



More info and code samples on the olsr.org git repo. I'd like to also encourage Babel coders to take a look at it and collectively improve this.
It will be - as Dave already mentioned - anyway a hard problem to have this working for many radios in a standardized way, so it would really be helpful if different mesh developers for once could work *together* on some general feature which improves everybody's metrics.


Aaron.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 203 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <https://lists.bufferbloat.net/pipermail/bloat-devel/attachments/20120702/562caafa/attachment.pgp>


More information about the Bloat-devel mailing list