-
-
Notifications
You must be signed in to change notification settings - Fork 6.3k
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
Ipsec Server + wireguard client same server #1059
Comments
@AnonymousWebHacker Hello! This use case is not currently supported. If you start WireGuard on the server, it may no longer be able to accept incoming IPsec connections on UDP ports 500/4500. This is probably because all traffic on the VPN server would go through the WireGuard connection. |
Thanks for your answer. Is this something that happens to me in my vps provider? something new in wireguard or what? Because, there are some articles on the internet of this use L2PT + Wireguard Client, example Anyway, I'm going to find out, if there are any rules that I can add in the wireguard configuration, that allow connections on 500/4500. |
@hwdsl2 In fact, I tried to install outline server through docker
Outline, use an API-port to connect the Manager and a user-port to connect the client. And I start wireguard with that configuration above, and I can connect perfectly to the outline server, using the IP of eth0 |
1 - Install the L2PT server using the script, and it installed perfect. I can connect to him
2 - I install wireguard, and use it as a client, to connect to another server.
My idea is to forward the traffic from the L2PT to the wireguard. I found that #990 (comment) , but i have a problem first
What's the matter?
If I start the wireguard client, I cannot connect to L2PT. I have to turn off the wireguard, to be able to connect. This is my wireguard configuration.
eth0 = 144.100.1.1/21 gw 144.100.1.254
wg0 = 10.66.66.6/24 wg 10.66.66.6
The text was updated successfully, but these errors were encountered: