Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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:
sometimes when autoconnect profile is created and zone changed while the profile is connected NM may set zone incorrectly. This can be a security problem.
firewalld debug log:
2014-06-02 09:58:33 DEBUG1: zone.addInterface('', 'eth0')
2014-06-02 09:58:33 DEBUG1: zone.InterfaceAdded('public', 'eth0')
2014-06-02 09:58:36 DEBUG1: zone.addInterface('', 'eth6')
2014-06-02 09:58:36 DEBUG1: zone.InterfaceAdded('public', 'eth6')
2014-06-02 09:58:41 DEBUG1: zone.removeInterface('drop', 'eth6')
2014-06-02 09:58:41 ERROR: ZONE_CONFLICT
2014-06-02 09:58:41 DEBUG1: zone.addInterface('drop', 'eth6')
2014-06-02 09:58:41 ERROR: ZONE_CONFLICT
2014-06-02 09:58:45 DEBUG1: zone.getInterfaces('drop')
2014-06-02 09:58:45 DEBUG1: zone.getSources('drop')
2014-06-02 09:58:45 DEBUG1: zone.getServices('drop')
2014-06-02 09:58:45 DEBUG1: zone.getPorts('drop')
2014-06-02 09:58:45 DEBUG1: zone.queryMasquerade('drop')
2014-06-02 09:58:45 DEBUG1: zone.getForwardPorts('drop')
2014-06-02 09:58:45 DEBUG1: zone.getIcmpBlocks('drop')
2014-06-02 09:58:45 DEBUG1: zone.getRichRules('drop')
2014-06-02 09:58:45 DEBUG1: getDefaultZone()
2014-06-02 09:58:45 DEBUG1: zone.removeInterface('drop', 'eth6')
2014-06-02 09:58:45 ERROR: ZONE_CONFLICT
Version-Release number of selected component (if applicable):
NetworkManager-0.9.9.1-20.git20140326.4dba720.el7_0.x86_64
How reproducible:
occasionally
Steps to Reproduce:
1.create a connection via: nmcli con add type ethernet ifname device con-name profile
2.edit the connection via: nmcli con edit profile
3.set connection.zone drop
4.save
5.quit
6.start connection via: nmcli con up profile
Actual results:
sometimes there is a zone_conflict error and the zone is not set correctly
Expected results:
no errors
Additional info:
Description of problem: sometimes when autoconnect profile is created and zone changed while the profile is connected NM may set zone incorrectly. This can be a security problem. firewalld debug log: 2014-06-02 09:58:33 DEBUG1: zone.addInterface('', 'eth0') 2014-06-02 09:58:33 DEBUG1: zone.InterfaceAdded('public', 'eth0') 2014-06-02 09:58:36 DEBUG1: zone.addInterface('', 'eth6') 2014-06-02 09:58:36 DEBUG1: zone.InterfaceAdded('public', 'eth6') 2014-06-02 09:58:41 DEBUG1: zone.removeInterface('drop', 'eth6') 2014-06-02 09:58:41 ERROR: ZONE_CONFLICT 2014-06-02 09:58:41 DEBUG1: zone.addInterface('drop', 'eth6') 2014-06-02 09:58:41 ERROR: ZONE_CONFLICT 2014-06-02 09:58:45 DEBUG1: zone.getInterfaces('drop') 2014-06-02 09:58:45 DEBUG1: zone.getSources('drop') 2014-06-02 09:58:45 DEBUG1: zone.getServices('drop') 2014-06-02 09:58:45 DEBUG1: zone.getPorts('drop') 2014-06-02 09:58:45 DEBUG1: zone.queryMasquerade('drop') 2014-06-02 09:58:45 DEBUG1: zone.getForwardPorts('drop') 2014-06-02 09:58:45 DEBUG1: zone.getIcmpBlocks('drop') 2014-06-02 09:58:45 DEBUG1: zone.getRichRules('drop') 2014-06-02 09:58:45 DEBUG1: getDefaultZone() 2014-06-02 09:58:45 DEBUG1: zone.removeInterface('drop', 'eth6') 2014-06-02 09:58:45 ERROR: ZONE_CONFLICT Version-Release number of selected component (if applicable): NetworkManager-0.9.9.1-20.git20140326.4dba720.el7_0.x86_64 How reproducible: occasionally Steps to Reproduce: 1.create a connection via: nmcli con add type ethernet ifname device con-name profile 2.edit the connection via: nmcli con edit profile 3.set connection.zone drop 4.save 5.quit 6.start connection via: nmcli con up profile Actual results: sometimes there is a zone_conflict error and the zone is not set correctly Expected results: no errors Additional info: