[Olsr-users] Default-Route Problem / Feature Request

[Michael Rack]

When will it be able to jail default-routes, network-routes and 
host-routes into a seperate linux-routing-tables?

Currently all routes will added to the main-routing-table. I need to 
seperate all route-classes to avoid problems with local private connections.

OLD: ip route add default via y.y.y.y table main
NEW: ip route add default via y.y.y.y table 200 (200 is a variable 
"default", defined in config-file)

OLD: ip route add 172.16.0.2 dev eth1 table main
NEW: ip route add 172.16.0.2 dev eth1 table 100 (100 is a variable 
"host", defined in config-file)

OLD: ip route add 172.16.4.0/22 via 172.16.0.2 table main
NEW: ip route add 172.16.4.0/22 via 172.16.0.2 table 150 (150 is a 
variable "net", defined in config-file)

Add config-options like "rountingtable default 200" "routingtable host 
100" "routingtable net 150" to seperate default-, host- and network-routes.

My networksetup is designed to route traffic from 192.168.0.0/24 via 
eth0 (ISP) and 172.16.0.0/22 via tap1 (VPN with running OLSR-Network). I 
will be able to reach the VPN-Clients form network 192.168.0.0 directly, 
but this can not be done in the current situation of routes-handling.

Thanks,
Michael.