From: Rod Roark <rod@sunsetsystems.com>
To: lartc@vger.kernel.org
Subject: [LARTC] HOWTO correction re multiple uplinks/providers
Date: Fri, 14 Feb 2003 07:42:33 +0000 [thread overview]
Message-ID: <marc-lartc-104520863614932@msgid-missing> (raw)
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/
reply other threads:[~2003-02-14 7:42 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=marc-lartc-104520863614932@msgid-missing \
--to=rod@sunsetsystems.com \
--cc=lartc@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.