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.
  • Hi. In my network scenarios, yes. Typically, I will connect the firewall to a core switch via a LACP LAG. This is because the firewall is being used for L3 routing between local networks for high bandwidth applications, high speed Internet, etc. Also allows for redundant configs for varying degrees. All networks, for various purposes and uses are provided over the LAG with VLANs to the switching gear.

  • Hello. Upgraded yesterday from SFOS 19.5.3 MR-3-Build652 to SFOS 20.0.0 GA-Build222. All went well except for two issues related to icmp/ping.

    1) the ping/icmp does not seem to be working the same. Before upgrade from 19.5.3, ping worked across Site-to-Site IPsec VPN. Now ping is being blocked even though the VPN is working fine. Settings in my Admin->Device Access are the same with Ping/Ping6 checked on VPN and LAN.
    2) I think the related issue is the WAN link manager shows the Active status incorrectly. After upgrade the Backup connection shows green, but Active shows red. They were both green before upgrade. My Active connection is up and working. My Active rule uses ping to my ISP gateway. I can ping the same address from the LAN zone (my laptop) and from the Diagnostics Tools so not sure why it is showing as down.

    Regards, Gary

  • So neither of my issues were v20.

    1) my Admin->Device Access was correct on my upgraded unit, but not in my VPN remote unit.

    2) After rebooting one more time after the upgrade, my WAN Link statuses were correct.

  • "user" based authentication is meaningless for most IoT devices.

  •   Good to see that issue is resolved. While re-downloading cleared, we can see if logs points to what went wrong first time and if any improvement is possible to improve the experience that you had during this upgrade. If you can share the logs - applog.log, migration, log, u2d.log, garner.log and csc.log from /log  we can check if it has any hints. -Shrikant

  • New Access ID sent to ShrikantSophos

  • Is it possible that there is an issue with editing an existing S2S VPN connection?
    I have rolled out several XGS136 with V20 at a bigger customer project now and experienced the same issue with 3 firewalls.

    I have an existing S2S tunnel (checkbox "Activate on save" is checked).
    I have a several local networks to any remote network tunnel setup with policy based vpn (since I need DHCP relay).

    When I add a new subnet on the local side and save the connection the state of it goes red/red instead of green/red or green/green.
    I then have to connect via WAN to the firewall, click the "Activate" icon and it goes up green/green like expected.

    Regards,

    Kevin

    Sophos CE/CA (XG, UTM, Central Endpoint)
    Gold Partner

  • It is an IPsec tunnel... correct? or SSLVPN?

  • IPSEC IKEv1

    Regards,

    Kevin

    Sophos CE/CA (XG, UTM, Central Endpoint)
    Gold Partner