All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Beverley <andy@andybev.com>
To: netfilter@lists.netfilter.org
Subject: Connlimit and linux-2.6.17
Date: Sun, 16 Jul 2006 22:53:34 +0100	[thread overview]
Message-ID: <44BAB55E.4010501@andybev.com> (raw)

I am having trouble using connlimit with kernel 2.6.17.4 and
iptables-1.3.5-20060508. When I run:

iptables -t mangle -A PREROUTING -p tcp -i eth0 -m \
	connlimit --connlimit-above 5 -j LOG

I get "iptables: Invalid argument"

The kernel and iptables are patched with patch-o-matic-ng-20060626,
which in turn is patched as per
http://patchwork.netfilter.org/netfilter-devel/patch.pl?id=3456 to
uupdate the connlimit patch

I have noticed that when compiling the kernel I get error messages as
follows when compiling connlimit:

net/ipv4/netfilter/ipt_connlimit.c:211: warning: initialization from
incompatible pointer type
net/ipv4/netfilter/ipt_connlimit.c:212: warning: initialization from
incompatible pointer type
net/ipv4/netfilter/ipt_connlimit.c:213: warning: initialization from
incompatible pointer type

The above error messages do not appear when using 2.6.15, and connlimit
works.

Any ideas?

On another note, will connlimit ever form part of the stable kernel? It
is a real pain having to mess around patching each time I get a new
kernel, especially as currently the patch-o-matic also requires patching!

Andy Beverley



             reply	other threads:[~2006-07-16 21:53 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-16 21:53 Andrew Beverley [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-07-19 15:13 Connlimit and linux-2.6.17 Adlan
2006-07-19 21:21 ` Andrew Beverley
2006-07-19 21:29 Andrew Beverley
2006-07-19 22:39 ` Krzysztof Oledzki
2006-07-19 22:45   ` Andrew Beverley
2006-07-21 20:06     ` Krzysztof Oledzki
2006-07-21 20:23       ` Andrew Beverley
2006-07-21 20:32         ` Krzysztof Oledzki
2006-07-21 23:30       ` Andrew Beverley
2006-07-22  0:10       ` Andrew Beverley
2006-07-22  0:37         ` Krzysztof Oledzki
2006-07-22  9:34           ` Andrew Beverley

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=44BAB55E.4010501@andybev.com \
    --to=andy@andybev.com \
    --cc=netfilter@lists.netfilter.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.