Skip to content
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

Wireguard working but cant access S2S traffic #78

Open
sudo-kraken opened this issue Feb 27, 2023 · 1 comment
Open

Wireguard working but cant access S2S traffic #78

sudo-kraken opened this issue Feb 27, 2023 · 1 comment

Comments

@sudo-kraken
Copy link

I have this all up and working I can access all VLANs I need to from the client however I have a S2S VPN setup in the UDM Pro to connect to my firends network, which is reachable from my VLANs but my Wireguard VPN can not see anything across the S2S VPN, how do I fix this as I need access to the other site, meaning that it would go Client >> My UDMP >> S2S Endpoint. I assume this is a routing issue but I cant fathom it out

@sudo-kraken
Copy link
Author

Server

[Interface]
Address = 10.10.10.1/24
ListenPort = 51820
PrivateKey = xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

[Peer]
PublicKey = xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
AllowedIPs = 10.10.10.2/32

Client

[Interface]
Address = 10.10.10.2/24
PrivateKey = xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
ListenPort = 21841

[Peer]
PublicKey = xxxxxxxxxxxxxxxxxxxxxxxxxx
Endpoint = xx.xx.xxx.xx:51820
AllowedIPs = 10.10.10.0/24,192.168.100.0/24

PersistentKeepalive = 25

This is the configuration that I have. I can't access the subnet 192.168.100.0/24 which is a site to site ipsec-vpn configured in the UDM Pro, if I change this to be any of my other local subnets then access works flawlessly, I just cant route over to the remote subnet on the S2S VPN.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant