Bug 1238044 - [doc] firewall commands do not match to the table of required ports
Summary: [doc] firewall commands do not match to the table of required ports
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Docs Install Guide
Version: 6.1.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: Unspecified
Assignee: Peter Ondrejka
QA Contact: Tahlia Richardson
URL:
Whiteboard:
: 1250938 (view as bug list)
Depends On: 1226727
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-07-01 04:58 UTC by Jan Hutař
Modified: 2019-09-26 18:06 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-08-12 11:52:21 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Jan Hutař 2015-07-01 04:58:41 UTC
Document URL:
https://access.redhat.com/documentation/en-US/Red_Hat_Satellite/6.1/html/Installation_Guide/sect-Red_Hat_Satellite-Installation_Guide-Prerequisites.html#form-Red_Hat_Satellite-Installation_Guide-Prerequisites-Required_Network_Ports


Section Number and Name:
"Table 1.3. Required Network Ports" and "Procedure 1.1. To modify the firewall with the iptables command:"


Describe the issue:
Not all ports from the table are being opened in the procedure (in either RHEL6 or RHEL7 variant of it). I'm confused what is a correct.


Suggestions for improvement:
Sync all ports from the table to the commands there.


Additional information:
It would be good to have someone knowledgeable to review

Comment 1 RHEL Program Management 2015-07-01 05:13:34 UTC
Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.

Comment 4 PixelDrift.NET Support 2015-07-05 11:06:46 UTC
Table 1.4 'SELinux Commands' is also out of sync with Table 1.3 'Required Network Ports'.

Comment 7 Peter Ondrejka 2015-08-06 13:49:48 UTC
*** Bug 1250938 has been marked as a duplicate of this bug. ***


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