Maintenance Release (MR) version 1.2.1584 has the following new features and bug fixes.

New Features

Wireless Mesh: AP6 Series access points can be configured in a wireless mesh mode. A wireless mesh allows the AP6s to create a private SSID that is only visible to other AP6 access points that are configured to take part within the mesh network. The access points function as a wireless bridge for different wireless network segments. Wireless mesh is used for deployments where physical cabling may not be available for all access points deployed within a location. The feature can be managed from Sophos Central or using the local user interface for each AP6 access point.

For additional information on how to set up a mesh network with the AP6 Series access points. 

Other Wireless News

PoE++ Injector (60W)

We recently started shipping a 60W PoE++ injector (802.3bt). This provides sufficient power for an individual AP6 840E and is backward compatible, so it could be used for an access point that requires less power.

For additional power information please visit: https://support.sophos.com/support/s/article/KB-000045501?language=en_US

Bug fixes

Issue Key Summary
WIFIX-3715 The Mesh configuration is not synchronized between the Root node and Mesh nodes when the Mesh ID contains a space.
WIFIX-3489 MacBook wireless devices cannot connect to a mesh network when OWE authentication is selected.
WIFIX-3478 The client load balancing setting does not get displayed on wireless mesh nodes that are not the root node.
WIFIX-3387 We have seen the Mesh backhaul connection get disconnected every 30-40 seconds when auto-channel is configured on that radio.
WIFIX-3821 The SSID used for the Mesh backhaul is broadcast when using the 2.4 GHz band. Wireless clients may be able to connect to this SSID if they know the Mesh password.
WIFIX-3387 If you enable auto-channel on the backhaul SSID you may notice instability with the Mesh network. We recommend manually setting the channels to use with the back-haul SSID.
WIFIX-3798 A Mesh “Node’s” radio parameters can be changed from Sophos Central. Any radio changes should be done through the Root Node.

Known Issues:

Issue Key Summary Work Around 
WIFIX-4530 If the default management VLAN is changed on the AP6 Root Node, that configuration change does not currently get synchronized with the AP6 nodes taking part in the mesh network.

From Central navigate to the Access Point page and manually set the correct management VLAN for each node taking part in the mesh network.

Go to the local GUI of the AP6 nodes and manually change the management VLAN ID. This can be done from the Network Settings<<VLAN page in the local GUI on the node access points.

WIFIX-4297 In certain scenarios, we have seen that using more than a single hop (2-hop or more) for a node to create a mesh network does not work properly. Any nodes try to connect through an intermediary node and then the root does not create a mesh connection. The nodes currently will only connect with the root node in the mesh network. Locate the node access points closer to the root node so all nodes in the mesh connect to the root node.
WIFIX-4586 The VLAN interface set up for Captive Portal does not receive an IP address after editing an existing SSID and adding a new Captive Portal configuration. This is seen both from Central and the local AP6 GUI. This issue does not seem to happen if you edit other parameters within the SSID including Captive portal vouchers, passphrase, and encryption for example.

From Central update the existing Captive Portal SSID and “Save” the configuration to re-apply the changes to the access point.

From the local AP6 GUI, ensure that you hit the apply button after completing all the Captive Portal changes.

Rebooting the access point from Central or the local AP6 GUI will resolve the issue.

For more known issues please visit https://doc.sophos.com/support/kil/index.html