From: Andrew Beverley <andy@andybev.com>
To: Krzysztof Oledzki <olenf@ans.pl>
Cc: netfilter@lists.netfilter.org, martin.bene@icomedias.com,
kraxel@bytesex.org, netfilter-devel@lists.netfilter.org
Subject: Re: Connlimit and linux-2.6.17
Date: Sat, 22 Jul 2006 10:34:31 +0100 [thread overview]
Message-ID: <44C1F127.5040704@andybev.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0607220227500.2260@bizon.gios.gov.pl>
Krzysztof Oledzki wrote:
>
>
> On Sat, 22 Jul 2006, Andrew Beverley wrote:
>
>>>>>> I (and others, see netfilter list) are having trouble compiling
>>>>>> kernel 2.6.17.4 and iptables-1.3.5-20060508 to use connlimit. Once
>>>>>> compiled in and I run:
>>>>
>>>> <snip>
>>>>
>>>>> Yes, the API was changed in 2.6.17, so small fixes are required to
>>>>> allow extensions to work. I'm currently traveling a lot so
>>>>> connlimit & TARPIT is still on my TODO list. I'm going to finish it
>>>>> ASAP but with limited GPRS/EDGE access it is not so simple.
>>>
>>> OK, I fixed the connlimit extension. Please:
>>>
>>> - tell me if it works (or not).
>>>
>>
>> I forgot to mention - I get a lot of 'ipt_connlimit: Oops: invalid ct
>> state' error messages scrolling up the screen.
>
> But when did it start? In 2.6.17?
Sorry - should have said. It has always done it. I thought I'd take the
opportunity to ask as I've never found the answer.
>
>> Is it safe for me to edit ipt_connlimit.c to not print them? Or are
>> they telling me there is something wrong with my setup?
>
> Plase try adding "-m conntrack --ctstate INVALID -j DROP" before "-m
> connlimit (...)". Did it help?
Yes, that sorts it. I have a lot of clients on my network and these look like
they're generated by some p2p software of one PC.
Many thanks,
Andy
next prev parent reply other threads:[~2006-07-22 9:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-19 21:29 Connlimit and linux-2.6.17 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 [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-07-19 15:13 Adlan
2006-07-19 21:21 ` Andrew Beverley
2006-07-16 21:53 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=44C1F127.5040704@andybev.com \
--to=andy@andybev.com \
--cc=kraxel@bytesex.org \
--cc=martin.bene@icomedias.com \
--cc=netfilter-devel@lists.netfilter.org \
--cc=netfilter@lists.netfilter.org \
--cc=olenf@ans.pl \
/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.