Hi, I have frequent internet dropouts with my aging Asus router. Below is a hour worth of snippet from my log. I am requesting help from anyone that understands the below so they could tell me what's causing these dropouts? Is it the router or the ISP?
Many thanks in advance.
-----------------------------
Dec 3 09:03:33 acsd: selected channel spec: 0xe02a (36/80)
Dec 3 09:03:33 acsd: Adjusted channel spec: 0xe02a (36/80)
Dec 3 09:03:33 acsd: selected channel spec: 0xe02a (36/80)
Dec 3 09:03:33 acsd: acs_set_chspec: 0xe02a (36/80) for reason APCS_CSTIMER
Dec 3 09:06:53 kernel: 7C:DD:90:77:21:CE not mesh client, can't update it's ip
Dec 3 09:08:22 kernel: 7C:DD:90:77:21:CE not mesh client, can't update it's ip
Dec 3 09:11:33 syslog: wlceventd_proc_event(474): eth1: Deauth_ind 08:D2:3E:DD:ED:4D, status: 0, reason: Unspecified reason (1)
Dec 3 09:11:34 syslog: wlceventd_proc_event(510): eth1: Auth 08:D2:3E:DD:ED:4D, status: Successful (0)
Dec 3 09:11:34 syslog: wlceventd_proc_event(520): eth1: ReAssoc 08:D2:3E:DD:ED:4D, status: Successful (0)
Dec 3 09:11:36 kernel: 7C:DD:90:77:21:CE not mesh client, can't update it's ip
Dec 3 09:18:36 acsd: selected channel spec: 0xe02a (36/80)
Dec 3 09:18:36 acsd: Adjusted channel spec: 0xe02a (36/80)
Dec 3 09:18:36 acsd: selected channel spec: 0xe02a (36/80)
Dec 3 09:18:36 acsd: acs_set_chspec: 0xe02a (36/80) for reason APCS_CSTIMER
Dec 3 09:18:53 kernel: 7C:DD:90:77:21:CE not mesh client, can't update it's ip
Dec 3 09:20:23 kernel: 7C:DD:90:77:21:CE not mesh client, can't update it's ip
Dec 3 09:20:35 miniupnpd[545]: upnp_event_process_notify: connect(192.168.1.158:2869): Connection timed out
Dec 3 09:20:40 miniupnpd[545]: upnp_event_process_notify: connect(192.168.1.158:2869): Connection timed out
Dec 3 09:23:24 kernel: 7C:DD:90:77:21:CE not mesh client, can't update it's ip
Dec 3 09:23:29 syslog: wlceventd_proc_event(510): eth1: Auth 4C:B0:08:E0:32:D3, status: Successful (0)
Dec 3 09:23:29 syslog: wlceventd_proc_event(539): eth1: Assoc 4C:B0:08:E0:32:D3, status: Successful (0)
Dec 3 09:23:29 kernel: 7C:DD:90:77:21:CE not mesh client, can't update it's ip
Dec 3 09:23:59 syslog: wlceventd_proc_event(474): eth1: Deauth_ind 4C:B0:08:E0:32:D3, status: 0, reason: Disassociated due to inactivity (4)
Dec 3 09:24:54 kernel: 7C:DD:90:77:21:CE not mesh client, can't update it's ip
Dec 3 09:26:24 kernel: 7C:DD:90:77:21:CE not mesh client, can't update it's ip
Dec 3 09:32:24 kernel: 7C:DD:90:77:21:CE not mesh client, can't update it's ip
Dec 3 09:33:25 syslog: wlceventd_proc_event(474): eth1: Deauth_ind 08:D2:3E:DD:ED:4D, status: 0, reason: Unspecified reason (1)
Dec 3 09:33:26 syslog: wlceventd_proc_event(510): eth1: Auth 08:D2:3E:DD:ED:4D, status: Successful (0)
Dec 3 09:33:26 syslog: wlceventd_proc_event(520): eth1: ReAssoc 08:D2:3E:DD:ED:4D, status: Successful (0)
Dec 3 09:33:29 kernel: 7C:DD:90:77:21:CE not mesh client, can't update it's ip
Dec 3 09:33:39 acsd: selected channel spec: 0xe02a (36/80)
Dec 3 09:33:39 acsd: Adjusted channel spec: 0xe02a (36/80)
Dec 3 09:33:39 acsd: selected channel spec: 0xe02a (36/80)
Dec 3 09:33:39 acsd: acs_set_chspec: 0xe02a (36/80) for reason APCS_CSTIMER
Dec 3 09:38:24 kernel: 7C:DD:90:77:21:CE not mesh client, can't update it's ip
Dec 3 09:41:31 syslog: wlceventd_proc_event(474): eth1: Deauth_ind 08:D2:3E:DD:ED:4D, status: 0, reason: Unspecified reason (1)
Dec 3 09:41:44 syslog: wlceventd_proc_event(510): eth1: Auth 08:D2:3E:DD:ED:4D, status: Successful (0)
Dec 3 09:41:44 syslog: wlceventd_proc_event(510): eth1: Auth 08:D2:3E:DD:ED:4D, status: Successful (0)
Dec 3 09:41:44 syslog: wlceventd_proc_event(539): eth1: Assoc 08:D2:3E:DD:ED:4D, status: Successful (0)
Dec 3 09:41:45 kernel: 7C:DD:90:77:21:CE not mesh client, can't update it's ip
Dec 3 09:41:45 kernel: 08:D2:3E:DD:ED:4D not mesh client, can't update it's ip
Dec 3 09:41:47 kernel: 7C:DD:90:77:21:CE not mesh client, can't update it's ip
Dec 3 09:46:49 syslog: wlceventd_proc_event(474): eth1: Deauth_ind 08:D2:3E:DD:ED:4D, status: 0, reason: Unspecified reason (1)
Dec 3 09:47:02 syslog: wlceventd_proc_event(510): eth1: Auth 08:D2:3E:DD:ED:4D, status: Successful (0)
Dec 3 09:47:02 syslog: wlceventd_proc_event(539): eth1: Assoc 08:D2:3E:DD:ED:4D, status: Successful (0)
Dec 3 09:47:04 kernel: 7C:DD:90:77:21:CE not mesh client, can't update it's ip
Dec 3 09:48:43 acsd: selected channel spec: 0xe02a (36/80)
Dec 3 09:48:43 acsd: Adjusted channel spec: 0xe02a (36/80)
Dec 3 09:48:43 acsd: selected channel spec: 0xe02a (36/80)
Dec 3 09:48:43 acsd: acs_set_chspec: 0xe02a (36/80) for reason APCS_CSTIMER
Dec 3 09:51:55 kernel: 7C:DD:90:77:21:CE not mesh client, can't update it's ip
Dec 3 09:53:02 syslog: wlceventd_proc_event(474): eth1: Deauth_ind 08:D2:3E:DD:ED:4D, status: 0, reason: Unspecified reason (1)
Dec 3 09:53:16 syslog: wlceventd_proc_event(510): eth1: Auth 08:D2:3E:DD:ED:4D, status: Successful (0)
Dec 3 09:53:16 syslog: wlceventd_proc_event(539): eth1: Assoc 08:D2:3E:DD:ED:4D, status: Successful (0)
Dec 3 09:53:16 kernel: 7C:DD:90:77:21:CE not mesh client, can't update it's ip
Dec 3 09:53:16 kernel: 08:D2:3E:DD:ED:4D not mesh client, can't update it's ip
Dec 3 09:53:19 kernel: 7C:DD:90:77:21:CE not mesh client, can't update it's ip
Dec 3 09:53:25 kernel: 7C:DD:90:77:21:CE not mesh client, can't update it's ip
Dec 3 09:54:48 syslog: wlceventd_proc_event(474): eth1: Deauth_ind 08:D2:3E:DD:ED:4D, status: 0, reason: Unspecified reason (1)
Dec 3 09:55:01 syslog: wlceventd_proc_event(510): eth1: Auth 08:D2:3E:DD:ED:4D, status: Successful (0)
Dec 3 09:55:01 syslog: wlceventd_proc_event(539): eth1: Assoc 08:D2:3E:DD:ED:4D, status: Successful (0)
Dec 3 09:55:04 kernel: 7C:DD:90:77:21:CE not mesh client, can't update it's ip
Dec 3 09:56:19 syslog: wlceventd_proc_event(474): eth1: Deauth_ind 08:D2:3E:DD:ED:4D, status: 0, reason: Unspecified reason (1)
Dec 3 09:56:20 syslog: wlceventd_proc_event(510): eth1: Auth 08:D2:3E:DD:ED:4D, status: Successful (0)
Dec 3 09:56:20 syslog: wlceventd_proc_event(520): eth1: ReAssoc 08:D2:3E:DD:ED:4D, status: Successful (0)
Dec 3 09:56:25 syslog: wlceventd_proc_event(474): eth1: Deauth_ind 08:D2:3E:DD:ED:4D, status: 0, reason: Unspecified reason (1)
Dec 3 09:56:26 syslog: wlceventd_proc_event(510): eth1: Auth 08:D2:3E:DD:ED:4D, status: Successful (0)
Dec 3 09:56:26 syslog: wlceventd_proc_event(539): eth1: Assoc 08:D2:3E:DD:ED:4D, status: Successful (0)
Dec 3 09:56:29 kernel: 7C:DD:90:77:21:CE not mesh client, can't update it's ip
Dec 3 10:00:13 syslog: wlceventd_proc_event(474): eth1: Deauth_ind 08:D2:3E:DD:ED:4D, status: 0, reason: Unspecified reason (1)
Dec 3 10:01:28 syslog: wlceventd_proc_event(510): eth1: Auth 08:D2:3E:DD:ED:4D, status: Successful (0)
Dec 3 10:01:28 syslog: wlceventd_proc_event(539): eth1: Assoc 08:D2:3E:DD:ED:4D, status: Successful (0)
Dec 3 10:01:31 kernel: 7C:DD:90:77:21:CE not mesh client, can't update it's ip
Dec 3 10:03:46 acsd: selected channel spec: 0xe02a (36/80)
Dec 3 10:03:46 acsd: Adjusted channel spec: 0xe02a (36/80)
Dec 3 10:03:46 acsd: selected channel spec: 0xe02a (36/80)
Dec 3 10:03:46 acsd: acs_set_chspec: 0xe02a (36/80) for reason APCS_CSTIMER
Try changing the wireless channels (on both 2.4 and 5 GHz) from auto to a fixed channel.
On 2.4 GHz use channel 1, 6 or 11. On 5 GHz, channel 48 or lower usually works best.
Do you have mesh turned on with another Asus?
Seems to be a lot of mesh messages but I don't see them without aimesh working.
Asus do seem like most routers to have the wifi die first. So the router runs ok.. but the wifi is poor.
How old exactly is the Asus? It is likely to just need replacement.
Just to add to double-mint.. I would do a full factory reset and reconfigure it manually all over again.. fixed wireless channels if you like.. I personally get better speed and signal on 149 due to amplified output rather than 36-48 area.. but it is often dependent on the building.
Do you have mesh turned on with another Asus?
Not turned on.
How old exactly is the Asus? It is likely to just need replacement.
its 5 and a bit years old.
its 5 and a bit years old.
IMHO that is about the expected lifespan of better grade domestic routers.
If you want to play by downgrading firmware.. always a good idea as sometimes latest is not so greatest.. even try a Merlin if you are using standard Asus or visa versa.
Factory reset and reconfigure from scratch..
Power supply replacement being the last and most difficult of that list.
And it could give you another 6months without issues.. or a week.. or a few hours.
Depends on how much your time is worth and how desperate you are to get decent wireless working again.
Time to replace.. at least that is what I do.
Please try this version of firmware released at 2021-07-02 targeted to solve the problem "not mesh client, can't update it's ip".
https://www.asuswebstora
