-
Notifications
You must be signed in to change notification settings - Fork 130
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
the command "wg show" displays my interface but nothing goes through the tunnel #174
Comments
If you want to route all traffic through wg interface you need to use 0.0.0.0/0 as allowed IP on this device. Anyway the allowedip in your diskstation config is wrong and doesn’t match the vpn IP of your oracle vps. And the allowedip for the peer of your diskstation in the vps config is also wrong. |
Thanks for your answer. When I try : 0.0.0.0/0
I don't get why my AllowedIPs of the client are wrong
|
As stated here: #59 (comment) I found the solution. Hello everyone! I know this issue was open for a long time but I just found the solution today. AllowedIPs 0.0.0.0/0 doesn't work So you have to put AllowedIPs: 0.0.0.0/1, 128.0.0.0/1, the only problem is that you also send the traffic to the Public IP of your Wireguard Endpoint Sever... The only solution I found was to add this at the end of your PostUp rule :
To get this ip : 172.20.0.1, Use this command line
The It looks like that in my client config on Synology:
|
Is AllowedIPs: 0.0.0.0/1, 128.0.0.0/1 a full tunnel like 0.0.0.0/0? If so is there any way to not use the full tunnel setup. Anything else I use for Allowed IPs doesn't allow traffic to pass until the peer pings the server. |
Looks adding PersistentKeepalive = 25 will allow the user to use other AllowIP blocks to avoid a full tunnel. |
My setup is : Oracle VPS to act as the server, and I wan't to use my synology NAS as the client with docker.
When I curl ifconfig.co, inside the wireguard docker container on my synology, I see the public IP of my router, on which my NAS is connected. Instead of the public IP of my oracle VPS.
My Oracle wireguard server config (wg0.conf) generated by wireguard docker:
My synology client config wg0.conf:
ip route
output inside synology wireguard container:The text was updated successfully, but these errors were encountered: