On Mon, 15 Dec 2008, Patrick McHardy wrote:
I agree that it doesn't belong to the generic networking code.
But the way its handled in netfilter is far from perfect as well.
Currently multiple modules will spam the ringbuffer repeatedly,
but offer no possibility to change anything in the behaviour of
how these packets are treated. Unfortunately we can't handle this
in the ruleset (which is exactly the reason why we're spamming
the ringbuffer), so how about we add a module option controlling
how to treat those packets and remove the printk?
How about this: let the printk be removed from conntrack and the mangle table but put (back) into the filter table with a module option, which controls the behaviour (drop/accept & log/nolog)?