On Tue, Jun 16, 2015 at 12:12:39AM -0700, David Highley wrote:
Generally we are needing to run a test to see if we have a firewall
issue so we want to stop for the test and then start the firewall up
again.
Currently, firewalld has a panic mode which, as you might expect,
drops everything. It
Quite interesting to know Matthew, thanks.
Btw, F21 and F22 releases - alongside their new distribution scheme - have
proven to be phenomenal so far, kudos!
-Martin
On Tue, Jun 16, 2015 at 1:36 PM Matthew Miller mat...@fedoraproject.org
wrote:
On Tue, Jun 16, 2015 at 12:12:39AM -0700, David
If you do a systemctl status -l firewalld
after starting up again that should you the errors it has from starting up
(the log lines would be from journald itself).
But as suggested earlier the
--panic-on
--panic-off
flags seem really cool.
--state, flag will show you if firewalld is running or
Joe Zeff wrote:
On 06/15/2015 07:44 PM, David Highley wrote:
We always see failures after doing; systemctl stop firewald followed by
systemctl start firewalld. To clear the issue we seem to have to reboot
the system.
Have you tried using this:
systemctl restart firewald
Generally
Use stop and start then.
On Tue, Jun 16, 2015 at 4:12 AM David Highley
dhigh...@highley-recommended.com wrote:
Joe Zeff wrote:
On 06/15/2015 07:44 PM, David Highley wrote:
We always see failures after doing; systemctl stop firewald followed by
systemctl start firewalld. To clear the
On Tue, Jun 16, 2015, 10:44 David Highley dhigh...@highley-recommended.com
wrote:
We always see failures after doing; systemctl stop firewald followed by
systemctl start firewalld. To clear the issue we seem to have to reboot
the system.
It may be helpful to know what the errors are.
--
We always see failures after doing; systemctl stop firewald followed by
systemctl start firewalld. To clear the issue we seem to have to reboot
the system.
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
On 06/15/2015 07:44 PM, David Highley wrote:
We always see failures after doing; systemctl stop firewald followed by
systemctl start firewalld. To clear the issue we seem to have to reboot
the system.
Have you tried using this:
systemctl restart firewald
--
users mailing list
