Bug 751443 - iptables-ipv6 missing comment module
Summary: iptables-ipv6 missing comment module
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: iptables
Version: 6.1
Hardware: All
OS: Linux
unspecified
low
Target Milestone: rc
: ---
Assignee: Thomas Woerner
QA Contact: qe-baseos-daemons
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-11-04 18:33 UTC by jcpunk
Modified: 2012-09-13 12:38 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-09-13 12:38:45 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description jcpunk 2011-11-04 18:33:46 UTC
Description of problem: iptables for ipv4 has the ability to add --comment to a rule for describing the rule and commenting on its addition.  The ipv6 version of iptables lacks this module


Version-Release number of selected component (if applicable):iptables-ipv6-1.4.7-4.el6


How reproducible: always


Steps to Reproduce:
1. take any existing ipv6 rule add '-m comment --comment "TESTING COMMENT"' to it
2. attempt to load rule
3. watch it fail
  
Actual results: rule fails to load


Expected results: a comment exists for the rule as it does in ipv4


Additional info:

Comment 2 RHEL Program Management 2011-11-04 19:08:47 UTC
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unfortunately unable to
address this request at this time. Red Hat invites you to
ask your support representative to propose this request, if
appropriate and relevant, in the next release of Red Hat
Enterprise Linux. If you would like it considered as an
exception in the current release, please ask your support
representative.

Comment 3 Thomas Woerner 2012-09-13 12:38:45 UTC
The comment module is part of the iptables package and can be used by ip6tables also.


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