-
Notifications
You must be signed in to change notification settings - Fork 388
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fedora: WStunnel & Wireguard conflicting ports #367
Comments
Hello, could you please check if the port 51820 is not already taken before you start wstunnel?
Can you also please post your wireguard configratuon and possibly try test with wg-quick directly? |
Hi there, I don't use wg-quick, however, I can attempt to use that instead. Gnome usually allows me to import VPN Profiles and it has it's own Wireguard compatibility. As for the first question, I get the following W/O Wireguard, W/O WStunnel
W/ Wireguard, W/O WStunnel
W/O Wireguard, W/ WStunnel
|
I installed Config
|
UpdateI was able to get Wireguard to connect to WStunnel by doing the following:
For whatever reason though, WStunnel client won't connect to WStunnel server. I will add my logs and replace my WStunnel's domain with an example one.
|
You need to set a static route to avoid your traffic looping. |
Describe the bug
After I start WStunnel, I attempt to enable my modified Wireguard config in Network Manager (I use GNOME with Network Manager). When clicking the enable toggle for the Wireguard profile that has it's endpoint set to localhost:51820, it immediately shuts off. When trying to start the Wireguard profile first, and then WStunnel, WStunnel returns the following error:
To Reproduce
clear; sudo ./wstunnel client -L 'udp://51820:[VPN LOCAL IP]:51820?timeout_sec=0' wss://[WSTUNNEL PUBLIC IP]:8443
Expected behavior
Like on Windows, I expected Wireguard to work and send traffic to localhost:51820 (WStunnel Server), but it instead errors out.
Your wstunnel setup
Paste your logs of wstunnel, started with
--log-lvl=DEBUG
, and with thecommand line used
N/A
Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: