Forum Replies Created
-
Posts
-
Could you please test this experimental build?
P.S. Please note to download v3.4.2, I had to fix the link.
Have you confirmed whether your system utilizes jumbo frames when the Windows Packet Filter option is unchecked or the driver was uninstalled?
I have conducted tests on the Windows Packet Filter over a 10 Gbit network and did not observe any significant performance degradation solely from enabling the driver. It’s important to note that the test system was quite powerful, equipped with an E-2378G processor and Broadcom P210tep NetXtreme network interfaces. Furthermore, even when running a test packet filtering application with minimal output (such as dnstrace), the bandwidth was not substantially affected.
Would you mind sharing your hardware configuration, so we can make a rough comparison?
Hi there!
Firstly, I want to thank you for your kind words and appreciation of our work on WireSock! It’s always great to hear that our project is helpful to users like you. I understand that you are trying to use WireSock as a client to access your work’s internal network and need to configure a DNS suffix for the adapter.
From the information you’ve provided, it seems like you’ve managed to find a workaround using PowerShell. While this method works for now, I can see how having a more seamless integration with WireSock would be beneficial. I’ll be sure to do some research and look into potential solutions or improvements to better support the DNS suffix configuration in WireSock. In particular, in instances where it is available (Windows 10 and later), SetInterfaceDnsSettings could potentially be utilized. For earlier versions of Windows, similar functionality may be achievable by manipulating the Windows registry.
Again, thank you for your feedback and for sharing your experience with us. Your input is invaluable in helping us improve our project for all users.
I will look into adding support for your configuration when I have some free time, hopefully during the upcoming weekend.
It’s great to see that you’re testing the driver performance over a 10GB network.
Exploring multithreading is a good approach, as it can help distribute the load across multiple CPU cores and potentially improve performance. For example, in a project I encountered, packets were read by one thread, processed by two additional threads (one for incoming and another for outgoing), and injected into the stack by a fourth thread.
To provide more specific suggestions and help optimize your code, it would be helpful to see a code snippet demonstrating how you’re reading and re-injecting packets per operation. The more data you read from the driver in a single call, the better performance you can achieve. For instance, if you’re currently reading 256 packets per operation, you might try increasing this value to 1024 and see if it improves the results.
Thank you for reaching out regarding the issue you’re experiencing with Wiresock in your restricted network environment.
Please note that Wiresock does not support using localhost IP (127.0.0.1) as an endpoint. I recommend trying to specify the real local IP address instead of 127.0.0.1 for the WireGuard config endpoint.
However, I must mention that I am not certain if this change will work out-of-the-box, and some code adjustments may be necessary to ensure proper functionality of local redirect
If you encounter any issues, we recommend first trying to start the application/service with the ‘-log-level all’ command line parameter. If running the application, this will output the debug log to the console and save processed packets into PCAP files for analysis.
The method to bypass the Egyps wireguard vpn blocking won’t work any more,I just tested it.
The post was created over a year ago, so the situation may have changed since then and I am unable to verify if the information is still accurate.
BTW,is it any quick method or tools to detect if the ISP blocks UDP or not,since some ISP may block the UDP protocol so wireguard won’t work at all.It would be nice to do so before to install wireguard.
One possible solution to test whether UDP is blocked or not is to use performance measurement tools such as iperf3. These tools can help to determine if there are any issues with network performance that could be impacting the use of UDP. By conducting these tests prior to installing Wireguard, you can proactively identify any potential issues and take appropriate steps to address them.
It’s Windows Server 2016 X64
It is peculiar, but configuring the Network Category to Private can be beneficial, although it is not required.
To the best of my recollection, there was a similar issue on Windows 7, although it did not impact the overall functionality of Wiresock VPN Gateway. However, configuring the VPN network adapter as a private network (which failed according to your log) can often provide greater convenience and ease of use.
With this in mind, may I kindly inquire as to which operating system you are currently using?
In addition, I am also considering the possibility of opening the source code for wg-quick-config to facilitate the analysis of such issues in the future. By making the source code more accessible and transparent, it will be easier for users to understand and diagnose potential issues, as well as contribute to the development of the project.
To properly uninstall the service, follow these steps:
- Use the command “wiresock-service uninstall” to uninstall the service.
- Reboot your system.
- Check if the service still exists in the registry. If it does, remove it using regedit.
- Reboot your system again to ensure that all changes take effect.
After completing these steps, the service should be fully uninstalled, and you can proceed with a fresh installation.
1. Determining the root cause of the issue is challenging without access to the MSI log. If you collect one I can check.
2. It’s important to note that SHA-1 code signing reached its end-of-life on December 1, 2020, and it’s no longer possible to sign drivers for Windows Vista/2008/7/8 using this method. However, an update for Windows 7 added support for SHA-256 code signing certificates, which may also work for Windows 2008 R2. But yes, it is sometimes a real pain to sign drivers for EOL Windows versions.
