Bug 1326462

Summary:	rich rule with destination and no element give error
Product:	Red Hat Enterprise Linux 7	Reporter:	Saul Serna <sserna>
Component:	firewalld	Assignee:	Thomas Woerner <twoerner>
Status:	CLOSED ERRATA	QA Contact:	Tomas Dolezal <todoleza>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	7.2	CC:	brian, todoleza
Target Milestone:	rc
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	firewalld-0.4.2-1.el7	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-11-03 21:02:55 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Saul Serna 2016-04-12 17:57:58 UTC

Customer states they are running into the same exact issue as the following bug, except on RHEL 7.2


Bug 1163428 - rich rule with destination and no element 


Customer Comment:
----------------------------------------------------------

I am seeing the same issue as described by this unresolved Fedora bug (https://bugzilla.redhat.com/show_bug.cgi?id=1163428). 
It occurs with newer firewalld packges (firewalld-0.3.9-14.el7.noarch). 
I get the same issue when I attempt to create a rich rule with destination address but no protocol/port it gives error:

ERROR: INVALID_RULE: no element, no source

Also, when using a source AND destination address but no protocol/port I get:

Error: INVALID_RULE: destination action

Firstly, the error messages provide no useful information about the problem. Secondly, I would like to understand why a port and/or protocol are required in these scenarios. I think it is a perfectly logical use-case to allow all traffic (protocols) coming into a particular interface/address. Furthermore, "all" is not a valid selection for the protocol, why?

Not urgent but would like to understand the function better and possibly get it fixed to be more intuitive.

Comment 3 Thomas Woerner 2016-05-25 15:34:33 UTC

Fixed upstream: https://github.com/t-woerner/firewalld/commit/221d810557deb62e0c402bfadf2f965ebdab70f1

Comment 6 Thomas Woerner 2016-07-12 11:56:08 UTC

*** Bug 1352179 has been marked as a duplicate of this bug. ***

Comment 9 errata-xmlrpc 2016-11-03 21:02:55 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHSA-2016-2597.html