[Wiresock] Bugs and Feature Requests

[Diyagi]

Hello,

I am having some issues while using Wiresock, some of them seems like bugs and others are features that are not avaliable.
Im using Wiresock in Windows 11 [23h2]

•  [Bug] %i is not being properly replaced when using Powershell commands. Tested with command powershell.exe -command "Set-NetIPInterface -InterfaceAlias '%i' -InterfaceMetric 5000"
• [Bug] Table config is not working. When using Table = off the routes are still being created. This options is in the Wiresock docs, which is why i think its a bug.
• [Feature Request] Turn off WPF. It seems theres no way to not use WFP, when not using AllowedApp or DisallowedApp the WPF will throw everything into the VPN.

More about my use case below.

For my use case i need something that i can change on the go without having to restart the VPN, i also need permanent interfaces which is why i have chosen Wiresock over Wireguard, to achieve what i need my plan was to leave the VPN interface up and connected but not as an default route, this would allow me to bind the software i need VPN for to that interface.

Yes this could be done with WPF (tho i would need to restart the VPN) but then i ran into another issue, WPF will route every instance of that software into to VPN which is not what i want, if i want to run something in powershell for example WPF would route every powershell instance into the VPN.

[Vadim Smirnov]

Thank you for your message! Let me clarify a few points:

Interface Name in Commands
Instead of using the placeholder %i, you can safely rely on the WIRESOCK_TUNNEL_NAME environment variable in your scripts and commands. This variable provides the actual Wiresock tunnel name at runtime, ensuring proper command execution.

Table = off Setting
Currently, Table = off is not supported by Wiresock. Could you let us know where you found this setting mentioned in the Wiresock documentation? If it’s listed somewhere, we’d like to correct that reference to prevent confusion.

If you have any additional questions or need further assistance, feel free to let me know!

[Diyagi]

Thank you for the answer, the WIRESOCK_TUNNEL_NAME env var worked, the table setting is in https://wiresock.net/documentation/wireguard/config.html
Thought I’m just now seeing that despite it being in the Wiresocks documentation website it is saying Wireguard so that’s probably my mistake for not reading properly.

If you could implement both the table and WPF config that would be great, if not thats fine, i figured i can just fork Wireguard client and Wireguard dll and modify them to make the interfaces permanent.

[Author]

Posts