Oh sorry! I should have told you I made a Github issue: https://github.com/henrypp/simplewall/issues/274 He said it there. But it looks like he misunderstood me or something, so I don't think he is changing anything.
Oh thanks for doing that and for trying to clarify with the author. I think summary is, in the current version of Simplewall: - A special rule with check acts as full access. - If you want special rule (for restricted IP access), do not add check mark. - Enable or disable special rules only from "settings -> user rules" Overall, better to just enable "loopback" for all programs (this matches with default of Windows Firewall and WFC). This way no need to add special rules for 127.0.0.1 Good discussion friend. Thank you. Overall, I think it is a great program. There is still one *small* issue with Simplewall. I will also create Github issue for it: If you open a program and see a notification, then close the notification using the x/cross on top-right, notification will go away. Good so far. Now if you exit the program, Simplewall will still give notification again, even though the program is not running.
On that github page, henry said that block special rules still work on an allowed (checked) app, if the special block rule is activated too ofc
Yes, there are still many issues with notifications. Despite him having fixed the issue where notification wont appear, they still appear very rarely for me. And now I'm unsure if he takes me serious or not. I'm honestly a little upset.
You should not be. Everything is fine with his reply imo. Anyone who has ever used a rule based firewall knows how to answer prompts - select port for a desired protocol and you're good to go - you don't click on allow to a blank rule, this clearly implies that you are allowing it all comms. The fact that some people allowed all comms to apps is not henry's fault. Yeah, the GUI is a bit unintuitive but this just means that you have to look closely. What is his fault though is that comms should obey application rules, which as it seems is not quite the case atm.
I suspect here a 3rd party software that resets the auditing settings on your machine. Some major Windows Updates (like version 1809) also overwrites auditing settings with the default ones when they are installed through Windows Update. Re-enabling the notifications system sets again the auditing settings required for WFC to be notified when a new connection is blocked in Windows Firewall. I did not receive any other similar reports that describe this as a recurrent behavior. This happens occasionally for the reason explained above. Re-enabling the notifications fixes the problem.
Hi Alex, So now I've replicated the issue many times throughout the day (even after restarting the computer). The notifications only work for about one hour. After that they stop, and I have to manually reset them (using 2 steps: disable logging, then re-enable notifications). Anything I can do to fix this? Other than this issue, I really like WFC.
