Important note about SSL VPN compatibility for 20.0 MR1 with EoL SFOS versions and UTM9 OS. Learn more in the release notes.

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

Sophos Firewall: v20.0 GA: Feedback and experiences

Release Post:  Sophos Firewall v20 is Now Available  

The EAP Post:  Sophos Firewall: v20.0 EAP1: Feedback and experiences  

The old V19.5 MR3 Post:  Sophos Firewall: v19.5 MR3: Feedback and experiences  

To make the tracking of issues / feedback easier: Please post a potential Sophos Support Case ID within your initial post, so we can track your feedback/issue. 

Release Notes:  https://docs.sophos.com/releasenotes/output/en-us/nsg/sf_200_rn.html 



This thread was automatically locked due to age.
  • Give up. Been on the road map for more than a decade. A bit like NAT rule grouping. Sophos will tell customers what they need, not the other way around.

  • 5 hours on the phone to Sophos support (so far) and they still can't work it out. 40 users offline. These are the Cyberoam days all over again.

  • Hi Stuart,

    We regret to hear about your experience. Would you be able to share the case ID so that we can further check it?

    I haven’t found any recent cases under your registered Community email.

    Erick Jan
    Community Support Engineer | Sophos Technical Support
    Sophos Support Videos Product Documentation  |  @SophosSupport  | Sign up for SMS Alerts
    If a post solves your question use the 'Verify Answer' link.

  • Ticket 07103611

    Sophos finally escalated the call and said they'd get L2 to ring me back within the hour. While I was waiting I deleted the tunnel at both ends, recreated and the problem is now resolved. Wish I'd never logged a ticket in hindsight.

    I had an IPSEC tunnel between 19.5.3 and 19.5.3 - upgraded one side to 20.0.0 and nothing else - tunnel was up and green but traffic refused to flow.

    Very nervous about upgrading any of my clients who are all remote.

  • Hi Stuart,

    Thank you for sharing the case ID, and I am glad to hear that the issue is resolved.

    Again, we sincerely regret your experience and will further Note this.

    Erick Jan
    Community Support Engineer | Sophos Technical Support
    Sophos Support Videos Product Documentation  |  @SophosSupport  | Sign up for SMS Alerts
    If a post solves your question use the 'Verify Answer' link.

  • Thanks for the clarification.

    Reg. IPv6 lease table improvements, it's there in the roadmap. I will check with product management about its priority.

    Reg. multiple IPv6 address management, I believe it might be due to transition in your setup from manual way of managing prefix network via DHCPv6 server to DHCPv6-PD. If it would have been a fresh deployment, I guess you would have got single IPv6 address in your LAN network via Router advertisement. For multiple IPv6 address management, cleaner approach is to use "user" based authentication to not worry about IP address at all to identify client machine(s).

    If there is a need to have multiple IPv6 addresses to be managed (which I think you don't need as of now), DHCPv6 server with lease pool management will be required on delegated interface on top of prefix distribution via router advertisement. We will consider this requirement based on deployment feedback we get from the customer.

    Thanks for your cooperation and support.

    Regards,

    Sanket Shah

    Director, Software Development, Sophos Firewall

  • Hi  ,

    Nope, SD-WAN probe support is currently targeted for v21 - we're currently in the planning phase. We will update once we have further details on timeline and release vehicle.

  • Hi Stuart,

    I did that same upgrade with v20 now running in our HQ and several customers connected through IPsec tunnels with older releases (V19.5.3 and V19.5.2), no problems here.

    Some there must be something special in your setup.

    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.

  • Could it be related to this: 

    KIL Item? 

    Did you use a HA? 

    __________________________________________________________________________________________________________________

  • Yep, we have HA on both ends of the tunnel, however there are no XFRM interfaces as it's a policy based VPN not route based. Additionally, we activated/deactived tunnels several times, rebooted both appliances multiple times and even booted back in to 19.5.3 with no luck.

    Packet capture was showing that traffic was being forwarded to IPSEC0 but the other end saw nothing whatsoever.

    Strangely, we had three IPSEC tunnels on the device, two worked fine after the upgrade, it was only one that had the issue.