Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: "Andy Coates" <andy@bribed.net>
To: lartc@vger.kernel.org
Subject: RE: [LARTC] Latest techniques for multiple PPP load-balancing
Date: Mon, 20 Jan 2003 18:16:48 +0000	[thread overview]
Message-ID: <marc-lartc-104308666314442@msgid-missing> (raw)
In-Reply-To: <marc-lartc-104294009631701@msgid-missing>

> Andy Coates wrote:
> 
> >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.

Thanks for that, from what I've read I'd have never known it wasn't
included.

> >"ip route" shows:
> >default equalize
> >        nexthop via 212.104.130.141  dev ppp0 weight 1
> >        nexthop via 212.104.130.141  dev ppp1 weight 1
> >
> >So 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 / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

  parent reply	other threads:[~2003-01-20 18:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-19  1:32 [LARTC] Latest techniques for multiple PPP load-balancing Andy Coates
2003-01-19  9:49 ` Jasper Spaans
2003-01-19 14:12 ` Andy Coates
2003-01-20  6:51 ` Patrick McHardy
2003-01-20 18:16 ` Andy Coates [this message]
2003-01-20 19:58 ` Andreas Hasenack

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-104308666314442@msgid-missing \
    --to=andy@bribed.net \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox