From: Jerome Kerdreux <Jerome.Kerdreux@finix.eu.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Multiple ADSL link
Date: Thu, 11 Jul 2002 14:12:07 +0000 [thread overview]
Message-ID: <marc-lartc-102639693421111@msgid-missing> (raw)
In-Reply-To: <marc-lartc-102638295007824@msgid-missing>
Today, mahhy a écrit:
m>On Thu, 11 Jul 2002, Jerome Kerdreux wrote:
m>> ip route add default scope global nexthop via $P1 dev $IF1 weight 1
m>> nexthop via $P2 dev $IF2 weight 1
m>I havent looked at the LARTC HOWTO in depth yet, but I believe you are
m>wanting to implement Equal Cost Multipath Routing. ECM allows for
m>*outgoing* traffic to be load-balanced across multiple ISP connections.
m>
m>There is some good information in the Advanced Routing HOWTO on
m>http://www.linuxdoc.org, I suggest you read that as well.
m>
m>Here is the general script I use to implement ECM, you will have to edit
m>it for your own values (different interface names, IP addresses, gateway
m>addresses, etc):
m>
m> /sbin/ip rule add from <IP Num 1> table 124
m> /sbin/ip rule add from <IP Num 2> table 120
m> /sbin/ip route add default via <IP-GW Num 1> dev eth0 table 124
m> /sbin/ip route add default via <IP-GW Num 2> dev ppp0 table 120
m> /sbin/ip route delete default
m> /sbin/ip route add default scope global nexthop via <IP-GW Num 1> dev
m>eth0 nexthop via <IP-GW Num 2> dev ppp0
m> /sbin/ip route flush cache
m>
m><IP Num 1> is the first IP address on my Linux Router
m><IP Num 2> is the second IP address on my Linux Router
m><IP-GW Num 1> is the first IP address's default Gateway
m><IP-GW Num 2> is the second IP address's default Gateway
m>
m>replace them with appropriate values for your system.
Oh thanks Mahhy I test that :)
Here is what I test :
/sbin/ip rule add from <IP Num 1> table T1
/sbin/ip rule add from <IP Num 2> table T2
/sbin/ip route add default via <IP-GW Num 1> dev ppp0 table T1
/sbin/ip route add default via <IP-GW Num 2> dev ppp1 table T2
/sbin/ip route delete default
/sbin/ip route add default scope global nexthop via <IP-GW Num 1> dev ppp0 nexthop via <IP-GW Num 2> dev ppp1
/sbin/ip route flush cache
but I still have the same pb
===================================================================
ip route:
194.206.78.3 dev ppp1 proto kernel scope link src 62.212.102.172
80.15.151.1 dev ppp0 proto kernel scope link src 80.15.151.117
192.168.0.0/16 dev eth2 proto kernel scope link src 192.168.0.1
default
nexthop via 80.15.151.117 dev ppp0 weight 1 dead
nexthop via 62.212.102.172 dev ppp1 weight 1
===================================================================
ppp0 seems to be detected as dead.
So all the trafic go throught ppp1 and only get this on ppp0
===================================================================
tcpdump -i ppp0:
15:50:22.786991 80.24.174.28.1073 > 80.15.151.117.4665: udp 6
15:50:22.787074 80.15.151.117 > 80.24.174.28: icmp: 80.15.151.117 udp
port 4665 unreachable [tos 0xc0]
15:50:36.917769 62.178.40.99.1275 > 80.15.151.117.4665: udp 6
15:50:36.917855 80.15.151.117 > 62.178.40.99: icmp: 80.15.151.117 udp
port 4665 unreachable [tos 0xc0]
15:50:37.446685 217.235.251.61.2588 > 80.15.151.117.4665: udp 6
15:50:37.446767 80.15.151.117 > 217.235.251.61: icmp: 80.15.151.117
udp port 4665 unreachable [tos 0xc0]
===================================================================
all the trafic i get it that :(
Another thing is that when I drop all the route and just put
ppp0 as default route. this interface works well . this sound
really strange.
Any body have a idea ?
I put the list in Cc: too :)
/Thanks
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2002-07-11 14:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-11 10:18 [LARTC] Multiple ADSL link Jerome Kerdreux
2002-07-11 14:12 ` Jerome Kerdreux [this message]
2002-07-11 20:40 ` Julian Anastasov
2002-07-11 22:04 ` Jkx
2002-07-11 22:16 ` Julian Anastasov
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-102639693421111@msgid-missing \
--to=jerome.kerdreux@finix.eu.org \
--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.