RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

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:

in case it may matter - I use net.ifnames=0 for kernel

(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

--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.

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