Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Bgs <bgs@bgs.hu>
To: Jan Engelhardt <jengelh@computergmbh.de>
Cc: netfilter@vger.kernel.org
Subject: Re: connlimit: 2.6.24.4 + p-o-m 20080331 compile problems
Date: Thu, 03 Apr 2008 16:52:31 +0200	[thread overview]
Message-ID: <47F4EF2F.2030607@bgs.hu> (raw)
In-Reply-To: <alpine.LNX.1.10.0804031642390.1301@fbirervta.pbzchgretzou.qr>

Funny... IPV4 is marked as experimental. And I can compile in 
ftp/irc/etc contrack helpers without enabling ipv4 conntrack. Shouldn't 
this be a dependency? (require ipv4 or ipv6 conntrack)

Also: the connlimit description says: "This match allows you to match 
against the number of parallel connections to a server per client IP 
address (or address block)." 1) It's a conntrack module 2) it states 
that it's an ipvX module -> but it does not depend on having ipvX 
conntrack enabled.

Just recompiled and the rules loaded ok.

Bye
Bgs


Jan Engelhardt wrote:
> 
> On Thursday 2008-04-03 16:40, Bgs wrote:
>>
>> I have this in the kernel:
>>
>> CONFIG_NF_CONNTRACK_ENABLED=y
>> CONFIG_NF_CONNTRACK=y
>>
> That is not enough, you need the others too, CONFIG_NF_CONNTRACK_IPV4
> 

      reply	other threads:[~2008-04-03 14:52 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-03 12:08 connlimit: 2.6.24.4 + p-o-m 20080331 compile problems Bgs
2008-04-03 12:30 ` Jan Engelhardt
2008-04-03 13:11   ` Pascal Hambourg
2008-04-03 13:45     ` Bgs
2008-04-03 13:39   ` Bgs
2008-04-03 13:47     ` Jan Engelhardt
     [not found]     ` <47F4DFF6.5000107@bgs.hu>
2008-04-03 14:18       ` Jan Engelhardt
2008-04-03 14:32         ` Bgs
2008-04-03 14:36           ` Jan Engelhardt
2008-04-03 14:40             ` Bgs
2008-04-03 14:43               ` Jan Engelhardt
2008-04-03 14:52                 ` Bgs [this message]

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=47F4EF2F.2030607@bgs.hu \
    --to=bgs@bgs.hu \
    --cc=jengelh@computergmbh.de \
    --cc=netfilter@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox