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: v19.5 MR3: Feedback and experiences

Release Post:  Sophos Firewall OS v19.5 MR3 is Now Available  

The old V19.5 MR2 Post:  Sophos Firewall: v19.5 MR2: 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/index.html?productGroupID=nsg&productID=xg&versionID=19.5 



This thread was automatically locked due to age.
Parents
  • I had two extra zones defined. Sophos was doing DHCP and handling DNS request. After updating to 19.5.3, those two extra zones could not access DNS and I found the device access table had unselected DNS. Found this doing a packet trace and port 53 errors and VIOLATION hitting Local_ACL.

    I thought this was strange. Checked logs and found no admin had logged in. The update had been pushed through the partner portal.

    Solution was TICK DNS in Device Access for those two Zones.

Reply
  • I had two extra zones defined. Sophos was doing DHCP and handling DNS request. After updating to 19.5.3, those two extra zones could not access DNS and I found the device access table had unselected DNS. Found this doing a packet trace and port 53 errors and VIOLATION hitting Local_ACL.

    I thought this was strange. Checked logs and found no admin had logged in. The update had been pushed through the partner portal.

    Solution was TICK DNS in Device Access for those two Zones.

Children
No Data