Development discussion of WireGuard
 help / color / mirror / Atom feed
From: Chengbo Zhao <cbzhao.cn@gmail.com>
To: wireguard@lists.zx2c4.com
Subject: Upload speed slow in Windows through ipv6
Date: Sun, 13 Aug 2023 21:36:18 +0800	[thread overview]
Message-ID: <CAMFsdgwjDzvLtJS5R_t1CMeP2zQkmMMRUCHtXro-vwJxDF_O_Q@mail.gmail.com> (raw)

Hello:

I just changed my way back home from OpenVPN to WireGuard. Nice work,
faster and easier to configure!

But when I tried to connect through ipv6, I had some troubles: the
download speed seems normal, but upload speed (Both to LAN and WAN)
was limited to ~10Mbps (about 10~20% of full speed).

I thought it was a network issue at first, so I used a process of
elimination to find out what went wrong. On the mobile phone, using
the same configuration, both upload and download can reach the upload
rate of my broadband ~60Mbps. This indicates that the computer may not
be working properly. So, I went on to test on my laptop and found that
when using ipv4 for connection, the upload and download can also run
at full speed. I guess that there may be a performance problem with
the forwarding of ipv6 packets in WireGuard NT. By the way, I just
configure ipv4 for all clients in WireGuard's internal network.

  Test Device     ipv4-download   ipv4-upload   ipv6-download   ipv6-upload
 --------------- --------------- ------------- --------------- -------------
  PC-Win11        ~60Mbps         ~60Mbps       ~60Mbps         ~10Mbps
  Phone-Android   ~60Mbps         ~60Mbps       ~60Mbps         ~60Mbps

Can you guys do further tests to resolve this issue?

---
Thanks,
Chengbo Zhao

                 reply	other threads:[~2023-12-20  5:25 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=CAMFsdgwjDzvLtJS5R_t1CMeP2zQkmMMRUCHtXro-vwJxDF_O_Q@mail.gmail.com \
    --to=cbzhao.cn@gmail.com \
    --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).