Facebook
Twitter
QWeb Ric
Regular Pleskian
- Server operating system version
- AlmaLinux 9.7 (Moss Jungle Cat)
- Plesk version and microupdate number
- Obsidian 18.0.75
We have a number of firewall scripts that work by creating custom IPTables chains and attaching them to INPUT, but we also use Plesk's firewall management UI which of course recreates the IPTables rules everytime changes are saved.
To work around this, currently we also have a script which just reattaches our custom chains to INPUT on execution, and every time the firewall is saved via Plesk, I SSH in and run this script manually.
Just wondering if there's a way to automate? Is there a way to expand the firewall save process to also run our script, or a way to just add chains to it's own internal list for reattaching on save? Presumably the Fail2Ban extension must be latching on to this mechanic somehow since those chains are always kept?
To work around this, currently we also have a script which just reattaches our custom chains to INPUT on execution, and every time the firewall is saved via Plesk, I SSH in and run this script manually.
Just wondering if there's a way to automate? Is there a way to expand the firewall save process to also run our script, or a way to just add chains to it's own internal list for reattaching on save? Presumably the Fail2Ban extension must be latching on to this mechanic somehow since those chains are always kept?
