norcat wrote:Different operating systems have tools for looking at what routes are in play, for example Windows has a 'route print' command to view from Command Prompt.
Ok using 'route print' I get a bunch of IPv4 Route Table entries. One is 192.168.0.0 | 255.255.252.0 . What should I see here?
norcat wrote:I didn't have to set up anything. It just works, but it wouldn't if the local and remote networks had the same subnet configurations, since then routing is not possible.
I'm pretty sure both my subnet configurations are ok but I can't talk to
the VPN clients from
the router's subnet. The subnet mask of 255.255.252.0 might be an issue though? Like if I am supposed to use static routes or something instead of a larger subnet mask. I don't know.
norcat wrote:What is a "main router"?? and what does DHCP has to do with this? You're asking for trouble if you start to change network settings that you don't know what is and what does.
I don't know what most of this stuff does yet it doesn't work and I still need to change things to make it work... Main router is the 192.168.1.1 router subnet. I can disable the dhcp-option line in the client config if that isn't necessary. Seemed like it might be whats missing.
norcat wrote:You really need to think in terms of how the network is configured at one location (local), as opposed to at a different location (remote). VPN client has a local network configuration, and it then connects to VPN server at remote network. A route is needed in client for it to be able reach hosts both its local network and the remote network, and that is what VPN Server does automatically with that option, it pushes the server local subnet to the client.
Yes that is what I need help with - I don't know how to configure each end so they can talk to each-other. The default settings are not sufficient nor is whatever this checkbox does in Synology's OpenVPN configuration. When I connect to my VPN with a client, it gets an IP of 192.168.2.6 which is not the local subnet of the router I want to be on. It's the subnet the VPN server sets up.
norcat wrote:Firstly "192.168.1.1" is a single host address, and a subnet calculator will show you the host range for that mask. That's a supernet with host range 192.168.0.1 to 192.168.3.254. Obviously ..1.1 and ..2.2 is both within that range.
Yes I gathered that the 255.255.252.0 mask should allow communication from 192.168.0.1 to 192.168.3.254 from this post: https://serverfault.com/questions/88314 ... -168-2-254
I don't know how or what it's doing or if this is the right way to do what I am trying to do - get 192.168.1.0 clients talking two-way to 192.168.2.0 clients.