Re: firewalld question

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, 2023-06-19 at 13:07 -0500, Chris Adams wrote:
> One quirk of fireall-cmd is that there are two distinct modes - one that
> operates on the stored configuration (with --permanent) and one that
> operates on the running config (without --permanent).  

While the logic of the above makes sense, the below bit is somewhat
surprising since it's not quite what we expect.  You expect stored
settings to be stored AND applied.  There doesn't appear to be a one-
step process to do that, either in command line or using the GUI.

> When you make a change with --permanent, it is stored, and will take
> effect on future boots, but it is not applied to the current config. 
> You need to run the same command without the --permanent to apply to
> the current running config.

Adding to the confusion, if you're using the GUI, is that you see
messages at the bottom of the screen after making any changes:

   Connection to firewalld established.  Changes applied.

You expect that to mean something more than it says.

However, like with the command line, there is a reload firewalld option
in the GUI menu which will make your permanently settings apply now. 
So you don't have to make the same changes in both modes.  And there is
the opposite, to store your temporary runtime changes into the
permanent settings.  So the same kind of thing you mentioned (about
storing and reloading commands) can be done in GUI operations and
command line modes.

We're more used to controls doing something immediately.  This is more
akin to editing a configuration file, then restarting the service.
 
-- 
 
uname -rsvp
Linux 3.10.0-1160.90.1.el7.x86_64 #1 SMP Thu May 4 15:21:22 UTC 2023 x86_64
 
Boilerplate:  All unexpected mail to my mailbox is automatically deleted.
I will only get to see the messages that are posted to the mailing list.
 
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue



[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux