Uploaded image for project: 'FreePBX'
  1. FreePBX
  2. FREEPBX-22543

Firewall service restart is not adding the fail2ban chains to iptables.

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 15.0.8.21
    • Fix Version/s: 15.0.8.22
    • Component/s: None
    • Labels:
      None
    • ToDo:

      Description

      Firewall service restart is not adding the fail2ban chains to iptables.

      I flushed the iptables rules then restarted the firewall service and checked for the iptables and all the fail2ban chains were not present. Then I restarted the fail2ban service and all the fail2ban chains got added back.

      
      [root@~]# iptables -L INPUT
      Chain INPUT (policy ACCEPT)
      target     prot opt source               destination
      fpbxfirewall  all  --  anywhere             anywhere
      fail2ban-SIP  all  --  anywhere             anywhere
      [root@~]# service fail2ban restart
      Systemd shim for fail2ban running '/usr/sbin/systemctl restart fail2ban'
      [root@~]# iptables -L INPUT
      Chain INPUT (policy ACCEPT)
      target     prot opt source               destination
      fail2ban-recidive  all  --  anywhere             anywhere
      fail2ban-zulu  tcp  --  anywhere             anywhere
      fail2ban-BadBots  tcp  --  anywhere             anywhere             multiport dports http,https
      fail2ban-FTP  tcp  --  anywhere             anywhere             multiport dports ftp
      fail2ban-apache-auth  all  --  anywhere             anywhere
      fail2ban-SSH  tcp  --  anywhere             anywhere             multiport dports ssh
      fail2ban-PBX-GUI  all  --  anywhere             anywhere
      fail2ban-SIP  all  --  anywhere             anywhere
      fpbxfirewall  all  --  anywhere             anywhere
      [root@~]#  

       

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  Unassigned
                  Reporter:
                  psandesh Sandesh Prakash
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  4 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved:

                    NextupJiraPlusStatus

                    Error rendering 'slack.nextup.jira:nextup-jira-plus-status'. Please contact your Jira administrators.