Hello,
I recently upgraded from 384.13_0 to 384.14_2, and since then i have an issue with all my Android TVs not connecting to the wireless network when they boot up. The only way i can solve this is by getting into the TV menu and manually connect them. Then it works fine until the next power cycle.
Windows laptops don't seem to be affected.
Whenever that happens, i see the following in the system log:
Jan 28 13:21:07 syslog: WLCEVENTD wlceventd_proc_event(420): eth2: Auth XX:XX:XX:XX:XX:XX, status: 0, reason: d11 RC reserved (0)
Jan 28 13:21:07 syslog: WLCEVENTD wlceventd_proc_event(420): eth2: Auth XX:XX:XX:XX:XX:XX, status: 0, reason: d11 RC reserved (0)
Jan 28 13:21:07 syslog: WLCEVENTD wlceventd_proc_event(449): eth2: Assoc XX:XX:XX:XX:XX:XX, status: 0, reason: d11 RC reserved (0)
Jan 28 13:21:15 syslog: WLCEVENTD wlceventd_proc_event(386): eth2: Deauth_ind XX:XX:XX:XX:XX:XX, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Jan 28 13:21:36 syslog: WLCEVENTD wlceventd_proc_event(420): eth2: Auth XX:XX:XX:XX:XX:XX, status: 0, reason: d11 RC reserved (0)
Jan 28 13:21:36 syslog: WLCEVENTD wlceventd_proc_event(449): eth2: Assoc XX:XX:XX:XX:XX:XX, status: 0, reason: d11 RC reserved (0)
Jan 28 13:21:44 syslog: WLCEVENTD wlceventd_proc_event(386): eth2: Deauth_ind XX:XX:XX:XX:XX:XX, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
I did perform a restore to factory defaults but hasn't solved the issue.
Has anyone else encountered this issue in 384.14_2? Maybe a suggestion on how to fix it? It's relatively annoying having to manually connect the TVs to the network every time.
Please note that 384.13_0 or previous versions did not have this issue. I'll probably revert back to that.
Thanks in advance!
I recently upgraded from 384.13_0 to 384.14_2, and since then i have an issue with all my Android TVs not connecting to the wireless network when they boot up. The only way i can solve this is by getting into the TV menu and manually connect them. Then it works fine until the next power cycle.
Windows laptops don't seem to be affected.
Whenever that happens, i see the following in the system log:
Jan 28 13:21:07 syslog: WLCEVENTD wlceventd_proc_event(420): eth2: Auth XX:XX:XX:XX:XX:XX, status: 0, reason: d11 RC reserved (0)
Jan 28 13:21:07 syslog: WLCEVENTD wlceventd_proc_event(420): eth2: Auth XX:XX:XX:XX:XX:XX, status: 0, reason: d11 RC reserved (0)
Jan 28 13:21:07 syslog: WLCEVENTD wlceventd_proc_event(449): eth2: Assoc XX:XX:XX:XX:XX:XX, status: 0, reason: d11 RC reserved (0)
Jan 28 13:21:15 syslog: WLCEVENTD wlceventd_proc_event(386): eth2: Deauth_ind XX:XX:XX:XX:XX:XX, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Jan 28 13:21:36 syslog: WLCEVENTD wlceventd_proc_event(420): eth2: Auth XX:XX:XX:XX:XX:XX, status: 0, reason: d11 RC reserved (0)
Jan 28 13:21:36 syslog: WLCEVENTD wlceventd_proc_event(449): eth2: Assoc XX:XX:XX:XX:XX:XX, status: 0, reason: d11 RC reserved (0)
Jan 28 13:21:44 syslog: WLCEVENTD wlceventd_proc_event(386): eth2: Deauth_ind XX:XX:XX:XX:XX:XX, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
I did perform a restore to factory defaults but hasn't solved the issue.
Has anyone else encountered this issue in 384.14_2? Maybe a suggestion on how to fix it? It's relatively annoying having to manually connect the TVs to the network every time.
Please note that 384.13_0 or previous versions did not have this issue. I'll probably revert back to that.
Thanks in advance!