You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What works as expected: WFN shows a notification, when an outgoing connection of an application is blocked because of a block all policy. after adding an explicit blocking rule to the windows firewall (manually or via WFN notifier) the notifier stops to show notifications.
But: It does not work with blocking rules that are distributed by local group policy. There may be an actual active firewall rule that blocks those connections, but WFN does not seem to recognize it and continues to show notifications. in the wf.msc UI such rules are listed with source = local group policy alongside with the normal rules (source = local setting).
Would you consider fixing that, or is it too much of an edge case?
Greetings!
The text was updated successfully, but these errors were encountered:
gepardec-wf
changed the title
Blocking Rules of Group Polidyignored
Blocking Rules distributed via Group Policy not recognized by Notifier
Jan 16, 2023
Hi (again),
Thanks for this - this is indeed an edge case but still I have to look at this since it's not expected at all. It seems we missed something when working on the rules retrieval!
Adding this to the backlog (but not promising it will be fixed for 2.6...).
Regards
Hi Wokhan,
What works as expected: WFN shows a notification, when an outgoing connection of an application is blocked because of a block all policy. after adding an explicit blocking rule to the windows firewall (manually or via WFN notifier) the notifier stops to show notifications.
But: It does not work with blocking rules that are distributed by local group policy. There may be an actual active firewall rule that blocks those connections, but WFN does not seem to recognize it and continues to show notifications. in the wf.msc UI such rules are listed with source = local group policy alongside with the normal rules (source = local setting).
Would you consider fixing that, or is it too much of an edge case?
Greetings!
The text was updated successfully, but these errors were encountered: