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

[Michael Rack]

Hi Bernd,

it make sense in some network-configurations!

I will give you an exemple:

eth0 is an interface to an ISP (95.14.1.2/29)
eth1 is an interface to an Wireless Network (172.16.0.1/24)
eth2 is an interface to an Private Network (192.168.0.1/24)

ip route add 0.0.0.0/0 via 95.14.1.1 dev eth0 src 95.14.1.2 table default
== DEFAULT-ROUTE via ISP will match in table default ==

ip rule add from 192.168.0.1 table main prio 100
== DEFAULT-ROUTE via ISP will match in table default ==

ip rule add from 172.16.0.0/24 table main prio 200
ip rule add from 172.16.0.0/24 table 200 prio 201
== DEFAULT-ROUTE will match in table 200 ==

Now, i have to separate default-route by olsr to table >> 200 << and 
host / network-routes to >> main-table <<.

eth1 should route all traffic trought ISP.
eth2 should route all traffic trought OLSRD-Preffered Default-Route.

eth1 should contact all users behind the OLSRD-Netzwork directly.
eth2 should contact all users behind the OLSRD-Running client (no 
problem with HNA-Section).

Is this able to do with current version of olsr?

Thanks,
Michael.


Bernd Petrovitsch schrieb:
> On Fre, 2008-06-20 at 11:13 +0200, Michael Rack wrote:
>   
>> When will it be able to jail default-routes, network-routes and 
>> host-routes into a seperate linux-routing-tables?
>>     
>
> You can put all of them in one routing-table since months.
>
> [...]
>   
>> Add config-options like "rountingtable default 200" "routingtable host 
>> 100" "routingtable net 150" to seperate default-, host- and network-routes.
>>     
>
> In the IPv4 world, host routes are network routes with a prefix of /32.
> And a default route is merely 0.0.0.0/0 which happen to match all routes
> in the IPv4 world.
> IMHO it makes absolutely no sense to differentiate them in anyway on
> that low layer.
>
> 	Bernd
>