Bug - AP15 needs reboot as ping becomes high

In any case: We're recommending to use Central Wireless for managing supported AP and APX models. This is free and has massive advantages over using the FW as wireless controller.

I do not want to have another account for managing one AP at home. More interfances, more accounts, more windows to from across. It does not make sense for even for SMBs.

I would disagree for SMB as lot of Sophos customers have and look for multiple products in one console. Access Points and now Switches are products that typically are purchased when it's part of the same solution - was UTM now Central.

EMEA and NA are too different markets. People in EMEA prefers to use one console. If they have AP connected to XG, they expect to manage them in one console.

From what I can see from usage numbers SMB and MM in EMEA and NA are very similar in this respect (maybe a difference in the definitions of what SMB is in EMEA and NA). We'll see when the switch becomes more widely used as it can not be managed from the Firewall but Central. We just started ;)

Thanks Sascha. So, at the end, the issue will not be fixed and I need to stay on v18.5 or use central wireless to manage just one AP at home? At this point, you can even remove the wi-fi feature on XG, if this is the approach you are following. I personally do not agree. I hope I am wrong.

Essentially Legacy AP is end of support anyway. See: https://support.sophos.com/support/s/article/KB-000035279?language=en_US#sophosaccesspoints

End of Support After this date:
Sophos will process RMAs but no longer offers support.
The affected model will no longer receive any software updates or bug fixes of any kind.
The AP will continue to work on the last supported firmware version.
RMAs: Will be processed for any model with a valid warranty or support license (if the same model is not available, an equivalent model will be supplied as a replacement).

Support: Technical support is no longer provided. Hotline calls will only be accepted for RMA processing.

So if there was / is a change of the software and affecting a certain kind of installation, this is up to Sophos development to decide, if we can fix this or not. 

In Central Wireless, it seems still to work without any issue, as far as i can tell. 

Essentially Legacy AP is end of support anyway. See: https://support.sophos.com/support/s/article/KB-000035279?language=en_US#sophosaccesspoints

End of Support After this date:
Sophos will process RMAs but no longer offers support.
The affected model will no longer receive any software updates or bug fixes of any kind.
The AP will continue to work on the last supported firmware version.
RMAs: Will be processed for any model with a valid warranty or support license (if the same model is not available, an equivalent model will be supplied as a replacement).

Support: Technical support is no longer provided. Hotline calls will only be accepted for RMA processing.

So if there was / is a change of the software and affecting a certain kind of installation, this is up to Sophos development to decide, if we can fix this or not. 

In Central Wireless, it seems still to work without any issue, as far as i can tell. 

Hi Iferrara,

As mentioned in the above comment, AP15 is now end of support and hence unfortunately we cannot continue with any further investigation on this issue.

Thanks Rohan for your reply. Nothing against this, but you are cutting our all home users for use wi-fi on XG. Home users won't spend 300€ to buy an APX 120. In this way, you won't get any feedbacks on new feature you will release on XG Wireless controller, unless from people who owns an expensive AP or from people whom are using the XG in their organization. After closing the advanced shell to home users, you are cutting-off even Wireless features. THANK YOU VERY MUCH. This is the power of sharing!

XG logs are clear and straightforward: https://community.sophos.com/sophoswireless/f/discussions/132460/unable-to-move-ap15-from-xg-18-5-mr2-to-central see what is happening here. AP has been rebooted twice.