The error is since I start more things at boot such as boinc client and an kvm guest. For a while I could help myself with a low priority in /etc/init.d scripts.

My impression is that it has something to do with the boot order and services not being available when shorewall starts. I’m not an linux expert but for sure can help with the right instructions to reproduce the error with more info.

the first time I noticed this was after enabling the Virt Manager with only one autostart ubuntu guest on a fresh NS installation.

I’m not using custom templates yet. In the meantime I registered three services in nethserer according to the manual with their firewall rules. Boinc starts with a init.d script with chkconfig: 235 95 95.

Unfortunately the issue does not occur at every boot.

The shorewall log shows a couple of warnings which I have not yet futher investigated.

Some of those Shorewall warnings should be fixed in the next upcoming update

All of them should disappear.

@tmb I had one case of shorewall not starting at boot in the past, only once and with a different message. But it happened after I enabled libvirt and added a virtual machine.
We should find a way to reproduce the problem.

One additional information. I run NS in bridge mode: a RED interface with static IP from the router and a green interface with DHCP enabled.

I also lean towards an issue in connection with libvirt manager and not with the other services.

Therefore I increased START_DELAY= in the /etc/sysconfig/libvirt-guests file to a value greater 0
But given my novice experience with LINUX you should see this more as a trial and error approach than a knowledgable solution. I’m also not yet confident that this is really the issue.

The last two reboots were without error, the firewall started as it should. I will come back to this thread when I see it again and will take notes what has changed in between.