I was thinking about updating to MR2 from MR1 but the reported issues keep me from updating. I thought of bringing them together in this thread so everybody can easily follow the progress of them to decide wether to install or not.
UPDATE: MR3 does not fix all issues. Still problems with Garner service and high cpu load.
Is 17.1.2 MR-2 ready for prime time?
Many positive feedbacks but MR2 seems to forget the cached FQDN Hosts on a regular basis. Further a report on broken Garner service and VPN issue as well as issues with HA mode
SFOS 17.1.2 MR-2 . Really?
Seeing a lot of RST packets and the connection either times out or the streams (youtube) disconnect and have to reconnect. Refers to large downloads and streaming.
Seems that it is not a generic issue.
High CPU-load with SFOS 17.1.2 MR-2 and HA
High CPU load on XG HA-cluster in A/P mode after updating to MR2. Reported for XG125 and XG330.
This issue occurs only if the RED feature is enabled and at least one RED interface is connected. The more RED interfaces are used, the heavier the issue occurs. Also happens on non-HA setups. Will be fixed in MR3 but it seems MR3 has the same issue...
A fix can be obtained which will be included in MR3: https://community.sophos.com/products/xg-firewall/f/firewall-and-policies/105431/sophos-notification-sophos-xg-firewall-some-customers-are-experiencing-high-cpu-utilization-after-updating-to-v17-1-mr2
upgrade to SFOS 17.1.2 MR-2
APs are shown normally and functional. They are connected and offer connectivity to clients but there is no data transfer from the connected clients
DHCP_Port2_GW has wrong address since SFOS 17.1.2 MR-2
DHCP_Port2_GW has an address that is way off of what the WAN address
SOLVED and seems not to be a generic issue [:)]
SNMP Issue after update to 17.1.2
SNMP connections failing and logging daemon service keeps restarting
Issue has been confirmed and will be fixed in MR3. A temporary workaround seems to be available at support.
Missing DHCP Relay configuration after upgrade to SFOS 17.1.2 MR-2
DHCP relay configuration missing after update
Seems not to be an generic issue
This thread was automatically locked due to age.