This repository was archived by the owner on Nov 18, 2025. It is now read-only.
[bug] wiresockUI and wiresock-client.exe -lac watchdog cyclic restart #97
Description
WireSockUI v0.2.8 ran first, created the tunnel interface. Ran into issues, attempted to use the severely handicapped WireSockUI logging capability in that tiny window with no filtering, copy-pasting, lines flying through I'd have to record my screen to read that. Impossible to see what's going on.
Started wiresock-client.exe with the same config and -lac switch first as a regular user: it could not modify the virtual adapter 🙄 blah blah permissions, regedit, restart windows, blah blah. Likely because WireSockUI creates it with permissions other than the user running the software.
2025-01-20 13:10:57 WireSock WireGuard VPN Client Service 1.4.7
The service is starting using C:\Users\me\AppData\Roaming\WireSockUI\Configs\wiresock.conf WireGuard client configuration.
WireSock WireGuard VPN Client 1.4.7 is running as a regular process.
2025-01-20 13:10:57 WireSock Service has started.
2025-01-20 13:10:57 [MGR]: Using WireGuard server: WIREGUARD_SERVER : 250
2025-01-20 13:10:57 Successfully renamed the network connection accordingly active profile.
2025-01-20 13:10:57 [TUN]: Failed to assign DNS to WireSock virtual adapter!
2025-01-20 13:10:57 [TUN]: WireSock virtual adapter is not available!
2025-01-20 13:10:57 [MGR]: Tunnel has failed to start
2025-01-20 13:10:57 [TUN]: cancel_notify_ip_interface_change has failed, lasterror: 6
2025-01-20 13:10:57 WireGuard tunnel has failed to start.
2025-01-20 13:10:57 Switching WireGuard configuration to C:\Users\me\AppData\Roaming\WireSockUI\Configs\wiresock.conf
2025-01-20 13:10:58 [MGR]: Using WireGuard server: WIREGUARD_SERVER : 250
2025-01-20 13:10:58 Successfully renamed the network connection accordingly active profile.
2025-01-20 13:10:58 [TUN]: Failed to assign DNS to WireSock virtual adapter!
2025-01-20 13:10:58 [TUN]: WireSock virtual adapter is not available!
2025-01-20 13:10:58 [MGR]: Tunnel has failed to start
2025-01-20 13:10:58 [TUN]: cancel_notify_ip_interface_change has failed, lasterror: 6
2025-01-20 13:10:58 WireGuard tunnel has failed to start.So I started it from an administrator prompt. Now it has access to modify the virtual adapter but the watchdog process issues a restart every few seconds. I don't think it sees the tunnel being up. If I drop the -lac switch, it works just fine.
2025-01-20 13:31:52 WireSock WireGuard VPN Client Service 1.4.7
The service is starting using C:\Users\me\AppData\Roaming\WireSockUI\Configs\wiresock.conf WireGuard client configuration.
WireSock WireGuard VPN Client 1.4.7 is running as a regular process.
2025-01-20 13:31:52 WireSock Service has started.
2025-01-20 13:31:52 [MGR]: Using WireGuard server: WIREGUARD_SERVER : 250
2025-01-20 13:31:52 Successfully renamed the network connection accordingly active profile.
2025-01-20 13:31:52 [TUN]: WireSock virtual adapter successfully identified
2025-01-20 13:31:54 [TUN]: Detected default interface {17A2F72B-4289-9E98-A8E0-2DC89B121B8C}
2025-01-20 13:31:54 [TUN]: start_internal: NDIS filter successfully started for the default network interface!
2025-01-20 13:31:54 [TUN]: Sent handshake packet to the WireGuard server at WIREGUARD_SERVER:250
2025-01-20 13:31:54 [TUN]: start_internal: Starting keep-alive thread!
2025-01-20 13:31:54 [MGR]: Tunnel has started
2025-01-20 13:31:54 Wireguard tunnel has been started.
2025-01-20 13:31:54 [TUN]: watchdog: started!
2025-01-20 13:31:54 [TUN]: keep_alive_thread: Started!
2025-01-20 13:31:54 [FILTER]: C:\Users\me\AppData\Local\Programs\Opera\opera.exe : UDP : LOCAL_MACHINE:54769 -> 239.255.255.250:1900
2025-01-20 13:31:54 [FILTER]: Skipping C:\ProgramData\Safing\Portmaster\updates\windows_amd64\core\portmaster-core_v1-6-28.exe : TCP : LOCAL_MACHINE:32036 -> 1.0.0.1:853
2025-01-20 13:31:57 [FILTER]: Skipping D:\Jellyfin_Server\Server\jellyfin.exe : TCP : LOCAL_MACHINE:8096 <- LAN_MACHINE:48868
2025-01-20 13:31:59 [TUN]: keep_alive_thread: Sending packet to WireGuard Server success
2025-01-20 13:31:59 [TUN]: wireguard_read returned: result = 2 size = 13
2025-01-20 13:31:59 [TUN]: watchdog: Tunnel is not active. Last restart was over 5s timeout. Schedule restart attempt!
2025-01-20 13:31:59 [TUN]: wireguard_read returned: result = 2 size = 13
2025-01-20 13:31:59 [TUN]: wireguard_read returned: result = 2 size = 13
2025-01-20 13:31:59 [TUN]: keep_alive_thread: exiting
2025-01-20 13:31:59 [TUN]: internal_restart: WireGuard tunnel was successfully stopped!
2025-01-20 13:31:59 [TUN]: WireSock virtual adapter successfully identified
2025-01-20 13:32:01 [TUN]: Detected default interface {17A2F72B-4289-9E98-A8E0-2DC89B121B8C}
2025-01-20 13:32:01 [TUN]: start_internal: NDIS filter successfully started for the default network interface!
2025-01-20 13:32:01 [TUN]: Sent handshake packet to the WireGuard server at WIREGUARD_SERVER:250
2025-01-20 13:32:01 [TUN]: start_internal: Starting keep-alive thread!
2025-01-20 13:32:01 [TUN]: internal_restart: WireGuard tunnel was successfully started!
2025-01-20 13:32:01 [TUN]: watchdog: WireGuard tunnel was successfully started!
2025-01-20 13:32:01 [TUN]: keep_alive_thread: Started!
2025-01-20 13:32:01 [TUN]: wireguard_read returned: result = 2 size = 13
2025-01-20 13:32:01 [TUN]: wireguard_read returned: result = 2 size = 13
2025-01-20 13:32:01 [TUN]: wireguard_read returned: result = 2 size = 13
2025-01-20 13:32:01 [TUN]: wireguard_read returned: result = 2 size = 13
2025-01-20 13:32:01 [FILTER]: C:\Users\me\AppData\Local\Programs\Opera\opera.exe : UDP : LOCAL_MACHINE:61433 -> 239.255.255.250:1900
2025-01-20 13:32:02 [FILTER]: Skipping D:\Jellyfin_Server\Server\jellyfin.exe : TCP : LOCAL_MACHINE:8096 <- LAN_MACHINE:48880
2025-01-20 13:32:03 [TUN]: wireguard_read returned: result = 2 size = 13
2025-01-20 13:32:03 [TUN]: wireguard_read returned: result = 2 size = 13
2025-01-20 13:32:04 [TUN]: watchdog: Tunnel is not active. Last restart was over 5s timeout. Schedule restart attempt!
2025-01-20 13:32:05 [TUN]: keep_alive_thread: exiting
2025-01-20 13:32:05 [TUN]: internal_restart: WireGuard tunnel was successfully stopped!
2025-01-20 13:32:05 [TUN]: WireSock virtual adapter successfully identified
2025-01-20 13:32:06 [TUN]: Detected default interface {17A2F72B-4289-9E98-A8E0-2DC89B121B8C}
2025-01-20 13:32:06 [TUN]: start_internal: NDIS filter successfully started for the default network interface!
2025-01-20 13:32:06 [TUN]: Sent handshake packet to the WireGuard server at WIREGUARD_SERVER:250
2025-01-20 13:32:06 [TUN]: start_internal: Starting keep-alive thread!
2025-01-20 13:32:06 [TUN]: internal_restart: WireGuard tunnel was successfully started!
2025-01-20 13:32:06 [TUN]: watchdog: WireGuard tunnel was successfully started!
2025-01-20 13:32:06 [TUN]: keep_alive_thread: Started!
2025-01-20 13:32:06 [FILTER]: Skipping C:\Program Files\RustDesk\rustdesk.exe : TCP : LOCAL_MACHINE:61224 -> REMOTE_SERVER:21114
2025-01-20 13:32:07 [FILTER]: Skipping C:\Program Files\RustDesk\rustdesk.exe : TCP : LOCAL_MACHINE:61224 -> REMOTE_SERVER:21114
2025-01-20 13:32:07 [FILTER]: Skipping D:\Jellyfin_Server\Server\jellyfin.exe : TCP : LOCAL_MACHINE:8096 <- LAN_MACHINE:46074
2025-01-20 13:32:07 [TUN]: wireguard_read returned: result = 2 size = 13
2025-01-20 13:32:07 [TUN]: wireguard_read returned: result = 2 size = 13
2025-01-20 13:32:07 [TUN]: wireguard_read returned: result = 2 size = 13
2025-01-20 13:32:07 [TUN]: wireguard_read returned: result = 2 size = 13Why? WireSockUI kept on blocking my LAN traffic every now and then, not always. Since I don't wanna fiddle with routing and crap, I just added a DisallowedIps entry *before* AllowedIPs and that seems to do the trick.