Hi Wouter,
You are correct. The only packaging difference between 5.0.4-1 and
5.0.7-1 is that it now correctly enables the systemd service on
installation and disables it on removal.
Regards,
-Roberto
On Fri, Apr 01, 2016 at 08:57:29PM +0200, Wouter Deurholt wrote:
>Aha!
>I see now (ove
Aha!
I see now (overlooked it before) that the
/etc/systemd/system/shorewall.service I made myself (first post) was not
necessary... and even pointless :).
If you just do a 'sudo systemctl enable shorewall.service' after you
installed shorewall 5.0.4: all is well :).
I recon this is the only chan
Wouter,
That is a problem that I discovered a few weeks after I uploaded 5.0.4.
I was actually surprised that (a) I overlooked it, and (b) nobody ever
reported it. The problem was corrected with the 5.0.7-1 upload to
Debian unstable last week.
Executing 'systemctl enable shorewall.service' is th
Greetings,
I installed Shorewall (5.0.4) on my Ubuntu server 16.04 (currently beta).
It is functioning perfectly fine when started. There is however one
problem. It is not starting at boot-time.
I even tried to add a wait_interface="eno1" and wait_interface="eno2" to
my /etc/default/shorewall.
