| 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: Sun, 28 Mar 2010 10:50:06 +0200 From: Andi Kleen <andi@...stfloor.org> To: Glen Turner <gdt@....id.au> Cc: netdev@...r.kernel.org Subject: Re: UDP path MTU discovery Glen Turner <gdt@....id.au> writes: > In IPv6 routers do not fragment packets, so there is no work > around. Transactional servers which use UDP over IPv6 encounter > exponential backoffs within the application and the client > abandons the transaction. There is no way for the server to > know that the packet was lost due to Path MTU Discovery and > to immediately re-transmit it (without an exponential penalty) > so that the MTU can be probed again. You can still turn path mtu discovery off and Linux will fragment based on the known path MTU (I believe when the too big fragment gets a icmp back the pmtu gets updated) However you might lose a few packets in the process until the path MTU is known, but at least it will stay cached (unless you thrash the routing cache) In theory one could probably add some hack in the the kernel UDP code to hold one packet and retransmit it immediately with fragments when the ICMP comes in. However that would be quite far in behaviour from traditional UDP and be considered very ugly. It could also mess up congestion avoidance schemes done by the application. Still might be preferable over rewriting zillions of applications? -Andi -- ak@...ux.intel.com -- Speaking for myself only. -- 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