1 Topic by jbou

  • jbou
  • Member
  • Offline
  • Registered: 2009-11-13
  • Posts: 18

Topic: fail2ban log with many errors on Rocky 10.2

==== REQUIRED BASIC INFO OF YOUR IREDMAIL SERVER ====
- iRedMail version (check /etc/iredmail-release): 1.8.4
- Deployed with iRedMail Easy or the downloadable installer?  downloadable
- Linux/BSD distribution name and version: Rcocky Linux 10.2
- Store mail accounts in which backend (LDAP/MySQL/PGSQL): MySQL mariadb
- Web server (Apache or Nginx): Nginx
- Manage mail accounts with iRedAdmin-Pro? not yet
- [IMPORTANT] Related original log or error message is required if you're experiencing an issue.
====
RHEL-10 dont use iptables any more, everything seems working with firewalld but I have alot of error messages into the logfile
I can do something to prevent the system to call iptables?

fail2ban.log attached

----

Spider Email Archiver: On-Premises, lightweight email archiving software developed by iRedMail team. Supports Amazon S3 compatible storage and custom branding.

2 Reply by ploversspin

  • ploversspin
  • Member
  • Offline
  • Registered: 2024-11-11
  • Posts: 2

Re: fail2ban log with many errors on Rocky 10.2

ou don't need to reinstall iptables at all. Simply override Fail2ban's action configuration:

Edit (or create) /etc/fail2ban/jail.local and add the following lines under the [DEFAULT] section:

Ini, TOML
[DEFAULT]
banaction = firewallcmd-richrules
banaction_allports = firewallcmd-richrules
After that, just run systemctl restart fail2ban. The errors related to calling iptables in your log file will completely disappear

ploversspin's Website

3 Reply by jbou

  • jbou
  • Member
  • Offline
  • Registered: 2009-11-13
  • Posts: 18

Re: fail2ban log with many errors on Rocky 10.2

ploversspin wrote:

ou don't need to reinstall iptables at all. Simply override Fail2ban's action configuration:

Edit (or create) /etc/fail2ban/jail.local and add the following lines under the [DEFAULT] section:

Ini, TOML
[DEFAULT]
banaction = firewallcmd-richrules
banaction_allports = firewallcmd-richrules
After that, just run systemctl restart fail2ban. The errors related to calling iptables in your log file will completely disappear

Thanks, that's the solution.