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 921403 - ip6tables "Can't specify HL option twice"
Summary: ip6tables "Can't specify HL option twice"
Keywords:
Status: CLOSED CANTFIX
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: iptables
Version: 6.4
Hardware: x86_64
OS: Linux
unspecified
low
Target Milestone: rc
: ---
Assignee: Thomas Woerner
QA Contact: qe-baseos-daemons
URL:
Whiteboard:
Depends On:
Blocks: 947775
TreeView+ depends on / blocked
 
Reported: 2013-03-14 06:55 UTC by Phillip Smith
Modified: 2013-08-14 12:52 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-08-14 12:52:46 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
CentOS 6315 0 None None None Never

Description Phillip Smith 2013-03-14 06:55:39 UTC
When trying to create certain rules, an invalid error is returned:

~ # ip6tables -A INPUT -p icmpv6 --icmpv6-type redirect -m hl ! --hl-eq 255 -j
DROP -m comment --comment "this is a comment"
ip6tables v1.4.7: Can't specify HL option twice
Try `ip6tables -h' or 'ip6tables --help' for more information.

The error is invalid because the HL option is not specified twice. Removing the
comment from the rule works as expected.


Version-Release number of selected component (if applicable):
ip6tables v1.4.7


How reproducible:
Always.


Steps to Reproduce:
Execute the following command as root:
ip6tables -A INPUT -p icmpv6 --icmpv6-type redirect -m hl ! --hl-eq 255 -j
DROP -m comment --comment "husk line 13"

  
Actual results:
ip6tables v1.4.7: Can't specify HL option twice
Try `ip6tables -h' or 'ip6tables --help' for more information.


Expected results:
No error; corresponding rule is entered into the appropriate kernel netfilter table/chain.

Additional info:
The issue has been reported and appears to have been resolved upstream:
http://bugzilla.netfilter.org/show_bug.cgi?id=766

Original bug report when I discovered the problem:
https://github.com/fukawi2/husk/issues/8

Comment 2 RHEL Program Management 2013-06-07 14:31:22 UTC
This request was evaluated by Red Hat Product Management for
inclusion in a Red Hat Enterprise Linux release.  Product
Management has requested further review of this request by
Red Hat Engineering, for potential inclusion in a Red Hat
Enterprise Linux release for currently deployed products.
This request is not yet committed for inclusion in a release.

Comment 3 Thomas Woerner 2013-08-14 12:52:46 UTC
I am sorry, but this can not be easily fixed without breaking other parts of iptables. iptables upstream created a completely new parser because of similar problems and this is too invasive for version 1.4.7.

Closing as CANTFIX.


Note You need to log in before you can comment on or make changes to this bug.