On Wed, 10 May 2017 21:00:33 +0200 "Jason A. Donenfeld" <[email protected]> wrote:
> On Wed, May 10, 2017 at 8:05 PM, Bzzzz <[email protected]> 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 _______________________________________________ WireGuard mailing list [email protected] https://lists.zx2c4.com/mailman/listinfo/wireguard
