[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <trinity-ece5a90d-72c2-4db9-a1f7-8c9af2bbfa65-1391156847114@3capp-gmx-bs01>
Date: Fri, 31 Jan 2014 09:27:27 +0100 (CET)
From: "Simon Schneider" <simon-schneider@....net>
To: "Hannes Frederic Sowa" <hannes@...essinduktion.org>
Cc: netdev@...r.kernel.org
Subject: Aw: Re: Re: IPv4 / IPv6 over IPv4 IPsec tunnel: setting the DF bit
<resending in text format>
Hi Hannes,
thanks.
I think your IPv6 related statements are for a IPv6-over-IPv6 case.
However, I'm especially after the IPv6-over-IPv4 case.
In that case, you cannot copy the DF bit from the inner IPv6 packet.
But you still have the option to set or not set the DF bit in the IPv4 outer packet.
How is that decided?
best regards, Simon
Gesendet: Donnerstag, 30. Januar 2014 um 16:59 Uhr
Von: "Hannes Frederic Sowa" <hannes@...essinduktion.org>
An: "Simon Schneider" <simon-schneider@....net>
Cc: netdev@...r.kernel.org
Betreff: Re: Re: IPv4 / IPv6 over IPv4 IPsec tunnel: setting the DF bit
On Thu, Jan 30, 2014 at 04:26:24PM +0100, Simon Schneider wrote:
> Hi Hannes,
> thanks once again for the quick reply.
>
> Quickly checked the ip manpage. I'm clear about the case where pmtudisc is in effect (default) - the DF bit must be TRUE in this case, for PMTUD to work.
>
> Not sure what you meant by:
>
> "but DF bit should get copied from inner packet up to tunnel header in every
> case"
>
> Do you mean the nopmtudisc case?
Exactly. In nopmtudisc mode the flag is set based on the inner protocols df
bit, default cleared. In pmtudisc mode the DF-flag is always set.
> Also, IPv6 must be different then - there's no DF bit to be copied.
If packet cannot traverse a router frag_needed is returned, tunnel
endpoint relays the icmp info to the original sender and it should update
its pmtu. There is no way to fragment the packet mid-path.
Also IPv6 tunnel endpoint do not fragment the tunnel packets while
encapsulating.
ipsec mode tunnel is allowed to fragment the packets while encapsulation.
> Could you please clarify?
Hope I did. ;)
Greetings,
Hannes
--
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