Forum Replies Created
-
Posts
-
Note that Fast I/O is an experimental API and is only useful under certain conditions. For example, when you need minimal packet capture latency, and you can dedicate one (or more) CPU cores to poll packets from the driver. Historically, I added it at the request of a user who needed it for an arbitrage trading platform. And it is generally focused on server applications, where you manage and control all available resources. For client-side solutions, I would recommend using traditional I/O.
Regarding your questions, please note that only one driver file object (one instance of CNdisApi) is allowed to use Fast I/O. And once you no longer want to use Fast I/O, just close the corresponding driver file object (destroy the CNdisApi instance) and the driver will do all the necessary cleanup. If you only want to pause packet capture, simply clear the adapter mode flags. To re-enable packet capture, just set appropriate flags back again.
Please let me know if you have any further questions.
Hmm, there are two main cases where a service can temporarily stop filtering the network (and thus allow AllowedApps to bypass the VPN):
1. If the primary WireGuard server is down and a secondary server configuration
-fallback-configis available, the tunnel will attempt to restart using it.2. When changing the configuration of network adapters (Wi-Fi/LAN switch, disconnecting/reconnecting the Wi-Fi network), the tunnel is also reconfigured and restarted.
Thanks, I have added a validation for these fields.
Could you share the config file you are having trouble with? Another question, did you test adapter (
-lac) or adapterless mode?Regarding mysqld, do you mean that it initiates an outgoing connection? Because otherwise, i.e. mysqld listen for the incoming connections and needs to be reachable through the tunnel, binding to the address of the VPN adapter will probably suffice.
I use DisallowedIPs to exclude my LAN (192.168.1.0/24) for Chrome:
AllowedApps = chrome DisallowedIPs = 192.168.1.0/24Hi!
Have you installed Windows Packet Filter driver?
I will add a proxy option. This can be really useful.
Wiresock VPN Client is standalone, you don’t need the official Wireguard client to make it work.
WireSock VPN Gateway needs an official Wireguard client and allows it to act as a WireGuard server.
The problem was parsing a configuration that expected the Address parameter to have a specified netmask, e.g.
Address = 10.10.0.4/32, 2001:dc8:a260::4/128while in your configuration the Address parameter looked likeAddress = 10.10.0.4 , 2001:dc8:a260::4.I have fixed the configuration parser in 1.2.8. Please give it a try.
Problems with
-lacoptions are caused by insufficient user privileges, please note that Wiresock should be run as administrator.You can email PCAP files directly to [email protected]. We can continue to review the issue privately, after which I will post the final solution here. Unfortunately, without anti-spam, I would have to delete too many users/spam daily…
Hello, could you please provide the generated PCAP files in addition to the application log? Also, could you check if using
-lacmakes a difference? With the latter option, Wiresock works closer to the stock client. One more question, do you have DNS specified in the config file (‘server not found’ points to DNS problem)?Currently, only the process name is checked, the path is ignored. It’s easy to change the check to a fully qualified pathname, but in the current implementation with a config file, this can lead to unwanted collisions. I plan to add an advanced configuration that will allow this.
You definitely read in my mind! I really was considering adding a proxy (as a dedicated process) that would be connected and intercepted by Wiresock. I implemented a similar thing for one side project.
