making node bandwidth changes in version 4.26.10.0.
In previous versions, changing the bandwidth from 10MHz to 5MHz prompted a commit followed by a reboot prompt, updating both the bandwidth and the node SID.
In version 4.26.10.0, the bandwidth updates upon commit, but the SID fails to update. This causes the link to drop and prevents re-establishing a connection over RF. Currently, the only way to recover is by connecting to the failed node through another node via a switch to initiate a reboot, or via direct LAN access.
I confirmed that the SID is not updating by running a Wi-Fi scan, which showed the SID remained AREDN-10-v3 instead of updating to AREDN-5-v3.
Please let me know if you need any additional details to help investigate.
Bill KA2FNK
In previous versions, changing the bandwidth from 10MHz to 5MHz prompted a commit followed by a reboot prompt, updating both the bandwidth and the node SID.
In version 4.26.10.0, the bandwidth updates upon commit, but the SID fails to update. This causes the link to drop and prevents re-establishing a connection over RF. Currently, the only way to recover is by connecting to the failed node through another node via a switch to initiate a reboot, or via direct LAN access.
I confirmed that the SID is not updating by running a Wi-Fi scan, which showed the SID remained AREDN-10-v3 instead of updating to AREDN-5-v3.
Please let me know if you need any additional details to help investigate.
Bill KA2FNK