Home › Forums › Discussions › Support › Specify wiresock interface type on connection
- This topic has 5 replies, 3 voices, and was last updated 2 weeks ago by
Vadim Smirnov.
-
AuthorPosts
-
June 10, 2024 at 12:28 pm #13728
Hello,
first of all, thank you for your great work. Working with Wiresock after an official Wireguard client is a relief π
I have a little question, however. When Wiresock connects, it creates a new interface every time. By default, this interface receives a “public” type that blocks any incoming traffic that had not been explicitly allowed. This is a good practice of course, but there are “road warrior” scenarios where you need to have a connectivity to a client computer. I could have sorted this out with post-connection script (e.g. Set-NetConnectionProfile -NetworkCategory Private for Wiresock interface), but this would only work if Wiresock runs with elevated admin privileges. I, hovewer, have to run it in user mode.
Of course I can allow some of my apps through firewall in a Public profile as well, but this would be a security flaw. I use Wiresock to connect to a private network with a potentially unsafe applications, and that’s the reason why I want to mark the interface as Private not allowing those apps to connect on Public networks.
Is there a possibility to automatically mark the interface as Public, or to make it persistent so that I will mark it once and for all?
Thank you in advance π
June 11, 2024 at 8:57 am #13729Typo: of course, I want to mark it as Private, not Public π
June 11, 2024 at 1:07 pm #13731Hello 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.
March 8, 2025 at 12:57 pm #13989OK, I little bit flood support forume, but =))
In transparent Mode I have significant perf issues, I have 800mbs network, and gets drop in network speed as 2-6 times worse, I can’t understand issue, but think it is something in wiresock core. Wireshark shows on wiresock Interface a lot of retransmissions, lost packets and sufficient delays in packets transmission
I run speed.cloudflare and see 5-10% of losses, as well as upload speed drops as 2x-4x times and download as 4x-6x times
Any suggestions how to investigate these issues and find bottle-neck?
March 8, 2025 at 12:59 pm #13990I have 1280 mtu on a client and server side, btw
March 10, 2025 at 9:18 am #13993Packet retransmissions, lost packets, and significant delays on the WireSock interface are clear signs of an issue affecting performance. Since WireSock itself does not introduce artificial delays or excessive packet processing overhead, I suspect that some external network component is interfering with its operation.
Packet reordering and loss at this scale can be caused by third-party network software (such as antivirus, firewall, or another filtering driver) that intercepts traffic before it reaches WireSock. This can disrupt the expected flow, leading to degraded speeds.
To investigate, I recommend:
- Testing on a clean machine with a well-known WireGuard profile (e.g., Cloudflare Warp) to rule out external software conflicts.
- Testing against Cloudflare Warp to ensure that the issue is not related to the server side of your current WireGuard configuration.
- Temporarily disabling any third-party security software or VPN-related network filtering drivers to see if performance improves.
- Monitoring CPU and network adapter utilization to ensure that the system isnβt bottlenecked at the hardware or driver level.
If you can gather more details from these tests, it will help narrow down the issue. Let me know what you find!
-
AuthorPosts
- You must be logged in to reply to this topic.