Forum Replies Created
-
Posts
-
This behavior makes sense since the VPN connection is managed by a background service rather than the UI itself. Force-closing the application through AutoHotKey prevents the UI from sending the proper disconnect command, so the tunnel remains active. Instead of terminating the process, a cleaner approach would be to have the AutoHotKey script call the official WireSock CLI to disconnect the VPN first and then close the application if needed. Using the CLI for automation is generally more reliable than simulating UI interactions or force-killing the process, especially when scripting startup and shutdown workflows. It keeps the automation predictable while ensuring the VPN session is terminated gracefully. Good luck!
That’s definitely not expected. Just installing the Windows Packet Filter driver shouldn’t normally reduce your throughput from 10 Gb/s to around 2.5 Gb/s without any filtering application running.
A few things I’d check:
- Make sure the NIC driver didn’t change or get reconfigured after the installation.
- Verify that features like RSS, RSC, and Large Send Offload are still enabled, as those can have a big impact on 10 Gb performance.
- Try uninstalling the Windows Packet Filter package and rerun the same iperf3 test to confirm the performance drop is directly related.
- If possible, test with the latest version of the driver and the WFP package, as there may have been fixes since the version you’re using.
Out of curiosity, what network adapter are you using (Intel, Mellanox, Broadcom, etc.) and which version of Windows? That information might help narrow down whether it’s a driver compatibility issue or something specific to the filter driver.
