Release Post: Sophos Firewall OS v19.5 MR1 is Now Available
The old V19.5 GA Thread: Sophos Firewall: v19.5 GA: Feedback and experiences
Removed Prio.
[gesperrt von: LuCar Toni um 11:37 AM (GMT -7) am 9 May 2023]
Important note about SSL VPN compatibility for 20.0 MR1 with EoL SFOS versions and UTM9 OS. Learn more in the release notes.
Release Post: Sophos Firewall OS v19.5 MR1 is Now Available
The old V19.5 GA Thread: Sophos Firewall: v19.5 GA: Feedback and experiences
I am running two XG125 in an active/passive-HA and got some issues with/after the upgrade:
- the failover during the upgrade-process happened way to early. The new primary took another minute or two to complete initialization and the admin interface to be available.
- Startup takes forever. about 7-10 Minutes for each node.
- For some reason TuneIn Radio doesn't work as long as the Firewalls are in a HA-Configuration. Everything is fine in Standalone.
Regards
Fabian
I experienced the slow surfing that lferrara wrote about as well. Most of the time is spent on content delivery, but it seems highly dependend on concurrency. e.g if only a single web page with a moderate number of external resources is loaded, delivery times are in the low milliseconds, but as soon as i try to load multiple pages at once everything slows to a crawl.
I experienced the slow surfing that lferrara wrote about as well. Most of the time is spent on content delivery, but it seems highly dependend on concurrency. e.g if only a single web page with a moderate number of external resources is loaded, delivery times are in the low milliseconds, but as soon as i try to load multiple pages at once everything slows to a crawl.
Did you create a support ID? Could you share it please?
__________________________________________________________________________________________________________________
I am using a home license as this is my private home setup. My understanding was that i couldn't open support tickets with this license type. I might get another xg125 for now to make sure the second node isn't busted, since the problems all disappear as soon as i revert the setup to standalone operation on the primary node.