[olsr-dev] Policy Routing Hack

[Sven-Ola Tuecke]

Hi Bernd,

you hopefully do not apply the 120-default-rttable-is-111.patch? This is a 
special for the foneras. The rtnetlink interface is somewhat different from 
the ioctl interface - maybe I've missed something that's special on your 
machine. I've tested on Kubuntu-Dapper as well as on OpenWrt Kamikaze 
(uClibc). This is the reason, I've entitled this patch as "hack" ;-)

@daniel: Definitely nono - different tables for routes with 
netmask!=255.255.255.255 and routes with netmask==255.255.255.255 does not 
make sense. You do not really want 32 differnt rttable options. Make sure, 
your background routing tables has the correct "throw" entries. This will 
do. As a P.S.: I'am willing to make an "advanced routing workshop" on the 
WCW next weekend as announced on http://wiki.freifunk.net/WCW2007

Cheers,
// Sven-Ola

"Bernd Petrovitsch" <(spam-protected)> schrieb im Newsbeitrag 
news:(spam-protected)
> On Mon, 2007-04-23 at 15:53 +0200, Bernd Petrovitsch wrote:
>> On Mon, 2007-04-23 at 15:33 +0200, Sven-Ola Tuecke wrote:
>> [...]
>> > for me it's working fine. However, the struct tcmsg change is 
>> > appreciated of
>>
>> I believe that. But it doesn't help me;-)
>>
>> > course. What's wrong on your side? Does-not-compile or has-no-effect? 
>> > In the
>>
>> I usually fix compile errors (if it's easy enough).
>>
>> > latter case, you need to add some policy stuff first. Example: set
>> > rttable=123 in olsrd.conf and hack in something in the start script, 
>> > e.g.
>> > "ip rule add from 10.0.0.0/8 table 123" and maybe "ip rule add from
>> > 192.168.0.0/16 to 10.0.0.0/8 table 123" provided that your mesh runs on
>> > 10.x.x.x. After starting olsrd, the "route -n" command does not show 
>> > any
>> > OLSR route. You need to enter "ip route ls table 123" for this. And you 
>> > need
>> > the ip command, "apt-get install iproute" or so...
>>
>> Routes are simply not added. I get only
>> ----  snip  ----
>> 237#ip r show table 42
>> 193.238.156.50 dev tap0  proto static  metric 1
>> 193.238.156.204 dev eth0  proto static  metric 1
>> ----  snip  ----
>
> BTW these to are exactly one hop away (as one can see on the metric) and
> there are no others exactly one hop away.
>
>> Is it necessary to have a valid  `ip rule` (as stated above) so that it
>> works?
>> I assumed that the routes are properly added and deleted - even if the
>> rest is not properly setup.
>>
>> Hmm, I added now a (IMHO proper) `ip rule`. Doesn't change anything.
>
> Bernd
> -- 
> Firmix Software GmbH                   http://www.firmix.at/
> mobil: +43 664 4416156                 fax: +43 1 7890849-55
>          Embedded Linux Development and Services
>
>
> _______________________________________________
> olsr-dev mailing list
> (spam-protected)
> https://www.olsr.org/mailman/listinfo/olsr-dev