9.506 is released. 
Maybe we could use this thread for reporting successful updated system and maybe not so many bugs. Who wants to be first to update? :-)
This thread was automatically locked due to age.
9.506 is released.
Maybe we could use this thread for reporting successful updated system and maybe not so many bugs. Who wants to be first to update? :-)
Scheduled the update for 3am, woke up to broken ipv6 again!
Toggled ipv6 on/off which left the interface DOWN across ipv4 and ipv6.
I've done very limited testing but have had to switch ipv6 off for the time being and will do some further investigation tonight.
Was hoping that my ipv6 UTM woes had gone away as it's been stable for a couple of months now. Sigh.
no issues here with IPv6 other than the persistent bugs and issues that had been in for a while now...
EDIT: Managed to break ipv6 that even a config restore wouldn't fix. Reinstalled 9.504-2 - all working fine again.
---
Sophos UTM 9.3 Certified Engineer
Thanks for the link. On the same page I found this: (translated from German by Google)
"Attention, there are problems in HA mode in the ESXi environment. After updating from 9.505-4 to 9.506-2, certain VM servers (the VMs running on the same host where the Passive UTM VM was running) were no longer accessible on the network! Only after shutting down the "passive" node were they suddenly reachable again. Rebuilding the HA did not help. I had to rest again on 9.505-4, then everything went OK again. I wait for the first time 1-2 updates, then we'll see :)"
I posted the following workaround there that might work. This applies to VMs in HA running on the same host.
How to resolve issues with Virtual UTMs configured for High Availability:
1. Login to the UTM console as root.
2. Enter the following command to determine if HA virtual_mac is enabled:
cc get ha advanced virtual_mac
3. If the output is 1, you can disable it by entering the following:
cc set ha advanced virtual_mac 0
4. Restart all virtual UTMs.
Please let us know if this worked.
Cheers - Bob
WAF is broken for me.
It affects Windows 7 clients using Outlook 2010 connecting to Exchange 2010.
Other combinations like Windows 10, or Outlook 2013 work fine.
TLS 1 is required somewhere in this chain.
|
9.505-4 added a TLS Verion dropdown that allowed you to pick you Min. TLS level. 9.506-2 removed the option. I have an open support ticket, do not have a work around yet.
I was sent this as a workaround:
It doesn't seem to apply since the lines Sophos references to change no longer exist in the file. |
Hope this helps,
Ron
Latest Update from Sophos Support.
If I understood correctly.
TLS 1 support has been removed.
After you do: cc set reverse_proxy min_tls 1
Check the result with: grep SSLProtocol /var/chroot-reverseproxy/usr/apache/conf/reverseproxy.conf
Now is WAF still "broken" for that one situation?
Note that this probably is not supported and that you should upgrade your software to eliminate its dependence on TLSv1. After upgrading, use the trick above to set the value back to 1.1.
Cheers - Bob
