All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michał Margula" <alchemyx@uznam.net.pl>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Multipath routing
Date: Thu, 07 Jun 2007 09:07:01 +0000	[thread overview]
Message-ID: <4667CAB5.5020308@uznam.net.pl> (raw)
In-Reply-To: <CHEKIDJGBLPDJGGHOGPKGEMHCFAA.lists@aptedtech.com>

Piotr Chytla pisze:
> First of all equal cost multipathing is evil ;>, It simply doesn't work for packets in
> forwarding path besides support in kernel is not maintained
> 
> Realy if you want load balance both uplinks disable
> CONFIG_IP_ROUTE_MULTIPATH_CACHED and you will have random traffic 
> distribiution between both links.
> 

Unfortunately it still doesn't work as expected. When i ping some host
it always go trough one nexthop. It does per-destination loadbalancing,
I am afraid.

-- 
Micha³ Margula, alchemyx@uznam.net.pl, http://alchemyx.uznam.net.pl/
"W ¿yciu piêkne s± tylko chwile" [Ryszard Riedel]

_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

  parent reply	other threads:[~2007-06-07  9:07 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-24  2:18 [LARTC] multipath routing Lists @ Aptedtech
2004-03-24  6:05 ` RonSenykoff
2004-03-25  1:22 ` Lists @ Aptedtech
2005-10-26 21:47 ` comp.techs
2005-10-27 14:20 ` Edmundo Carmona
2005-10-27 16:02 ` comp.techs
2005-10-27 18:05 ` comp.techs
2005-11-17 20:47 ` comp.techs
2007-06-05  9:13 ` [LARTC] Multipath routing Michał Margula
2007-06-05 19:46 ` Piotr Chytla
2007-06-06 10:05 ` Michał Margula
2007-06-07  9:07 ` Michał Margula [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-08-16  4:11 [LARTC] Multipath Routing Daniel Frederiksen
2005-08-16  8:39 ` Alexander Samad

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=4667CAB5.5020308@uznam.net.pl \
    --to=alchemyx@uznam.net.pl \
    --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.