wireguard.lists.zx2c4.com archive mirror
 help / color / mirror / Atom feed
From: Vasili Pupkin <diggest@gmail.com>
To: alpha_one_x86 <alpha_one_x86@first-world.info>,
	wireguard@lists.zx2c4.com
Subject: Re: Buggy MTU with Wireguard (attached pcapng)
Date: Mon, 3 Feb 2020 21:04:23 +0300	[thread overview]
Message-ID: <139c80c5-64f4-217a-f08c-e612e0591b85@gmail.com> (raw)
In-Reply-To: <1a0f7114-37dc-64e5-fded-03863c98add5@first-world.info>


[-- Attachment #1.1: Type: text/plain, Size: 959 bytes --]

The TCP connection MSS is set to 1460 bytes and also Don't fragment flag 
is set. The server selects this MSS as a frame size on its side and 
packet is dropped, probably. If you are using linux router try to use 
this command "iptables -I FORWARD -p tcp --tcp-flags SYN,RST SYN -j 
TCPMSS --clamp-mss-to-pmtu" or be careful to set MTU on all client 
machines adapters correctly.


On 10.01.2020 1:05, alpha_one_x86 wrote:
>
> Hi,
>
> I have wireguard interface "veth", and my real interface "eth0".
>
> No bug with openvpn, but with wireguard on IPv4 for https, I have bug, 
> see the attached file, the returned data is 3300byte, then Destination 
> unreachable (Fragmentation needed).
>
> Bug into wireguard? How fix this?
>
> The ok.pcapng it's same https download do with openvpn.
>
> Cheers,
>
>
> _______________________________________________
> WireGuard mailing list
> WireGuard@lists.zx2c4.com
> https://lists.zx2c4.com/mailman/listinfo/wireguard


[-- Attachment #1.2: Type: text/html, Size: 2093 bytes --]

[-- Attachment #2: Type: text/plain, Size: 148 bytes --]

_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard

      reply	other threads:[~2020-02-03 18:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-09 22:05 Buggy MTU with Wireguard (attached pcapng) alpha_one_x86
2020-02-03 18:04 ` Vasili Pupkin [this message]

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=139c80c5-64f4-217a-f08c-e612e0591b85@gmail.com \
    --to=diggest@gmail.com \
    --cc=alpha_one_x86@first-world.info \
    --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).