https://bugs.contribs.org/show_bug.cgi?id=10422
--- Comment #2 from Michael McCarn <[email protected]> ---
I've created a new firewall rule so that traffic blocked by fail2ban itself is
logged in /var/log/iptables using "fail2ban" instead of "denylog" so that it
the two block methods can be differentiated.
The change required 3 custom templates for 'masq', then
# stop fail2ban
service fail2ban stop
# rebuild and restart masq
expand-template /etc/rc.d/init.d/masq
/etc/rc.d/init.d/masq restart
# restart fail2ban
service fail2ban start
(sv t masq doesn't necessarily recreate iptables rules from scratch, and
"signal-event remoteaccess-update" generates lots of errors in
/var/log/messages about the new "f2b-denylog" chain missing)
To implement, download these attachments to
/etc/e-smith/templates-custom/etc/rc.d/init.d/masq.
--
You are receiving this mail because:
You are the QA Contact for the bug.
_______________________________________________
Mail for each SME Contribs bug report
To unsubscribe, e-mail [email protected]
Searchable archive at https://lists.contribs.org/mailman/public/contribteam/
