Red Hat Bugzilla – Bug 993655
GUI: missing name of active zone
Last modified: 2015-03-05 08:22:40 EST
Description of problem:
firewall-config: missing name of active zone
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. change zone of connection to non default, like home:
$ firewall-cmd --get-active-zone
$ firewall-cmd --get-default-zone
GUI > you are not able to see which zone is current
for ex there is name of active zone in the status bar per interface.
Actually this stuff like NM connection ~ zone users don't understand much.
There is settings in the NM applet but its hard to understand why users should look at there.
(In reply to Petr Sklenar from comment #0)
> Expected results:
> for ex there is name of active zone in the status bar per interface.
Currently we make name of default zone bold in the list of zones and also show it on the status bar on the bottom. Maybe we could show the active zones on the status bar instead of default zone while still marking the default zone bold in the list.
(In reply to Petr Sklenar from comment #3)
> Actually this stuff like NM connection ~ zone users don't understand much.
I see. It's even not been easy for me to explain it to somebody else in a simple way :-(
another request for this is bug #1008118
Please have a look at the Interface tab in zones. All interfaces (also bound to connections with NM) are located there. You can now also easily change the zone for this connection in there. It is not opening nm-connection-editor anymore.
If this already fits your needs, please close this bug.
(In reply to Jiri Popelka from comment #4)
> Currently we make name of default zone bold in the list of zones and also
> show it on the status bar on the bottom. Maybe we could show the active
> zones on the status bar instead of default zone while still marking the
> default zone bold in the list.
Or vice-versa, i.e. keep showing default zone on bottom status bar and make *active* zones (instead of default zone) bold in the list of zones.
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.