Forum Replies Created
-
Posts
-
Hello,
I’m glad you’re finding the Wiresock VPN Client user-friendly and easy to navigate.
To answer your question, the Wiresock VPN Client itself does not have the functionality to expose itself as a local proxy server. However, you can certainly achieve your goal by setting up a local proxy server (either SOCKS or HTTP) on your device.
Once you’ve set up the local proxy server, you can add the process name of this proxy server to the “AllowedApps” list in the Wiresock VPN Client. This way, all the connections initiated through the local proxy will be tunneled via the Wireguard tunnel, while other connections will proceed as usual.
For example, if you want certain websites to automatically use the VPN in Firefox, you can set the proxy for different containers to point to the local proxy server that you have set up and added to the “AllowedApps” list.
This should enable you to use some websites via the VPN while others use a direct connection, as you mentioned in your example.
I hope this helps! If you have any more questions, feel free to ask.
While SOCKS5 is utilized solely for the Wireguard handshake, it may induce a slight delay for it. However, this should not impact the rest of your traffic, which is directed straight to your Wireguard server.
WiresockUI provides a real-time display of the Round-Trip Time (RTT) for a WireGuard tunnel, which operates using the UDP protocol. This feature allows you to monitor network latency effectively, ensuring optimal performance of your WireGuard tunnel.
show Round-trip time 1209 ms
Your considerable latency is causing the slowdown you’re experiencing. To rectify this, consider setting up a VPN server that is geographically closer to you.
At the moment, the functionality to name the virtual network adapter based on the configuration file does not exist. However, I acknowledge the value of this feature and will consider implementing it in the upcoming update.
I’m sorry, but it does not seem reasonable to rename the network interface from ‘Wiresock’ to ‘Example’. Instead, it could be more sensible to name it after the configuration file, which would provide better context and clarity.
Absolutely, you can do this. However, during initialization, WireSock identifies the instances of the virtual network adapter, selects the first one to be used for the routing purposes, and renames the selected connection to “WireSock”. This is done for your convenience, allowing you to easily recognize the network adapter currently utilized by the client. If you have any suggestions for improvement, I would be happy to consider them.
This task is achievable, albeit requiring a bit of effort. Wiresock would need to intercept and decode all DNS responses, subsequently maintaining dynamic AllowedIps/DisallowedIps tables. I concur that this could be an intriguing feature. I will endeavor to allocate some spare time to work on its implementation.
Это возможно сделать, однако есть пара моментов и видимо придется несколько пересмотреть существующую архитектуру. В настоящее время при перехвате первого пакета для новой TCP сессии и непустом списке AllowedApps/DisallowedApps в обрабатывающем потоке через IP Helper API запрашивается таблица текущих соединений и выясняется контекст процесса. Результаты этих запросов кешируются, но само по себе это довольно дорогая операция, которая при большом количестве создаваемых соединений может замедлять сеть. Если добавить сюда еще и проверку переменных окружения, это может стать неприемлемо дорого. Так что пожалуй для начала надо будет добавить отложенную обработку пакетов для новых соединений, чтобы не тормозить сеть. Постараюсь найти время поработать над этим.
In the Windows Packet Filter v3.4.0, we’ve made a minor update to the structure layout for static filters in order to comply with ARM64 memory alignment requirements. To resolve any issues with your static filters, simply rebuild your code using the updated common.h file.
At present, the WireSock VPN Client is unable to detect processes operating within containers, including those on the Universal Windows Platform (UWP) and the Windows Subsystem for Linux (WSL). Consequently, you cannot configure the WireSock VPN Client to selectively tunnel applications running within WSL, such as Firefox in your particular situation.
I hope that IP leakage is not a common issue while using a VPN client, as it is designed to protect your privacy and maintain anonymity. However, if you have a proven case of IP leakage, I would be more than glad to analyze the situation and help find a solution.
No, setting directory prefix wildcards in allowed and disallowed apps is generally not supported. However, if you include “C:\Program Files (x86)\Steam\steamapps\common” in the list of allowed apps, it should grant access to all files within that folder.
Hey, I apologize for the delay in getting back to you. I’ve had very limited time recently, and I devoted most of it to preparing the ARM64 build. I understand the importance of adding support for your configuration, and I will do my best to allocate some time to address this issue soon. Thank you for your patience and understanding.
Thank you for the update; I’m pleased to hear that everything is working now. By the way, you might also consider using WireSockUI, as it provides support for the ARM64 platform.
