![]() I also experience some slow DNS resolution and occasional failed attempts that need to be retried (web page not found - hit the enter key again, and it comes up - and occasional messages in terminal about temporary address resolution failure). I suspect it might be a temporary loss of cable modem connectivity, (could also be an intermittent NIC interface) and it might also be some sort of bug in my program. If for some reason none of them connect, then this is logged and the test is skipped. Monit synology code#I have a website pinger that checks the startus of my shared host every 5 minutes and as part of the code it does a quick UDP socket connection to about a half dozen differnt public DNS servers. I use the VPN to route all my guest WiFi network traffic though - most traffic goes straight out. I have never noticed a significant loss of Internet connectivity on the main WAN, just on the guest WiFi network. In any case, if this is the issue, it should be fairly easy to solve after looking at the routing table.ĭo you notice a loss of Internet connectivity when the VPN dies? This is likely not reconnecting because if the server IP address is changing and you're routing all traffic via the VPN, it could struggle to reconnect because the default route to establish a new VPN connection (via a changed server IP) will be via the now broken VPN tunnel. If you're using the directive redirect-gateway def1 (route all IPv4 traffic via VPN). In this case will the watchdog package work? I need to determine if dpinger is successful on the VPN, and restart it if it said in Automatically Restarting OpenVPN This is interesting. I know I had something like this happen on my main WAN when my ISP changed my IP address - I had to restart or something. I think what is happening is the the VPN provider changes the server IP addresses from time to time. rc.newwanip: The command '/usr/local/bin/dpinger -removed- >/dev/null' returned exit code '1', the output was '' The only thing that I noticed in the log was this, and I think it was just showing that the VPN didn't have a connection, so dpinger was failing. Do not retry connection when authentication fails is not checked, but for some reason the VPN does not reconnect unless I start/stop the service. Monit synology install#Just install that package, and then go to Services > Service Watchdog and add your OpenVPN client(s). However, if the client service itself dies, you can use the Service Watchdog package to automatically restart it. The client itself should attempt to automatically reconnect unless an authentication failure occurs and you have enabled the "Do not retry connection when authentication fails" option enabled for that client. Said in Automatically Restarting OpenVPN Client: ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |