FreePBX Version
FreePBX 17
Issue Description
I have FreePBX installed with its firewall disabled via the GUI as I want to manage the firewall myself at the CLI level via iptables, however it's periodically flushing my iptables rules (i.e. removing them, leaving nothing left), and having done some troubleshooting I think it's the voipfirewalld hook that's doing this. I've tried uninstalling the System Firewall module via the module admin so as to stop its hooks from running, but it won't let me do that without disabling the System Admin module, which would mean that I wouldn't be able to use the GUI at all, so I don't want to do that, and the fact that those two modules are coupled in that way seems strange? This feels like a bug, hence me reporting it as such, but is there a way of preventing my iptables rules from being flushed in this scenario? Applying my firewall rules at the hypervisor level isn't an option unfortunately, otherwise I would just do that. I could make a change at the CLI level if need be, as long as it's not something that might get overwritten by a future FreePBX module patch or an APT patch of FreePBX itself.
Operating Environment
Debian 12.12
FreePBX 17.0.25
System Firewall 17.0.1.35
Relevant log output
FreePBX Version
FreePBX 17
Issue Description
I have FreePBX installed with its firewall disabled via the GUI as I want to manage the firewall myself at the CLI level via iptables, however it's periodically flushing my iptables rules (i.e. removing them, leaving nothing left), and having done some troubleshooting I think it's the
voipfirewalldhook that's doing this. I've tried uninstalling the System Firewall module via the module admin so as to stop its hooks from running, but it won't let me do that without disabling the System Admin module, which would mean that I wouldn't be able to use the GUI at all, so I don't want to do that, and the fact that those two modules are coupled in that way seems strange? This feels like a bug, hence me reporting it as such, but is there a way of preventing my iptables rules from being flushed in this scenario? Applying my firewall rules at the hypervisor level isn't an option unfortunately, otherwise I would just do that. I could make a change at the CLI level if need be, as long as it's not something that might get overwritten by a future FreePBX module patch or an APT patch of FreePBX itself.Operating Environment
Debian 12.12
FreePBX 17.0.25
System Firewall 17.0.1.35
Relevant log output