Forum Replies Created
-
Posts
-
I’m seeing something very similar on my setup. I’m running Windows 11 Enterprise with a Marvell AQtion AQC113, and I tested Windows Packet Filter 3.6.2.1.
With the driver installed, iperf3 performance over LAN drops dramatically to around 1.7 Gbit/s. Without the driver, the same setup reaches the expected 10 Gbit/s. 🚀
I also have jumbo frames disabled, and other filters such as AdGuard, AdGuard VPN, and Symantec don’t seem to affect the 10 Gbit/s speed when Windows Packet Filter isn’t installed.
The drop from 10 Gbit/s to 1.7 Gbit/s is quite significant. I’m wondering if the AQC113 is particularly sensitive to the NIC offloading changes mentioned here. Has anyone tested this combination and found which offload setting makes the biggest difference? 🤔
I can understand why the licensing structure would be confusing, especially when the project itself is described as MIT-licensed. The distinction between the open-source library and the NDIS drivers seems to be the key point here. For a small business, it would definitely be worth clarifying exactly which components require a commercial license and whether there are affordable options available. Hopefully, the maintainers can provide a clear breakdown so developers can make an informed decision before building the technology into their products. 👍
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.
