Bug 606552 - Cobbler iptables configuration documentation bug within Satellite webUI and redhat.com/docs
Summary: Cobbler iptables configuration documentation bug within Satellite webUI and r...
Status: CLOSED DUPLICATE of bug 571473
Alias: None
Product: Red Hat Satellite 5
Classification: Red Hat
Component: Documentation   
(Show other bugs)
Version: 530
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: John Ha
QA Contact: Martin Minar
Depends On:
Blocks: sat540-docs
TreeView+ depends on / blocked
Reported: 2010-06-21 23:04 UTC by Xixi
Modified: 2018-10-27 13:24 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-09-29 08:28:12 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Xixi 2010-06-21 23:04:55 UTC
Description of problem:
In Satellite's webUI "Referance Guide", Chapter 11. Cobbler (rhn/help/reference/en-US/ch-cobbler.jsp#s2-cobbler-reqs-security), the IPTable configuration command has an incorrect entry:

/sbin/iptables -A INPUT -m state --state NEW -m tcp -p udp --dport 25150 -j ACCEPT
should be:
/sbin/iptables -A INPUT -m state --state NEW -m udp -p udp --dport 25150 -j ACCEPT

(-m options has to be "udp" and not "tcp".)

The redhat.com documentation section also has the same error - 

Version-Release number of selected component (if applicable):
Red Hat Network (RHN) Satellite 5.3.0

How reproducible:

Steps to Reproduce:
1. See above

Actual results:
See above.

Expected results:
See above.
The docs should show "/sbin/iptables -A INPUT -m state --state NEW -m udp -p udp --dport 25150 -j ACCEPT" within Satellite webUI and redhat.com/docs section.

Additional info:

Comment 1 John Ha 2010-08-26 21:49:01 UTC
Fixed in the latest draft of the Satellite 5.4 Reference Guide here:


Thanks for the correction!

Comment 3 Martin Minar 2010-09-29 08:28:12 UTC

*** This bug has been marked as a duplicate of bug 571473 ***

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