I debugged quite a few errors and fixed some memory management, and so this update should provide a much more stable experience. Please see below for information on creating new rules.
Bug fixes
- Modified three methods in FirewallActionsService.cs to ensure that when a simple rule is created, it's not restricted to your current network type. This change I made a couple updates back has led to continuous problems with popups even if there was a rule. It should be fixed now. However, you will probably need to delete the rules that say something other than "any"
- Fixed confusion between reading service/application, causing the program to alert you of a blocked connection even if you already had a rule.
- Important: This fix only applies to new rules you create. For the apps that are still causing problems, you should delete their existing rules from the "Rules" tab and then recreate them. The new rules will be saved with the correct, broader scope and will work correctly on your VPN.
- To do this, simply go to the rule tab, click the protocol column to sort by protocol, and shift+select all the rules that say something other than "any" in the protocol.
- Fixed audit counter.
- Should now start at startup on Windows 10 if you have that setting added.
- Updated backend monitoring/memory issues.
Other
- Consolidated code.