[Olsr-dev] local broadcast/custom message types

Henning Rogge (spam-protected)
Thu Feb 21 08:53:31 CET 2013

On 02/21/2013 08:49 AM, Lotte Steenbrink wrote:
> As far as I/we understood it, the TTL that olsr routers (so in our
> case the nexus 7s) will decrement is the one in the olsr-header. If
> they get a packet that does not have this header, they will forward
> it to whatever hop they consider appropriate, flooding the subnet
> that forms our MANET with these broadcasts (and only the gateway node
> would actually decrement the IP TTL). So based on this assumption we
> figured it would be a better idea to make use of the already
> implemented header creation rather than build these packets from
> scratch... Is this assumption correct?

Similar, but not completely correct.

Have a look at the OLSR RFC:

As you can see, every OLSR message (within the packet container) has a 
number of mandatory fields. You cannot have OLSR messages without them.

One of the fields is the TTL, the other one is the hopcount.

If you set the TTL of an OLSR message to 1 and the hopcount to 0, it 
will not be forwarded by the receivers (the same is done to the HELLO 

Henning Rogge

Diplom-Informatiker Henning Rogge , Fraunhofer-Institut für
Kommunikation, Informationsverarbeitung und Ergonomie FKIE
Kommunikationssysteme (KOM)
Fraunhofer Straße 20, 53343 Wachtberg, Germany
Telefon +49 228 9435-961,   Fax +49 228 9435 685
mailto:(spam-protected) http://www.fkie.fraunhofer.de

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 6169 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://lists.olsr.org/pipermail/olsr-dev/attachments/20130221/6f51418f/attachment.bin>

More information about the Olsr-dev mailing list