itsmee Hi, OpenVPN is working fine for me for quite a while. Access to home via TUN (TAP on android seems to be a pain) works well from multiple platforms, base concepts of routing (default GW != OpenVPN Server) are understood & working. Linux skill is average or slightly above. Now I'm trying to connect two subnets so any node on either side can ping any node on the remote side. Basically to connect Home & Remote via routing to the TUN device. IP Setup VPN Range: 192.168.200.0/24 Home IP range: 192.168.177.0/24 Remote IP range: 17.18.0.0/24 The VPN Client is able to access the VPN Server as well as the entire Home subnet (ping rom 192.168.200.6 to 192.168.177.70 or 192.168.177.2 are working fine) Machines in Home subnet are able to ping the VPN client via its .200.6 address. Challenge: I'm trying to get access from Home Subnet to Remote Subnet B via "route add -net 172.18.0.0 netmask 255.255.255.0 gw 192.168.200.6" on the VPN Server. Same if using 192.168.200.2 as GW. Any guidance why that does't lead to success? How to analyse that not even 172.18.0.10 can be pinged from 192.168.177.70? VPN Server: # ip r default via 192.168.177.1 dev eth0 172.18.0.0/24 via 192.168.200.2 dev tun0 192.168.177.0/24 dev eth0 proto kernel scope link src 192.168.177.70 192.168.200.0/24 via 192.168.200.2 dev tun0 192.168.200.2 dev tun0 proto kernel scope link src 192.168.200.1 Remote # ip r 0.0.0.0/1 via 192.168.200.5 dev tun0 default via 172.18.0.1 dev eth0 128.0.0.0/1 via 192.168.200.5 dev tun0 172.18.0.0/16 dev eth0 proto kernel scope link src 172.18.0.10 192.168.177.0/24 via 192.168.200.5 dev tun0 192.168.200.0/24 via 192.168.200.5 dev tun0 192.168.200.5 dev tun0 proto kernel scope link src 192.168.200.6 ItsMee
itsmee Hi, I was looking for 'ccd files' or 'routed lans' - both well documented, so I got it up and running. Topic closed. http://www.synology-forum.de/entry.html?66-Entfernte-und-lokale-Netze-mit-OpenVPN-verbinden https://community.openvpn.net/openvpn/wiki/RoutedLans ItsMee
