On Fri, Dec 09, 2016 at 14:41:27 -0500, Nathan Stratton Treadway wrote: > I have only worked with this under Ubuntu (not Debian per se), but I > believe the issue you are seeing is that the Shorewall documentation has > not been updated to reflect the use of systemd instead of the old-style > /etc/init.d/shorewall script. [...]> > To turn on automatic startup of shorewall under systemd, you need to > "enable" the service: > # systemctl enable shorewall
Actually, I found in the Debian changelog: http://metadata.ftp-master.debian.org/changelogs/main/s/shorewall/shorewall_5.0.14.1-1_changelog that (assuming you are in fact using v5.0.14.1-1 as specified in the bug report) the package should now already be enabling itself upon installation: ---- shorewall (5.0.7-1) unstable; urgency=low * New Upstream Version * Enable systemd service on package installation and disable on removal ---- (Ubuntu Xenial has v5.0.4-1, so it doesn't get enabled automatically on installation there.) So, I'm not sure if "systemctl enable shorewall" will fix your problem, but in any case running "systemctl status shorewall" immediately after a reboot may give some indication as to what is going wrong. Nathan
