When I need to log some firewall rule, I must create new similar rule with action set to log, insert it before rule I want to check and only then I can watch log.
Would it be possible to implement same behavior in 2.9 as it was in 2.8? I mean independent Log action regardless of action actually set?
At first I did not like this, but now I understand why they did this. The previous 2-3 times we were attacked our router would go down because it was logging too much, so this way you can create a log rule and tell it to limit to 1 per second or something, that way it doesn’t kill your router under a heavy load.
Sam
Old way is better. When you set some rule and want it logged it is natural just to turn logging on for that rule. If too much logging is an issue then it should be adjustable withn rule.
It is impractical to be forced to repeat rule settings in another rule just to log it.
It would be ok if we can set log rule which logs some already defined rule. This way it is very hard to maintain and very easy to make errors.
It would be ok if we can set log rule which logs some already defined rule.
Mangle allows you to do precisely that.
I stumbled int this problem again. It is quite frustrating.
If I want to log something either I must repeat the same rule twice (to log and then to do the action) which leads to requieemnt to change log rule each time I change actionrule, or, I can use mangling to make it easier to log but aditionaly complicate even simple rules.