Bug 994134

Summary:	cli: direct rule: add examples and default table
Product:	Red Hat Enterprise Linux 7	Reporter:	Tomas Dolezal <todoleza>
Component:	firewalld	Assignee:	Thomas Woerner <twoerner>
Status:	CLOSED NOTABUG	QA Contact:	qe-baseos-daemons
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	7.0	CC:	pkotvan
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-10-23 14:44:07 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:
Embargoed:
Bug Depends On:
Bug Blocks:	980210

Description Tomas Dolezal 2013-08-06 14:46:12 UTC

Description of problem:
cli: RFE direct rule: set "filter" table as default. in iptables it may be omitted because it defaults to it. firewalld should not ignore that.

manpage: add examples of direct rules (there isn't even one)

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

How reproducible:
always

Steps to Reproduce:
works: firewall-cmd --direct --add-rule ipv4 filter INPUT 1 -s 192.168.253.253 -p tcp --dport 80 -j DROP
not work: firewall-cmd --direct --add-rule ipv4 INPUT 1 -s 192.168.253.253 -p tcp --dport 80 -j DROP


Expected results:
* direct rule without table specification defaults to "filter" table
* the rule may be shown and represented with it, the point is just to ease it for the user when configuring

Additional info:

Comment 3 Thomas Woerner 2013-10-23 14:44:07 UTC

The use of a default table for the direct interface will make parsing much more complicated and also ambiguous. This could end up in big problems.

Closing as NOT A BUG.