Bastille Firewall Doesn't Automatically Start After Reboot

Discussion in 'ISPConfig 3 Priority Support' started by skycity, Sep 19, 2014.

  1. skycity

    skycity New Member

    This is more of an FYI than a support question. After following "The Perfect Server - CentOS 6.5 x86_64 (Apache2, MySQL, PHP, PureFTPD, Postfix, Dovecot and ISPConfig 3)" and applying a firewall record in ISPConfig, I can see the results with "iptables -L". However- after a reboot, Bastille does not start automatically. Hence the user is unknowingly left with the default firewall.

    Simply running "chkconfig --levels 235 bastille-firewall on" fixes it, but this was unexpected as it is never mentioned in the guide.

    I've also confirmed the same behavior using the virtual machine provided in the HowtoForge VMWare downloads page:
    "The Perfect Server - CentOS 6.5 x86_64 (Apache2, MySQL, PHP, PureFTPD, Postfix, Dovecot, ISPConfig 3) as virtual machine in ovf format, compatible with vmware and virtualbox."
    (both before and after upgrading to 3.0.5.4p3)
     
    Last edited: Sep 19, 2014
  2. till

    till Super Moderator Staff Member ISPConfig Developer

    Thank you for reporting the issue. Bastille is activated by ispconfig at the time you add a new direall record in the ispconfig interface, so its not activated at install time. I added a bugreport in the bugtracker to check if something is broken there.
     
  3. Doug G

    Doug G Member

    Thanks for posting this, my two centos servers had the same issue.
     

Share This Page