Reboot after Update

Comments

6 comments

  • Avatar
    Firewalla

    The box was not designed to reboot and clean things, so in theory and practice, the box should stay up, unless we send an update that requires reboot. (so far we have not).  

    As of your VPN problem, we can take a look.  Is it VPN Server to the VPN client feature?  

    0
    Comment actions Permalink
  • Avatar
    James Willhoite

    It is a OpenVPN client (On RaspberryPi) to OpenVPN Server (On Firewalla Gold).

    I guess I need it to reboot when the upgrade happens because it overwrites some of the scripting I have in place during boot. The iptables get flushed and I have some custom filters that are applied at boot. Is there a script I can hook into during an upgrade that can rerun a install script that is run at boot?

    0
    Comment actions Permalink
  • Avatar
    James Willhoite

    I've got that set up. Works like a charm. That is why I need the device to reboot it seems like. I'm not sure if that is the issue. The programs and the files that script installs are there, but still no connectivity on vpn. That folder runs a script that installs StrongSwan for my IKEv2/L2TP/Ipsec VPN. I use StrongSwan for a VPN connection into my work (which was still up). But I could not have any connections IN to the Firewalla either via OpenVPN, or via IKEv2. Once I restarted the Firewalla everything was fine.

    0
    Comment actions Permalink
  • Avatar
    Firewalla

    Nice!  Did you use StrongSwan and then applied iptables to route traffic?

    0
    Comment actions Permalink
  • Avatar
    James Willhoite

    Strong swan is policy based. I had to apply iptable rules to allow traffic coming in and some rules to block traffic on specific networks etc.

     

    Just need to figure out why both OpenVPN, and the IKEv2 would not allow incoming connections .....

    0
    Comment actions Permalink

Please sign in to leave a comment.