From mboxrd@z Thu Jan 1 00:00:00 1970 From: Rod Roark Date: Fri, 14 Feb 2003 07:42:33 +0000 Subject: [LARTC] HOWTO correction re multiple uplinks/providers Message-Id: List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: lartc@vger.kernel.org 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 _______________________________________________ LARTC mailing list / LARTC@mailman.ds9a.nl http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/