Forum Replies Created
-
Posts
-
Привет!
В России пока трюк с SOCKS5-прокси вроде работает. У меня есть идея сделать этот механизм более гибким, например, добавив возможность использования локального SOCKS5 (shadowsocks). Также интересной выглядит идея использовать в этом качестве SSH3, но пока там отсутствует интерфейс для SOCKS5-прокси.
Regrettably, the locations for captured packets and log files in Wiresock are not configurable. This means that it’s not possible to direct Wiresock to save these files to a different drive or a specific location of your choosing.
It seems there might be an issue with the Wireguard server or the network route. Gathering additional log entries would be beneficial, particularly to see if any handshakes received responses. Note that VPN restrictions can vary based on your location. For instance, in certain countries like Russia, Wireguard protocols might be blocked, but using a SOCKS5 option for the handshake can circumvent these restrictions. Also, have you attempted to use the same configuration on both your phone and PC at the same time? Employing the same key (configuration) across multiple devices can lead to erratic behavior.
Of course, you’re welcome to proceed. However, acquiring the Source Code could significantly streamline the process. Should resource limitations arise, please feel free to reach out to me privately. We can discuss a more favorable price for the Source Code to accommodate your needs.
Hello,
Certainly, you can rename the driver binary. However, it’s important to be aware that this change will not affect the device’s name, which will remain unchanged.
As of now, WireSock is designed to support only one active tunnel at a time, regardless of the mode. I am aware of the growing need for the ability to operate multiple tunnels simultaneously and am contemplating adding this feature in future releases. However, my availability for this project is significantly limited due to my full-time job that often extends into weekends, alongside my family obligations. Additionally, working through the night is no longer a viable option for me, as it might have been previously.
However, I am hopeful that my schedule will soon allow me to devote additional time to this endeavour.
When you connect to a VPN, it usually routes all your traffic, including LAN traffic, through the VPN tunnel by adding a default route. However, setting
0.0.0.0/1and128.0.0.0/1on your VPN adapter creates specific routes that prioritize external traffic through the VPN, while excluding local network addresses. This means local network traffic, which typically uses private IP ranges like192.168.x.x, doesn’t match these VPN routes and instead uses the default local routing. This setup allows direct access to LAN devices without routing their traffic through the VPN.The Wiresock VPN client in NAT mode operates differently from typical VPN configurations. It doesn’t set up a virtual VPN network interface or alter your routing table. Instead, it selectively routes traffic based on specified parameters like AllowedIPs, DisallowedIPs, AllowedApps, and DisallowedApps. For those seeking functionality akin to the original WireGuard for Windows, the Wiresock VPN Client can be executed with the
-laccommand line option. This mode enables Wiresock to configure a virtual network interface and modify the routing table, similar to traditional VPN clients. However, it’s important to note that while the NAT mode permits usage by non-admin users, the mode involving a virtual network interface necessitates administrative privileges or needs to be run as a Windows service.Are you operating Wiresock in adapter mode (using the -lac command line option) or in adapterless mode? The former mode closely resembles the behavior of the original Wireguard client. Are you encountering this issue exclusively in one of these modes, or does it occur in both? A more detailed description of your network setup would be immensely helpful for further analysis.
If your Wireguard server is located within your LAN, it’s possible to access local devices via the tunnel. However, if this isn’t applicable in your scenario, you will need to add the addresses of these devices to the ‘DisallowedIPs’ section of your configuration.
Could you please let me know the details of your AllowedIPs configuration? If your intention is to keep your LAN outside the scope of the Wireguard tunnel, you have the option to incorporate ‘DisallowedIPs’ into your configuration file. As an example, in my setup, I utilize the following configuration:
DisallowedIPs = 192.168.3.0/24, 10.10.1.0/24The issue seems to be that qBittorrent frequently establishes and terminates TCP sessions, necessitating that Wiresock repeatedly determines the process context for each new connection. This process of context resolution is resource-intensive and currently takes place within a shared flow that manages all traffic. To enhance efficiency, it would be beneficial to shift the process context resolution to a dedicated thread. This would prevent it from impacting connections that are already established. I plan to implement this improvement in the forthcoming release.
I’m delighted to hear that my suggestion worked out for you! It’s always rewarding to know that my assistance has been effective. Thank you for your kind words about the software. If you have any more questions or need further assistance in the future, feel free to reach out. Your success and satisfaction with the software is our top priority. 😊👍
Добрый день, Дмитрий!
Большое спасибо за ваши теплые слова о WireSock VPN Gateway! Я рад, что он вам нравится и помогает в работе.
Что касается вашего вопроса по wg-quick-config, насколько я помню, действительно, при использовании параметра -add скрипт пересоздает файл конфигурации на основе шаблона config.json, что может привести к потере ручных изменений.
По поводу QR-кода, видимо, происходит аналогичная ситуация — скрипт использует данные из config.json, а не из конкретного конфига пира.
Идея с добавлением аргумента для генерации PresharedKey при добавлении нового пира кажется полезной и не слишком сложной. Я постараюсь найти для нее время. Впрочем, можете принять в этом посильное участие, исходный код wg-quick-config доступен на github.
Если у вас возникнут дополнительные вопросы или предложения, пожалуйста, не стесняйтесь обращаться.
С уважением,
Вадим
In version 1.2.36, the virtual network adapter driver received an update to meet ARM64 memory alignment standards. It seems that during the transition from version 1.2.32 to 1.2.36, this driver may not have been updated correctly. Typically, the recommended course of action in such instances is to fully uninstall the software, restart the system, and then carry out a clean reinstallation.
