Bug 1174909

Summary: interface put in a zone is lost on reboot and reassigned to default zone
Product: Red Hat Enterprise Linux 7 Reporter: lejeczek <peljasz>
Component: firewalldAssignee: Thomas Woerner <twoerner>
Status: CLOSED DUPLICATE QA Contact: qe-baseos-daemons
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 7.0CC: jpopelka, peljasz, riehecky
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-04-02 12:10:04 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:

Description lejeczek 2014-12-16 17:39:10 UTC 
Description of problem:

I have eth0 & eth1 & virbr0 - pretty standard setup.
I put eth1 into external zone and eth0 into work(default)
reboot the system and eth1 has gone "miraculously" into work zone.



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

firewalld-0.3.9-7.el7.noarch

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 1 lejeczek 2014-12-16 17:45:41 UTC 
in case it may matter - I use net.ifnames=0 for kernel
Comment 3 Jiri Popelka 2014-12-17 09:32:43 UTC 
(In reply to lejeczek from comment #0)
> I put eth1 into external zone

how ?
Correct way is either using NM GUI (nm-connection-editor) or
# echo ZONE=external >> /etc/sysconfig/network-scripts/ifcfg-eth1

If you used
# firewall-cmd --permanent --zone=external --add-interface=eth1
see bug #1112742
Comment 4 lejeczek 2014-12-17 10:15:51 UTC 
--permanent --add-interface

but I was looking at nmcli and thinking this - connection.zone - might be relevant, but! it's not documented anywhere.
Jiri I recommend reassigning or at least letting NM devel know, or doc/man devel know that this should be included in man pages.
Comment 6 Jiri Popelka 2015-04-02 12:10:04 UTC 

*** This bug has been marked as a duplicate of bug 1112742 ***