On Monday 2009-01-12 05:07, Patrick McHardy wrote: >>> >>> The out-of-tree xt_portscan module currently (ab)uses skb->mark and >>> nfct->mark to store its state, but such may collide with >>> user-specified marks. >>> >>> Using nfct_extend alleviates that problem and hopefully paves way >>> for inclusion of the module. >> >> Sorry, I would not reserve an entry unless I know what xt_portscan is. http://article.gmane.org/gmane.linux.kernel/502344 > I feel the same way. And I would like to know why it needs > connection state. That seems counterintuitive to a portscan > detector, which is by definition trying to detect something > happening in multiple connections. Is it so? Maybe it should be called portscantype then, but what's in a name. -- 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
