tarzan2000
Regular Contributor
Good afternoon!
There is a router RT-AX56v2
The problem is this: some time after rebooting the router, connected clients are displayed in the list of networks even if the device is turned off.
Installed firmware version: 3.0.0.4.386_52294
Solved by restarting the Wifi module in the settings by changing some parameter or rebooting the router
In the log I get this:
After contacting support, I received a new firmware named RT-AX55_9.0.0.4_386_52297-g05e2188_puresqubi.zip (31.62 MB)
True, and unfortunately it did not eliminate the problem described above.
To be fair, the firmware works stably and without any complaints.
But why does it have the first number “9” at the beginning of the version and, as I understand it, it is not on the official product support channel?
Does anyone know anything interesting about this topic?
There is a router RT-AX56v2
The problem is this: some time after rebooting the router, connected clients are displayed in the list of networks even if the device is turned off.
Installed firmware version: 3.0.0.4.386_52294
Solved by restarting the Wifi module in the settings by changing some parameter or rebooting the router
In the log I get this:
Apr 1 11:03:18 wlceventd: wlceventd_proc_event(530): eth2: Auth 38
2:50:639:45, status: Successful (0), rssi:0
Apr 1 11:03:18 wlceventd: wlceventd_proc_event(559): eth2: Assoc 18:6E:57:64:89:45, status: Successful (0), rssi:-46
Apr 1 11:03:22 wlceventd: wlceventd_proc_event(494): eth2: Deauth_ind 3C:35:00:25:37:94, status: 0, reason: Previous authentication no longer valid (2), rssi:-42
Apr 1 11:03:22 wlceventd: wlceventd_proc_event(494): eth2: Deauth_ind 32:33:23:21:32:94, status: 0, reason: Disassociated due to inactivity (4), rssi:-42
Apr 1 11:03:23 wlceventd: wlceventd_proc_event(494): eth2: Deauth_ind 3C:33:00:21:37:92, status: 0, reason: Disassociated due to inactivity (4), rssi:0
Apr 1 11:03:23 wlceventd: wlceventd_proc_event(530): eth2: Auth 3C:32:03:21:37:94, status: Successful (0), rssi:0
Apr 1 11:03:23 wlceventd: wlceventd_proc_event(559): eth2: Assoc 33:25:03:21:37:24, status: Successful (0), rssi:-41
2:50:639:45, status: Successful (0), rssi:0Apr 1 11:03:18 wlceventd: wlceventd_proc_event(559): eth2: Assoc 18:6E:57:64:89:45, status: Successful (0), rssi:-46
Apr 1 11:03:22 wlceventd: wlceventd_proc_event(494): eth2: Deauth_ind 3C:35:00:25:37:94, status: 0, reason: Previous authentication no longer valid (2), rssi:-42
Apr 1 11:03:22 wlceventd: wlceventd_proc_event(494): eth2: Deauth_ind 32:33:23:21:32:94, status: 0, reason: Disassociated due to inactivity (4), rssi:-42
Apr 1 11:03:23 wlceventd: wlceventd_proc_event(494): eth2: Deauth_ind 3C:33:00:21:37:92, status: 0, reason: Disassociated due to inactivity (4), rssi:0
Apr 1 11:03:23 wlceventd: wlceventd_proc_event(530): eth2: Auth 3C:32:03:21:37:94, status: Successful (0), rssi:0
Apr 1 11:03:23 wlceventd: wlceventd_proc_event(559): eth2: Assoc 33:25:03:21:37:24, status: Successful (0), rssi:-41
After contacting support, I received a new firmware named RT-AX55_9.0.0.4_386_52297-g05e2188_puresqubi.zip (31.62 MB)
True, and unfortunately it did not eliminate the problem described above.
To be fair, the firmware works stably and without any complaints.
But why does it have the first number “9” at the beginning of the version and, as I understand it, it is not on the official product support channel?
Does anyone know anything interesting about this topic?
