From: Roman Mamedov <email@example.com> To: Houman <firstname.lastname@example.org> Cc: Janne Johansson <email@example.com>, WireGuard mailing list <firstname.lastname@example.org> Subject: Re: How to improve Wireguard speed? Date: Wed, 1 Jun 2022 14:51:43 +0500 [thread overview] Message-ID: <20220601145143.75234bd8@nvm> (raw) In-Reply-To: <CABBZOs=kxe4DwHN=utdb8FzDTt3=TcSo05JVAo=-JCUjC_eEug@mail.gmail.com> On Wed, 1 Jun 2022 10:07:31 +0100 Houman <email@example.com> wrote: > I didn't change the MTU settings, but I have a suspicion about MTU. I > found this article here that makes some interesting suggestions to set > MTU to 1280: https://keremerkan.net/posts/wireguard-mtu-fixes/ > > And beyond that iptables -A FORWARD -p tcp --tcp-flags SYN,RST SYN -j > TCPMSS --clamp-mss-to-pmtu So did you apply both of that, and what was the effect? What are the other point that you test against, is it another VPS (better if you could try with that), or your home connection? It could be your home provider has different speed limits (shaping) in place for UDP. Should be possible to test this with: iperf3 -s # on VPS iperf3 -u -b 500M -c <VPS IP> -R # on the other side And then see how many "Lost/Total Datagrams" (xx %) you get. A high percentage would indicate that the actual top speed for UDP is less than 500Mbit by this value. -- With respect, Roman
next prev parent reply other threads:[~2022-06-01 9:54 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-06-01 7:42 Houman 2022-06-01 8:50 ` Janne Johansson 2022-06-01 9:07 ` Houman 2022-06-01 9:51 ` Roman Mamedov [this message] 2022-06-01 11:40 ` Houman 2022-06-01 12:41 ` Frank Carmickle
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=20220601145143.75234bd8@nvm \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: How to improve Wireguard speed?' \ /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
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).