What's new

I need help on routing for vpn clients

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

Teymur

Regular Contributor
Hi All,

So my situation is as following:

Router A (asus rt-ac3200) - my home router - open vpn server. LAN 10.10.10.0/24
Router B (asus rt-ac66u) - friend’s home router - open vpn client. LAN 192.168.50.0/24
Router C (tplink) - connected behind router A. LAN 10.10.9.0/24

There is a static route from router A to router C. Router C has it’s NAT disabled.

I can get to the LAN of router B from the LANs of routers A and C.
I can get to the LAN of router A from the LAN of router B.
I can’t get to the LAN of router C from from router B - and this is what I want to achieve.

How do I make open vpn server to advertise to its clients the route to the LAN of router C?

All your inputs are highly appreciated.

Regards

Teymur
 
I assume router C is patched over its WAN to router B.

Two requirements here. First, the OpenVPN server needs to push Router C's local IP network to the OpenVPN client.

Code:
push "route 10.10.9.0 255.255.255.0"

Second, normally the WAN of router C (like any router) will not allow access into the LAN without either dropping the firewall or using port forwarding. Merely disabling NAT is not sufficient. In fact, disabling NAT is not even necessary or relevant. The benefit of disabling NAT is merely for efficiency purposes. But doing so then requires static routing. So NAT or no NAT, the problem between router B and router C is the firewall on the WAN of router C.
 
I assume router C is patched over its WAN to router B.

Two requirements here. First, the OpenVPN server needs to push Router C's local IP network to the OpenVPN client.

Code:
push "route 10.10.9.0 255.255.255.0"

Second, normally the WAN of router C (like any router) will not allow access into the LAN without either dropping the firewall or using port forwarding. Merely disabling NAT is not sufficient. In fact, disabling NAT is not even necessary or relevant. The benefit of disabling NAT is merely for efficiency purposes. But doing so then requires static routing. So NAT or no NAT, the problem between router B and router C is the firewall on the WAN of router C.

Hi,

Thanks for your reply,

I figured that long ago already, but since it’s been quite here, i didn’t post the update that all works now. And you’re absolutely right. That’s exactly what I ended up doing.
 
Similar threads

Similar threads

Latest threads

Support SNBForums w/ Amazon

If you'd like to support SNBForums, just use this link and buy anything on Amazon. Thanks!

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!

Staff online

Top