User Tools

Site Tools


computing:fail2ban

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
computing:fail2ban [2019/11/03 05:30] oemb1905computing:fail2ban [2023/12/27 16:08] (current) oemb1905
Line 3: Line 3:
   * **Jonathan Haack**   * **Jonathan Haack**
   * **Haack's Networking**   * **Haack's Networking**
-  * **oemb1905@jonathanhaack.com**+  * **oemb1905@jonathanhaack.com** 
  
 ------------------------------------------- -------------------------------------------
Line 58: Line 58:
   sudo fail2ban-client status   sudo fail2ban-client status
  
-Hope this helps!+Hope this helps!  Oh yeah ... here is how to remove a false positive!
  
- --- //[[oemb1905@jonathanhaack.com|oemb1905]] 2019/11/02 19:48//+  fail2ban-client set ssh unbanip 10.xx.15x.12x 
 +  fail2ban-client unban --all 
 + 
 +Another method that does more than individual services, and instead zaps all records: 
 + 
 +  sudo systemctl stop fail2ban 
 +  sudo truncate -s 0 /var/log/fail2ban.log 
 +  sudo rm /var/lib/fail2ban/fail2ban.sqlite3 
 +  sudo systemctl restart fail2ban 
 + 
 +Systemd log issues. Change the sshd jail as follows 
 + 
 +  sudo nano /etc/fail2ban/jail.local 
 +  backend = systemd 
 +  #backend = %(sshd_backend)s 
 +   
 +Some recommend adding backend = systemd into jail.conf, but I've found that does nothing. The error over ipv6 not being set and using auto can be removed as follows: 
 +   
 +  sudo nano /etc/fail2ban/fail2ban.conf 
 +  'allowipv6 = auto' 
 + 
 + --- //[[jonathan@haacksnetworking.org|oemb1905]] 2023/12/27 16:01//
computing/fail2ban.1572759041.txt.gz · Last modified: 2019/11/03 05:30 by oemb1905