From: bruce@perens.com (Bruce Perens)
To: lartc@vger.kernel.org
Subject: [LARTC] Need information on multi-homing
Date: Sat, 02 Mar 2002 23:49:49 +0000 [thread overview]
Message-ID: <marc-lartc-101511305202598@msgid-missing> (raw)
Is there a multi-homing FAQ? I've not been able to find it.
Here's my system's configuration:
eth0: SDSL at 216.15.108.186 (dnai-net)
eth1: ADSL at 67.114.175.138 (sbc-net)
eth2: DHCP network at 192.168.1.1 .
lo: 127.0.0.1
There is a firewall box acting as the DHCP server and router for the
systems on the DHCP net. The Linux system doesn't run DHCP or
masquerading.
If a connection is accepted on the IP address of one of these interfaces,
I'd like its packets to go out on the same interface. If there is a failure
on the path to eth0, connections to eth1 should continue to work, and vice
versa. But right now, eth0 has the default route and just about every packet
goes out of eth0 regardless of what interface they come in. So, I tried this:
ip rule add from 216.15.108.186 table dnai-net
ip rule add from 67.114.175.138 table sbc-net
ip route add default via 216.15.108.186 dev eth0 table dnai-net
ip route add default via 67.114.175.138 dev eth1 table sbc-net
This doesn't work. I get a destination unreachable if I try to follow either
route. So, what am I doing wrong?
Thanks
Bruce Perens
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next reply other threads:[~2002-03-02 23:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-02 23:49 Bruce Perens [this message]
2002-03-03 1:21 ` [LARTC] Need information on multi-homing bert hubert
2002-03-03 5:36 ` Bruce Perens
2002-03-03 11:16 ` bert hubert
2002-03-04 18:51 ` Bruce Perens
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-101511305202598@msgid-missing \
--to=bruce@perens.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.