On Wednesday 28 June 2006 11:01, Andrew Lyon wrote: > Luciano Ruete wrote: > > On Wednesday 28 June 2006 05:19, Andrew Lyon wrote: > >> Peter Surda wrote: > >>> On Tuesday 27 June 2006 15:16, Luciano Ruete wrote: > >>>> how about: > >>>> ip route add default nexthop via a.a.a.a weight 4 nexthop via > >>>> b.b.b.b weight 3 > >>> > >>> exactly. > >>> > >>>> Not tested but i think it can work. > >>> > >>> tested, works. > >>> > >>>> Luciano > >>> > >>> Yours sincerely, > >>> Peter > >> > >> It works in so far as the command is accepted and there is no error, > >> but having changed the default route and then doing a upload by ftp I > >> can see that both lines are still getting 1/2 of the outgoing > >> packets. > > > > One upload means nothing, plain multipath(vanilla kernel, with > > multipath cached not set) take in account destination address(DA for > > convenience) and TOS. For each new pair of DA and TOS it takes the > > nexthop available. So doing an ftp to a single host will make no > > difference. Think in connections instead of packets, for a 'per > > packet multipath' you need to have same source address for all your > > choosed gw/isps and to patch your kernel. > > It am not using plain multipath, its equalized multipath using the patch > eql-patch-2.4.30.gz. > > My upload was using both lines, our ISP graphs include bandwidth and I can > see the upload was approx 550kbit on each line, but the capacity is 600kbit > and 800kbit. That's probably an equalize bug, that does not take in account 'weight' for packet balance. Equalize is unmaintained software AFAIK. -- Luciano _______________________________________________ LARTC mailing list LARTC@xxxxxxxxxxxxxxx http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
