[andrea_m83]

Hi to all, my issue is quite frequent in this period, because my WAN connection is repeatedly falling.
After it came back up, OpenVPN client does not restart-
I have to disable/enable it from panel.

I have only added this string to additional config :

[egc]

What build are you using?

How did you setup?

To get the best out of DDWRT and the forum read the forum guidelines with helpful pointers:
https://forum.dd-wrt.com/phpBB2/viewtopic.php?t=324087

If you have not already read the forum guidelines, please do !!

[SurprisedItWorks]

Also, when OpenVPN has failed, is the process still running? Do ps | grep [o]penvpn in the CLI. If it is running, you get something like this:

xxxx root yyyy S openvpn --daemon --config /tmp/openvpncl/openvpn.conf

If it has exited, you get nothing.

The keepalive thing is great, but the server needs a corresponding setting. Generally they'll decide on and set parameters on their end then "push" the client commands they want your end to use. They may use "ping" and "ping-restart" to specify the two numbers separately or "keepalive" to do it in one command.

[andrea_m83]

[egc]

What you could try is to let OpenVPN restart , the usual setup is with persist tun and persist key, so when a disconnection takes place it just tries to make a connection with the same key and tunnel.

This will not always work depending on what has changed in the network.

With the following commands (add to additional config) OpenVPN restarts after disconnection:

[andrea_m83]

Thanks egc, I will try with restarting openvpn, so firstly I'll check how many disconnections will follow for renegotiating the keys

[eibgrad]

For the record, rekeying does NOT typically have any effect on the OpenVPN connection. The renegotiation of keys is a normal part of the ongoing conversation held between the client and server on the control channel. That said, there may be *other* reasons the connection has to be renegotiated, thus causing a disconnect/reconnect, but it's NOT typically due to rekeying.

Notice in the following syslog that my own OpenVPN client became established at 8:00, then an hour later (due to the default of 3600 secs) rekeying took place, but without causing any disconnect/reconnect.

[andrea_m83]

same for me eibgrad, i didn't notice any disconnection from the logs

[andrea_m83]

@egc: I was unable to solve, SIGHUP does not keep openvpn active, with reneg-sec 0 I have continuous disconnections of a few seconds over 2-3 minutes.
I tried to install watchdog on a usb stick but once my DSL connection failed it was not able to restart the vpn autonomously, this is the log:

[eibgrad]

[andrea_m83]

[eibgrad]

Because you've edited the syslog, it's hard for me to be sure exactly what's happening. For example, I can't tell if the public IP to which you are connecting is the same or different each time the client attempts a connection. I understand the necessity if this is your own OpenVPN server, but not for a public one (ExpressVPN, PIA, etc.). The reason I care is because I'm trying to determine *why* it keeps trying to reconnect, then suddenly gets connected (makes sense if the client is trying different public IPs, but not if they are the same), but ultimately fails due to the route-down script failing.

At the following point in the syslog, it *finally* appears to be connecting after many failed attempts.

[eibgrad]

P.S. I see your current build is DD-WRT v3.0-r43320 std, which dates back to 5/31/2020. IIRC, @egc made some changes to the route-up/route-down scripts that I *believe* were intended to prevent this problem. But that was some time ago, and I don't know for sure if and when it became part of the official release. At the very least, I would upgrade to the latest build in case those changes were eventually applied.

[egc]

It is indeed a good idea to upgrade to the latest build

To get the best out of DDWRT and the forum read the forum guidelines with helpful pointers:
https://forum.dd-wrt.com/phpBB2/viewtopic.php?t=324087

If the OpenVPN does not restart with the script then reboot the router, in this line of the script:

[SurprisedItWorks]

This whole thread reminds me of a problem I had in a few builds last year that involved a segfault when OpenVPN ran route-up.sh or route-down.sh.

From 44048's Marvell new-build thread https://forum.dd-wrt.com/phpBB2/viewtopic.php?t=326070&postdays=0&postorder=asc&start=28: