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

Unable to reach resources on the server network #5

Open
mruin opened this issue Jun 11, 2023 · 2 comments
Open

Unable to reach resources on the server network #5

mruin opened this issue Jun 11, 2023 · 2 comments

Comments

@mruin
Copy link

mruin commented Jun 11, 2023

Hi! I've followed your nice guide, and all seems being working, i can ping machines from one network to the other, but i'm still not able to reach resources (e.g. nas) on the other network.
I've this configuration:

Network 1 (server):
192.168.188.0/24 (eth0 is on 192.168.188.8)
wg0 is on 10.0.0.1

Network 2 (client):
192.168.0.0/24 (eth0 is on 192.168.0.24)
wg0 is on 10.0.0.3

I've just opened port 51820/UDP on both routers, pointing to the machines where wireguard in running.
Both networks have static public IPs.
wg show command gives both demons up, running and connected each other.
Why can't I reach my nas at 192.168.0.30 if i can ping it?
I think i'm missing something, like a static route, but i don't know where and how to confjgure it...

@mruin
Copy link
Author

mruin commented Jun 11, 2023

EDIT: i can ping machines from network 1 to network 2, but can't ping from network 2 to network 1.

@mruin
Copy link
Author

mruin commented Jun 12, 2023

I've added the static route on the client with the command:

route add -net 192.168.188.0 netmask 255.255.255.0 metric 1024 dev wg0

Now i can ping the server (192.168.188.8), but i'm still unable to ping other machines on the same network.

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