Bug 197202 - wrong iptables target in example
wrong iptables target in example
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: rhel-sg (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Ryan Lerch
John Ha
: Documentation
Depends On:
  Show dependency treegraph
Reported: 2006-06-29 03:32 EDT by Andrew Martynov
Modified: 2014-08-04 18:16 EDT (History)
1 user (show)

See Also:
Fixed In Version: web
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-07-22 01:27:48 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Andrew Martynov 2006-06-29 03:32:21 EDT
Description of problem:
The given example contains non-standard target rule for iptables command

Version-Release number of selected component (if applicable):
rhel-sg(EN)-4-HTML-RHI (2004-09-30T17:12)

How reproducible:

Steps to Reproduce:
1. open chapter 7.6. iptables and Connection Tracking
2. look into bottom of page
3. read example
Actual results:
iptables -A FORWARD -m state --state ESTABLISHED,RELATED -j ALLOW

Expected results:
iptables -A FORWARD -m state --state ESTABLISHED,RELATED -j ACCEPT

Additional info:
ACCEPT - is embedded target.
ACCEPT - is non standard target, so requires additional pre-defenition.
Comment 1 Christopher Stone 2007-03-14 11:55:13 EDT
Hi, last night you added six dependencies to my review request, then proceeded
to remove three of those.  Of the remaining three, I cannot view two of them. 
This is the only bug I can view, and I do not see how this is related to my
review request.  Did you mistake my bug for some other bug?  There was no
comment made on my bug as to what the blocking bugs are.
Comment 2 Michael Hideo 2007-10-22 22:44:26 EDT
Removing automation notification
Comment 3 Don Domingo 2008-01-28 22:31:12 EST
already revised in source, setting bug as MODIFIED.

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