[opensuse] Why doesn't firewalld start at boot?
Hi, I first did a google and a word search in this list and the support list and the only mention of firewalld not starting at boot didn't have any replies. I did a bug search but found nothing, in fact it seems that people want to stop it at boot not start it. My Leap:15.0 laptop has it starting at boot, the only difference is that the laptop uses network manager and this pc uses wicked. I haven't bothered with this until now because kde connect doesn't work without the firewall running. Why doesn't firewalld start at boot suse firewall did. Thanks Dave P -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
did you enable it? Am Sonntag, 28. Oktober 2018, 12:53:16 CET schrieb Dave Plater:
Hi, I first did a google and a word search in this list and the support list and the only mention of firewalld not starting at boot didn't have any replies. I did a bug search but found nothing, in fact it seems that people want to stop it at boot not start it. My Leap:15.0 laptop has it starting at boot, the only difference is that the laptop uses network manager and this pc uses wicked. I haven't bothered with this until now because kde connect doesn't work without the firewall running. Why doesn't firewalld start at boot suse firewall did.
Thanks Dave P
-- Mathias Homann Senior Systems Engineer, IT Consultant. IT Trainer Mathias.Homann@openSUSE.org http://www.tuxonline.tech gpg key fingerprint: 8029 2240 F4DD 7776 E7D2 C042 6B8E 029E 13F2 C102
On 28/10/2018 15:11, Mathias Homann wrote:
did you enable it?
Am Sonntag, 28. Oktober 2018, 12:53:16 CET schrieb Dave Plater:
Hi, I first did a google and a word search in this list and the support list and the only mention of firewalld not starting at boot didn't have any replies. I did a bug search but found nothing, in fact it seems that people want to stop it at boot not start it. My Leap:15.0 laptop has it starting at boot, the only difference is that the laptop uses network manager and this pc uses wicked. I haven't bothered with this until now because kde connect doesn't work without the firewall running. Why doesn't firewalld start at boot suse firewall did.
Thanks Dave P
Yast services says it's enabled but inactive systemctl start firewalld starts it so does yast but it's enabled but inactive after boot. Don't know if this is something to do with wicked? Dave P -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* Dave Plater <dplater.list@gmail.com> [10-28-18 14:04]:
On 28/10/2018 15:11, Mathias Homann wrote:
did you enable it?
Am Sonntag, 28. Oktober 2018, 12:53:16 CET schrieb Dave Plater:
Hi, I first did a google and a word search in this list and the support list and the only mention of firewalld not starting at boot didn't have any replies. I did a bug search but found nothing, in fact it seems that people want to stop it at boot not start it. My Leap:15.0 laptop has it starting at boot, the only difference is that the laptop uses network manager and this pc uses wicked. I haven't bothered with this until now because kde connect doesn't work without the firewall running. Why doesn't firewalld start at boot suse firewall did.
Thanks Dave P
Yast services says it's enabled but inactive systemctl start firewalld starts it so does yast but it's enabled but inactive after boot. Don't know if this is something to do with wicked?
why would it have anything to do with wicked? -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 28/10/2018 21:48, Patrick Shanahan wrote:
* Dave Plater <dplater.list@gmail.com> [10-28-18 14:04]:
On 28/10/2018 15:11, Mathias Homann wrote:
did you enable it?
Am Sonntag, 28. Oktober 2018, 12:53:16 CET schrieb Dave Plater:
Hi, I first did a google and a word search in this list and the support list and the only mention of firewalld not starting at boot didn't have any replies. I did a bug search but found nothing, in fact it seems that people want to stop it at boot not start it. My Leap:15.0 laptop has it starting at boot, the only difference is that the laptop uses network manager and this pc uses wicked. I haven't bothered with this until now because kde connect doesn't work without the firewall running. Why doesn't firewalld start at boot suse firewall did.
Thanks Dave P
Yast services says it's enabled but inactive systemctl start firewalld starts it so does yast but it's enabled but inactive after boot. Don't know if this is something to do with wicked?
why would it have anything to do with wicked?
According to the man page: "If NetworkManager is not in use and firewalld gets started after the network is already up" but it doesn't say what starts it. For the requesters this is firewalld after boot: # systemctl status firewalld ● firewalld.service - firewalld - dynamic firewall daemon Loaded: loaded (/usr/lib/systemd/system/firewalld.service; enabled; vendor preset: disabled) Active: inactive (dead) Docs: man:firewalld(1) Dave P -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 29/10/2018 11.04, Dave Plater wrote:
For the requesters this is firewalld after boot: # systemctl status firewalld ● firewalld.service - firewalld - dynamic firewall daemon Loaded: loaded (/usr/lib/systemd/system/firewalld.service; enabled; vendor preset: disabled) Active: inactive (dead) Docs: man:firewalld(1)
And the rest of the output? -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)
On 29/10/2018 12:20, Carlos E. R. wrote:
On 29/10/2018 11.04, Dave Plater wrote:
For the requesters this is firewalld after boot: # systemctl status firewalld ● firewalld.service - firewalld - dynamic firewall daemon Loaded: loaded (/usr/lib/systemd/system/firewalld.service; enabled; vendor preset: disabled) Active: inactive (dead) Docs: man:firewalld(1)
And the rest of the output?
That's all there is, if I start it : # systemctl status firewalld ● firewalld.service - firewalld - dynamic firewall daemon Loaded: loaded (/usr/lib/systemd/system/firewalld.service; enabled; vendor preset: disabled) Active: active (running) since Mon 2018-10-29 13:10:52 SAST; 4s ago Docs: man:firewalld(1) Main PID: 13188 (firewalld) Tasks: 2 (limit: 4915) CGroup: /system.slice/firewalld.service └─13188 /usr/bin/python3 -Es /usr/sbin/firewalld --nofork --nopid Oct 29 13:10:49 Arbuthnot systemd[1]: Starting firewalld - dynamic firewall daemon... Oct 29 13:10:52 Arbuthnot systemd[1]: Started firewalld - dynamic firewall daemon. Dave P -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 29/10/2018 12.11, Dave Plater wrote:
On 29/10/2018 12:20, Carlos E. R. wrote:
On 29/10/2018 11.04, Dave Plater wrote:
For the requesters this is firewalld after boot: # systemctl status firewalld ● firewalld.service - firewalld - dynamic firewall daemon Loaded: loaded (/usr/lib/systemd/system/firewalld.service; enabled; vendor preset: disabled) Active: inactive (dead) Docs: man:firewalld(1)
And the rest of the output?
That's all there is, if I start it :
There are two log lines more.
# systemctl status firewalld ● firewalld.service - firewalld - dynamic firewall daemon Loaded: loaded (/usr/lib/systemd/system/firewalld.service; enabled; vendor preset: disabled) Active: active (running) since Mon 2018-10-29 13:10:52 SAST; 4s ago Docs: man:firewalld(1) Main PID: 13188 (firewalld) Tasks: 2 (limit: 4915) CGroup: /system.slice/firewalld.service └─13188 /usr/bin/python3 -Es /usr/sbin/firewalld --nofork --nopid
Oct 29 13:10:49 Arbuthnot systemd[1]: Starting firewalld - dynamic firewall daemon... Oct 29 13:10:52 Arbuthnot systemd[1]: Started firewalld - dynamic firewall daemon.
Well, it is running. No problem with it that I can see. -- Cheers / Saludos, Carlos E. R. (from openSUSE 15.0 (Legolas))
Carlos E. R. wrote:
Well, it is running. No problem with it that I can see.
That is when it is started manually - the problem is $SUBJ. -- Per Jessen, Zürich (5.6°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 29/10/2018 13.12, Per Jessen wrote:
Carlos E. R. wrote:
Well, it is running. No problem with it that I can see.
That is when it is started manually - the problem is $SUBJ.
Then check the logs after boot. That's the only way to know what happened. -- Cheers / Saludos, Carlos E. R. (from openSUSE 15.0 (Legolas))
On 29/10/2018 14:21, Carlos E. R. wrote:
On 29/10/2018 13.12, Per Jessen wrote:
Carlos E. R. wrote:
Well, it is running. No problem with it that I can see.
That is when it is started manually - the problem is $SUBJ.
Then check the logs after boot. That's the only way to know what happened.
All I can find, the two bottom lines are when I started it manually. # journalctl -b|grep firewalld Oct 29 11:46:54 Arbuthnot systemd[1]: is_symlink_with_known_name(firewalld.service, dbus-org.fedoraproject.FirewallD1.service) → 1 Oct 29 13:10:49 Arbuthnot systemd[1]: Starting firewalld - dynamic firewall daemon... Oct 29 13:10:52 Arbuthnot systemd[1]: Started firewalld - dynamic firewall daemon. maybe if I uninstall it and install it again. Dave P -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 29/10/2018 13.30, Dave Plater wrote:
On 29/10/2018 14:21, Carlos E. R. wrote:
On 29/10/2018 13.12, Per Jessen wrote:
Carlos E. R. wrote:
Well, it is running. No problem with it that I can see.
That is when it is started manually - the problem is $SUBJ.
Then check the logs after boot. That's the only way to know what happened.
All I can find, the two bottom lines are when I started it manually. # journalctl -b|grep firewalld Oct 29 11:46:54 Arbuthnot systemd[1]: is_symlink_with_known_name(firewalld.service, dbus-org.fedoraproject.FirewallD1.service) → 1 Oct 29 13:10:49 Arbuthnot systemd[1]: Starting firewalld - dynamic firewall daemon... Oct 29 13:10:52 Arbuthnot systemd[1]: Started firewalld - dynamic firewall daemon.
As far as I can see, you did not have it enabled previously. -- Cheers / Saludos, Carlos E. R. (from openSUSE 15.0 (Legolas))
On 29/10/2018 14:33, Carlos E. R. wrote:
On 29/10/2018 13.30, Dave Plater wrote:
On 29/10/2018 14:21, Carlos E. R. wrote:
On 29/10/2018 13.12, Per Jessen wrote:
Carlos E. R. wrote:
Well, it is running. No problem with it that I can see.
That is when it is started manually - the problem is $SUBJ.
Then check the logs after boot. That's the only way to know what happened.
All I can find, the two bottom lines are when I started it manually. # journalctl -b|grep firewalld Oct 29 11:46:54 Arbuthnot systemd[1]: is_symlink_with_known_name(firewalld.service, dbus-org.fedoraproject.FirewallD1.service) → 1 Oct 29 13:10:49 Arbuthnot systemd[1]: Starting firewalld - dynamic firewall daemon... Oct 29 13:10:52 Arbuthnot systemd[1]: Started firewalld - dynamic firewall daemon.
As far as I can see, you did not have it enabled previously.
After boot : # systemctl status firewalld ● firewalld.service - firewalld - dynamic firewall daemon Loaded: loaded (/usr/lib/systemd/system/firewalld.service; enabled; vendor preset: disabled) Active: inactive (dead) Docs: man:firewalld(1) Note what line 3 says: Loaded: loaded (/usr/lib/systemd/system/firewalld.service; enabled; It doesn't start at boot. Dave P -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* Dave Plater <dplater.list@gmail.com> [10-29-18 08:44]:
On 29/10/2018 14:33, Carlos E. R. wrote:
On 29/10/2018 13.30, Dave Plater wrote:
On 29/10/2018 14:21, Carlos E. R. wrote:
On 29/10/2018 13.12, Per Jessen wrote:
Carlos E. R. wrote:
Well, it is running. No problem with it that I can see.
That is when it is started manually - the problem is $SUBJ.
Then check the logs after boot. That's the only way to know what happened.
All I can find, the two bottom lines are when I started it manually. # journalctl -b|grep firewalld Oct 29 11:46:54 Arbuthnot systemd[1]: is_symlink_with_known_name(firewalld.service, dbus-org.fedoraproject.FirewallD1.service) → 1 Oct 29 13:10:49 Arbuthnot systemd[1]: Starting firewalld - dynamic firewall daemon... Oct 29 13:10:52 Arbuthnot systemd[1]: Started firewalld - dynamic firewall daemon.
As far as I can see, you did not have it enabled previously.
After boot : # systemctl status firewalld ● firewalld.service - firewalld - dynamic firewall daemon Loaded: loaded (/usr/lib/systemd/system/firewalld.service; enabled; vendor preset: disabled) Active: inactive (dead) Docs: man:firewalld(1) Note what line 3 says: Loaded: loaded (/usr/lib/systemd/system/firewalld.service; enabled; It doesn't start at boot.
correct, it's not directed to do so. explained in previous mail. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 29/10/2018 14:47, Patrick Shanahan wrote:
* Dave Plater <dplater.list@gmail.com> [10-29-18 08:44]:
On 29/10/2018 14:33, Carlos E. R. wrote:
On 29/10/2018 13.30, Dave Plater wrote:
On 29/10/2018 14:21, Carlos E. R. wrote:
On 29/10/2018 13.12, Per Jessen wrote:
Carlos E. R. wrote:
> > Well, it is running. No problem with it that I can see.
That is when it is started manually - the problem is $SUBJ.
Then check the logs after boot. That's the only way to know what happened.
All I can find, the two bottom lines are when I started it manually. # journalctl -b|grep firewalld Oct 29 11:46:54 Arbuthnot systemd[1]: is_symlink_with_known_name(firewalld.service, dbus-org.fedoraproject.FirewallD1.service) → 1 Oct 29 13:10:49 Arbuthnot systemd[1]: Starting firewalld - dynamic firewall daemon... Oct 29 13:10:52 Arbuthnot systemd[1]: Started firewalld - dynamic firewall daemon.
As far as I can see, you did not have it enabled previously.
After boot : # systemctl status firewalld ● firewalld.service - firewalld - dynamic firewall daemon Loaded: loaded (/usr/lib/systemd/system/firewalld.service; enabled; vendor preset: disabled) Active: inactive (dead) Docs: man:firewalld(1) Note what line 3 says: Loaded: loaded (/usr/lib/systemd/system/firewalld.service; enabled; It doesn't start at boot.
correct, it's not directed to do so. explained in previous mail.
I had SuSEfirewall2 installed also, don't know if that's got anything to do with it. I just uninstalled, with -u, all firewall packages then reinstalled firewalld. After a reboot it was completely disabled, I've enabled it and started it, the rules for kdeconnect were still there. /etc/sysconfig/network/config is set at yes and most probably was all along. (on that note it does state "if the SuSEfirewall when enabled should get started when network interfaces are started.") I'm going to reboot now and if it doesn't start automatically I'll try a bug report. Thanks Dave P -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 29/10/2018 14.14, Dave Plater wrote:
On 29/10/2018 14:47, Patrick Shanahan wrote:
* Dave Plater <> [10-29-18 08:44]:
After boot : # systemctl status firewalld ● firewalld.service - firewalld - dynamic firewall daemon Loaded: loaded (/usr/lib/systemd/system/firewalld.service; enabled; vendor preset: disabled) Active: inactive (dead) Docs: man:firewalld(1) Note what line 3 says: Loaded: loaded (/usr/lib/systemd/system/firewalld.service; enabled; It doesn't start at boot.
correct, it's not directed to do so. explained in previous mail.
I had SuSEfirewall2 installed also, don't know if that's got anything to do with it. I just uninstalled, with -u, all firewall packages then reinstalled firewalld. After a reboot it was completely disabled, I've enabled it and started it, the rules for kdeconnect were still there. /etc/sysconfig/network/config is set at yes and most probably was all along. (on that note it does state "if the SuSEfirewall when enabled should get started when network interfaces are started.") I'm going to reboot now and if it doesn't start automatically I'll try a bug report.
Remember that on Linux, reinstallation typically doesn't change the configuration, so the results are the same as before. SuSEfirewall2 is intentionally installed on 15.0 so that you can migrate the previous existing configuration; after doing that, you can uninstall it. There is a script to do the migration. If Patrick is correct, firewalld is started *after* network is actually started, not at boot. So check the status after the network goes up. I do not currently have a 15.0 system with wicked networking to verify. -- Cheers / Saludos, Carlos E. R. (from openSUSE 15.0 (Legolas))
On 29/10/2018 15:27, Carlos E. R. wrote:
I had SuSEfirewall2 installed also, don't know if that's got anything to do with it. I just uninstalled, with -u, all firewall packages then reinstalled firewalld. After a reboot it was completely disabled, I've enabled it and started it, the rules for kdeconnect were still there. /etc/sysconfig/network/config is set at yes and most probably was all along. (on that note it does state "if the SuSEfirewall when enabled should get started when network interfaces are started.") I'm going to reboot now and if it doesn't start automatically I'll try a bug report. Remember that on Linux, reinstallation typically doesn't change the configuration, so the results are the same as before.
SuSEfirewall2 is intentionally installed on 15.0 so that you can migrate the previous existing configuration; after doing that, you can uninstall it.
There is a script to do the migration.
If Patrick is correct, firewalld is started*after* network is actually started, not at boot. So check the status after the network goes up.
I do not currently have a 15.0 system with wicked networking to verify.
I can vaguely remember installing SuSEfirewall2 after updating to 15.0, there's a script installed with firewalld - "susefirewall2-to-firewalld" for the rules migration. Thanks Dave P -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 29/10/2018 15:14, Dave Plater wrote:
I had SuSEfirewall2 installed also, don't know if that's got anything to do with it. I just uninstalled, with -u, all firewall packages then reinstalled firewalld. After a reboot it was completely disabled, I've enabled it and started it, the rules for kdeconnect were still there. /etc/sysconfig/network/config is set at yes and most probably was all along. (on that note it does state "if the SuSEfirewall when enabled should get started when network interfaces are started.") I'm going to reboot now and if it doesn't start automatically I'll try a bug report.
:) It works, must have been SuSEfirewall2, for the first time, after a reboot firewalld is running. Thanks for the motivation, Dave P -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
29.10.2018 16:14, Dave Plater пишет:
On 29/10/2018 14:47, Patrick Shanahan wrote:
* Dave Plater <dplater.list@gmail.com> [10-29-18 08:44]:
On 29/10/2018 14:33, Carlos E. R. wrote:
On 29/10/2018 13.30, Dave Plater wrote:
On 29/10/2018 14:21, Carlos E. R. wrote:
On 29/10/2018 13.12, Per Jessen wrote: > Carlos E. R. wrote: > >> >> Well, it is running. No problem with it that I can see. > > That is when it is started manually - the problem is $SUBJ.
Then check the logs after boot. That's the only way to know what happened.
All I can find, the two bottom lines are when I started it manually. # journalctl -b|grep firewalld Oct 29 11:46:54 Arbuthnot systemd[1]: is_symlink_with_known_name(firewalld.service, dbus-org.fedoraproject.FirewallD1.service) → 1 Oct 29 13:10:49 Arbuthnot systemd[1]: Starting firewalld - dynamic firewall daemon... Oct 29 13:10:52 Arbuthnot systemd[1]: Started firewalld - dynamic firewall daemon.
As far as I can see, you did not have it enabled previously.
After boot : # systemctl status firewalld ● firewalld.service - firewalld - dynamic firewall daemon Loaded: loaded (/usr/lib/systemd/system/firewalld.service; enabled; vendor preset: disabled) Active: inactive (dead) Docs: man:firewalld(1) Note what line 3 says: Loaded: loaded (/usr/lib/systemd/system/firewalld.service; enabled; It doesn't start at boot.
correct, it's not directed to do so. explained in previous mail.
I had SuSEfirewall2 installed also, don't know if that's got anything to do with it.
Yes, it does. SuSEfirewall2.service conflicts with firewalld.service meaning if something cause SuSEfirewall2.service be started firewalld.service will be stopped (although in this case we should see it in status output). Also if both are part of the same transaction, one of them will be dropped. That is likely what happens here. I just installed SuSEfirewall2, enabled service and rebooted. firewalld.service is dead after reboot. Unfortunately systemd is notoriously bad with logging so you do not see it. With debug you will get Oct 29 20:08:05 linux-99af systemd[1]: firewalld.service: Looking at job firewalld.service/start conflicted_by=no Oct 29 20:08:05 linux-99af systemd[1]: firewalld.service: Looking at job firewalld.service/stop conflicted_by=yes Oct 29 20:08:05 linux-99af systemd[1]: firewalld.service: Fixing conflicting jobs firewalld.service/start,firewalld.service/stop by deleting job firewalld.service/start But note that even *NOW* it does not say what other service causes conflict. I just uninstalled, with -u, all firewall packages then
reinstalled firewalld. After a reboot it was completely disabled, I've enabled it and started it, the rules for kdeconnect were still there. /etc/sysconfig/network/config is set at yes and most probably was all along. (on that note it does state "if the SuSEfirewall when enabled should get started when network interfaces are started.") I'm going to reboot now and if it doesn't start automatically I'll try a bug report. Thanks Dave P
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 29/10/2018 13.43, Dave Plater wrote:
On 29/10/2018 14:33, Carlos E. R. wrote:
As far as I can see, you did not have it enabled previously.
After boot : # systemctl status firewalld ● firewalld.service - firewalld - dynamic firewall daemon Loaded: loaded (/usr/lib/systemd/system/firewalld.service; enabled; vendor preset: disabled) Active: inactive (dead) Docs: man:firewalld(1) Note what line 3 says: Loaded: loaded (/usr/lib/systemd/system/firewalld.service; enabled; It doesn't start at boot.
That line says that it is enabled, and that the default is not enabled. All correct. The important line is the next one, "inactive (dead)". And what do the logs say about that? -- Cheers / Saludos, Carlos E. R. (from openSUSE 15.0 (Legolas))
* Carlos E. R. <robin.listas@telefonica.net> [10-29-18 08:49]:
On 29/10/2018 13.43, Dave Plater wrote:
On 29/10/2018 14:33, Carlos E. R. wrote:
As far as I can see, you did not have it enabled previously.
After boot : # systemctl status firewalld ● firewalld.service - firewalld - dynamic firewall daemon Loaded: loaded (/usr/lib/systemd/system/firewalld.service; enabled; vendor preset: disabled) Active: inactive (dead) Docs: man:firewalld(1) Note what line 3 says: Loaded: loaded (/usr/lib/systemd/system/firewalld.service; enabled; It doesn't start at boot.
That line says that it is enabled, and that the default is not enabled. All correct.
The important line is the next one, "inactive (dead)".
And what do the logs say about that?
there is no setting short of constructing a service script to start the firewall prior to networking. starting networking will start the firewall. see previous mail. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* Dave Plater <dplater.list@gmail.com> [10-29-18 08:33]:
On 29/10/2018 14:21, Carlos E. R. wrote:
On 29/10/2018 13.12, Per Jessen wrote:
Carlos E. R. wrote:
Well, it is running. No problem with it that I can see.
That is when it is started manually - the problem is $SUBJ.
Then check the logs after boot. That's the only way to know what happened.
All I can find, the two bottom lines are when I started it manually. # journalctl -b|grep firewalld Oct 29 11:46:54 Arbuthnot systemd[1]: is_symlink_with_known_name(firewalld.service, dbus-org.fedoraproject.FirewallD1.service) → 1 Oct 29 13:10:49 Arbuthnot systemd[1]: Starting firewalld - dynamic firewall daemon... Oct 29 13:10:52 Arbuthnot systemd[1]: Started firewalld - dynamic firewall daemon.
maybe if I uninstall it and install it again. Dave P
there is configuration in yast system->/etcsysconfig Editor->network->general->firewall # With this variable you can determine if the SuSEfirewall when enabled # should get started when network interfaces are started. FIREWALL="yes" it doesn't start the firewall on system startup but when the network interface is started. you should not need the firewall before then as there is no access to your computer except what you have physically allowed. does that provide the information you seek? if not and you still want your firewall running on boot, you will have to construct a service script to do that. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
please copy the output of "systemctl status firewalld". also, consider moving from wickedd to networkmanager, networkmanager and firewalld make a great team. cheers MH Am Sonntag, 28. Oktober 2018, 16:06:45 CET schrieb Dave Plater:
On 28/10/2018 15:11, Mathias Homann wrote:
did you enable it?
Am Sonntag, 28. Oktober 2018, 12:53:16 CET schrieb Dave Plater:
Hi, I first did a google and a word search in this list and the support list and the only mention of firewalld not starting at boot didn't have any replies. I did a bug search but found nothing, in fact it seems that people want to stop it at boot not start it. My Leap:15.0 laptop has it starting at boot, the only difference is that the laptop uses network manager and this pc uses wicked. I haven't bothered with this until now because kde connect doesn't work without the firewall running. Why doesn't firewalld start at boot suse firewall did.
Thanks Dave P
Yast services says it's enabled but inactive systemctl start firewalld starts it so does yast but it's enabled but inactive after boot. Don't know if this is something to do with wicked?
Dave P
-- gpg key fingerprint: 8029 2240 F4DD 7776 E7D2 C042 6B8E 029E 13F2 C102
On Sun, 28 Oct 2018 21:07:30 +0100 Mathias Homann <Mathias.Homann@opensuse.org> wrote:
also, consider moving from wickedd to networkmanager, networkmanager and firewalld make a great team.
Sorry, but firewalld should work regardless of the network stack. ? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* Dave Howorth <dave@howorth.org.uk> [10-28-18 16:25]:
On Sun, 28 Oct 2018 21:07:30 +0100 Mathias Homann <Mathias.Homann@opensuse.org> wrote:
also, consider moving from wickedd to networkmanager, networkmanager and firewalld make a great team.
Sorry, but firewalld should work regardless of the network stack. ?
I have no problem with firewalld on my latest tw install, which is also wired using wicked -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 28/10/2018 16.06, Dave Plater wrote:
On 28/10/2018 15:11, Mathias Homann wrote:
did you enable it?
Am Sonntag, 28. Oktober 2018, 12:53:16 CET schrieb Dave Plater:
Hi, I first did a google and a word search in this list and the support list and the only mention of firewalld not starting at boot didn't have any replies. I did a bug search but found nothing, in fact it seems that people want to stop it at boot not start it. My Leap:15.0 laptop has it starting at boot, the only difference is that the laptop uses network manager and this pc uses wicked. I haven't bothered with this until now because kde connect doesn't work without the firewall running. Why doesn't firewalld start at boot suse firewall did.
Yast services says it's enabled but inactive systemctl start firewalld starts it so does yast but it's enabled but inactive after boot. Don't know if this is something to do with wicked?
Just show the exact output of the status command. The procedure is the same for all services. -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)
On 28/10/2018 12.53, Dave Plater wrote:
Hi, I first did a google and a word search in this list and the support list and the only mention of firewalld not starting at boot didn't have any replies. I did a bug search but found nothing, in fact it seems that people want to stop it at boot not start it. My Leap:15.0 laptop has it starting at boot, the only difference is that the laptop uses network manager and this pc uses wicked. I haven't bothered with this until now because kde connect doesn't work without the firewall running. Why doesn't firewalld start at boot suse firewall did.
Is it enabled? Whaat happens when you start the service? What is the status? systemctl enable|start|status firewald -- Cheers / Saludos, Carlos E. R. (from openSUSE 15.0 (Legolas))
Dave Plater wrote:
Hi, I first did a google and a word search in this list and the support list and the only mention of firewalld not starting at boot didn't have any replies. I did a bug search but found nothing, in fact it seems that people want to stop it at boot not start it. My Leap:15.0 laptop has it starting at boot, the only difference is that the laptop uses network manager and this pc uses wicked. I haven't bothered with this until now because kde connect doesn't work without the firewall running. Why doesn't firewalld start at boot suse firewall did.
Very wild guess - is anything renaming the network interface after firewalld is started? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (8)
-
Andrei Borzenkov -
Carlos E. R. -
Dave Howorth -
Dave Plater -
Mathias Homann -
Patrick Shanahan -
Per Jessen -
Peter Suetterlin