227
edits
Changes
From SME Server
Jump to navigationJump to search→Installation sme9
== Maintainer ==
== Maintainer ==
[[User:VIP-ire|Daniel B.]]<br/>
[[User:VIP-ire|Daniel B.]]<br />
[http://www.firewall-services.com Firewall Services]<br>
[http://www.firewall-services.com Firewall Services]<br>
mailto:daniel@firewall-services.com
mailto:daniel@firewall-services.com
Please discuss, provide feedback and share epxeriences on the forums [http://forums.contribs.org/index.php/topic,51127.0.html '''here''']
Please discuss, provide feedback and share experiences on the forums [http://forums.contribs.org/index.php/topic,51127.0.html '''here''']
== Description ==
== Description ==
== Requirements ==
== Requirements ==
This contrib has been developped and tested on SME Server 8 and later. It probably won't work on SME 7.
This contrib has been developed and tested on SME Server 8 and later.
{{Note box|The SME feature [http://wiki.contribs.org/AutoBlock AutoBlock SSH] should be disabled to ensure that fail2ban controls SSH traffic and not the SME build-in firewall.}}
{{Note box|The SME feature [http://wiki.contribs.org/AutoBlock AutoBlock SSH] should be disabled to ensure that fail2ban controls SSH traffic and not the SME build-in firewall.}}
== Installation sme8 and sme9 ==
==Koozali SME v9==
{{#smeversion: smeserver-fail2ban}}
== Installation sme9 ==
Configure EPEL's repository:
Configure EPEL's repository:
<onlyinclude>{{#ifeq:{{{transcludesection|epel9}}}|epel9|
<onlyinclude>{{#ifeq:{{{transcludesection|epel9}}}|epel9|
*install the rpms
*install the rpms
yum --enablerepo=fws --enablerepo=epel install smeserver-fail2ban
yum --enablerepo=smecontribs --enablerepo=epel install smeserver-fail2ban
{{warning box| Failing to run either of these command will completely lock network access next time iptables rules are reloaded}}
{{warning box| Failing to run either of these command will completely lock network access next time iptables rules are reloaded}}
{{warning box| The masq service must be enabled for fail2Ban to work correctly. If you disable it, Fail2ban won't ban anything}}
{{warning box| The masq service must be enabled for fail2Ban to work correctly. If you disable it, Fail2ban won't ban anything}}
== Disable SME Feature AutoBlock SME 9 or greater ==
It's been noted that one of the features of fail2ban overlaps the built-in ssh AutoBlock feature of SME (https://wiki.contribs.org/AutoBlock).
It is possible to disable the AutoBlock feature using the following optional steps.
1. View what your current settings are for the built in SME AutoBlock feature by entering the following at the cli.
# config show sshd
2. If AutoBlock is disabled no action is required. If AutoBlock is enabled, set it to disabled with the following commands:
# config setprop sshd AutoBlock disabled
# signal-event remoteaccess-update
==DB command==
==DB command==
there is no panel yet you can manage the contrib by the db configuration, it is quite simple
While there is a panel in the server-manager, you can also manage the contrib by the db configuration, it is quite simple
# config show fail2ban
# config show fail2ban
Available options are below:
Available options are below:
* '''IgnoreIP''': a comma separated list of IP or CIDR networks which will never be blocked by fail2ban. Exemple: 12.15.22.4,17.20.0.0/16. All your local networks and networks allowed to access the server-manager are already automatically whitelisted
* '''IgnoreIP''': a comma separated list of IP or CIDR networks which will never be blocked by fail2ban. Example: 12.15.22.4,17.20.0.0/16. All your local networks and networks allowed to access the server-manager are already automatically whitelisted
* '''FilterLocalNetworks''' can be enabled or disabled (default is disabled). If set to enabled, local networks won't be whitelisted, and fail2ban can also ban hosts from the internal networks. Note that networks allowed to access the server-manager are not affected (they will never be blocked)
* '''FilterLocalNetworks''' can be enabled or disabled (default is disabled). If set to enabled, local networks won't be whitelisted, and fail2ban can also ban hosts from the internal networks. Note that networks allowed to access the server-manager are not affected (they will never be blocked)
* '''BanTime''': Duration (in seconds) of a ban. Default to 1800
* '''BanTime''': Duration (in seconds) of a ban. Default to 1800 (about 30 minutes)
* '''FindTime''': The window fail2ban will check, in seconds. Default is 900. So, this mean fail2ban will only check for the number of failed login attempts in the last 15 minuts
* '''FindTime''': The time window fail2ban will check, in seconds. Default is 900. So, this means fail2ban will only check for the number of failed login attempts in the last 15 minutes
* '''MaxRetry''': Number of failed attempts in the last '''FindTime''' seconds to trigger a ban. Default is 3
* '''MaxRetry''': Number of failed attempts in the last '''FindTime''' seconds to trigger a ban. Default is 3
* '''Mail''': can be enabled or disabled (default is enabled). If enabled, each ban will be notified by mail
* '''Mail''': can be enabled or disabled (default is enabled). If enabled, each ban will notify the admin by email
* '''MailRecipient''': if '''Mail''' is enabled, the email address which should receive ban notifications. Default is root (the admin account will receive)
* '''MailRecipient''': if '''Mail''' is enabled, the email address which should receive ban notifications. Default is root (the admin account will receive)
== Uninstall ==
== Uninstall ==
yum remove smeserver-fail2ban fail2ban
yum remove smeserver-fail2ban fail2ban
for SERVI in $(fail2ban-client status|grep 'Jail list'|cut -d':' -f2|sed 's/, / /g'| sed -e 's/^[ \t]*//')
for SERVI in $(fail2ban-client status|grep 'Jail list'|cut -d':' -f2|sed 's/, / /g'| sed -e 's/^[ \t]*//')
do
do
fail2ban-client status $SERVI |grep -E 'Banned IP list|Status for the jail'
fail2ban-client status $SERVI |grep -E 'IP list|Status for the jail'|sed 'N;s/\n/:/'|cut -d: -f2,4
done
done
then do
then do
output:
output:
# sfail2ban
# sfail2ban
ftp:
imap:
pam-generic:
qpsmtpd:
recidive: 141.98.80.15
ssh:
ssh-ddos:
wordpress:
====Print a summary of the fail2ban db====
mkdir -p /root/bin
vi /root/bin/bansummary.sh
Paste this
<nowiki>#!/bin/bash
echo -e \
"IP \t"\
"BanTime \t"\
"UnbanTime \t"\
"Jail"
for ban in $(db fail2ban show |awk -F\= ' $2=="ban" {print $1}');
do
IP=$(db fail2ban getprop $ban Host)
Bantime=$(date +"%F %T" -d @$(db fail2ban getprop $ban BanTimestamp))
UnBanTime=$(date +"%F %T" -d @$(db fail2ban getprop $ban UnbanTimestamp))
LastJail=$(zgrep -H "Ban $IP" $(find /var/log/fail2ban -type f -ctime -7) |tail -1 |awk '{print $6}')
printf "%-15s" "$IP"
echo -e "\t$Bantime\t$UnBanTime\t$LastJail"
done
</nowiki>
save, then make executable
chmod 755 /root/bin/bansummary.sh
Usage:
bansummary.sh
Output:
<nowiki>IP BanTime UnbanTime Jail
46.246.39.228 2017-09-09 18:45:00 2017-09-10 18:45:00 [http-scan]
124.239.180.102 2017-09-09 12:07:32 2017-09-10 12:07:32 [http-scan]
212.237.54.93 2017-09-09 19:27:32 2017-09-10 19:27:32 [http-scan]
</nowiki>
===WordPress===
Fail2Ban works with WordPress but needs some extra configuration. Please review the WordPress page, https://wiki.contribs.org/Wordpress#Fail2Ban
== Bugs ==
Please raise bugs under the SME-Contribs section in [http://bugs.contribs.org/enter_bug.cgi bugzilla]
and select the smeserver-fail2ban component or use {{BugzillaFileBug|product=SME%20Contribs|component=smeserver-fail2ban|title=this link}}.
Below is an overview of the current issues for this contrib:{{#bugzilla:columns=id,product,version,status,summary|sort=id|order=desc|component=smeserver-fail2ban|noresultsmessage=No open bugs found.}}
===Changelog===
Only released version in smecontrib are listed here.
{{#smechangelog: smeserver-fail2ban}}
----
[[Category: Contrib]]
[[Category: Contrib]]
[[Category: Security]]
[[Category: Security]]
