netdev - Re: [RFC] ipv6: dst_allfrag() not taken into account by TCP

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <184325098dff696295968e09accafa9d@localhost>
Date:	Wed, 18 Jan 2012 16:14:40 +0100
From:	Tore Anderson <tore@....no>
To:	Eric Dumazet <eric.dumazet@...il.com>
Cc:	netdev <netdev@...r.kernel.org>
Subject: Re: [RFC] ipv6: dst_allfrag() not taken into account by TCP


* Eric Dumazet

> Le mercredi 18 janvier 2012 à 15:43 +0100, Tore Anderson a écrit :
> 
>> Another way of solving it and avoiding the Fragmentation headers
>> altogether would be to allow the "route MTU" to drop below 1280 as a
>> result of Path MTU Discovery. I opened an enchancement bug report
>> requesting this:
>> 
>> https://bugzilla.kernel.org/show_bug.cgi?id=42599
> 
> Please dont open bugzilla entries for this kind of stuff, since there is
> no bug in this case.

Okay...but then what is the «enhanchement» severity's intended use?

> netdev is more appropriate to discuss future improvements.

No problem. Bottom line, I'd like a "min_pmtu" IPv6 sysctl or something
similar that would allow me to configure it so that the kernel would 
accept an arbitrary low PMTU being received in an ICMPv6 PTB. That 
would prevent having to deal with the Fragmentation headers completely.

Best regards,
-- 
Tore Anderson
--
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