Forums

[stonedface]

If the system shuts down (or is it sleep?) due to battery drain, and you boot it up again after charging, the WireSock VPN client appears in the task manager, but the WireGuard connection is lost.

Windows 11 Pro 23H2

• This topic was modified 2 years ago by stonedface.

[Vadim Smirnov]

Typically, the WireSock VPN client automatically attempts to reconnect if the VPN connection is lost, as in your situation. Could you provide more details, such as the client version and whether you’re running it as a service or an application? Additionally, any logs you can share would be helpful in diagnosing the issue.

[stonedface]

I’m using the latest 1.4.7.1 version as a service at the system is HP 14s with RTL 8821CE 802.11ac PCIe adapter. This device driver is a constant troublemaker according to various forums. There is a network speed drop every time it connects after sleep.

[Vadim Smirnov]

Collecting logs after wake-up could provide valuable insights into what’s happening.

[stonedface]

2024-09-11 18:02:34 [TUN]: keep_alive_thread: Sending Handshake packet to WireGuard Server success

2024-09-11 18:02:34 [TUN]: Handshake response received from 192.168.18.135 : 56053
2024-09-11 18:02:37 [TUN]: keep_alive_thread: Sending Keepalive packet to WireGuard Server success

2024-09-11 18:02:43 [FILTER]: MDCoreSvc : TCP : 192.168.18.135:52197 -> 52.113.194.132:443
2024-09-11 18:03:02 [TUN]: keep_alive_thread: error sending packet to WireGuard Server

2024-09-11 18:03:02 [TUN]: keep_alive_thread: Critical socket error detected. Trying to restart the tunnel!

2024-09-11 18:03:02 [TUN]: WireGuard tunnel was successfully stopped!
2024-09-11 18:14:24 [TUN]: Detected default interface {493A19C1-11B8-4097-8334-A3F71ABBA8BE}
2024-09-11 18:14:24 [TUN]: Using local IPv4 = 192.168.18.135 for the {493A19C1-11B8-4097-8334-A3F71ABBA8BE}
2024-09-11 18:14:24 [TUN]: Local IPv6 address for the {493A19C1-11B8-4097-8334-A3F71ABBA8BE} not available
2024-09-11 18:14:24 [TUN]: error sending handshake packet to WireGuard Server

[Vadim Smirnov]

It appears the system entered sleep mode at 18:03:02 and resumed at 18:14:24, right? However, the error remains unclear—it looks like the handshake packet failed to send over the UDP socket. I can build a version with extended logging to gather more details. At the very least, knowing the specific error code would be helpful. Is the Internet connection functioning correctly after the resume?

[stonedface]

With the previous version of wiresock i was experiencing this error on sleep. But with the latest version that doesn’t seem to happen as far as i have noticed. Since the network driver i mentioned have speed drop after waking from sleep, i have set sleep off.

The internet connection works correctly after the resume. There is no speed drop also. I have found a workaround of this wiresock issue by creating a task which  stops and starts the service again on workstation unlock.

[Author]

Posts