You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
we experienced issues with changing the wireless channel off of 5. We changed it to 11, saved and applied, and although the menu records the channel as changed, Wi-Fi analyzer and iwconfig record it as still set to 5.
the node, upon bringing up its wireless interface, will always scan channels to see if there is a mesh to join, and it will join that mesh and set its channel to that mesh's channel regardless of the choice the user made. Thus far, it seems the workaround is to bring up the first node in a new mesh in the absence of any other mesh network, set its channel to the channel you want, then bring up the other nodes in its presence.
(Was issue 545 on code.commotionwireless.net)
The text was updated successfully, but these errors were encountered:
I've experienced problems with older versions of AA on UBNT devices not actually changing channel after modifying /etc/config/wireless and restarting interfaces. Full reboot seemed necessary to ensure channel change.
This problem does not occur in r38347, and it may also have been fixed as early as r36682 (upon which DR2 is still pinned).
we experienced issues with changing the wireless channel off of 5. We changed it to 11, saved and applied, and although the menu records the channel as changed, Wi-Fi analyzer and iwconfig record it as still set to 5.
the node, upon bringing up its wireless interface, will always scan channels to see if there is a mesh to join, and it will join that mesh and set its channel to that mesh's channel regardless of the choice the user made. Thus far, it seems the workaround is to bring up the first node in a new mesh in the absence of any other mesh network, set its channel to the channel you want, then bring up the other nodes in its presence.
(Was issue 545 on code.commotionwireless.net)
The text was updated successfully, but these errors were encountered: