Forum Replies Created
-
Posts
-
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.
The issue you’re experiencing appears similar to what’s outlined in a related topic. Based on the installation logs, the NDIS filter driver installation is failing due to an ACCESS DENIED error code. This indicates that there may be an obstruction within your system preventing the driver installation.
Could it be that Kaspersky Antivirus is installed on your system? If so, would you be willing to try disabling or temporarily uninstalling it to see if this rectifies the problem?
