Hi: On 21 November 2017 at 17:23, Tom Eastep <teas...@shorewall.net> wrote: > On 11/21/2017 07:59 AM, Tom Eastep wrote: > >>> Rebooted again and now shorewall started automatically when the >>> firewall boots up. >>> I found this a bit strange but now it works as expected. >>> >> >> Do you recall what the output of 'systemctl status shorewall' was when >> Shorewall failed to start? >> > > If not, please look in /var/log/shorewall-init.log to see if Shorewall > attempted to start but got an error.
I don't recall output of systemctl status shorewall. However, I actually looked in /var/log/shorewall-init.log immediately after reboot (when shorewall failed to start) and I was puzzled to find that nothing was logged. I could only find entries from the successfull manual start of shorewall. After configuring everything I started my firewall with 'sudo shorewall start' and shorewall started just fine. I have a box here running debian sid and shorewall 5.1.8.1. I will play around to see if I can reproduce my findings when setting up shorewall 5.0.15.6 on debian stretch. This box is only a single nic box though but I don't that matters here. I will purge shorewall and install it again and let you guys know as soon as I get a chance playing with it. I will use the universal config. ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Shorewall-users mailing list Shorewall-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/shorewall-users
