RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 412441 - [RFE] iptables to report meaningful error messages
Summary: [RFE] iptables to report meaningful error messages
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: iptables
Version: 6.0
Hardware: All
OS: Linux
low
medium
Target Milestone: rc
: ---
Assignee: iptables-maint-list
QA Contact:
URL:
Whiteboard:
Depends On: 205268
Blocks:
TreeView+ depends on / blocked
 
Reported: 2007-12-05 17:18 UTC by Daniel Riek
Modified: 2010-02-24 18:11 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
: 508895 (view as bug list)
Environment:
Last Closed: 2010-02-24 18:11:46 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Comment 1 Karel Volný 2009-06-26 09:31:08 UTC 
I've just come across this too (iptables-1.3.5-5.3.el5) ...

I wanted to do

# iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE

but being somnambulist, I've written instead:

# iptables -t nat -A OUTPUT -o eth0 -j MASQUERADE

and got the response:

iptables: Unknown error 18446744073709551615


googling for it revealed that there is a very wide variety of causes that may lead to this message, making it totally useless ... so *please* do something about that
Comment 4 Thomas Woerner 2009-09-17 07:46:15 UTC 
The latest iptables version (1.4.4) prints another error message:

# iptables -t nat -A OUTPUT -o eth0 -j MASQUERADE
iptables: Invalid argument. Run `dmesg' for more information.

# dmesg | tail -1
ip_tables: MASQUERADE target: used from hooks OUTPUT, but only usable from POSTROUTING

What do you think about this?
Comment 5 Thomas Woerner 2009-09-17 10:40:05 UTC 
Same with fresh landed iptables-1.4.5.
Comment 6 Phil Knirsch 2009-09-22 09:30:52 UTC 
As Thomas already mentioned, especially in comment #4 the issue here is that the iptables upstream developers seem to have decided to virtually remove all kernel related error handling/parsing and in case something goes wrong with the sysctl() call just tell you to use dmesg.

As long as upstream iptables development doesn't include at least basic error messages again for the common kernel modules and error cases i don't see how we can sanely implement and support that for a long time ourselves.

Putting this bug therefore in Cond NAK Upstream for now.

Thanks & regards, Phil
Note You need to log in before you can comment on or make changes to this bug.