Forum Replies Created
-
Posts
-
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.
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?
PostUp => start SOCKS5 local proxy server
PreDown/PostDown => stop SOCKS5 local proxy serverThis also looks like an interesting possibility 🤔
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.
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.
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.
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 wiresockTo 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 -forcePlease let me know if any errors occur during this process.
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.
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.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.
WireSock uninstall removes all components, but under some circumstances, a reboot may be required afterward. For example, some components may be marked for deletion but not immediately removed.
Thank you for the detailed explanation. I will conduct a more thorough analysis. However, I have a hypothesis. It seems the system might prefer using IPv6 DNS over IPv4, which could be causing the behaviour you’re observing. Could you please perform a quick test? Disable the IPv6 protocol on your network interface in the Control Panel connection properties and check if it makes a difference.
I apologize for the delay; I’ve been quite overloaded these past few weeks. Could you please provide a detailed description of the issue? In the logs I previously reviewed, I did not notice any problems. However, I suspect that sending DNS queries to different DNS servers could cause issues with CDN-based services. I need a detailed description, preferably with screenshots or a video recording of the problem, as well as the WireSock textual log and PCAP files. This will allow me to conduct a thorough analysis.
