[Bug 365539] Re: iptables recent match broken

2009-07-10 Thread Leann Ogasawara
Based on Roman's comment that a patch was merged for 2.6.29, I've confirmed this patch is indeed in the latest Karmic Alpha kernel (see commit id below). I'm marking this Fix Released for Karmic which will target a 2.6.31 kernel and has most recently rebased with 2.6.31-rc2 from upstream. Images

[Bug 365539] Re: iptables recent match broken

2009-04-29 Thread Roman Hoog Antink
Please ask Jan Engelhardt (jengelh at medozas de) whether there is a patch for 2.6.28. Since it perfectly works with kernel 2.6.29, a diff of xt_recent.c might reveal the required changes (see attachment). I think, the struct to union transition is a good point to start. ** Attachment added:

[Bug 365539] Re: iptables recent match broken

2009-04-28 Thread Amit Kucheria
Roman, has this patch been sent upstream? Could you provide me with a pointer? If so, I could cherry-pick that patch into 9.04 ** Changed in: linux (Ubuntu) Importance: Undecided = Low ** Changed in: linux (Ubuntu) Status: New = Incomplete -- iptables recent match broken

[Bug 365539] Re: iptables recent match broken

2009-04-24 Thread Roman Hoog Antink
This morning (after a good night's rest) I refined my tests and came to this pattern: with Kernel 2.6.28: /proc/net/xt_recent/* have no effect on iptables rules. I did not test /proc/net/ipt_recent/* (requires Kernel option CONFIG_NETFILTER_XT_MATCH_RECENT_PROC_COMPAT which is not set in Jaunty)

[Bug 365539] Re: iptables recent match broken

2009-04-24 Thread Roman Hoog Antink
There is a patch for kernel 2.6.29 that fixes the compat path issue (thanks to Jan Engelhardt and the Netfilter team). ** Attachment added: Fix non effective /proc/net/ipt_recent/* http://launchpadlibrarian.net/25922182/xt_recent-compat-2.6.29.patch -- iptables recent match broken