netdev - RE: [PATCHv2 net-next 0/4] Small fix for TCP PMTU

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]

Date:	Thu, 26 Feb 2015 13:40:32 +0000
From:	David Laight <David.Laight@...LAB.COM>
To:	'Fan Du' <fan.du@...el.com>,
	"johnwheffner@...il.com" <johnwheffner@...il.com>
CC:	"edumazet@...gle.com" <edumazet@...gle.com>,
	"davem@...emloft.net" <davem@...emloft.net>,
	"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
	"fengyuleidian0615@...il.com" <fengyuleidian0615@...il.com>
Subject: RE: [PATCHv2 net-next 0/4] Small fix for TCP PMTU

From: Fan Du
> This patchset performs some small fix and enhancement
> for current TCP PMTU as per RFC4821 with below changes:
> 
> Patch1/4: Set probe mss base to 1024 Bytes per RFC4821
> Patch2/4: Do not double probe_size for each probing,
>           use a simple binary search to gain maximum performance.
> Patch3/4: When it comes to blackhole detection, shrink current
> 	  mss for next probing.
> Patch4/4: Create a probe timer to detect enlarged path MTU.

Isn't the most likely problem PPPoE blackholes?
Where a reduction of the PMTU from 1500 to (IIRC) 1492 is
all that is required?

Would seem appropriate to test that value reasonable quickly.

	David

--
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