From 46aa7a787bc22049a6dd1b96782a6e6e45de88c5 Mon Sep 17 00:00:00 2001 From: Neil Alexander Date: Fri, 13 Jul 2018 12:09:15 +0100 Subject: [PATCH] Update title --- _posts/2018-07-13-about-mtu.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/_posts/2018-07-13-about-mtu.md b/_posts/2018-07-13-about-mtu.md index ba7c86c..c09f602 100644 --- a/_posts/2018-07-13-about-mtu.md +++ b/_posts/2018-07-13-about-mtu.md @@ -43,10 +43,10 @@ link with an MTU of 1500 would require the packet to be fragmented 43 times, right? Instead, Yggdrasil uses TCP connections for peerings. This not only allows us to -take advantage of SOCKS proxies in a way that we cannot with UDP, but it also -gives us stream properties on our connections instead of being manually forced -to chunk UDP packets. In fact, we did this in the past, and it was ugly, and -actually worse than TCP performance-wise in many cases. +take advantage of SOCKS proxies (and Tor) in a way that we cannot with UDP, but +it also gives us stream properties on our connections instead of being manually +forced to chunk UDP packets. In fact, we did this in the past, and it was ugly, +and actually worse than TCP performance-wise in many cases. TCP will adjust the window size to match the lower link - in this case a probable 1500 MTU - and will stream the large packet in chunks until it arrives