netdev - Re: [PATCH net-next] ipv6: Use 1280 as min MTU for ipv6 forwarding

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Fri, 26 Feb 2010 04:34:59 -0800 (PST)
From:	David Miller <davem@...emloft.net>
To:	uweber@...aro.com
Cc:	netdev@...r.kernel.org
Subject: Re: [PATCH net-next] ipv6: Use 1280 as min MTU for ipv6 forwarding

From: Ulrich Weber <uweber@...aro.com>
Date: Fri, 26 Feb 2010 13:32:44 +0100

> Clients will set their MTU to 1280 if they receive a
> ICMPV6_PKT_TOOBIG message with an MTU less than 1280.
> 
> To allow encapsulating of packets over a 1280 link
> we should always accept packets with a size of 1280
> for forwarding even if the path has a lower MTU and
> fragment the encapsulated packets afterwards.
> 
> In case a forwarded packet is not going to be encapsulated
> a ICMPV6_PKT_TOOBIG msg will still be send by ip6_fragment()
> with the correct MTU.
> 
> Signed-off-by: Ulrich Weber <uweber@...aro.com>

Applied, thanks for fixing up this patch.
--
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