netdev
[Top] [All Lists]

Re: [17/*] [NET] Replace dst_pmtu with dst_mtu

To: "David S. Miller" <davem@xxxxxxxxxxxxx>
Subject: Re: [17/*] [NET] Replace dst_pmtu with dst_mtu
From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
Date: Wed, 16 Mar 2005 07:31:52 +1100
Cc: kuznet@xxxxxxxxxxxxx, yoshfuji@xxxxxxxxxxxxxx, kaber@xxxxxxxxx, netdev@xxxxxxxxxxx
In-reply-to: <20050315102450.0f3f1618.davem@xxxxxxxxxxxxx>
References: <20050306213214.7d8a143d.davem@xxxxxxxxxxxxx> <20050307103536.GB7137@xxxxxxxxxxxxxxxxxxx> <20050308102741.GA23468@xxxxxxxxxxxxxxxxxxx> <20050314102614.GA9610@xxxxxxxxxxxxxxxxxxx> <20050314105313.GA21001@xxxxxxxxxxxxxxxxxxx> <20050314111002.GA29156@xxxxxxxxxxxxxxxxxxx> <20050315091904.GA6256@xxxxxxxxxxxxxxxxxxx> <20050315095837.GA7130@xxxxxxxxxxxxxxxxxxx> <20050315100522.GA7275@xxxxxxxxxxxxxxxxxxx> <20050315102450.0f3f1618.davem@xxxxxxxxxxxxx>
Sender: netdev-bounce@xxxxxxxxxxx
User-agent: Mutt/1.5.6+20040907i
On Tue, Mar 15, 2005 at 10:24:50AM -0800, David S. Miller wrote:
> 
> So, at that point, I guess the next task is to handle PMTU events of already
> encrypted packets properly?  We still have that problem right?  When the
> ICMP payload is encrypted we have to cache some information on IPSEC output
> so that a proto+SPI key can find us the encrypted inner IP header info, which
> we'll need in order to process (and/or forward) the ICMP PMTU information
> correctly.

Yes, that's going to be the second part of the MTU work.

Cheers,
-- 
Visit Openswan at http://www.openswan.org/
Email: Herbert Xu ~{PmV>HI~} <herbert@xxxxxxxxxxxxxxxxxxx>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt

<Prev in Thread] Current Thread [Next in Thread>