<div dir="ltr"><div>After normal server reboot (manual), the tunnel comes up automatically.</div><div>In past it happened several times, that suddenly clients were not able to connect, I thought it was a bug and would be solved in next version, so I didn't pay much attention to it. <br></div><div>Just after the recent incident, It happened to be right after the reboot caused by windows updates and I started looking into the logs.<br></div><div><br></div><div>The last updates were:</div><div>- 2020-01 Cumulative Update for .NET</div><div>- 2020-01 Cumulative update for window server 2019 (1809)</div><div>- Windows malicious software removal tool x64 - january 2020<br></div><div><br></div><div>I will watch more closely and collect logs by the next occurrence.</div><div><br></div><div>Thanks</div><div>Peter<br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sun, 26 Jan 2020 at 10:57, Jason A. Donenfeld <<a href="mailto:Jason@zx2c4.com">Jason@zx2c4.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="auto">Thanks for the report. Is this reproducible every time you reboot your system, or only that one time after Windows Update?<div dir="auto"><br></div><div dir="auto">If the latter, do you have a list of what was being updated?</div><div dir="auto"><br></div><div dir="auto">Thanks,</div><div dir="auto">Jason</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Jan 22, 2020, 20:51 Peter Selc <<a href="mailto:peter.selc@gmail.com" target="_blank">peter.selc@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div>Hello all,</div><div><br></div><div>I'm running version 0.0.38 on Windows 2019 server. Admin user logs in, starts the tunnel via GUI, disconnects from RDP session. Clients can connect.</div><div><br></div><div>After the server is rebooted (windows updates), the tunnel doesn't come up automatically as it should, error is:</div><div><br></div><div>2020-01-15 15:00:56.197: [TUN] [Server] peer(SuXT…9iko) - Sending keepalive packet<br>2020-01-15 15:01:06.198: [TUN] [Server] peer(SuXT…9iko) - Sending keepalive packet<br>2020-01-15 15:01:31.236: [TUN] [Server] peer(SuXT…9iko) - Receiving keepalive packet<br>2020-01-15 15:01:49.729: [TUN] [Server] peer(SuXT…9iko) - Sending keepalive packet<br>2020-01-15 15:09:43.727: [TUN] [Server] peer(SuXT…9iko) - Removing all keys, since we haven't received a new one in 540 seconds<br><br>-- reboot happens here--<br><br>2020-01-15 17:19:00.356: [MGR] Exited UI process for user 'admin_user@winserver' for session 2 with status 40010004<br>2020-01-15 17:19:01.417: [MGR] Starting UI process for user ‘admin_user@winserver’ for session 2<br>2020-01-15 17:19:02.350: [MGR] Exited UI process for user 'admin_user@winserver' for session 2 with status 1<br>2020-01-15 17:19:46.142: [TUN] [Server] Device closing<br>2020-01-15 17:19:46.146: [TUN] [Server] Routine: TUN reader - stopped<br>2020-01-15 17:19:46.217: [TUN] [Server] Routine: event worker - stopped<br>2020-01-15 17:19:46.222: [TUN] [Server] Routine: receive incoming IPv4 - stopped<br>2020-01-15 17:19:46.223: [TUN] [Server] Routine: receive incoming IPv6 - stopped<br>2020-01-15 17:19:46.223: [TUN] [Server] Routine: decryption worker - stopped<br>2020-01-15 17:19:46.224: [TUN] [Server] peer(1WB6…G/xk) - Stopping...<br>2020-01-15 17:19:46.224: [TUN] [Server] peer(1WB6…G/xk) - Routine: sequential receiver - stopped<br>2020-01-15 17:19:46.225: [TUN] [Server] peer(1WB6…G/xk) - Routine: nonce worker - stopped<br>2020-01-15 17:19:46.225: [TUN] [Server] Routine: encryption worker - stopped<br>2020-01-15 17:19:46.225: [TUN] [Server] Routine: handshake worker - stopped<br>2020-01-15 17:19:46.226: [TUN] [Server] Routine: encryption worker - stopped<br>2020-01-15 17:19:46.228: [TUN] [Server] Routine: decryption worker - stopped<br>2020-01-15 17:19:46.228: [TUN] [Server] Routine: handshake worker - stopped<br>2020-01-15 17:19:46.229: [TUN] [Server] peer(1WB6…G/xk) - Routine: sequential sender - stopped<br>2020-01-15 17:19:46.229: [TUN] [Server] peer(akUl…uaHM) - Stopping...<br>2020-01-15 17:19:46.230: [TUN] [Server] peer(akUl…uaHM) - Routine: sequential receiver - stopped<br>2020-01-15 17:19:46.268: [TUN] [Server] peer(akUl…uaHM) - Routine: sequential sender - stopped<br>2020-01-15 17:19:46.280: [TUN] [Server] peer(akUl…uaHM) - Routine: nonce worker - stopped<br>2020-01-15 17:19:46.319: [TUN] [Server] peer(UUvS…DwEo) - Stopping...<br>2020-01-15 17:19:46.321: [TUN] [Server] peer(UUvS…DwEo) - Routine: sequential receiver - stopped<br>2020-01-15 17:19:46.321: [TUN] [Server] peer(UUvS…DwEo) - Routine: sequential sender - stopped<br>2020-01-15 17:19:46.322: [TUN] [Server] peer(UUvS…DwEo) - Routine: nonce worker - stopped<br>2020-01-15 17:19:46.322: [TUN] [Server] peer(SuXT…9iko) - Stopping...<br>2020-01-15 17:19:46.322: [TUN] [Server] peer(SuXT…9iko) - Routine: sequential receiver - stopped<br>2020-01-15 17:19:46.323: [TUN] [Server] peer(SuXT…9iko) - Routine: nonce worker - stopped<br>2020-01-15 17:19:46.323: [TUN] [Server] peer(SuXT…9iko) - Routine: sequential sender - stopped<br>2020-01-15 17:19:46.324: [TUN] [Server] peer(JRsL…401s) - Stopping...<br>2020-01-15 17:19:46.325: [TUN] [Server] peer(JRsL…401s) - Routine: sequential receiver - stopped<br>2020-01-15 17:19:46.325: [TUN] [Server] peer(JRsL…401s) - Routine: nonce worker - stopped<br>2020-01-15 17:19:46.326: [TUN] [Server] peer(JRsL…401s) - Routine: sequential sender - stopped<br>2020-01-15 17:19:46.326: [TUN] [Server] peer(mWrq…/Xnc) - Stopping...<br>2020-01-15 17:19:46.327: [TUN] [Server] peer(mWrq…/Xnc) - Routine: sequential receiver - stopped<br>2020-01-15 17:19:46.327: [TUN] [Server] peer(mWrq…/Xnc) - Routine: sequential sender - stopped<br>2020-01-15 17:19:46.328: [TUN] [Server] peer(mWrq…/Xnc) - Routine: nonce worker - stopped<br>2020-01-15 17:19:46.328: [TUN] [Server] Interface closed<br>2020-01-15 17:19:46.328: [TUN] [Server] Shutting down<br>2020-01-15 17:21:00.637: [MGR] Starting WireGuard/0.0.38 (Windows Server 10.0.17763; amd64)<br>2020-01-15 17:21:00.637: [TUN] [Server] Starting WireGuard/0.0.38 (Windows Server 10.0.17763; amd64)<br>2020-01-15 17:21:00.760: [TUN] [Server] SCM locked for 27s by .\NT Service Control Manager, marking service as started<br>2020-01-15 17:21:00.784: [TUN] [Server] Watching network interfaces<br>2020-01-15 17:21:00.837: [TUN] [Server] Resolving DNS names<br>2020-01-15 17:21:01.033: [TUN] [Server] Creating Wintun interface<br>2020-01-15 17:21:08.159: [TUN] [Server] Unable to create Wintun interface: Error creating interface: SetupDiCallClassInstaller(DIF_REGISTERDEVICE) failed: winapi error #3758096907<br>2020-01-15 17:21:08.207: [TUN] [Server] Shutting down<br>2020-01-15 17:21:11.161: [MGR] Removing Wintun interface ‘Local Area Connection’ because determining tunnel service name failed: Tunnel name is not valid</div><div><br></div><div>Is this some known behaviour with a known fix, or not supported yet?<br></div><div>Many thanks,</div><div><br></div><div>Peter<br></div></div>
_______________________________________________<br>
WireGuard mailing list<br>
<a href="mailto:WireGuard@lists.zx2c4.com" rel="noreferrer" target="_blank">WireGuard@lists.zx2c4.com</a><br>
<a href="https://lists.zx2c4.com/mailman/listinfo/wireguard" rel="noreferrer noreferrer" target="_blank">https://lists.zx2c4.com/mailman/listinfo/wireguard</a><br>
</blockquote></div>
</blockquote></div>