<br><font size=2 face="sans-serif">Hi Andrew,</font><br><br><font size=2 face="sans-serif">I would use a combination with iptables.
You should mark the packets, for example using average or n-th, and then
use ip rules to send half of the packets vía one router and the rest to
the other router according to the marks you set with iptables.</font><br><font size=2 face="sans-serif">Just a question ¿ dont you have problems
with your source IP and the returning responses when you are sending packets
from one connection over multiple routers ? ¿ do you have something like
an AS ?</font><br><br><br><font size=2 face="sans-serif">Best regards,</font><br><font size=2 face="sans-serif">Eric Janz <br></font><br><br><br><table width=100%><tr valign=top><td width=40%><font size=1 face="sans-serif"><b>Andrew Lyon <andrew.lyon@josims.com></b></font><br><font size=1 face="sans-serif">Enviado por: lartc-bounces@mailman.ds9a.nl</font><p><font size=1 face="sans-serif">10/04/2007 14:36</font><td width=59%><table width=100%><tr valign=top><td><div align=right><font size=1 face="sans-serif">Para</font></div><td><font size=1 face="sans-serif">"'lartc@mailman.ds9a.nl'"
<lartc@mailman.ds9a.nl></font><tr valign=top><td><div align=right><font size=1 face="sans-serif">cc</font></div><td><tr valign=top><td><div align=right><font size=1 face="sans-serif">Asunto</font></div><td><font size=1 face="sans-serif">[LARTC] equalize / ecmp not working
as expected in 2.6 vs 2.4</font></table><br><table><tr valign=top><td><td></table><br></table><br><br><br><tt><font size=2>Hi,<br><br>With kernel 2.4 I was able to use equalize to send our outgoing packets
to<br>two different routers (our isp supports this setup), like this:<br><br>ip route add default src ip.a.dd.rr equalize nexthop via <router1>
weight 1<br>nexthop via <router2> weight 1<br><br>The two routes were used equally on a per packet basis, not per flow or
per<br>cached route, but per packet, each line has 800k upload and with that route<br>we could upload to a single remote host at 1.6mbit.<br><br>We replaced the server with a newer one and changed to 2.6 (2.6.20) kernel,<br>I found that equalize no longer works as expected, it does choose a router<br>at random but once a single packet has been sent to a remote host the same<br>route/router is used for all packets going to that remote host. Once the<br>cached route expires a random route is chosen again, but that is not what
we<br>want.<br><br>I had made no changes to the ip route commands, but then I realised that<br>kernel 2.6.20 has options for multipath (IP: equal cost multipath with<br>caching support), I enabled that and now our kernel options are:<br><br>CONFIG_IP_ROUTE_MULTIPATH=y<br>CONFIG_IP_ROUTE_MULTIPATH_CACHED=y<br>CONFIG_IP_ROUTE_MULTIPATH_RR=m<br>CONFIG_IP_ROUTE_MULTIPATH_RANDOM=m<br>CONFIG_IP_ROUTE_MULTIPATH_WRANDOM=m<br>CONFIG_IP_ROUTE_MULTIPATH_DRR=m<br><br>But even with these options, and default route set as follows:<br><br>ip route add default src ip.a.dd.rr mpath rr nexthop via <router1>
weight 1<br>nexthop via <router2> weight 1<br><br>The result is the same, a single upload to a remote host only uses 800k<br>bandwidth on one of the lines, it does not send packets to both lines,<br>although two uploads to two different hosts will usually make use of both<br>lines.<br><br>It seems to me that the multipath with caching support is broken in 2.6.20?<br><br>The exact kernel we use is 2.6.20.4, with that kernel how would you specify<br>a remote route such that packets going to a remote host are sent 50/50
ratio<br>to two different routers?<br><br>Thanks<br>Andy<br><br>JOSEDV001TAG<br>_______________________________________________<br>LARTC mailing list<br>LARTC@mailman.ds9a.nl<br>http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc<br></font></tt><br>--<BR>
<BR>
ADVERTENCIA LEGAL<BR>
El contenido de este correo es confidencial y dirigido unicamente a su destinatario. Para acceder a su clausula de privacidad consulte http://www.barceloviajes.com/privacy<BR>
<BR>
LEGAL ADVISORY<BR>
This message is confidential and intended only for the person or entity to which it is addressed. In order to read its privacy policy consult it at http://www.barceloviajes.com/privacy<BR>
<BR>