In my mesh system running on a mixed LTS 4.3.8 and 4.3.6.2 ecosystem, whenever I change the "Allowed Wi-Fi System Nodes for Connection" setting for a specific client, I receive random notifications from the RMM Telegram bot indicating that devices have rebooted. These entries also appear in the RMM event log.
However, the devices are not actually rebooting. (There are also no reboot notifications triggered in the Keenetic mobile app.) For example, in the cropped screenshots attached, you can verify that the device named Backbone 10 never actually restarted.
Since this is the 3rd time I’ve encountered this behavior, I decided to open a ticket. I am attaching the self-test file from the Peak DSL (main controller). The client device I modified the settings for was the Samsung Projector (B0:99:D7:E5:27:44).
Prior to this, I disabled the 802.1r (Fast Transition) feature on the main controller. I believe doing so also triggered the same false node reboot alerts from RMM. I will double-check this behavior when I re-enable it.
On a side note, I previously opened a thread regarding an issue where I couldn't access RMM with LTS 4.3.8 due to the error: Core::Scgi::Tools: ignored floating point value "channel". That thread seems to have disappeared, but @eralde had suggested repacking the FW, which successfully brought my 4.3.8 system back online in RMM. Should I perform this FW repack action for all nodes receiving these false reboot alerts? (Though some of these nodes are currently on 4.3.6.2—I suppose I should check their logs first).
You can post now and register later.
If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.
Question
KYTECHNGAMING
Hello,
In my mesh system running on a mixed LTS 4.3.8 and 4.3.6.2 ecosystem, whenever I change the "Allowed Wi-Fi System Nodes for Connection" setting for a specific client, I receive random notifications from the RMM Telegram bot indicating that devices have rebooted. These entries also appear in the RMM event log.
However, the devices are not actually rebooting. (There are also no reboot notifications triggered in the Keenetic mobile app.) For example, in the cropped screenshots attached, you can verify that the device named Backbone 10 never actually restarted.
Since this is the 3rd time I’ve encountered this behavior, I decided to open a ticket. I am attaching the self-test file from the Peak DSL (main controller). The client device I modified the settings for was the Samsung Projector (
B0:99:D7:E5:27:44).Prior to this, I disabled the 802.1r (Fast Transition) feature on the main controller. I believe doing so also triggered the same false node reboot alerts from RMM. I will double-check this behavior when I re-enable it.
On a side note, I previously opened a thread regarding an issue where I couldn't access RMM with LTS 4.3.8 due to the error:
Core::Scgi::Tools: ignored floating point value "channel". That thread seems to have disappeared, but @eralde had suggested repacking the FW, which successfully brought my 4.3.8 system back online in RMM. Should I perform this FW repack action for all nodes receiving these false reboot alerts? (Though some of these nodes are currently on 4.3.6.2—I suppose I should check their logs first).Thanks in advance for looking into this!
0 answers to this question
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.