Dec 11, 2018
OpenVPN - UntangleWiki May 15, 2020 Enabling OpenVPN clients to access to the LAN. – Life in route add -p 10.8.0.0 mask 255.255.255.0 172.25.87.20. This will add a static route for the 10.8.0.0 network with a netmask of 255.255.255.0 to route via. 172.25.87.20; 172.25.87.20 is the IP address of the “gateway” and is our Windows Server 2012 R2 server which is running the OpenVPN server software as well as our DHCP and DNS server. How to pair Pi-hole with an OpenVPN to block ads and Apr 24, 2020 EdgeRouter - OpenVPN Server – Ubiquiti Networks Support
Thanks arne, you are right! At least in part. The remote LAN route is there, using policy: ip rule show 0: from all lookup local 100: from all fwmark 0x3c lookup 60 32766: from all lookup main 32767: from all lookup default infact there is a routing table #60 which goes through the VPN: ip route show table 60 default dev tun0 scope link and remote private traffic is marked with iptables mangle
The title says it all really. I have an OpenVPN server (On ubuntu), and I can connect to it through my client (Windows 8) The problem starts when I try to route ALL traffic through the VPN. I have added the push flags in server.conf: push "redirect-gateway def1" push "dhcp-option DNS 8.8.8.8" When I connect from the client, the client outputs:
Route traffic from internal network (eth1) through openvpn
May 15, 2020