From: Roman Mamedov <rm@romanrm.net>
To: XRP <xrp@airmail.cc>
Cc: wireguard@lists.zx2c4.com
Subject: Re: Wireguard fails to start when adding IPv6 to AllowedIP
Date: Thu, 21 Mar 2019 03:36:38 +0500 [thread overview]
Message-ID: <20190321033638.1ff82682@natsu> (raw)
In-Reply-To: <196a105a94a39c3a2e23338880d647f5825dd97a.camel@airmail.cc>
On Sun, 03 Mar 2019 08:56:12 +0100
XRP <xrp@airmail.cc> wrote:
> [#] ip link set mtu 1200 up dev wg1
> [#] ip route add fdb8:a70c:b109:9935::/64 dev wg1
> RTNETLINK answers: No such device
IPv6 cannot work with MTU less than 1280 on the device.
--
With respect,
Roman
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
prev parent reply other threads:[~2019-03-20 22:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-03 7:56 Wireguard fails to start when adding IPv6 to AllowedIP XRP
2019-03-20 22:36 ` Roman Mamedov [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=20190321033638.1ff82682@natsu \
--to=rm@romanrm.net \
--cc=wireguard@lists.zx2c4.com \
--cc=xrp@airmail.cc \
/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).