Lantis wrote:I will look at it when I have time. It will make my job easier if you can find an exact procedure that reproduces the error.
Because as I noted earlier, I currently have no problem with this.
If you want immediate help, look into it yourself.
nothing special to reproduce the error in my case
1. on ovpn server (192.168.2.1) configure ovpn server settings an save
2. on ovpn server (192.168.2.1) add new ovpn client with routed subnet (under ovpn settings: allowed client)
3. save the settings. wait until settings applied
4. go to connection/ routing
5. I can see the route to 192.168.1.0 (segment behind client router) through gateway 10.1.0.2 on tun interface
6.wait for some time (2-3 min)
7 open connection/ routing again, and there is no route to 192.168.1.0 anymore
8. configure the client (192.168.1.1) through zip file, save the settings. Vpn is on.
9. check the ping
from 192.168.1.x to 192.168.2.x - OK
reverse from lan behind the server (and from 192.168.2.1 as well) to 192.168.1.x - false
10. on server router 192.168.2.1 add route manually
/sbin/route add -net 192.168.1.0 netmask 255.255.255.0 gw 10.1.0.2
11. reverse ping is ok and i can see the route to 192.168.1.0 in routes' list
for me the scenario is the same on linksys wrt1900ac and tplink archer c7 v5
the route to network behind the client disappears after server router restarted. it is the main problem
I spent time to understand it by myself without success
i can see in log that the reverse route has been successfully added and then "route delete" is coming after
daemon.warn openvpn(custom_config)[7271]: Could not determine IPv4/IPv6 protocol. Using AF_INET
any suggestion how i can keep the permanent route after router's reboot
route add -net 192.168.1.0 netmask 255.255.255.0 gw 10.1.0.2