bugzilla-daemon at bugzilla.netfilter.org
2011-Sep-13 12:11 UTC
[Bug 748] New: Range check for ulog-cprange is wrong
http://bugzilla.netfilter.org/show_bug.cgi?id=748 Summary: Range check for ulog-cprange is wrong Product: iptables Version: unspecified Platform: All OS/Version: All Status: NEW Severity: normal Priority: P5 Component: iptables AssignedTo: netfilter-buglog at lists.netfilter.org ReportedBy: nils.rennebarth at funkwerk-ec.com Estimated Hours: 0.0 Created an attachment (id=365) --> (http://bugzilla.netfilter.org/attachment.cgi?id=365) Use right restrictions for options cprange and qthreshold The --ulog-cprange option for the ULOG target restricts its numerical argument to the range 1..ULOG_MAX_QLEN and ULOG_MAX_QLEN is defined in include/linux/netfilter_ipv4/ipt_ULOG.h to 50 The explanation given there however makes no sense. It does make sense as soon as the restriction is moved to the --ulog-qthreshold option, and the name then makes sense as well. -- Configure bugmail: http://bugzilla.netfilter.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. You are watching all bug changes.
bugzilla-daemon at bugzilla.netfilter.org
2013-Feb-14 16:33 UTC
[Bug 748] Range check for ulog-cprange is wrong
http://bugzilla.netfilter.org/show_bug.cgi?id=748 Pablo Neira Ayuso <pablo at netfilter.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |pablo at netfilter.org Resolution| |FIXED --- Comment #1 from Pablo Neira Ayuso <pablo at netfilter.org> 2013-02-14 17:33:11 CET --- Already fixed in iptables: 6111382 libipt_ULOG: fix --ulog-cprange -- Configure bugmail: http://bugzilla.netfilter.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.
Maybe Matching Threads
- [Bug 921] New: log, ulog and nflog: command-line parameters are not supported
- [ANNOUNCE] iptables 1.4.14 release
- [Bug 758] New: Retry iptables command on transient failure
- shorewall 2.0.3a, (ULOG) doesn''t log anything
- [PATCH] A default log level of ULOG is ignored by the shorewall-perl compiler (but not by shorewall-shell)