From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Roman Mamedov <rm@romanrm.net>
Cc: Luis Ressel <aranea@aixah.de>,
WireGuard mailing list <wireguard@lists.zx2c4.com>,
Roman Mamedov <rm.wg@romanrm.net>
Subject: Re: Mixed MTU hosts on a network
Date: Sat, 14 Apr 2018 16:45:32 +0200 [thread overview]
Message-ID: <CAHmME9ra=DZiaUS7pP3xAxC_7H-yqfiTefU3Q8gufpP7e6H2zw@mail.gmail.com> (raw)
In-Reply-To: <20180414193815.0d0cd039@natsu>
Hi Roman,
That's strange; I'm unable to reproduce what you've described:
[+] NS1: ip link set wg0 mtu 1412
[+] NS2: ip link set wg0 mtu 1412
[+] NS1: wg set wg0 peer QXloTaPOwUTzqFElVLSD0vBc4sxjyoKtPBSaTkZHokY=
endpoint 127.0.0.1:2
[+] NS2: wg set wg0 peer X0p7+UWc4wjaAmT73xAEuXLY80I6Gv8vTg6KwFHCPGs=
endpoint 127.0.0.1:1
[+] NS0: iptables -A INPUT -m length --length 1473 -j DROP
[+] NS2: ping -c 1 -W 1 -s 1384 192.168.241.1
PING 192.168.241.1 (192.168.241.1) 1384(1412) bytes of data.
1392 bytes from 192.168.241.1: icmp_seq=1 ttl=64 time=0.752 ms
--- 192.168.241.1 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.752/0.752/0.752/0.000 ms
In this case, WireGuard seems to be doing the right thing. Think you
could come up with some minimal test that exhibits the behavior you're
seeing?
Jason
next prev parent reply other threads:[~2018-04-14 14:31 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-16 9:25 Roman Mamedov
2018-03-16 9:35 ` Matthias Ordner
2018-03-16 10:53 ` Roman Mamedov
2018-03-16 16:20 ` Roman Mamedov
2018-03-16 10:01 ` Kalin KOZHUHAROV
2018-03-26 19:12 ` Luis Ressel
2018-04-14 1:38 ` Jason A. Donenfeld
2018-04-14 2:40 ` Jason A. Donenfeld
2018-04-14 13:16 ` Jason A. Donenfeld
2018-04-14 13:40 ` Roman Mamedov
2018-04-14 14:15 ` Jason A. Donenfeld
2018-04-14 14:38 ` Roman Mamedov
2018-04-14 14:45 ` Jason A. Donenfeld [this message]
2018-04-14 15:20 ` Roman Mamedov
2018-04-14 23:08 ` Jason A. Donenfeld
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='CAHmME9ra=DZiaUS7pP3xAxC_7H-yqfiTefU3Q8gufpP7e6H2zw@mail.gmail.com' \
--to=jason@zx2c4.com \
--cc=aranea@aixah.de \
--cc=rm.wg@romanrm.net \
--cc=rm@romanrm.net \
--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).