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
| ||
|
Date: Wed, 13 Aug 2008 10:00:28 +0200 From: Thomas Jarosch <thomas.jarosch@...ra2net.com> To: David Miller <davem@...emloft.net> Cc: ilpo.jarvinen@...sinki.fi, billfink@...dspring.com, fragabr@...il.com, netdev@...r.kernel.org, kaber@...sh.net, sr@...urenet.de, netfilter-devel@...r.kernel.org, kadlec@...ckhole.kfki.hu Subject: Re: [PATCH] tcp FRTO: in-order-only "TCP proxy" fragility workaround On Tuesday, 12. August 2008 10:18:22 David Miller wrote: > From: Thomas Jarosch <thomas.jarosch@...ra2net.com> > Date: Tue, 12 Aug 2008 09:46:17 +0200 > > > David, I agree with you, though I'm not sure about the end user > > experience: > > We had the same situation with ECN and window scaling, and my proposal > is the same as how we handled those situations involving broken > middleware boxes. Yes, that is true. IMHO there's a slight difference with FRTO trouble compared to ECN/window scaling issues: ECN trouble -> No access at all Broken window scaling -> Large transfers don't work MTU issues -> No access at all / large transfers don't work FRTO problems -> Hard to spot as they only happen when packet loss occurs. Though I guess Ilpo knows best if there's an "easy" way to detect this or not. Thomas -- 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