Hej,
now that MR-1 has appeared, I wanted to ask when MR-2 will appear? The problems and instabilities of IPSec in v17 (especially in connection with V16.5) are very annoying.
This thread was automatically locked due to age.
Hej,
now that MR-1 has appeared, I wanted to ask when MR-2 will appear? The problems and instabilities of IPSec in v17 (especially in connection with V16.5) are very annoying.
For users continuing to see IPsec site-to-site VPN issues on v17 MR-3, please contact Support and open a ticket to provide logs & report possible BUG. Once you do please provide me with your case ID so I can be sure that the case is escalated.
For non-licensed users, please share or DM me the following information:
We appreciate all your feedback.
Thanks,
Karlos
I've had case #7758347 open for a while trying to work on this. Unfortunately I replaced a Cisco ASA with a Sophos appliance already running v17 on the other side of the country. Debating whether or not to wait for a fix or go ahead and fly out there and go through the process of downgrading to 16, which essentially does a factory reset, or just stick the ASA back in place and ask Sophos for my money back. I have another identical Sophos UTM running at another datacenter in another state with v16 that isn't experiencing any of these issues.
Our issue is that every few hours one of our main ipsec tunnel will drop and doesn't come back up unless someone resets it on our end. My current workaround is that I have Solarwinds monitoring devices on the other end of the tunnel. When Solarwinds loses that connection it kicks off a script using Devolutions RDM to open an ssh session to the UTM and restart the VPN service. This obviously isn't a doable workaround for everyone.... and still causes a lot of issues for us since we have a lot of realtime data coming across that tunnel. So every time it drops is trouble.
MR2 and MR3 cause the tunnel to completely stop working. So right now I'm stuck on MR1 because that seems to be the only spot where the tunnel at least works. 17 GA had a bug that caused the UTM to become unresponsive and we kept having to do hard resets on it, by shutting off power to it from the PDU it's plugged into. But the tunnel seemed to be stable on GA. MR1 seemed to be where the IPSEC issues started for me. But I'm in between the rock (UTM becoming completely locked up) and the hard place (the tunnel randomly dropping).
HI all,
And finally i've got the WHY.....
Sophos has migrated the ipsec engine to https://strongswan.org/ which is free.
There is no hazard, and that why every of us was asking by support to completely recreate the ipsec profiles. We know that after recreating everything it's not stable too.
Today i upgrade a v15.1 to v16.5.8 and ipsec vpn are still... perfectly STABLE !!! (without recreating anything)
I need V17 NOW (dns wildcard objects, IKEV2, object group for firewall) and i won't/can't recreate anything on my configurations.
PLEASE SOPHOS just give us a functionnal release !!!!!!
Yes they moved from openswan in v16 to strongswan in 17. The frustration we're all experiencing does not center around the ipsec engine but rather in whatever transitional code was required to bring existing connections and profiles from openswan to strongswan. I won't pretend to know what is involved exactly but I would assume that when looking at a firmware upgrade you would want something that translates your current config into whatever the new firmware is built on.
If you (Sophos) can't create such transitional code, at least let us know as part of the upgrade process we'll need to reconfigure some of our settings (e.g. completely delete and reconfigure ipsec profiles and connections).
Is StronSwan that bad ? I would like to hear.
On paper, I would say it is sexy. At least I like this part:
Now is there a TPM in a XG210 ? I will have to check.
What I realize over time, is Sophos uses open source at many places. For example, AP55C runs OpenWRT. https://openwrt.org/
Paul Jr
I don't think it's good or bad... it have been so badly implemented !!!
Many of us here tried to run IPSEC vpn between sophos in fresh v17 and it doesn't work !
haw can it be possible to don't release 4 version without ANY improvements of a problem, so simple to reproduce ????
Interesting. I will say that beyond re-creating the tunnels I had to fiddle around with a few different ipsec profiles before I found an encryption set that worked with Azure. I had also created a custom profile in Azure via powershell to ensure it matched what I had configured on the XG. I get a tunnel down/up notification daily but connectivity doesn't seem interrupted, indicating the issue (for me anyway) in this regard is related to the monitoring/notification in the XG.
Any way you shake it it seems unreasonable to me that we should even be having these discussions about an enterprise next-gen firewall running GA or MR software. Beta sure, but not production.
How did you figure this out?? I do recall the Sophos support engineer a few weeks ago running strongswan commands for hours on my firewall over ssh and I didn't know what that is but I thought it was just a funny command for a WAN or something.
Karlos,
I do not have access to the logs on the ASA. The ASA is managed by another company, and their security is dictated by Homeland Security. They will give me a verbal description of what they are seeing on their side in the logs, but getting something like actual logs is like pulling teeth. The one thing that I know is that this vpn tunnel worked when I was running an ASA on my side, it worked from another SG310 running UTM 9, it worked from another SG310 running XG 16. The only thing that it has issues with is XG 17.
I will add that the company that manages the ASA has been working with Cisco support since this began and Cisco has checked everything with their configuration, and Cisco support did review their logs and has said that they were unable to find any issues on their end.
