From: Edmundo Carmona <eantoranz@gmail.com>
To: netfilter@lists.netfilter.org
Subject: Re: experimenting with 2 ISP's
Date: Mon, 15 Aug 2005 17:08:11 -0400 [thread overview]
Message-ID: <65aa6af9050815140847213738@mail.gmail.com> (raw)
In-Reply-To: <65aa6af90508151406d10894@mail.gmail.com>
I mean.... you also have to define the default gateway as a multipath route.
On 8/15/05, Edmundo Carmona <eantoranz@gmail.com> wrote:
> That's not the right way to set the default GW.
>
> You have to use IP. Remove your default GWs. then:
>
> ip route add default netxhop via 196.36.10.114 dev eth0 nexthop via
> 196.168.10.100 dev eth2
> ip route flush cache.
>
> If you set the routing tables correctly, It should start working right away.
>
> On 8/15/05, Brent Clark <bclark@eccotours.dyndns.org> wrote:
> > Hi list
> >
> > I have just a added a few rules to my routing table.
> >
> > Would someone be so kind as to see if my setup is correct.
> >
> > My setup is as so
> >
> > eth0
> > IP 196.36.10.114
> > GW 196.36.10.113 (my routers IP)
> >
> > eth1 192.168.111.10
> > PRIVATE LAN
> >
> > eth2
> > IP 192.168.10.200
> > GW 192.168.10.100 (my adsl modem)
> >
> > Please keep in mind that my router that is connected to eth0 has a static ip, where as my adsl modem that is connected to eth2 is dynamically assigned.
> >
> > echo 200 IS >> /etc/iproute2/rt_tables
> > echo 201 TELKOM >> /etc/iproute2/rt_tables
> >
> > /sbin/ip route add 196.36.10.0 dev eth0 src 196.36.10.114 table IS
> > /sbin/ip route add default via 196.36.10.113 table IS
> >
> > /sbin/ip route add 192.168.10.0 dev eth2 src 192.168.10.100 table TELKOM
> > /sbin/ip route add default via 192.168.10.100 table TELKOM
> >
> > /sbin/ip route add 196.36.10.0 dev eth0 src 196.36.10.114
> > /sbin/ip route add 192.168.10.0 dev eth2 src 192.168.10.100
> >
> > /sbin/ip route add default via 196.36.10.113
> >
> > /sbin/ip rule add from 196.36.10.114 table IS
> > /sbin/ip rule add from 192.168.10.100 table TELKOM
> >
> > From my routing table all seem ok:
> > gate:~# route -n
> > Kernel IP routing table
> > Destination Gateway Genmask Flags Metric Ref Use Iface
> > 196.36.10.0 0.0.0.0 255.255.255.255 UH 0 0 0 eth0
> > 192.168.10.0 0.0.0.0 255.255.255.255 UH 0 0 0 eth2
> > 196.36.10.112 0.0.0.0 255.255.255.248 U 0 0 0 eth0
> > 192.168.111.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1
> > 192.168.10.0 0.0.0.0 255.255.255.0 U 0 0 0 eth2
> > 0.0.0.0 196.36.10.113 0.0.0.0 UG 0 0 0 eth0
> > gate:~#
> >
> > If anyone has any tips or advise they would care to add, it would be most appreciated.
> >
> > Kind Regards
> > Brent Clark
> >
> >
> >
>
prev parent reply other threads:[~2005-08-15 21:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-15 19:19 experimenting with 2 ISP's Brent Clark
2005-08-15 21:06 ` Edmundo Carmona
2005-08-15 21:08 ` Edmundo Carmona [this message]
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=65aa6af9050815140847213738@mail.gmail.com \
--to=eantoranz@gmail.com \
--cc=netfilter@lists.netfilter.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox