Re: [LARTC] Multiple Internet Links problem

[Stephen <meridian@tha.net>]

Julian I am already using a kernel patched with your routes-2.2.19 patch

here is an example of my rule and route list i am presently trying and the
errors i am getting. I have 202.1.1.0/25 + 2 other ips on ppp0 my main
static ip link. The 202.2.2 is my adsl on eth1. 202.3.3 is my cable
on eth2 which i try to route all my clients from 202.1.1.128/25 out of by
default.

I have built these on a working example of
ip ru add from 202.3.3.153/32 table 1
ip ro add 0.0.0.0/0 via 202.3.3.129 table 1


which ensures all data going to the cable ip leaves back out that
interface while my default gateway is still ppp0. Building on this however
causes problems


ip ru add from 202.1.1.0/25 pref 100 table ppp0
ip ru add from 202.1.1.151/32 pref 100 table ppp0
ip ru add from 202.1.1.152/32 pref 100 table ppp0
ip ru add from 202.1.1.128/25 pref 100 table eth0
ip ru add from 202.2.2.18/31 pref 200 table eth1
ip ru add from 202.2.2.20/31 pref 200 table eth1
ip ru add from 202.2.2.22/32 pref 200 table eth1
ip ru add from 202.3.3.153/32 pref 300 table eth2

ip ro add to 202.1.1.128/25 pref 1 dev eth0 table ppp0
ip ro add to 202.1.1.128/25 pref 1 dev eth0 table eth0
ip ro add to 202.1.1.128/25 pref 1 dev eth0 table eth1
ip ro add to 202.1.1.128/25 pref 1 dev eth0 table eth2
ip ro add 0.0.0.0/0 dev ppp0 table ppp0
ip ro add 0.0.0.0/0 dev ppp0 
ip ro add 0.0.0.0/0 via 202.2.2.17 table eth1
ip ro add 0.0.0.0/0 via 202.3.3.129 table eth2
ip ro add from 202.1.1.128/25 via 202.3.3.129 table eth2




+ ip ru add from 202.1.1.0/25 pref 100 table ppp0
+ ip ru add from 202.1.1.151/32 pref 100 table ppp0
+ ip ru add from 202.1.1.152/32 pref 100 table ppp0
+ ip ru add from 202.1.1.128/25 pref 100 table eth0
+ ip ru add from 202.2.2.18/31 pref 200 table eth1
+ ip ru add from 202.2.2.20/31 pref 200 table eth1
+ ip ru add from 202.2.2.22/32 pref 200 table eth1
+ ip ru add from 202.3.3.153/32 pref 300 table eth2
+ ip ro add to 202.1.1.128/25 pref 1 dev eth0 table ppp0
RTNETLINK answers: File exists
+ ip ro add to 202.1.1.128/25 pref 1 dev eth0 table eth0
RTNETLINK answers: File exists
+ ip ro add to 202.1.1.128/25 pref 1 dev eth0 table eth1
RTNETLINK answers: File exists
+ ip ro add to 202.1.1.128/25 pref 1 dev eth0 table eth2
RTNETLINK answers: File exists
+ ip ro add 0.0.0.0/0 dev ppp0 table ppp0
RTNETLINK answers: File exists
+ ip ro add 0.0.0.0/0 dev ppp0
+ ip ro add 0.0.0.0/0 via 202.2.2.17 table eth1
+ ip ro add 0.0.0.0/0 via 202.3.3.129 table eth2
+ ip ro add from 202.1.1.128/25 via 202.3.3.129 table eth2
RTNETLINK answers: File exists
+ exit 0



On Tue, 11 Dec 2001, Julian Anastasov wrote:

> Date: Tue, 11 Dec 2001 23:50:56 +0000 (GMT)
> From: Julian Anastasov <ja@ssi.bg>
> To: Stephen <meridian@tha.net>
> Cc: lartc@mailman.ds9a.nl
> Subject: Re: [LARTC] Multiple Internet Links problem
> 
> 
> 	Hello,
> 
> On Wed, 12 Dec 2001, Stephen wrote:
> 
> > Here is one example of what I have been trying.
> 
> 	Such order of rules and routes is not the recommended one.
> Use the links below to see how similar setups are handled, there are
> some rules you must follow. You can try them if you still don't
> prefer to use fwmarks. What is your preferred kernel?
> 
> http://www.linuxvirtualserver.org/~julian/nano.txt
> http://www.linuxvirtualserver.org/~julian/#routes
> 
> > ip rule add to privatenetwork pref 100 table eth0
> > ip rule add from default dev eth2 pref 200 table eth2
> > ip rule add from default dev ppp0 pref 500 table ppp0
> > ip rule add from default dev eth1 pref 600 table eth1
> > ip rule add from privatenetwork pref 5000 table eth0
> > ip rule add from pppip pref 5001 table ppp0
> >
> > ip route add to random_external_subnet via eth1gwip dev eth1
> > ip route add default from privatenetwork dev eth2 table eth0
> > ip route add to random_external_subnet via eth2gwip dev eth2
> > ip route add to privatenetwork dev eth0 table eth0
> > route add default dev ppp0
> > ip route add default dev ppp0 table ppp0
> > ip route add default dev eth0 table eth0
> > ip route add default via eth1gwip dev eth1 table eth1
> > ip route add default via eth2gwip dev eth2 table eth2
> > ip route add from eth1ip via eth1gwip dev eth1 table eth1
> > ip route add from eth1ip via eth2gwip dev eth2 table eth2
> >
> >
> > Thanks
> > Stephen
> 
> Regards
> 
> --
> Julian Anastasov <ja@ssi.bg>
> 


Stephen Fletcher
mailto:stephen@tha.net
Technologically Higher Altitudes
http://www.tha.com.au


_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/lartc/