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: Wed, 06 Jun 2007 10:05:58 +0000	[thread overview]
Message-ID: <46668706.9080906@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.
> 
> More details : 
>           http://lists.openwall.net/netdev/2007/03/14/50
>           http://lists.openwall.net/netdev/2007/03/12/76
>           http://lists.quagga.net/pipermail/quagga-users/2007-May/008469.html
>

Oh. I see. Thanks. BTW: google doesn't show that links when looking for 
multipath on linux :-)

Random load sharing over multiple routes is not a good idea, or maybe is 
it? Am I guessing right that with enough amount of traffic and having 
two nexthops it will split 50%/50% ?


> BGP always have alternative paths in BGP RIB and mostly don't insert them
> as multipath route to FIB.
> 
> Of course there is path : http://lebon.org.ua/quagga.html that force 
> route to be inserted to kernel with multiple gateways - but realy this
> is some kind of dirty-hack.

I know that site, but I thought that those patches were obsoleted, 
because of --multipath option when compiling quagga.

> Check thread 'Linux and BGP multipath' on quagga-dev, and especially this mail:
> 
>            http://lists.quagga.net/pipermail/quagga-dev/2007-April/004700.html


I know that also :). BTW: until now I was quite pleased with linux 
networking which quality is amazing. But now, when I need loadbalancing 
I am disapointed, because it doesn't support things that with cisco 
hardware you take for granted. I miss mostly recursive routes.

Something like that

	ip route add 80.245.177.4/32 via 80.245.176.11
	ip route add 10.0.0.0/24 via 80.245.177.4

It would solve problems with multipath bgp and loadbalancing because I 
could add remove additional routes to 80.245.177.4 (or some other 
imaginary loopback) and it would work as expected.

I hope it will be added some day :)

Thank you for your help!


-- 
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-06 10:05 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 [this message]
2007-06-07  9:07 ` Michał Margula
  -- 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=46668706.9080906@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.