-
-
Notifications
You must be signed in to change notification settings - Fork 364
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Consolidate firewall rules into a single rule? #79
Comments
Multiple entries can be specified for remoteip by separating them with a comma according to the Netsh AdvFirewall Firewall Commands but like you said it's easier to separate rules for testing purposes. |
The improvement should be minimal, beyond human recognition, in the scale of milliseconds. |
After some investigation there is no impact on system performance for firewall and hosts rules. |
By the way, it seems that adding multiple rules (on the Windows Firewall) takes a lot longer. For example, I just added the new rules with WindowsSpyBlocker and it took around a minute. Adding a single (merged) rule would probably require a couple of seconds. |
You right @Gittyperson I will make an improvement on this |
My previous statement was about Linux OS, not Windows. Sorry for that. |
Don't know if there's any impact on system performance (probably not), but is there a reason for creating separate rules (more than 150) instead of merging them into one? I believe Windows Firewall supports this and ranges can be entered too:
64.4.23.0-64.4.23.255,65.52.100.0-65.52.100.255, 191.239.54.52,207.46.41.202,207.68.166.254 etc.
Just a single, large line into "Remote address".
If anything, it will look better in the rules list. Perhaps the current method is preferred because separate rules are easier to enable/disable for testing purposes.
The text was updated successfully, but these errors were encountered: