From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Janne Johansson <icepic.dz@gmail.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: WireGuard on macOS stopped working after 1.0.10 update
Date: Fri, 18 Dec 2020 10:19:20 +0100 [thread overview]
Message-ID: <CAHmME9o8VcMiDwCCkOmke25uRFHKSh1Enri4bJ6te014nkPjkA@mail.gmail.com> (raw)
In-Reply-To: <CAA6-MF8ZZ1eD+7wTfgzuGaiw8JPM+WiivJ0CxBja3-GZ=GXMaA@mail.gmail.com>
On 12/18/20, Janne Johansson <icepic.dz@gmail.com> wrote:
> Den tors 17 dec. 2020 kl 22:56 skrev Jason A. Donenfeld <Jason@zx2c4.com>:
>> The macOS update went through, and version 1.0.11 is now available
>> from the App Store. In my tests, this fixes the issue, but some
>> confirmation from list subscribers is always helpful.
>
> So I held off updating until 1.0.11 was out (even though I already used to
> have a DNS = entry in the [Interface] section),
> but to my surprise I could not form a tunnel with my old configs. The gui
> says "I sent 186 bytes" (number not necessarily correct)
> and tcpdump showed I sent a packet to remote, it sent one back and after
> that tcpdump goes silent.
>
> The wg gui logs just went:
>
> 2020-12-18 08:48:52.045 [NET] peer(RQkh…JERY) - Failed to send handshake
> initiation no bind
> 2020-12-18 08:48:57.297 [NET] peer(RQkh…JERY) - Handshake did not complete
> after 5 seconds, retrying (try 2)
> 2020-12-18 08:48:57.297 [NET] peer(RQkh…JERY) - Sending handshake
> initiation
> 2020-12-18 08:48:57.298 [NET] peer(RQkh…JERY) - Failed to send handshake
> initiation no bind
> 2020-12-18 08:49:02.546 [NET] peer(RQkh…JERY) - Sending handshake
> initiation
> 2020-12-18 08:49:02.547 [NET] peer(RQkh…JERY) - Failed to send handshake
> initiation no bind
>
> So I tried removing my DNS entry, and now it works. So you seem to have
> made it the opposite in 1.0.11, now one can't have DNS in the [Interface]
> section, or the tunnel will not start.
> I run my own resolver on 127.0.0.1 for now, so I can work around it, but
> this seems very weird too.
Please send the complete logs along with the (redacted) configuration
file that caused the issue. I need to be able to reproduce the issue
in order to evaluate it.
next prev parent reply other threads:[~2020-12-18 9:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-16 23:52 Glenn Schmidt
2020-12-17 1:43 ` Jason A. Donenfeld
2020-12-17 2:09 ` Glenn Schmidt
2020-12-17 21:53 ` Jason A. Donenfeld
2020-12-17 22:34 ` Nicolas CAPEYRON
[not found] ` <CAA6-MF8ZZ1eD+7wTfgzuGaiw8JPM+WiivJ0CxBja3-GZ=GXMaA@mail.gmail.com>
2020-12-18 9:19 ` Jason A. Donenfeld [this message]
2020-12-18 23:53 ` Jason A. Donenfeld
2020-12-19 0:11 ` Jacob Lambert
2020-12-19 10:40 ` Jason A. Donenfeld
2020-12-17 15:19 Nicolas CAPEYRON
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=CAHmME9o8VcMiDwCCkOmke25uRFHKSh1Enri4bJ6te014nkPjkA@mail.gmail.com \
--to=jason@zx2c4.com \
--cc=icepic.dz@gmail.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).