On Mon, Nov 12, 2018 at 3:54 PM Jason A. Donenfeld <Jason@xxxxxxxxx> wrote: > > Hey Ivan, > > Sorry for not getting back to you sooner. > > On Mon, Nov 5, 2018 at 8:06 AM Ivan Labáth <labokml@xxxxxxx> wrote: > > Any news on this? > > > > To be clear, question is not about an insignificant documentation > > oversight. It is about copying bits from inner packets to outer packets > > The short answer is RFC6040 with DSCP fixed to 0 so as not to leak > anything. I've added a description of this to > <wireguard.com/protocol/>. you have a speling error (ECM). :) side note: I have to say that wireguard works really well with ecn and non-ecn marked flows against codel and fq_codel on the bottleneck router. I'd still rather like it if wireguard focused a bit more on interleaving multiple flows better rather than on single stream benchmarks, one day. In this case, codel is managing things not fq and we could possibly shave a few ms of induced latency off of it in this particular test series: http://tun.taht.net/~d/wireguard/rrul_-_comcast_v6.png vs wireguard (doing it ivp6 over that ipv6) http://tun.taht.net/~d/wireguard/rrul_-_wireguard.png That said, I've been deploying wireguard widely in replacement of my old tinc network particularly on machines that were formerly cpu bottlenecked and am insanely pleased with it. what's a few extra ms of latency between friends? > > Regards, > Jason -- Dave Täht CTO, TekLibre, LLC http://www.teklibre.com Tel: 1-831-205-9740
