You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm running dnsmasq on my server and in order to do this I need to disable systemd-resolved for it to work properly and resolve internal and external IPs. So if I have this disabled (resolved), is there a way to still have this script update or restart openvpn when I get a disconnection and then a re-connection? My main issue if my /etc/resolv.conf gets updated when openvpn starts to use the vpn's DNS IP, but when there is a lag in ping and openvpn wants to restart, it doesn't update the /etc/resolv.conf to be my service provider's DNS IP and it doesn't resolve the vpn's connection IP because it's using it's internal IP from resolv.conf.
The text was updated successfully, but these errors were encountered:
I had another related issue, that i resolved by adding the hosts to be resolved when vpn is restarting to /etc/hosts. But i think your wanted behaviour can be triggered by --up-restart which according to the manual should trigger the down and up scripts also for restarts. Found this via https://superuser.com/a/975365/458656 and that sounds like it could work.
I'm running dnsmasq on my server and in order to do this I need to disable systemd-resolved for it to work properly and resolve internal and external IPs. So if I have this disabled (resolved), is there a way to still have this script update or restart openvpn when I get a disconnection and then a re-connection? My main issue if my /etc/resolv.conf gets updated when openvpn starts to use the vpn's DNS IP, but when there is a lag in ping and openvpn wants to restart, it doesn't update the /etc/resolv.conf to be my service provider's DNS IP and it doesn't resolve the vpn's connection IP because it's using it's internal IP from resolv.conf.
The text was updated successfully, but these errors were encountered: