Bug 1393703 - Iptables rules can be added after terminal DROP or REJECT rule
Summary: Iptables rules can be added after terminal DROP or REJECT rule
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: opstools-ansible
Version: 10.0 (Newton)
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: ---
Assignee: Martin Magr
QA Contact: Leonid Natapov
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-10 08:07 UTC by Leonid Natapov
Modified: 2020-09-24 09:35 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-09-24 09:35:00 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Leonid Natapov 2016-11-10 08:07:25 UTC 
If the target server already has a firewall configured, it may have an existing DROP or REJECT rule in place, as in:

-A INPUT -j REJECT --reject-with icmp-host-prohibited

In this case, if we append additional rules they will effectively be no-ops. This is mostly RHEL's fault, because the iptables service support doesn't really provide a way to do this cleanly, but we should try to figure out a way around it.
Comment 2 Martin Magr 2020-09-24 09:35:00 UTC 
Project is deprecated.
Note You need to log in before you can comment on or make changes to this bug.