OpenVPN installed on 2019 server, clients connect but cant reach remote network?

markm75

I've installed the openvpn software and ran through tutorials on getting it set up, the remote client can connect.. gets an ip like 10.8.0.x

The 2019 server is on a LAN network with an address in the 172.16.0.x subnet (255.255.248.0) of 172.16.1.60
The router at the building is 172.16.0.1 (sonicwall).
The LAN network already has a dhcp server and dns server (windows 2022 servers) which give out 172.16.2.x addresses

The home network is something like 192.168.0.x (so the remote machine might be 192.168.0.7)

I've tried adding push "route 172.16.0.0 255.255.248.0" in the server file, but the client still cant ping or reach servers on the 172 subnet.
I added the registry key on the server to allow ip routing.

What am i missing here? I believe it has to do with the router not knowing anything about 10.8.0.x and needing a route somehow. Or i need to tap into the existing DHCP and use 172.x addresses somehow.

Thanks in advance

TinCanTech

Is it not obvious ?

https://community.openvpn.net/openvpn/wiki/GettingHelp

markm75

TinCanTech wrote Is it not obvious ?

https://community.openvpn.net/openvpn/wiki/GettingHelp

Well not entirely, no.

TinCanTech

So, this is for The Office and you are the Network administrator ?

markm75

TinCanTech wrote So, this is for The Office and you are the Network administrator ?

This is installed on a virtual machine on the office side, 2019 server. Remote side is just a client.
Also, more ideally i dont want to have to deal with setting routes manually on the clients, unless there is no other way.

markm75

*duplicate del*

markm75

*duplicate del*

markm75

I believe the only thing i need is a proper route set on the sonicwall gateway, but its choices in the dialogue are confusing as to what i should be setting for things like destination, interface etc.

markm75

TinCanTech

Being as the word sonic is an adjective relating to audible sound,
I would like-wise expect a firewall named sonicwall to be dangerously confused.

markm75

I was able to get the route configured on the sonicwall..
I can now ping machine ip addresses on the remote network, however, resolving them by name/dns doesnt work (i'm using dev tun mode with udp as of now).

markm75

i believe adding
dhcp-option DNS 172.16.1.71 to the client config has cured dns woes (this is our dns server), however ping ability is lost, but thats not a huge deal.

However, its necessary to add machinename.dns.local to the end to resolve, cant just do by machine name, perhaps another setting

markm75

adding this line cured the dns:
dhcp-option DOMAIN-SEARCH domain.local

I guess this is a self help forum lol, nonetheless, everything so far on my test is working... took a ton of digging to figure out but it is.

TinCanTech

You are being paid to do your job.

\we are not being paid to teach you DNS.

markm75

TinCanTech wrote You are being paid to do your job.

\we are not being paid to teach you DNS.

This is supposed to be a forum for assistance, not snarky/uninformative replies, but its all good.

Thanks for the help.

Pippin

TS was able to solve the issue, closing.

PS
There is a Special-Use Domain 'home.arpa.':
https://www.rfc-editor.org/rfc/rfc8375.html
instead of .local

TinCanTech

markm75 wrote This is supposed to be a forum for assistance

That is not true.

This forum is for the support of OpenVPN Community Edition.

markm75 wrote not snarky/uninformative replies

The reply was informative. If you found it to be snarky then that is because you came here with preconceived ideas about how we teach you how to do your job, for free,

I find it to be particularly infuriating when people who are being payed to do a job, expect other people to tell them how to do their job for free.

This is a basic naivety: In the REAL World, you hire a professional to teach you how to do your job.

There is no other reality, only the make-believe of naivety.