Policy route negation rules receive the same tracker ID as the rule they are based upon, which confuses the log parser
If the policy route negation rules are active, the automatic negation rule receives the same tracker ID as the rule it is based upon:
pass in quick on $LAN inet proto tcp from any to <negate_networks> tracker 1429792471 flags S/SA keep state label "NEGATE_ROUTE: Negate policy routing for destination"
pass in quick on $LAN $GWttest inet proto tcp from any to any tracker 1429792471 flags S/SA keep state label "USER_RULE: negate check test"
Since the tracker ID is the same and it comes first in the ruleset, when set to log, the logs show the negate rule as passing the traffic when that is not the case.
Fixes #4651 use proper var name on global to have the correct id put on the rule