All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Gaurav Sinha <vgsinha@gmail.com>
Cc: netfilter-devel <netfilter-devel@vger.kernel.org>
Subject: Re: iptables ulog-cprange
Date: Wed, 9 May 2012 00:36:11 +0200	[thread overview]
Message-ID: <20120508223611.GA18723@1984> (raw)
In-Reply-To: <4FA98904.3070008@gmail.com>

Hi Gaurav,

On Tue, May 08, 2012 at 01:58:44PM -0700, Gaurav Sinha wrote:
> Hi All,
> 
> I am getting this error which points out the ulog-cprange that I am
> using is incorrect. It
> should be a value in between 1-50. The man page says 0 is allowed
> too, i.e. any number of
> bytes. But, I cannot configure zero as well.
> 
> Is zero no longer supported? Probably the man page is not updated
> with this information.
> 
> iptables v1.4.12.2: ULOG: bad value for option "--ulog-cprange", or out of
> range (1-50).
> 
> Try `iptables -h' or 'iptables --help' for more information.
> Error: [iptables -t raw -I MY_PREROUTING_HOOK 1 -i eth0 -j ULOG
> --ulog-nlgroup 2 --ulog-cprange 64 --ulog-qthreshold 10] failed - 512

A bug was accidentally introduced in:

1f2474a libipt_ULOG: use guided option parser

I have applied the following patch to resolve this issue:

http://git.netfilter.org/cgi-bin/gitweb.cgi?p=iptables.git;a=commitdiff;h=6111382a6c27e73c1cef1777c1253be0453a9dbb;hp=8db1044ba608a78035bbf89007aab6b6d8ff6f68

Thanks for reporting the problem.

  reply	other threads:[~2012-05-08 22:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-08 20:58 iptables ulog-cprange Gaurav Sinha
2012-05-08 22:36 ` Pablo Neira Ayuso [this message]
2012-05-09  7:13   ` Gaurav Sinha

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=20120508223611.GA18723@1984 \
    --to=pablo@netfilter.org \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=vgsinha@gmail.com \
    /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.