ClearFoundation Tracker - ClearOS
View Issue Details
0015701ClearOSapp-attack-detector - Attack Detectorpublic2017-07-12 08:392021-11-09 05:39
user2 
 
normalminorhave not tried
closedwon't fix 
7.3.1 
 
0015701: Tidy up if fail2ban is stopped
If fail2ban is stopped, it should tidy up any existing rules or at least remove the firewall hook. As it stands, the rules will stay in place until the firewall is restarted.

Note: fail2ban takes a looong time to regenerate rules, so it would be good to differentiate between a "stop" and a "restart" (which is often coded as a "stop / start").
No tags attached.
txt firewall.txt (11,612) 2017-07-13 13:02
https://tracker.clearos.com/file_download.php?file_id=381&type=bug
txt firewall1.txt (8,835) 2017-07-13 13:03
https://tracker.clearos.com/file_download.php?file_id=391&type=bug
Issue History
2017-07-12 08:39user2New Issue
2017-07-12 08:40user2Statusnew => confirmed
2017-07-13 13:02NickHFile Added: firewall.txt
2017-07-13 13:03NickHFile Added: firewall1.txt
2017-07-13 13:06NickHNote Added: 0005851
2021-11-09 05:39NickHNote Added: 0015981
2021-11-09 05:39NickHStatusconfirmed => closed
2021-11-09 05:39NickHResolutionopen => won't fix

Notes
(0005851)
NickH   
2017-07-13 13:06   
This is a WFM on 7.3 with f2b 0.9.5-3. See the file firewall.txt with f2b running and firewall1.txt after stopping it.

The only "f2b native" way round this is to go towards ipset rules and use the ipset timeout feature. This improves the start up times and allows you to just destroy the set on stopping rather than delete the rules one by one.
(0015981)
NickH   
2021-11-09 05:39   
Ipset lists are now used and work in the backgrouns in an unobtrusive way