Bug #4995
closedOpenVPN bound to gateway group using CARP IP doesn't stop with CARP backup status
0%
Description
This Bug is related to the bugfix of Bug #4854
When CARP goes to backup on let say pfsense#1, it stops openvpn and it start the openvpn on the new master let it name pfsense#2. When i speak of openvpn it means a openvpn client.
However, when we go back to Master on pfsense#1, it starts the openvon on pfsense#1. But why is it restarted on pfsense#2??? This causes me a lot of Problems, because the openvpn Clients try to reconnect and throw out the newly started Clients on pfsense#1.
But what is strange, is that the openvpn Clients on pfsense#2 are shown as stoped in the Services Status. The logs say something different, the are restarting because of inactivity. Even ps -ax Shows that the Clients are still running...
What Comes to my mind, is that openvpn_restart('client', $Settings) does not really stop / terminate the openvpn Clients. So in the rc.carpbackup the command openvpn_restart only tiggers the restart of openvpn Clients, because they are currently running. How can you stop them? Something like
+openvpn_stop('client', $settings);
-openvpn_restart('client', $settings);
Updated by Chris Buechler over 8 years ago
- Status changed from New to Duplicate
- Target version deleted (
2.2.5)
The problem described in subject is fixed. The root cause of what you're seeing there is #4642. You seem to have an easily replicable case, could you send me a config backup? Email to cmb at pfsense dot org either as an attachment, or with some means of securely obtaining the file.