From: Tore Anderson <tore@linpro.no>
To: "David S. Miller" <davem@davemloft.net>
Cc: netdev@vger.kernel.org, Jarek Poplawski <jarkao2@o2.pl>
Subject: [PATCH] Improve cached ECMP documentation
Date: Wed, 07 Mar 2007 13:37:44 +0100 [thread overview]
Message-ID: <45EEB218.8000804@linpro.no> (raw)
In-Reply-To: <20070307073932.GA1675@ff.dom.local>
Document that equal-cost multipath routing with caching does not work
for forwarded packets.
Signed-Off-By: Tore Anderson <tore@linpro.no>
---
* Jarek Poplawski
> It is probably one of the most often asked questions
> on the LARTC, so I'd suggest to look at its archives.
>
> [...]
>
> Multipath with caching doesn't work with forwarding.
Well, I did look at LARTC's archives (and again after reading your
mail), still couldn't find anything. Sorry for bothering you, though.
When I disabled the support it worked just fine (no need for iptables
CONNMARK trickery or any of Julian's patches), so thanks for your help!
Anyway, it strikes me as a bit odd that this feature is found under
CONFIG_IP_ADVANCED_ROUTER when it doesn't work for routers. That
could at least be better documented - here's a patch to do just that.
--- a/net/ipv4/Kconfig
+++ b/net/ipv4/Kconfig
@@ -124,6 +124,10 @@ config IP_ROUTE_MULTIPATH_CACHED
routing cache. If you say Y here, alternative routes are cached
and on cache lookup a route is chosen in a configurable fashion.
+ Be warned that this feature does not work for forwarded packets,
+ and that enabling it will break equal cost multipath routing for
+ forwarded traffic.
+
If unsure, say N.
config IP_ROUTE_MULTIPATH_RR
next prev parent reply other threads:[~2007-03-07 12:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-06 20:36 Multipath routing in Linux 2.6 Tore Anderson
2007-03-07 7:39 ` Jarek Poplawski
2007-03-07 12:37 ` Tore Anderson [this message]
2007-03-07 13:54 ` [PATCH] Improve cached ECMP documentation Jarek Poplawski
2007-03-07 14:17 ` Tore Anderson
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=45EEB218.8000804@linpro.no \
--to=tore@linpro.no \
--cc=davem@davemloft.net \
--cc=jarkao2@o2.pl \
--cc=netdev@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.