[Olsr-dev] SOURCE_IP_ROUTES patch and router-id

Henning Rogge (spam-protected)
Thu Jan 28 14:38:55 CET 2010

On Thu January 28 2010 14:32:41 Jernej Kos wrote:
> Hi,
> I am looking into the SOURCE_IP_ROUTES in 0.5.6-r8 and see that first
> interface address is used as router ID. As this might change if an
> interface goes down (but router ID should never change) how should this
> be handled ?
> Adding a loopback interface would not work as olsrd currently ignores
> all loopback interfaces (if I am reading the code right) and as such
> would not use it for its primary IP. Is there a way to fix the router ID
> that olsrd uses so it stays the same no matter what interfaces are up or
> down ?
You could just configure this IP as an additional static loopback interface.
> Or a better question - is this doable with stock 0.5.6-r8 or do I have
> to make a patch for it ? In the latter case, what is the best part where
> this should be done ? I see that source-ip is set in
> linux/kernel_routes.c and there is also a comment about this becoming a
> configuration option in later releases. Adding such information to the
> config file seems a trivial modification, so is this the best way to do
> it ?

It might become a config option in the next OLSR revision... if yes OLSR will 
create a lo:olsr loopback interface with the IP to be sure it has an receiver 
for incoming traffic (the development OLSR already do this).

Henning Rogge
Diplom-Informatiker Henning Rogge , Fraunhofer-Institut für
Kommunikation, Informationsverarbeitung und Ergonomie FKIE
Kommunikationssysteme (KOM)
Neuenahrer Straße 20, 53343 Wachtberg, Germany
Telefon +49 228 9435-263,   Fax +49 228 9435 685
mailto:(spam-protected) http://www.fkie.fraunhofer.de
GPG: E1C6 0914 490B 3909 D944 F80D 4487 C67C 55EC CFE0
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.olsr.org/pipermail/olsr-dev/attachments/20100128/4e5936bc/attachment.sig>

More information about the Olsr-dev mailing list