From: Bzzzz <lazyvirus@gmx.com>
To: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: SSH stuck
Date: Wed, 10 May 2017 21:57:28 +0200 [thread overview]
Message-ID: <20170510215728.23275d88@msi.defcon1> (raw)
In-Reply-To: <CAHmME9rWXev+=cp6FLgwSh+_01nHp7uyRXWGZms9JjfVamhMeg@mail.gmail.com>
On Wed, 10 May 2017 21:00:33 +0200
"Jason A. Donenfeld" <Jason@zx2c4.com> wrote:
> On Wed, May 10, 2017 at 8:05 PM, Bzzzz <lazyvirus@gmx.com> wrote:
> > Correction: 4 bytes: from 1420 to 1416; done by a PostUp.
>
> In the next snapshot, if your primary ethernet device has a
> non-standard MTU, wg-quick will try to figure it out automatically and
> adjust. However, if your end router (adsl modem, for example) is doing
> something odd, you'll have to make this adjustment for yourself. Thus,
> the next version of wg-quick will have also an MTU= directive.
> Hopefully the snapshot will be out somewhat soon.
OK, it's noted.
> > I've also seen something that wasn't much expected:
> > manually changing the MTU from 1418 to 1416 on the server,
> > while VPN was on, also changed the IP address of the WG I/F:
> > inet addr:0.0.5.136 !(?)
>
> That's totally bizarre. I'm guessing you just entered the wrong
> command at some point. That's not wireguard-related code, anyhow.
>
> >>> 1416 & 0xff
> 136
> >>> 1416 >> 8
> 5
You're right, seems tied to the 4.9 kernel &| the ifconfig program
as it does the same weird thing to my eth0 I/F :/
JY
next prev parent reply other threads:[~2017-05-10 19:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-09 22:32 Bzzzz
2017-05-10 7:31 ` Jonathon Fernyhough
2017-05-10 8:10 ` Bzzzz
2017-05-10 8:13 ` Jason A. Donenfeld
2017-05-10 8:35 ` Bzzzz
2017-05-10 18:05 ` Bzzzz
2017-05-10 19:00 ` Jason A. Donenfeld
2017-05-10 19:57 ` Bzzzz [this message]
2017-05-10 21:55 ` Jason A. Donenfeld
2017-05-10 22:08 ` Bzzzz
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=20170510215728.23275d88@msi.defcon1 \
--to=lazyvirus@gmx.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).