netdev - Re: Has RFC4821 been implemented?

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]

Message-ID: <56A29CED.4090601@stressinduktion.org>
Date:	Fri, 22 Jan 2016 22:19:41 +0100
From:	Hannes Frederic Sowa <hannes@...essinduktion.org>
To:	Tom Herbert <tom@...bertland.com>,
	Linux Kernel Network Developers <netdev@...r.kernel.org>
Subject: Re: Has RFC4821 been implemented?

Hi,

On 22.01.2016 20:50, Tom Herbert wrote:
> Found it: tcp_mtu_probing

Exactly.

> On Fri, Jan 22, 2016 at 11:39 AM, Tom Herbert <tom@...bertland.com> wrote:
>> This came up on in one of the IETF mailing lists in the context that
>> PMTUD doesn't really work on the Internet so  PLPMTUD is the way to
>> go. Looking at the code I only see inet_csk_update_pmtu called from
>> ICMP PTB error. I am missing something?

If I recall correctly we don't store the MSS in the inetpeer tcp metrics 
cache neither do we update the MTU on the specific path (update the 
dst_entry). So it is a one connection only thing so far.

Bye,
Hannes