Shorewall will not restart after a system reboot after applying system upgrades

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP








up vote
0
down vote

favorite












My issue with shorewall-5.0.4 is it will not restart after
a system reboot after applying system upgrades.



The system:



  • Raspberry Pi 3 B

  • Ubuntu 16.04, Ma'Te desktop environment

  • Two USB/Ethernet dongles

The firewall/router topology:



  • On-board eth is the WAN

  • USB/Eths are two separate LAN networks but both set as the same zone in shorewall

I have to do the following to get the firewall up and running after a system upgrade:



shorewall stop
shorewall clear
iptables -F
iptables -X
iptables -L (to verify)


(using the desktop)



Shutdown the external eth0
Shutdown the internal eth1
Shutdown the internal eth2
enable the external eth0
shorewall compile
shorewall start
shorewall save
verify connectivity using Chromium->website, pings
enable the internal eth1
enable the internal eth2


Only then does masquerading work again.
Anybody offer any suggestions, recommendations?



Thanks in advance.










share|improve this question



























    up vote
    0
    down vote

    favorite












    My issue with shorewall-5.0.4 is it will not restart after
    a system reboot after applying system upgrades.



    The system:



    • Raspberry Pi 3 B

    • Ubuntu 16.04, Ma'Te desktop environment

    • Two USB/Ethernet dongles

    The firewall/router topology:



    • On-board eth is the WAN

    • USB/Eths are two separate LAN networks but both set as the same zone in shorewall

    I have to do the following to get the firewall up and running after a system upgrade:



    shorewall stop
    shorewall clear
    iptables -F
    iptables -X
    iptables -L (to verify)


    (using the desktop)



    Shutdown the external eth0
    Shutdown the internal eth1
    Shutdown the internal eth2
    enable the external eth0
    shorewall compile
    shorewall start
    shorewall save
    verify connectivity using Chromium->website, pings
    enable the internal eth1
    enable the internal eth2


    Only then does masquerading work again.
    Anybody offer any suggestions, recommendations?



    Thanks in advance.










    share|improve this question

























      up vote
      0
      down vote

      favorite









      up vote
      0
      down vote

      favorite











      My issue with shorewall-5.0.4 is it will not restart after
      a system reboot after applying system upgrades.



      The system:



      • Raspberry Pi 3 B

      • Ubuntu 16.04, Ma'Te desktop environment

      • Two USB/Ethernet dongles

      The firewall/router topology:



      • On-board eth is the WAN

      • USB/Eths are two separate LAN networks but both set as the same zone in shorewall

      I have to do the following to get the firewall up and running after a system upgrade:



      shorewall stop
      shorewall clear
      iptables -F
      iptables -X
      iptables -L (to verify)


      (using the desktop)



      Shutdown the external eth0
      Shutdown the internal eth1
      Shutdown the internal eth2
      enable the external eth0
      shorewall compile
      shorewall start
      shorewall save
      verify connectivity using Chromium->website, pings
      enable the internal eth1
      enable the internal eth2


      Only then does masquerading work again.
      Anybody offer any suggestions, recommendations?



      Thanks in advance.










      share|improve this question















      My issue with shorewall-5.0.4 is it will not restart after
      a system reboot after applying system upgrades.



      The system:



      • Raspberry Pi 3 B

      • Ubuntu 16.04, Ma'Te desktop environment

      • Two USB/Ethernet dongles

      The firewall/router topology:



      • On-board eth is the WAN

      • USB/Eths are two separate LAN networks but both set as the same zone in shorewall

      I have to do the following to get the firewall up and running after a system upgrade:



      shorewall stop
      shorewall clear
      iptables -F
      iptables -X
      iptables -L (to verify)


      (using the desktop)



      Shutdown the external eth0
      Shutdown the internal eth1
      Shutdown the internal eth2
      enable the external eth0
      shorewall compile
      shorewall start
      shorewall save
      verify connectivity using Chromium->website, pings
      enable the internal eth1
      enable the internal eth2


      Only then does masquerading work again.
      Anybody offer any suggestions, recommendations?



      Thanks in advance.







      firewall






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Apr 12 at 14:26









      Android Dev

      10.4k63257




      10.4k63257










      asked Apr 12 at 14:20









      John Rose

      143




      143

























          active

          oldest

          votes











          Your Answer







          StackExchange.ready(function()
          var channelOptions =
          tags: "".split(" "),
          id: "89"
          ;
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function()
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled)
          StackExchange.using("snippets", function()
          createEditor();
          );

          else
          createEditor();

          );

          function createEditor()
          StackExchange.prepareEditor(
          heartbeatType: 'answer',
          convertImagesToLinks: true,
          noModals: false,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: 10,
          bindNavPrevention: true,
          postfix: "",
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          );



          );













           

          draft saved


          draft discarded


















          StackExchange.ready(
          function ()
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1024384%2fshorewall-will-not-restart-after-a-system-reboot-after-applying-system-upgrades%23new-answer', 'question_page');

          );

          Post as a guest



































          active

          oldest

          votes













          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes















           

          draft saved


          draft discarded















































           


          draft saved


          draft discarded














          StackExchange.ready(
          function ()
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1024384%2fshorewall-will-not-restart-after-a-system-reboot-after-applying-system-upgrades%23new-answer', 'question_page');

          );

          Post as a guest













































































          Popular posts from this blog

          pylint3 and pip3 broken

          Missing snmpget and snmpwalk

          How to enroll fingerprints to Ubuntu 17.10 with VFS491