[LARTC] HOWTO correction re multiple uplinks/providers

Linux Advanced Routing and Traffic Control

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



In section 4.2 the HOWTO describes creating new routing
tables, like this:

ip route add $P1_NET dev $IF1 src $IP1 table T1
ip route add default via $P1 table T1
ip route add $P2_NET dev $IF2 src $IP2 table T2
ip route add default via $P2 table T2

However these tables are incomplete.  For example if you
ping $IP1 from a machine on the local network, the echo
reply will never find its way back because T1 contains no
route to the local network.

Similarly, it would be good to add a route for 127.0.0.0/8
in case an application binds to localhost and then wants to
connect to $IP1 or $IP2.

If $P0_NET is the local network and $IF0 is its interface,
the following additional entries are desirable:

ip route add $P0_NET     dev $IF0 table T1
ip route add $P2_NET     dev $IF2 table T1
ip route add 127.0.0.0/8 dev lo   table T1
ip route add $P0_NET     dev $IF0 table T2
ip route add $P1_NET     dev $IF1 table T2
ip route add 127.0.0.0/8 dev lo   table T2

Cheers,
--
Rod Roark, Sunset Systems     http://www.sunsetsystems.com/
Offering preconfigured Linux computers, custom software and
remote system administration services.
Public Key: http://www.sunsetsystems.com/rodspublickey.asc



[Index of Archives]     [LARTC Home Page]     [Netfilter]     [Netfilter Development]     [Network Development]     [Bugtraq]     [GCC Help]     [Yosemite News]     [Linux Kernel]     [Fedora Users]
  Powered by Linux