Michael Schönbauer

auto updates: i would rather not do that. right now, the service runs a localservice (not as localnetwork), meaning it can guarantee every admin, that it will never, under no...

we must stick to what the windows advanced firewall can do. wildcards, it cannot. but i will add support for ip ranges like 192.168.0.0/24 to the ban list

heres an interesting thing: https://social.msdn.microsoft.com/Forums/ie/en-US/32614b57-f3a3-437f-a659-4777f5e6bd68/windows-firewall-limits?forum=wfp they ARE talking about performance degradation when you significantly boost the numbers up, for example, when you roll out a * into ips they DONT...

it can push UNIT32 filters per rule (the banned ips) and UINT64 rules (1 rule called Evlwatcher). to practically, theres no real limit. ill make a load test because im...

dont know why this was closed. its a mistake.

Ah. Welp its not done. Maybe i planned doing it and forgot 🤔

hi, you can just parse config.xml, the list is persisted there

### ad Part 2: changed the comment in the config.xml so that it now states: 

### ad Part 1: that will be implemented, as it is also how fail2ban does it (iirc)

reopened for part 1