Guest User!

You are not Sophos Staff.

Thread Info
  • Locked Locked
  • Replies 39 replies
  • Subscribers 21 subscribers
  • Views 41922 views
  • Users 0 members are here
Options
Suggested
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

UTM Version 9.353-4 Released

utmadm

I received email notifications about the 9.353-4 update this morning. It appeared on both of my UTMs this morning. One is supported hardware and the other is a virtual machine at home. I have not installed the update yet. I am waiting to see if others (who are braver than me) report any serious issues.

I have learned that Sophos UTM updates go out in phases. Your UTM may not have the update available yet. I have seen a gap of several weeks between when an update appears on my home UTM and when it appears on the hardware UTM.

Moderators: Feel free to edit the subject of this thread to add "Do not install!" if it seems appropriate. I won't complain. Hopefully this is a good, solid release.

Other forum members: Please comment here if you have installed the 9.353-4 update. Please share your experiences (good and bad) here. Thanks!



This thread was automatically locked due to age.
Parents

  • 1 Feb 2016

    followup here guys, might help some of you, if you are on 9.353-4 and having the flow monitor break and backend errors...

    I connected to my utm from wan side and the flow monitor works with no backend errors...
    need to confirm if its sorted itself out or if the issue is exhibited internally only

    3 Feb 2016

    update:

    been playing around, and have discovered the following:

    connecting to the utm internally (LAN) via my internal DNS nameing causes flow monitor to break and backend connection errors follow shortly after that

    connecting to the utm internally (LAN) via utm's IP address seemingly works fine, flow monitor works and no backend connection errors.

    connectng to the utm using external (WAN) IP and external DNS resolution works fine, FLow monitorw orks and no backend connection errors

    Hope this helps guys out in some way, either in keeping their current builds or in actually tracking down the issues

    6 Feb 2016

    confirmed using IP of UTM on internal (LAN) instead of DNS name of UTM allows access to flow monitor and also no backend connection errors

    11 Feb 2016

    Other messages in this hread sent me off to do some testing,can confirm it looks like browser caching involved,hence why people trying a different (previously unused) browser had better luck;

    For me, I stuck with chrome and did the following:

    chrome settings > advanced settings > clear browsing data
    cookies and other site and plugin data - checked
    cached images and files - checked

    clear that cache with above two allowed me to get back in with working flow monitor and also no back-end errors!

    I suspect similar purge on IE will do the same

    So using an different DNS name or direct IP instead of the original DNS name meant the data was cached separately and also explains why it worked under those conditions but not under the old access url

Reply

  • 1 Feb 2016

    followup here guys, might help some of you, if you are on 9.353-4 and having the flow monitor break and backend errors...

    I connected to my utm from wan side and the flow monitor works with no backend errors...
    need to confirm if its sorted itself out or if the issue is exhibited internally only

    3 Feb 2016

    update:

    been playing around, and have discovered the following:

    connecting to the utm internally (LAN) via my internal DNS nameing causes flow monitor to break and backend connection errors follow shortly after that

    connecting to the utm internally (LAN) via utm's IP address seemingly works fine, flow monitor works and no backend connection errors.

    connectng to the utm using external (WAN) IP and external DNS resolution works fine, FLow monitorw orks and no backend connection errors

    Hope this helps guys out in some way, either in keeping their current builds or in actually tracking down the issues

    6 Feb 2016

    confirmed using IP of UTM on internal (LAN) instead of DNS name of UTM allows access to flow monitor and also no backend connection errors

    11 Feb 2016

    Other messages in this hread sent me off to do some testing,can confirm it looks like browser caching involved,hence why people trying a different (previously unused) browser had better luck;

    For me, I stuck with chrome and did the following:

    chrome settings > advanced settings > clear browsing data
    cookies and other site and plugin data - checked
    cached images and files - checked

    clear that cache with above two allowed me to get back in with working flow monitor and also no back-end errors!

    I suspect similar purge on IE will do the same

    So using an different DNS name or direct IP instead of the original DNS name meant the data was cached separately and also explains why it worked under those conditions but not under the old access url

Children
No Data