Hi!
I did not find anything of this in the forums or documention either,
so I was looking at port knocking, when this rule came up:
add action=drop chain=input disabled=yes in-interface-list=WAN src-address-list=blacklist
Now I doubt it is simply initiating the rule as disabled, would seem counterproductive as it was in their example guide to use that rule.
However I cannot wrap around what disabled=yes would do here.
Cheers for any illumination on the subject.
/X
It means rule is turned off.
Not doing anything.
Why port knocking if you can do wireguard??
Thought it an interesting idea, I am just getting started in understanding networks. So while I might not use it, it has been a bit educational reading about and how to implement.
Implementing then is not the goal but understanding the rules and how to use them in a config is a worthy process…
There are a number of reasons why you might have disabled rules. One example is that you are trying something that does not work. So instead of editing the rule, copy the rule and change the copy and disable the original rule. That makes it easier to go back to where you started. Eventually the non-working rules will get deleted.
I have a bunch of packet counter rules that are mainly for testing. They are normally left disabled, but enabled when I need to some specific testing.
Just a couple examples.