- This topic has 16 replies, 2 voices, and was last updated 1 month, 3 weeks ago by
.
-
Posts
-
This new build works!!
Thank you so much for your time and effort fixing this for me.
What’s going to happen when you release newer builds that contain fixes, etc? Will I need to contact you every time to update this “personal” build?
In the 1.2.39 build, I’ve adjusted our approach slightly. Instead of extracting the real source IP and port from the SOCKS header, which in your instance contained incorrect data, I’ve opted to directly assign the Wireguard server’s IP and port. This tweak seems to be more reliable, especially since SOCKS is only involved for the handshake process. This modification has been effective for both your setup and mine, so I’m considering it for inclusion in the mainline implementation.
Additionally, I’m curious about the need for handshake masquerading in the US. It’s clearly beneficial in countries like Egypt, Russia, and probably Iran too, as indicated by high traffic from this region. But in the US context, is this a necessary feature, or is it more about having the option to bypass potential Wireguard blocks?
- You must be logged in to reply to this topic.