Running Untangle: 16.5.0.20220125T104621.4a2ac8c1bf-1buster
I think I found a bug, I have a rule for the bypass that if tag a host with "bypass" it bypasses the NG Firewall stack. When I cleared the tag the host continues to be bypassed. Here is a image of rule:
bypass1.png
The host isn't tagged:
bypass2.png
And the sessions are still showing bypassed:
bypass3.png
If I disable the bypass rule in the bypass rule list the host 192.168.10.166 goes back to normal processing. When I turn the rule back on the host is bypassed again. So from my perspective the NG Firewall still thinks the tag is on the host even though the UI shows the tag isn't set.
I really wanted to use this for host testing where I can set the tag for a period of time and then have it auto revoked. Now that this host is struck in bypass how do I clear it?