Bug 1399143 - something (fundamentally) wrong with firewalld?
Summary: something (fundamentally) wrong with firewalld?
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: firewalld
Version: 7.2
Hardware: x86_64
OS: Linux
low
high
Target Milestone: rc
: ---
Assignee: Eric Garver
QA Contact: qe-baseos-daemons
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-28 12:07 UTC by lejeczek
Modified: 2021-08-11 11:57 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-09-08 19:00:36 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description lejeczek 2016-11-28 12:07:18 UTC
Description of problem:

using eg. two zones one would expect that when zones/interfaces forward between each other, ports only on the target(wanting to access) zone would be relevant, their state of open/close and not on the zone/interfaces which forwards, right?
One would expect this would work out-of-box and without use of -direct rules. 
Am I correct? Can this be fixed?


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 2 Thomas Woerner 2016-12-14 10:07:01 UTC
This has been proposed for firewalld version 0.5.

Comment 3 Eric Garver 2017-06-29 13:42:44 UTC
Hi lejeczek,

Could you provide some details? The Summary and Description don't make it very clear. Configuration, CLI output, etc are helpful.

Comment 4 lejeczek 2017-06-29 19:20:18 UTC
Will do, but not earlier than in three weeks time - away on holidays - sorry.

Comment 5 lejeczek 2021-08-11 11:57:35 UTC
ok


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