Sergey G. Brester

> Fail2ban is duplicating rules inside INPUT but also f2b-sshd. Normally fail2ban would never do that. Where I could imagine the double entries in iptables would be a restart of...

@K1LLUM1N471 I have a branch doing that, at the moment written relative #716 (as part of increment feature - ban-time-incr within factor plugin for observer). It can be easy configured...

@K1LLUM1N471 > How reliable is the identification of a IP this way? Good question, I would say how outdated the geoip database is. This applies of course to cymru-like services...

You have surely noticed that this is still open? In fact there is a couple of approaches that could help to "solve" (well rather implement) that, but still nothing to...

> they are banned als single ip xxx.yyy.zzz.0 Hmm... possibly you just misinterpret the output of iptables. Here is a test dropping some test subnet: ```bash $ sudo iptables -w...

> `$ iptables -nL INPUT | grep 134.73.51` > No entry for 134.73.51Chain INPUT (policy ACCEPT)) of course there is no entry, your chain (where fail2ban would add it) is...

@mcmilk: I saw your new branch 23 trying to update to 23.01... Do you try to update it by copy & paste source and do manual review hereafter? Or cherry-picking...

I assume it was multithreaded compression, was not it? The compression ratio may change from time to time if method uses multiple threads for compression (default by LZMA2 x9). You...

I guess I understand what you meant now - just not follow exact scenario (of unexpected case) - your description is a bit confusing... Do you mean this: 1. right-clicking...

I am sure the issue is not the version, but the inconsistency after upgrade (library for integration in file explorer didn't update therefore doesn't match new 7z.dll)... Basically same issue...