Delete alias. Currently in use by filter rule id 91
-
@Unoptanio
Never seen such a short ID.
But you can go to Diagnostic > command prompt and execute "cat /tmp/rules.debug" to list all the rules with their IDs.You should be able to find the responsible rule in the list.
-
That's the actual rule number not the tracking ID, which is much longer.
You can see it in the running ruleset using:
pfctl -vvsr | grep @91
Or you can see it in the Rules view in Diag > pfTop
Or you can open the config file and just search it for 'cancellare'
-
@stephenw10 said in Delete alias. Currently in use by filter rule id 91:
pfctl -vvsr | grep @91
return:
@91 block drop in log on ! ovpns1 inet from 10.10.94.0/24 to any ridentifier 1000011970
There is not here:
-
It looks like it's on the assigned interface from ovpns1 not the group OpenVPN interface. Burt also there are no ports defined there so no ports alias.....
I'd check the config file directly.
-
-
I'd also try running Status > Filter Reload and make sure it's rebuilding the ruleset correctly.
-
@stephenw10 said in Delete alias. Currently in use by filter rule id 91:
status > Filter Reload
done
The problem persists
-
Then look in the config directly. Or try running:
cat /cf/conf/config.xml | grep cancellare
-
-
OK there we go. What interface is opt9?
-
@Unoptanio Look for opt9 in Status / Interfaces
-
-
@Unoptanio Okay, now you know. The rule is on the interface named "WAN_AMPERSAND". Look at Firewall / Rules / WAN_AMPERSAND and you should be able to find it.
-
It may be disabled? Though if it was I wouldn't expect to see it in Status > Interfaces
-
yes is disabled
-
The enable it, remove the rule, then disable it again.
-
I'll try on Monday because now I'm connected remotely and I'm afraid of going to block.
I'll update you then, thanks -
I did as you said. It worked well. After re-enabling the interface I managed to eliminate the "cancellare" alias that was in a rule of this interface, thanks