From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: k@vodka.home.kg
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: [WireGuard] heavy packet loss
Date: Fri, 4 Nov 2016 17:04:29 +0100 [thread overview]
Message-ID: <CAHmME9r6uS+vwiKOjzk9FAAKLTxTst3E0vPiwt2=2FmDd+RmBw@mail.gmail.com> (raw)
In-Reply-To: <1518389796.20161104190140@vodka.home.kg>
Hi k,
I'll look into this. Which snapshot are you using? Or, which commit is this?
Jason
On Fri, Nov 4, 2016 at 5:01 PM, <k@vodka.home.kg> wrote:
> I'm trying to connect 2 endpoints with wireguard.
> One endpoint has MTU of inet inteface 1500, another 1456.
> To prevent packet fragmentation on inet interface i set up mtu 1383 for both wg interfaces. Checked that no frag occurs on inet interface in wireshark. Maximum packet data size is 1383-28 = 1355. Checked with no-fragment ping, packets pass well.
>
> First I checked packet loss between inet IPs
>
> iperf -c x.x.x.x -u -b 25M -l 1400
> 0.0-10.3 sec 29.6 MBytes 24.2 Mbits/sec 16.073 ms 175/23090 (0.76%)
>
> packet loss always within 0.5..1%. its normal
> now I try to do the same with much less bandwidth between wireguard ips
> on packet size <=1252 packet loss rate is 0.5..1%
>
> iperf -c 192.168.254.65 -w 500000 -u -b 1M -l 1252
> 0.0-10.0 sec 1.18 MBytes 991 Kbits/sec 0.659 ms 9/ 1000 (0.9%)
>
> but starting from packet size 1253 packets loss greatly increases. its 6..10%
>
> iperf -c 192.168.254.65 -w 500000 -u -b 1M -l 1253
> 0.0-10.0 sec 1.12 MBytes 936 Kbits/sec 0.328 ms 64/ 998 (6.4%)
>
> Thats why TCP is incredibly slow. If I set up mss for TCP to not exceed packets size threshold TCP is fast.
>
> _______________________________________________
> WireGuard mailing list
> WireGuard@lists.zx2c4.com
> http://lists.zx2c4.com/mailman/listinfo/wireguard
next prev parent reply other threads:[~2016-11-04 16:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-04 16:01 k
2016-11-04 16:04 ` Jason A. Donenfeld [this message]
2016-11-04 16:18 ` k
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAHmME9r6uS+vwiKOjzk9FAAKLTxTst3E0vPiwt2=2FmDd+RmBw@mail.gmail.com' \
--to=jason@zx2c4.com \
--cc=k@vodka.home.kg \
--cc=wireguard@lists.zx2c4.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).