[Olsr-dev] Use Case for rttable_tunnel

[Sven-Ola Tuecke]

Hey,

the (new) rttable_tunnel parameter as well as the following defaults will 
break some features:

#define DEF_RTTABLE_DEFAULT  112
#define DEF_RTTABLE_TUNNEL   113

Obviously, the tunnel-default-route should not be executed if olsrd sets a 
standard default route. I presume, the author has some "ip rules add" in mind 
otherwise it's useless...?

Where I expect conflicts: at a given time only ONE default route will be used 
by a particular station/user. I use that rttable_default setting for users 
which will join the mesh but do not want to share their inet connection (aka. 
my-Internet-for-me-alone). He/she will (of course) not block inet traffic 
generated by others. As a second use case, there is the "dyn_gw_plain" stuff. 
Which (if the gateway is unusable) shifts the 254-default route in a 
background table only valid for the current device. This is necessary, 
otherwise you cannot determine if that gateway will come up again.

Can someone shed some light on this setting? (BTW: there will be no 
IPv6-ipip-tunnel without backporting some 2.6.x code to linux-2.4)

// Sven-Ola