From: Silvan Nagl <mail@53c70r.de>
To: wireguard@lists.zx2c4.com
Subject: Re: wg-quick up automation fails
Date: Sun, 2 Jun 2019 12:38:38 +0200 [thread overview]
Message-ID: <978138c3-3366-72f0-3950-3e33e5eeefe5@53c70r.de> (raw)
In-Reply-To: <125a5194-c3c3-a409-3673-e2c752c398bf@53c70r.de>
Hi again,
i just noticed my default interface has MTU 1348 so when i am connected
to this one and use wg-quick it will break. Disconnecting from it first
and than using wg-quick will set higher MTUs on the WireGuard interface
so it wont break for ipv6.
Greetings,
53c70r
On 6/2/19 12:27 PM, Silvan Nagl wrote:
> Hi,
>
> as i already mentioned the problem persists on master branch for me.
>
> Greetings,
>
> 53c70r
>
> On 6/2/19 8:32 AM, XRP wrote:
>> On Sun, 2019-06-02 at 01:49 +0200, Silvan Nagl wrote:
>>> G'day,
>>>
>>> i recently upgrade WireGuard to the latest shipped Debian version
>>> (0.0.20190406-1) and noticed my wg-quick created interface did not
>>> come
>>> up as usual anymore. (Also tried the git master branch) I tried to
>>> single command trough wg-quick's automation to reproduce the error;
>>>
>>> automatic:
>>>
>>> [#] ip link add Y type wireguard
>>> [#] wg setconf Y /dev/fd/63
>>> [#] ip address add X.X.X.X/32 dev Y
>>> [#] ip address add fc00::XXXX/128 dev Y
>>> [#] ip link set mtu XXXX up dev Y
>>> [#] resolvconf -a tun.Y -m 0 -x
>>> [#] wg set Y fwmark 51820
>>> [#] ip -6 route add ::/0 dev Y table 51820
>>> RTNETLINK answers: No such device
>>> [#] resolvconf -d tun.Y
>>> [#] ip link delete dev Y
>>>
>>> manual:
>>>
>>>> ip link add Y type wireguard
>>>> wg setconf Y <(wg-quick strip /etc/wireguard/Y.conf)
>>>> ip address add X.X.X.X/32 dev Y
>>>> ip address add fc00::XXXX/128 dev Y
>>>> ip link set mtu 1268 up dev Y
>>>> resolvconf -a tun.X -m 0 -x
>>>> wg set Y fwmark 51820
>>>> ip -6 route add ::/0 dev Y table 51820
>>> < RTNETLINK answers: No such device
>>>
>>> (MTU may be to low here so i set it higher again)
>>>
>>>> ip link set mtu 1420 up dev Y
>>>> ip -6 route add ::/0 dev Y table 51820 (works now)
>>> breaks up @ this point because of error handling...
>>>
>>> Additionally it could be possible the MTU isn't set correctly.
>> I had a similar problem where I got a "RTNETLINK answers: No such
>> device" error. After that I tried to use the wg-quick version in the
>> master branch and that fixed my problem. I hope that helps.
>>
>> (MTU for IPv6 must be 1280 bytes at least.)
>>
> _______________________________________________
> WireGuard mailing list
> WireGuard@lists.zx2c4.com
> https://lists.zx2c4.com/mailman/listinfo/wireguard
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
prev parent reply other threads:[~2019-06-02 10:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-01 23:49 wg-quick up automation fails Silvan Nagl
2019-06-02 6:32 ` XRP
2019-06-02 10:27 ` Silvan Nagl
2019-06-02 10:38 ` Silvan Nagl [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=978138c3-3366-72f0-3950-3e33e5eeefe5@53c70r.de \
--to=mail@53c70r.de \
--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).