Bug #2913
closedOpenVPN servers and clients not reevaluated when gateway groups settings are saved and applied
0%
Description
I have a gateway group VPNgways with WAN=Tier1, OPT1=Tier2. The OpenVPN servers and clients use interface VPNgways. They are happily using WAN at the time, as per VPNgways settings. Then I edit VPNgways to be OPT1=Tier1, WAN=Tier2 - save and apply.
Firewall rules are reloaded (and I think polciy-based routing changes are implemented on-the-fly OK). But the OpenVPN servers and clients are not re-evaluated to select the current highest tier gateway.
Note: later restarting the OpenVPN server and client services does not work - that only restarts the process, it doesn't rewrite the conf file. To get the change to be effective each server/client config needs an edit/save, or do a real WAN or OPT1 unplug/replug event, or reboot.
It would be nice for gateway groups tier changes to be implemented to OpenVPN on-the-fly.
Updated by Chris Buechler over 9 years ago
- Assignee set to Chris Buechler
pretty sure I fixed this in a 2.2.x version and 2.3 some time ago, will check. Phil, if you know offhand whether it's still an issue, feedback appreciated.
Updated by Chris Buechler about 9 years ago
- Status changed from New to Resolved
Even further back, this was fixed by Phil via PR in 2013 and works.
cmb@cmb-m6600:~/gitroot/pfsense$ git show 30ca7b7e commit 30ca7b7ebcb6d48a6bd8bc57ddffcf6c64c68e7b Author: Phil Davis <phil.davis@world.inf.org> Date: Fri Mar 29 14:29:12 2013 +0545 Resync OpenVPN instances that use any changed gateway groups