From: "Einar Lück" <lkml@einar-lueck.de>
To: "David S. Miller" <davem@davemloft.net>
Cc: linux-kernel@vger.kernel.org, netdev@oss.sgi.com
Subject: Re: [PATCH 2/2] ipv4 routing: multipath with cache support, 2.6.10-rc3
Date: Wed, 09 Feb 2005 21:42:39 +0100 [thread overview]
Message-ID: <420A75BF.1080106@einar-lueck.de> (raw)
In-Reply-To: <20050209123004.2d65e1cf.davem@davemloft.net>
David S. Miller wrote:
> This was brought up before. It's the case where the system is acting
> as a router, you have to consider that case and not just the one where
> the local system is where the connections are originating from.
>
> Your trick only works because of how routes are cached per-socket.
> Once you get into the realm of traffic going through the machine as
> a router, the trick stops to work.
We considered the routing case: in the routing case ip_route_input is called.
In this case we just select the first route in the cache which is always the same
(we ensure that). Consequently, the routing behaviour is not changed in this case and
remains in the way you like it.
Regards,
Einar.
next prev parent reply other threads:[~2005-02-09 20:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-20 11:19 [PATCH 2/2] ipv4 routing: multipath with cache support, 2.6.10-rc3 Einar Lück
2004-12-20 15:10 ` Einar Lück
2005-02-03 1:23 ` David S. Miller
2005-02-09 13:28 ` Einar Lück
2005-02-09 20:01 ` David S. Miller
2005-02-09 20:23 ` Einar Lück
2005-02-09 20:30 ` David S. Miller
2005-02-09 20:42 ` Einar Lück [this message]
2005-02-09 21:17 ` David S. Miller
-- strict thread matches above, loose matches on Subject: below --
2004-12-20 11:15 Einar Lück
2004-12-20 11:13 Einar Lück
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=420A75BF.1080106@einar-lueck.de \
--to=lkml@einar-lueck.de \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.com \
/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;
as well as URLs for NNTP newsgroup(s).