Whitelisted IP is listed as temporary banned in console but it's not #111
Description
Hey this might just be the way your code orders things but when i add a whitelisted ip and i try to connect to RDP with wrong credentials the trigger count for that ip increases.
If we hit the limit the console states that 1 IP is temporary banned . This is not reflected in the GUI of "Currently Banned" and i still can login as expected.
03.02.2023 10:04:39 - [Verbose]: BlockRDPBrutersByRdpCore131: found 44.x.x.x, trigger count is 3
03.02.2023 10:04:39 - [Verbose]: BlockRDPBrutersByRdpCore131: found 44.x.x.x, trigger count is 4
03.02.2023 10:04:39 - [Verbose]: Provided 188 events for BlockRDPBrutersByRdpCore131_IPV6
03.02.2023 10:04:39 - [Verbose]: Polled BlockRDPBrutersBySecurity4625 and got 1 temporary and 0 permanent ban(s)
03.02.2023 10:04:39 - [Verbose]: Polled BlockRDPBrutersByRdpCore140 and got 0 temporary and 0 permanent ban(s)
03.02.2023 10:04:39 - [Verbose]: Polled BlockRDPBrutersByRdpCore131 and got 1 temporary and 0 permanent ban(s)
03.02.2023 10:04:39 - [Verbose]: Polled BlockRDPBrutersByRdpCore131_IPV6 and got 0 temporary and 0 permanent ban(s)
03.02.2023 10:04:39 - [Verbose]: Polled BlockSSHBrutersByOpenSsh and got 0 temporary and 0 permanent ban(s)
However in my opinion the console should reflect that the ip is indeed not banned because it is a whitelisted ip.