Bug 639026

Summary: iptables rate limiting leads to Unknown error 18446744073709551615
Product: Red Hat Enterprise Linux 5 Reporter: David Busby <d.busby>
Component: iptablesAssignee: Thomas Woerner <twoerner>
Status: CLOSED WONTFIX QA Contact: qe-baseos-daemons
Severity: medium Docs Contact:
Priority: low    
Version: 5.5CC: d.busby
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-06-02 13:03:25 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description David Busby 2010-09-30 16:23:20 UTC
Description of problem:

Apparent limit on --hitcount arg within iptables leading to 
iptables: Unknown error 18446744073709551615

A work around for this is to reduce the --seconds value to attain a raised hit/sec rate.

Version-Release number of selected component (if applicable):

iptables-1.3.5-5.3.el5_4.1

How reproducible: 


Steps to Reproduce:
1. iptables -I INPUT 2 -p tcp --dport http -m state --state NEW -m recent --update --seconds 60 --hitcount 30 -j LOG --log-level=7

this is also true of -j REJECT rules,
  
Actual results:

iptables: Unknown error 18446744073709551615


Expected results:

rate limiting iptables rule, logging exceeded rate via kernel messages

Comment 1 RHEL Program Management 2014-03-07 12:40:15 UTC
This bug/component is not included in scope for RHEL-5.11.0 which is the last RHEL5 minor release. This Bugzilla will soon be CLOSED as WONTFIX (at the end of RHEL5.11 development phase (Apr 22, 2014)). Please contact your account manager or support representative in case you need to escalate this bug.

Comment 2 RHEL Program Management 2014-06-02 13:03:25 UTC
Thank you for submitting this request for inclusion in Red Hat Enterprise Linux 5. We've carefully evaluated the request, but are unable to include it in RHEL5 stream. If the issue is critical for your business, please provide additional business justification through the appropriate support channels (https://access.redhat.com/site/support).

Comment 3 Red Hat Bugzilla 2023-09-14 01:22:15 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days