Forums

[Vadim Smirnov]

Эти локализации от компоненты TaskScheduler.

[Vadim Smirnov]

Если вопрос касается https://github.com/wiresock/WireSockUI, то в проекте пока нет русской локализации. Интерфейс достаточно простой, и пока не возникала острая необходимость в переводе. Однако, возможно, стоит рассмотреть добавление языковых локализаций в будущем. 🤔

[Vadim Smirnov]

Uninstalling already accomplishes this, except it does not call pnputil to remove the driver package from the system.

[Vadim Smirnov]

I believe a viable solution is possible, but it will require some development effort. If the system prefers using IPv6 DNS and there is no IPv6 DNS address in the tunnel configuration, we can potentially extract the DNS query from the IPv6 packet, package it into IPv4, and send it to an IPv4 DNS server. The reverse operation would need to be performed for the system to receive an IPv6 DNS response.

I will try to allocate time to work on this, but my current schedule is quite tight due to other commitments.

[Vadim Smirnov]

Hello Anton,

It seems there’s a bit of a misunderstanding. During the installation process, a single virtual network adapter is set up. This adapter is only renamed and configured (assigned an IP address, etc.) based on the tunnel configuration. However, these operations usually require elevated privileges, so WireSock in virtual adapter mode needs to be run as an administrator. If you can’t run it as an administrator, you can use WireSock in transparent mode instead.

In transparent mode, the virtual network adapter isn’t activated. Instead, it intercepts traffic from the default network interface and sends it over the tunnel. This way, you can run WireSock as a normal user and configure your default network adapter as private.

I hope this helps! If you have any more questions or need further assistance, feel free to ask.

[Vadim Smirnov]

I believe the NDIS filter driver is uninstalled, and it should be safe to remove the binary files and/or registry keys, though these are unlikely to cause any issues. What about the WireSock virtual network adapter? Was it removed from Devices as well?

[Vadim Smirnov]

PostUp => start SOCKS5 local proxy server
PreDown/PostDown => stop SOCKS5 local proxy server

This also looks like an interesting possibility 🤔

[Vadim Smirnov]

You can bind the local SOCKS5 proxy application to the WireSock network interface, following the same steps outlined for qBittorrent in this post. After that, add it to AllowedApps. This approach will meet all your requirements.

[Vadim Smirnov]

It might have been a system glitch, and the NDIS filter driver wasn’t fully uninstalled. Please check if the filter driver is still visible in the network connection properties and try uninstalling it from there.

[Vadim Smirnov]

I’m sorry, but while I know that one of our customers used Windows Packet Filter with GoLang, I have not created any samples myself.

[Vadim Smirnov]

Hmm, it looks like something went wrong. After rebooting, do you see any remaining artifacts?

[Vadim Smirnov]

Could you please run CMD as an Administrator and execute the following commands to uninstall the drivers:

netcfg -v -u nt_ndiswgc
devcon.exe remove wiresock

To completely remove the drivers from the system, you can also execute the following:

cd C:/Windows/Inf
pnputil /delete-driver oem57.inf -force
pnputil /delete-driver oem35.inf -force

Please let me know if any errors occur during this process.

[Vadim Smirnov]

If you set up a local SOCKS5 proxy on your machine and add its name to AllowedApps, it will function equivalently to WARP Proxy mode.

[Vadim Smirnov]

I performed a quick install/uninstall test on Windows 11 23H2 x64 using winget to ensure everything works as expected. All driver components were removed correctly.
If you can collect the MSI installer logs, I can investigate and try to determine what went wrong.

[Vadim Smirnov]

This is unusual; it seems the uninstallation process encountered an issue. Typically, reinstalling WireSock, rebooting, then uninstalling it again and rebooting once more resolves the problem. Additionally, if WireSock was installed as a Windows service, consider stopping and uninstalling the service before uninstalling the software.

[Author]

Posts