Sophos Firewall: v19.0 MR2: Feedback and experiences

So we had an interesting experience with an upgrade from 18.5.something to 19.0 MR2 at a customer site earlier this week; when we applied it none of the wifi (APX320, 740s, etc.) clients could connect; in the DHCP log (with the firewall providing DHCP for most of these) we saw constant lease activity on some test devices.  These are all wifi networks provisioned using the separate zone method.  As this needed to be working and in production, we rolled back to the old 18.5 firmware, and function returned.  Didn't have time for a support case, etc. but thank goodness for the rollback function!

So we had an interesting experience with an upgrade from 18.5.something to 19.0 MR2 at a customer site earlier this week; when we applied it none of the wifi (APX320, 740s, etc.) clients could connect; in the DHCP log (with the firewall providing DHCP for most of these) we saw constant lease activity on some test devices.  These are all wifi networks provisioned using the separate zone method.  As this needed to be working and in production, we rolled back to the old 18.5 firmware, and function returned.  Didn't have time for a support case, etc. but thank goodness for the rollback function!

Forgot to mention this was on XG hardware, not XGS.

Ask Sophos about NC-114092 and try this workaround, i received this from sophos

Workaround 1:

If you are facing this issue then remove and re-add the affected separate zone SSID from AP/APX.

Workaround 2:

If you are facing this issue then restart the awed service. Please note that all the connected AP/APX will be disconnected and connected back.

service awed:restart -ds nosync

Interesting, so a known issue.... We'll probably just wait until this is actually fixed.  Is it fixed in the recently released 19.5 MR2?