Latest techniques for multiple PPP load-balancing
Hey,
I've been scouring the web these past few days trying to find a suitable technique to load balance my network. Unfortunately I think my setup is very uncommon, so I'm looking to you guys to see if you can help.
I currently have 2 ADSL modems, provided by the same ISP and terminating on the same gateway (I think having the same gateway is what is causing the problems, since the nexthop is always the same for each interface). I've tried using equal cost multipath (using ip route to set two nexthops with equal weights). Problem is I believe this uses route lookups to determine which interface to use, and thus for sending data to common destinations it only ever uses 1 interface.
Does anyone know if its even possible to send packets over each interface "equally"? I read somewhere that you might be able to clear the route cache after every packet, but I've only seen people talk about it and don't know if its true.
Can anyone help?
I'm running 2.4.20 on Debian (woody), with both ADSL modems using PPPoA and with most of the QoS and network queuing modules installed. AFAIK, my provider doesn't support multilink.
Thanks,
Andy.
_______________________________________________
LARTC mailing list / [email protected]
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
Quoted 13 lines · Andy Coates
I currently have 2 ADSL modems, provided by the same ISP and terminating on the same gateway (I think having the same gateway is what is causing the problems, since the nexthop is always the same for each interface). I've tried using equal cost multipath (using ip route to set two nexthops with equal weights). Problem is I believe this uses route lookups to determine which interface to use, and thus for sending data to common destinations it only ever uses 1 interface.
Does anyone know if its even possible to send packets over each interface "equally"? I read somewhere that you might be able to clear the route cache after every packet, but I've only seen people talk about it and don't know if its true.
Quoted 5 lines
Can anyone help?
I'm running 2.4.20 on Debian (woody), with both ADSL modems using PPPoA and with most of the QoS and network queuing modules installed. AFAIK, my provider doesn't support multilink.
I've done this in a previous life on a [patched] 2.2 kernel with using ISDN-interfaces, using the 'equalize' parameter in the nexthop statement. Possibly, 2.4 supports this natively - but I cannot test it at home.
You could try something along the lines of the following though (note the equalize!):
ip route add default scope global equalize nexthop dev ppp0 via 12.34.56.78 \
nexthop dev ppp1 via 12.34.56.78
(It won't give you doubled download speed of course, this will only help you while uploading - but only if your provider isn't doing per-connection egress filtering in the upstream gateway)
Regards,
Signature · 2 lines
Jasper Spaans http://jsp.vs19.net/contact/
Quoted 35 lines · Andy Coates
Quoted 4 lines
I currently have 2 ADSL modems, provided by the same ISP and terminating on the same gateway (I think having the same gateway is what is causing the problems, since the nexthop is always
the same for
Quoted 1 line
each interface). I've tried using equal cost multipath
(using ip route
Quoted 2 lines
to set two nexthops with equal weights). Problem is I believe this uses route lookups to determine which interface to use, and
thus for
Quoted 4 lines
sending data to common destinations it only ever uses 1 interface.
Does anyone know if its even possible to send packets over each interface "equally"? I read somewhere that you might be
able to clear
Quoted 7 lines
the route cache after every packet, but I've only seen people talk about it and don't know if its true.
Can anyone help?
I'm running 2.4.20 on Debian (woody), with both ADSL modems using PPPoA and with most of the QoS and network queuing modules
installed.
Quoted 1 line
AFAIK, my provider doesn't support multilink.
I've done this in a previous life on a [patched] 2.2 kernel with using ISDN-interfaces, using the 'equalize' parameter in the nexthop statement. Possibly, 2.4 supports this natively - but I cannot test it at home.
You could try something along the lines of the following though (note the
equalize!):
Quoted 8 lines
ip route add default scope global equalize nexthop dev ppp0
via 12.34.56.78 \ nexthop dev ppp1 via 12.34.56.78(It won't give you doubled download speed of course, this will only help you while uploading - but only if your provider isn't doing per-connection egress filtering in the upstream gateway)
Hi,
I've tried that as well, but it still only seems to use one interface when attempting to send data to a specific host (and even trying another connection to the host results in the packets going over the same interface).
Seems like its using this route caching to determine which interface to go over still :(
"ip route" shows:
default equalize
nexthop via 212.104.130.141 dev ppp0 weight 1
nexthop via 212.104.130.141 dev ppp1 weight 1So it at least appears to have set it correctly (it added the weights itself)
Andy.
_______________________________________________
LARTC mailing list / [email protected]
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
Quoted 11 lines · Andy Coates
Hi,
I've tried that as well, but it still only seems to use one interface when attempting to send data to a specific host (and even trying another connection to the host results in the packets going over the same interface).
Seems like its using this route caching to determine which interface to go over still :(
thats what the equalize patch prevents. btw, it is not included in 2.4 (or 2.5), you
can find a 2.4.18 version at trash.net/~kaber.
Quoted 8 lines
"ip route" shows:
default equalizenexthop via 212.104.130.141 dev ppp0 weight 1 nexthop via 212.104.130.141 dev ppp1 weight 1So it at least appears to have set it correctly (it added the weights itself)
without the patch its won't do what you expect.
Patrick
_______________________________________________
LARTC mailing list / [email protected]
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
Andy Coates
AppliedQuoted 10 lines
Quoted 8 lines · Andy Coates
Hi,
I've tried that as well, but it still only seems to use one interface
when attempting to send data to a specific host (and even trying another connection to the host results in the packets going over the same interface).
Quoted 5 lines
Quoted 2 lines
Seems like its using this route caching to determine which interface to go over still :(
thats what the equalize patch prevents. btw, it is not included in 2.4 (or 2.5), you can find a 2.4.18 version at trash.net/~kaber.
Thanks for that, from what I've read I'd have never known it wasn't included.
Quoted 9 lines
Quoted 8 lines
"ip route" shows:
default equalizenexthop via 212.104.130.141 dev ppp0 weight 1 nexthop via 212.104.130.141 dev ppp1 weight 1So it at least appears to have set it correctly (it added the weights itself)
without the patch its won't do what you expect.
I've applied the patch and can confirm it does work as I expected! Thank you so much :)
Andy.
_______________________________________________
LARTC mailing list / [email protected]
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
Em Mon, Jan 20, 2003 at 06:16:48PM -0000, Andy Coates escreveu:
Quoted 4 lines
Quoted 1 line
without the patch its won't do what you expect.
I've applied the patch and can confirm it does work as I expected! Thank you so much :)
Let me get this straight.
Stock kernel has already multipath routing, right?
It also has the equalize option. BUT it doesn't work as expected, so there is this new patch which makes equalize better and sort of bypass the routing cache, is that it?
Or was the equalize option from ip being silently ignored?
_______________________________________________
LARTC mailing list / [email protected]
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/