[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re[2]: Is connlimit available in etch? Will it be available in future?

Dear Pascal,
It seems that "connlimit" doesn't work even on kernel etch-n-half.
(though error output in etch-n-half is quite different from that
 in default 2.6.18-6 kernel)

Friday, October 17, 2008, 4:54:48 PM, you wrote:

> The connlimit match support was included in the mainline kernel since 
> version 2.6.23, so it is not available in the default 2.6.18 kernels 
> included in Debian etch. However it is available in the newer 
> 2.6.24-etchnhalf kernel which was added to the latest release of Debian
> etch, 4.0r4.

I used two PCs with up-to-date "etch" for architectures AMD64 and 486,
and in both cases I've got error message:
"iptables: Invalid argument"

1)  Kernels used:

2) iptables package:  iptables-

3) Output of "zgrep CONNLIMIT /proc/config.gz" command:

4) iptables command:
        frya:/home/nick# iptables -t filter -A INPUT -p tcp --syn --dport 23 -m connlimit --connlimit-above 2 -j REJECT
   iptables error message:
        iptables: Invalid argument

5) The same command with "strace" produced bulk output that I can't
understand. I've compared this output with normally completed iptables
command, and I think that main difference is at last "setsockopt"
call. Please find below last 4 lines of strace for 486 architecture:
getsockopt(3, SOL_IP, 0x40 /* IP_??? */, "filter\0\313\200\267\t\313\10\0\0\0\200#\0\313\240\35\n"..., [84]) = 0
getsockopt(3, SOL_IP, 0x41 /* IP_??? */, "filter\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., [840]) = 0
setsockopt(3, SOL_IP, 0x40 /* IP_??? */, "filter\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 1136) = -1 EINVAL (Invalid argument)
write(2, "iptables: Invalid argument\n", 27iptables: Invalid argument
) = 27
exit_group(1)                           = ?

1) Is it a bug? If yes, should I report it via Bugzilla?
2) Does "connlimit" work in next release candidate "lenny"?

Best regards,

Reply to: