From: Patrick McHardy <kaber@trash.net>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: "David S. Miller" <davem@davemloft.net>, netdev@oss.sgi.com
Subject: Re: [XFRM]: Always reroute in tunnel mode
Date: Sat, 19 Feb 2005 07:23:06 +0100 [thread overview]
Message-ID: <4216DB4A.2000109@trash.net> (raw)
In-Reply-To: <20050218095344.GA19307@gondor.apana.org.au>
Herbert Xu wrote:
>Put it another way, my solution to Patrick's inconsistency would be to
>always inherit the routing decision from the top to the bottom of the
>bundle. For example, suppose you had
>
>ip ro add 192.168.0.0/16 \
> nexthop via 10.0.0.1 dev eth0 \
> nexthop via 10.0.0.2 dev eth0
>
>Then the packets to 192.168.0.0/16 should be sent via 10.0.0.1/10.0.0.2
>regardless of what IPsec protections are applied to it.
>
I agree it is a nice alternative to the current way. It would solve
another inconsistency caused by overriding the routing result in
tunnel mode: on output we don't care about oif, so packets from a
socket will be tunneled independent of sk_bound_dev_if. On input
packets won't be delivered to the socket if the encapsulated
packet arrived on a different interface.
Regards
Patrick
prev parent reply other threads:[~2005-02-19 6:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-17 6:22 [XFRM]: Always reroute in tunnel mode Patrick McHardy
2005-02-17 11:36 ` Herbert Xu
2005-02-17 18:15 ` Patrick McHardy
2005-02-17 18:25 ` Patrick McHardy
2005-02-17 20:38 ` Herbert Xu
2005-02-17 21:23 ` Patrick McHardy
2005-02-17 22:10 ` Herbert Xu
2005-02-17 23:02 ` Patrick McHardy
2005-02-17 23:11 ` David S. Miller
2005-02-18 9:53 ` Herbert Xu
2005-02-19 6:23 ` Patrick McHardy [this message]
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=4216DB4A.2000109@trash.net \
--to=kaber@trash.net \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--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 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.