On Tue, Sep 22, 2009 at 03:55:30PM +0200, Ondrej Zajicek wrote:
Sure. Just prepend 'ip ro add' and append 'table 3' to each line, like this:
ip ro add 172.18.68.254/32 dev tap5 scope link src 172.18.32.254 table 3 ip ro add 10.10.107.0/24 via 172.18.68.254 dev tap5 src 172.18.32.254 table 3
That i tried but doesn't work for me:
rb1:~# ip a a 10.0.0.1/32 dev eth0 rb1:~# ip r a 10.0.1.1/32 dev eth0 scope link src 10.0.0.1 table 3 rb1:~# ip r a 10.0.2.0/24 via 10.0.1.1 dev eth0 src 10.0.0.1 table 3 RTNETLINK answers: No such process
Weird. I've been using this setup for years now. What kernel is that? For example, one of the particular interfaces I configure like this (Debian interfaces(5) snippet): auto tap2 iface tap2 inet static address 172.18.68.254 netmask 255.255.255.255 pre-up openvpn --rmtun --dev tap2 || true pre-up openvpn --mktun --dev tap2 pre-up ifconfig tap2 hw ether 00:FF:00:00:05:02 up ip ro add 172.18.17.254/32 dev tap2 src 172.18.68.254 up ip ro add 172.18.16.0/20 via 172.18.17.254 dev tap2 src 172.18.68.254 post-down openvpn --rmtun --dev tap2 I copied my routes from the other tables into table 3 using just ip ro sh | sed 's/^/ip ro add /;s/$/ table 3/' | sh and it worked flawlessly. Andras -- Andras Korn <korn at elan.rulez.org> - <http://chardonnay.math.bme.hu/~korn/> Reality is that which, when you stop believing in it, doesn't go away.