On 21/01/11 14:38, Richard Weinberger wrote: > Am Freitag 21 Januar 2011, 14:25:42 schrieb Pablo Neira Ayuso: >>> Using the TRACE target the kernel would produce a lot of log messages >>> which may slow down the firewall. Especially when tracing ESTABLISHED >>> connections. My extension does not have this overhead. >> >> AFAICS, this is an ad-hoc optimization for a specific case that you >> need. So, it's basically a subset of the trace infrastructure. > > But without the overhead... I guess that one runs after defining the rule-set for first time or if it finds a problem in his rule-set. Not in his daily ruleset. >>> All I want is a friendlier output from conntrack, why should I reinvent >>> the wheel? >> >> Why doing things in user-space is reinventing the wheel? > > When I'm using TRACE I'll get a lot of log messages. > But I'm not interested in logs, I have already enough of them. I know that. I'm proposing you to make a program in user-space that can process them and print the output in some compact format, more useful than the current. > I want a session table where I can see what sessions are allowed by > which rules. I know what you want but who else in this world needs this in the Linux kernel. Of course, you can maintain this hack in your internal tree if you need it. -- To unsubscribe from this list: send the line "unsubscribe netfilter-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
