This is very similar to the issues I had with simplewall. So not surprising really.
Is there a way to fix it?
Basically the scenario is as follows -- it appears the rules are properly applied only when the service starts, or when the rules are changed.
If you have a rule allowing an app, and default blocking action, all works with normal apps. But with portable apps, more specifically the ones which are not avail during service start, there is a problem. Their rules are not applied basically, even when such app eventually appears.
For my portable apps (which are portable browsers) I either restart the firewall service, or simply do block then allow on the app to make it working. As an example, I have "g:\lfox..... " portable browser, and this path is not avail during user logon. I add this manually later as a removable drive. The path is exactly same every time, and there is a rule in the fort's list to allow this app. Yet without e.g. service restart the fort blocks this app regardless.
This is very similar to the issues I had with simplewall. So not surprising really.
Is there a way to fix it?
Basically the scenario is as follows -- it appears the rules are properly applied only when the service starts, or when the rules are changed.
If you have a rule allowing an app, and default blocking action, all works with normal apps. But with portable apps, more specifically the ones which are not avail during service start, there is a problem. Their rules are not applied basically, even when such app eventually appears.
For my portable apps (which are portable browsers) I either restart the firewall service, or simply do block then allow on the app to make it working. As an example, I have "g:\lfox..... " portable browser, and this path is not avail during user logon. I add this manually later as a removable drive. The path is exactly same every time, and there is a rule in the fort's list to allow this app. Yet without e.g. service restart the fort blocks this app regardless.