This did not help unfortunately.
williamconley wrote:have you tried firewall-cmd --state at the cli yourself to see what the results are for YOU when you are root?
I get this:
- Code: Select all
firewall-cmd --state
ERROR:dbus.proxies:Introspect error on :1.4:/org/fedoraproject/FirewallD1: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
I can do this:
rm -rf /var/lib/ebtables/lock
systemctl restart firewalld
After that the firewall is running again but when i reboot the server the problem is back.
I finally got the firewall working again by reinstalling it:
systemctl stop firewalld
rm -rf /etc/firewalld
rm -rf /var/lib/firewalld
zypper in --force firewalld
systemctl enable firewalld
systemctl start firewalld
But i have to test and delve deeper if it still works as intended. I guess the vicibox-install and vicibox-express scripts change something in the firewall that breaks it in my case.
systemctl stop firewalld
rm -rf /etc/firewalld
rm -rf /var/lib/firewalld
zypper in --force firewalld
systemctl enable firewalld
systemctl start firewalld
