[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20131121114553.GC31491@secunet.com>
Date: Thu, 21 Nov 2013 12:45:53 +0100
From: Steffen Klassert <steffen.klassert@...unet.com>
To: Christophe Gouault <christophe.gouault@...nd.com>
Cc: Saurabh Mohan <saurabh.mohan@...cade.com>,
"David S. Miller" <davem@...emloft.net>,
Herbert Xu <herbert@...dor.apana.org.au>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
Sergei Shtylyov <sergei.shtylyov@...entembedded.com>,
Eric Dumazet <eric.dumazet@...il.com>,
Andrew Collins <bsderandrew@...il.com>,
Fan Du <fan.du@...driver.com>
Subject: Re: [PATCH net v3] vti: fix spd lookup: match plaintext pkt, not
ipsec pkt
On Thu, Nov 21, 2013 at 11:07:27AM +0100, Christophe Gouault wrote:
>
> But you can optionally apply differentiated policies within the same
> tunnel, by setting SPs with narrower selectors: according to the
> plaintext traffic that crosses the tunnel, you can request to use
> different protocols (esp/ah), different SAs, maybe drop some traffic.
This raises the question about the MTU of a vti device. If the SA
is not unique, it is not clear which MTU we should use for that device.
> Only ipsec tunnel mode and drop policies should be bound to a VTI interface.
>
> And the patch restores the SP semantics: the selector is used to match
> the plaintext traffic, not the IPsec encrypted traffic.
>
On the other hand, I've spend quite some time to figure out how
inter address family tunneling can work with vti devices. It
seems that we need plaintext matching to get this to work.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists