This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Working IPsec site to site VPN won't restart after reboot

Am running Sophos UTM ver 9.705-3 and have an IPsec site to site VPN with Sonicwall TZ300 (which is set to "initiate connection") that works well until I reboot the Sophos.

After rebooting the Sophos, I've watched the sonicwall keep retrying to reconnect for well over 5 mins with no answer back. At the sophos end, the VPN live log only shows the following entries and won't budge until I do something to the VPN, e.g. toggle on/off, change a setting, etc. then it reconnects no problem:

2021:02:20-11:58:48 lyneutm pluto[5866]: adding interface br0/br0 192.168.2.2:500

2021:02:20-11:58:48 lyneutm pluto[5866]: adding interface br0/br0 192.168.2.2:4500
2021:02:20-11:58:48 lyneutm pluto[5866]: adding interface lo/lo 127.0.0.1:500
2021:02:20-11:58:48 lyneutm pluto[5866]: adding interface lo/lo 127.0.0.1:4500
2021:02:20-11:58:48 lyneutm pluto[5866]: adding interface lo/lo ::1:500
2021:02:20-11:58:48 lyneutm pluto[5866]: loading secrets from "/etc/ipsec.secrets"
2021:02:20-11:58:48 lyneutm pluto[5866]: loaded PSK secret for <local FQDN> < remote FQDN> 
2021:02:20-11:58:48 lyneutm pluto[5866]: listening for IKE messages
2021:02:20-11:58:48 lyneutm pluto[5866]: added connection description "S_JT VPN"
2021:02:20-11:58:48 lyneutm pluto[5866]: "S_JT VPN": we have no ipsecN interface for either end of this connection

(I've inserted the <local FQDN> and <remote FQDN> to replace the actual values.)

I've tried with Dead Peer Connection both on and off with same result.

Is there a known issue with IPSec VPN restarts at reboot? Is there something I may have configured wrong?

Any info would be appreciated.



This thread was automatically locked due to age.
Parents
  • I should add there's no problem going the other way, i.e. when Sonicwall end goes down and restarts the tunnel gets re-established no problem

  • Salut Jean,

    I assume that the Sophos side is set to respond only?

    BAlfson, didn‘t you say that both ends could be set to „initiate connection“?

    I would try that first.

    Mit freundlichem Gruß, best regards from Germany,

    Philipp Rusch

    New Vision GmbH, Germany
    Sophos Silver-Partner

    If a post solves your question please use the 'Verify Answer' button.



    Typos corrected
    [edited by: jprusch at 5:05 PM (GMT -8) on 21 Feb 2021]
  • Hi Philipp, thanks for the reply. I don't see a way to set Sophos end to "respond only", or, for that matter, to initiate. I only see option to set initiate/respond for remote site - in my case a sonicwall that is set to initiate.

    Here's a screenshot of the Sophos connection config tab, and two below is Sophos Remote Gateway tab, where I could have chosen "Respond Only" but chose "Initiate Connection" 

  • Salut Jean,

    once defined, you cannot change the behaviour of the remote GW object from "initiate connection" to "respond only". You have to recreate it or define another object and then associate this with your connection.

    Mit freundlichem Gruß, best regards from Germany,

    Philipp Rusch

    New Vision GmbH, Germany
    Sophos Silver-Partner

    If a post solves your question please use the 'Verify Answer' button.

  • I haven't changed anything with respect to who initiates and who responds because everything works fine until I reboot the Sophos. Then the VPN will not restart. Upon restart the Sophos should just respond to the other end's request, which I can see happens repeatedly but it doesn't. 

    It stops at "lyneutm pluto[5866]: "S_JT VPN": we have no ipsecN interface for either end of this connection"

    It seems like a bug to me but first seeing if anyone else has encountered this, and/or if there's another setting I'm not seeing that I have to turn on or off.

  • Something is definitely broken here. Try to create a new connection object with a different name AND a new Gateway object with a new name, too. Then delete the old entries after that. Is it working now?

    Mit freundlichem Gruß, best regards from Germany,

    Philipp Rusch

    New Vision GmbH, Germany
    Sophos Silver-Partner

    If a post solves your question please use the 'Verify Answer' button.

  • Hi Jean and welcome to the UTM Community!

    Are DPD and NAT-T enabled in both devices?  If that didn't fix this, please show us more of the log.

    1. Confirm that Debug is not enabled.
    2. Disable the IPsec Connection.
    3. Start the IPsec Live Log and wait for it to begin to populate.
    4. Enable the IPsec Connection.
    5. Copy here about 60 lines from enabling through the error.

    Cheers - Bob

     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
  • Thanks. Just to be clear the problem is ONLY at reboot of the Sophos. Otherwise everything works fine, including any lose of connectivity at either end (or a sonicwall reboot). The tunnel always comes back up EXCEPT when I restart the sophos. I've not had a chance to restart building it from scratch to see if that fixes it but I may have a chance to reboot tomorrow. II don't think there are many more log entries to see. I'll provide what both the "view log" and "live log" shows. I'll even force a restart at the sonicwall end while I'm running live log.  Someone from spiceworks community said this problem was reported 5 years ago in 9.4.

    In the meantime, I'll confirm that, yes, dead peer detection and NAT Traversal are on, and no, debug is not.

  • So this morning everything worked fine after reboot. The VPN tunnel came back up by itself. I must have done something to it over past several days. I did spend quite a bit of time setting up IPsec in "Remote Access" tab thinking I could maybe get in that way if there was a Sophos reboot and the "Site to Site" VPN was down. I wasn't able to get that going but I noticed some stuff was common to both ways of setting up IPsec VPN (which gave me grief on the sonicwall side) so maybe something I did setting that up fixed things,

    Thanks for your replies and offers of help.

    I will ask something else. I tried to get support support on this so I setup a Sophos ID at support.sophos.com but it refuses to let me login. Phone support sent me to Sophos Home, which is for the Windows/Mac software version, not the ASG appliance version I have. 

    I realize I have the free home edition so am not expecting miracles but I thought I read somewhere that there is support for it. Is support only through self help and this community, or is there an option to report something to the technical support folks and there's just a problem with the account I created?

    Any info would be appreciated.

    Thanks again

  • Correctomundo, Jean - just here in the Community.  There are Sophos folks that participate here, too.

    If you click on 'Management' in WebAdmin, you can see when you were logged in and what changes you made.  It would be interesting to see your related changes.

    Cheers - Bob

     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
  • thanks. I made sooo many changes for many things I don't really want to go through them to figure out which one tipped the scale. thanks for your replies.

Reply Children
No Data