Changed Guest SID, Full Stack Rebooted
John A last edited by
I had reason to change to the SID of my - inactive - guest network, only to find, that in order for the change to be made, my entire stack rebooted. I get that a loss of service would be needed if I was changing the primary SID, but for all nodes to reboot to change the SID of the inactive guest network seems a bit un-necessary, surely?
I'm running two HD's on the latest 2.7 firmware.