Bug 787348 - Incorrect iptables command
Summary: Incorrect iptables command
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Satellite 5
Classification: Red Hat
Component: Docs Deployment Guide
Version: unspecified
Hardware: Unspecified
OS: Unspecified
medium
low
Target Milestone: ---
Assignee: Athene Chan
QA Contact: ecs-bugs
URL:
Whiteboard:
Depends On:
Blocks: sat54-docs 824235
TreeView+ depends on / blocked
 
Reported: 2012-02-04 10:02 UTC by Pavel Zhukov
Modified: 2015-05-11 22:08 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-09-26 05:04:18 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Pavel Zhukov 2012-02-04 10:02:46 UTC
In 6.8.1.2.3.2. IPTables Configuration
Now:
/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

Comment 2 Pavel Zhukov 2012-05-24 05:25:18 UTC
Why worksforme???

You SHOULD NOT mix TCP module (-m tcp) and protocol UDP (-p udp) in the rule. 

Output:
WRONG:
$ sudo /sbin/iptables -A INPUT -m state --state NEW -m tcp -p udp --dport 25150 -j ACCEPT 

RIGHT:
iptables: Invalid argument. Run `dmesg' for more information.
$ sudo /sbin/iptables -A INPUT -m state --state NEW -m tcp -p tcp --dport 25150 -j ACCEPT

Comment 3 Pavel Zhukov 2012-05-24 05:30:29 UTC
I'm sorry:
Output:
WRONG:
$ sudo /sbin/iptables -A INPUT -m state --state NEW -m tcp -p udp --dport 25150 -j ACCEPT 
iptables: Invalid argument. Run `dmesg' for more information.

RIGHT:
$ sudo /sbin/iptables -A INPUT -m state --state NEW -m tcp -p tcp --dport 25150 -j ACCEPT

Comment 4 Athene Chan 2012-05-24 22:53:18 UTC
Hello Pavel,

My apologies. I accidentally set my comment to private. I've pasted my previous comments below:


============================

Hello Pavel,

The deployment guide has been deprecated and was recycled into the Getting Started Guide/Reference Guide/User Guide.

These errors have been resolved in the Reference Guide in both 5.4 and 5.5.

Should you find other discrepancies, please feel free to create a new ticket. Thank you!

============================

I hope this resolves your concern.

Regards,
Athene Chan


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