Please change the UI settings to be able to set a longer ban time
And it would be nice to see the log again in diagnostics
fail2ban - Jail Ban time & Log in services
-
- OMV 6.x
- mrHalfer
-
mrHalfer
Hat den Titel des Themas von „fail2ban - Jail Ban time“ zu „fail2ban - Jail Ban time & Log in services“ geändert. -
Please change the UI settings to be able to set a longer ban time
604800 seconds == 10080 minutes == 168 hours == 7 days == 1 week isn't enough time????
If you want permanent BAN use -1
The log is in Diagnostics --> System Logs
-
About ban time - It's not very important, but I'm used to banning for 2 days (172800 sec, it's better of 99999). Because bots often return exactly one day later, and then forget. But since this is a restriction on the part of the UI, it is very strange.
You will laugh, but these are the standard settings and there is even a hint:
About logs - I'm not about launch logs, about command output fail2ban-client status and etc. (it is more correct to call the status, it was possible in OMV 5):
-
You're on OMV6, correct?
You can go up to 1 week ban so, don't see what is the issue, really.
Instead of the maximum valeu, use what you want.
And, again the fail2ban log is where I told you.
There's no need to have it on another side.
And, perhaps it's due to the new framework of omv6 which is different of the one used on omv5.
-
Yes, currently OMV6 at now.
You can go up to 1 week ban so
Can't in Jail setting, only in general settings.
There's no need to have it on another side.
I only ask to return (in the future) a convenient function for viewing bans in OMV web-interface, without the need for a connection via SSH.
I'm not asking to do it soon. I just wrote so that they would not forget about the convenient features and return them when there is time
-
Can't in Jail setting, only in general settings.
Yes you can:
Select the Jail you want to edit and set the time you want.
Click save, and then accept the yellow banner on the top.
As for the log, it is available on the GUI, no need for SSH:
-
60000 is an acceptable value for Jail Ban Time, as you have shown. When I try to use 99999+1 = 100000 it fails.
-
As for the log, it is available on the GUI, no need for SSH
These are system logs. I'm talking about ban statistics.
OMV 5 had statistics, a complete analogue of command
BashJAILS=`fail2ban-client status | grep "Jail list" | sed -E 's/^[^:]+:[ \t]+//' | sed 's/,//g'` for JAIL in $JAILS do fail2ban-client status $JAIL doneIn OMV 6, this feature is gone.
-
Ok, maybe create a feature request and/or PR on github to apply it?
-
60000 is an acceptable value for Jail Ban Time, as you have shown. When I try to use 99999+1 = 100000 it fails.
Oh, now I see want you and mrHalfer mean:
Can't input a ban time value on individual jail config higher than 99999.
Sorry but never had an input bigger than 60000 (values I use on my rig).
But, as it is seen if you try a bigger value, a warning sticks out that it can't have a value higher than that.
Probably it is due to some limitation of fail2ban itself.
Maybe ryecoaaron can explain why is this?
-
can explain why is this?
The web interface is limited to 99999. I guess I thought that was a reasonable limit - https://github.com/OpenMediaVa…-jails-form-page.yaml#L44
Jetzt mitmachen!
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!
