In automatic mode, the firewall creates a huge number of rules. This is because the rule is created for a specific version of each application. After the update, the version of the application changes and the previously existing rule is no longer valid. A duplicate of the rule is created. The rule table grows uncontrollably.
Of course, I can manually create the rules I need.. However, this is not something I would like to do all the time. In policy-based mode, if I create all the rules and do not edit them after updating the applications, I risk sooner or later left without the Internet In an interactive mode, daily adjustments of the rules turn into a test for my nerves.
Why are application rules defined as an absolute path to the executable file? Are there any plans to fix the firewall?
Uncontrolled firewall rules creation (EIS)
in ESET Internet Security & ESET Smart Security Premium
Posted · Edited by jeepyebrilo
Hello,
In automatic mode, the firewall creates a huge number of rules. This is because the rule is created for a specific version of each application. After the update, the version of the application changes and the previously existing rule is no longer valid. A duplicate of the rule is created. The rule table grows uncontrollably.
Of course, I can manually create the rules I need.. However, this is not something I would like to do all the time. In policy-based mode, if I create all the rules and do not edit them after updating the applications, I risk sooner or later left without the Internet In an interactive mode, daily adjustments of the rules turn into a test for my nerves.
Why are application rules defined as an absolute path to the executable file? Are there any plans to fix the firewall?