All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arthur van Leeuwen <arthurvl@sci.kun.nl>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Balancing ip traffic over two or more internet (adsl)
Date: Thu, 15 Mar 2001 11:48:54 +0000	[thread overview]
Message-ID: <marc-lartc-98465693307570@msgid-missing> (raw)
In-Reply-To: <marc-lartc-98465591406063@msgid-missing>

On Thu, 15 Mar 2001, RoMaN SoFt / LLFB!! wrote:

>  I have set up a test machine to act as the "Linux IP Load balancer"
> and activated the "CONFIG_IP_ROUTE_MULTIPATH". Then I've set up two
> default routes with "ip route" and "equalize"-"nexthop" options. But
> it isn't working correctly. I think this method distribute packets in
> a round robin fashion but doesn't have the "session handling" problem
> into account, I fear.

Actually, the kernel does not necessarily send packets that already have
a source address out the interface associated with that address. That might
very well be your problem. The session problem does not really exist, as the
IP multipath code only multiplexes at the route-level. Once a route has been
set up it is entered into the route cache and will stay there, over the same
interfaces, for as long as packets are exchanged over it. Note that the
route-cache is keyed on the triple (src-address,dst-address,type-of-service).
The last part of that key may bite you with your 'session handling', as at
least one notable piece of client software, OpenSSH, changes the
type-of-service somewhere during the session. Fortunately, the TOS field
can be thwacked using ipchains or iptables so you can work around that...

Doei, Arthur. (Who hopes this is clearer than it looks...)

-- 
  /\    / |      arthurvl@sci.kun.nl      | Work like you don't need the money
 /__\  /  | A friend is someone with whom | Love like you have never been hurt
/    \/__ | you can dare to be yourself   | Dance like there's nobody watching


_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/2.4Routing/

  reply	other threads:[~2001-03-15 11:48 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-15 11:33 [LARTC] Balancing ip traffic over two or more internet (adsl) connections RoMaN SoFt / LLFB!!
2001-03-15 11:48 ` Arthur van Leeuwen [this message]
2001-03-15 15:44 ` RoMaN SoFt / LLFB!!
2001-03-15 16:56 ` [LARTC] Balancing ip traffic over two or more internet (adsl) Arthur van Leeuwen
2001-03-16 10:16 ` [LARTC] Balancing ip traffic over two or more internet (adsl) connections RoMaN SoFt / LLFB!!
2001-03-16 10:41 ` [LARTC] Balancing ip traffic over two or more internet (adsl) Arthur van Leeuwen
2001-03-16 11:52 ` [LARTC] Balancing ip traffic over two or more internet (adsl) connections RoMaN SoFt / LLFB!!
2001-03-16 12:41 ` [LARTC] Balancing ip traffic over two or more internet (adsl) Arthur van Leeuwen
2001-03-16 18:25 ` [LARTC] Balancing ip traffic over two or more internet (adsl) connections RoMaN SoFt / LLFB!!
2001-03-16 18:32 ` Mike Fedyk
2001-03-16 19:10 ` RoMaN SoFt / LLFB!!
2001-03-16 19:52 ` Mike Fedyk
2001-03-17 12:56 ` [LARTC] Balancing ip traffic over two or more internet (adsl) Arthur van Leeuwen

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-98465693307570@msgid-missing \
    --to=arthurvl@sci.kun.nl \
    --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.