On 12/18/20, Janne Johansson <icepic...@gmail.com> wrote: > Den tors 17 dec. 2020 kl 22:56 skrev Jason A. Donenfeld <ja...@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.
