What's new

Aimesh node keeps restarting wireless

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

bones20

Occasional Visitor
Hi All,
I have an Aimesh setup at home for the last 2 years:
APs (RT-AC68u) * 2
Firmware: 3.0.0.4.384_45717 (although tried all including latest)
Config: Fixed channels, 20MHZ for 2.4ghz, disabled these (airtime fairness, beam formations (except ac), Nat acceleration), everything else default.

Since the last 4-5 weeks, I am seeing jittery wifi near the Aimesh node in the bedroom. I see the below logs when that happens. I have tried everything I could think of including rebuilding from scratch, different firmware versions, reducing radio power etc. Why does the rc_service daemon keep restarting the wireless 5/6 times a day?:
Apr 4 12:07:45 rc_service: amas_wlcconnect 22852:notify_rc restart_wireless

At this point, I have given up and planning to buy a new system unless somehow here has a clue on how t solve this problem. Thanks in advance. Your help is much appreciated.
Code:
Apr 4 11:58:43 acsd: scan in progress ...

Apr 4 11:58:43 acsd: scan in progress ...

Apr 4 11:58:43 acsd: scan in progress ...

Apr 4 12:06:52 rc_service: watchdog 250:notify_rc start_cfgsync

Apr 4 12:07:45 rc_service: amas_wlcconnect 22852:notify_rc restart_wireless

Apr 4 12:07:51 kernel: dpsta enabled

Apr 4 12:07:52 acsd: scan in progress ...

Apr 4 12:07:52 acsd: scan in progress ...

Apr 4 12:07:52 rc_service: watchdog 250:notify_rc start_amas_bhctrl

Apr 4 12:07:52 rc_service: waitting "restart_wireless" via ...

Apr 4 12:07:52 acsd: scan in progress ...

Apr 4 12:07:52 acsd: scan in progress ...

Apr 4 12:07:53 acsd: scan in progress ...

Apr 4 12:07:53 acsd: scan in progress ...

Apr 4 12:07:53 acsd: scan in progress ...

Apr 4 12:07:53 acsd: scan in progress ...

Apr 4 12:07:54 acsd: scan in progress ...

Apr 4 12:07:54 acsd: scan in progress ...

Apr 4 12:07:54 acsd: scan in progress ...

Apr 4 12:07:54 acsd: selected channel spec: 0x1005 (5)

Apr 4 12:07:54 acsd: Adjusted channel spec: 0x1005 (5)

Apr 4 12:07:54 acsd: selected DFS-exit channel spec: 0x1005 (5)

Apr 4 12:07:54 acsd: selected channel spec: 0x1005 (5)

Apr 4 12:07:54 acsd: Adjusted channel spec: 0x1005 (5)

Apr 4 12:07:54 acsd: selected channel spec: 0x1005 (5)

Apr 4 12:07:55 acsd: scan in progress ...

Apr 4 12:07:55 acsd: scan in progress ...

Apr 4 12:07:55 acsd: scan in progress ...

Apr 4 12:07:55 acsd: scan in progress ...
 
Hi All,
I have an Aimesh setup at home for the last 2 years:
APs (RT-AC68u) * 2
Firmware: 3.0.0.4.384_45717 (although tried all including latest)
Config: Fixed channels, 20MHZ for 2.4ghz, disabled these (airtime fairness, beam formations (except ac), Nat acceleration), everything else default.

Since the last 4-5 weeks, I am seeing jittery wifi near the Aimesh node in the bedroom. I see the below logs when that happens. I have tried everything I could think of including rebuilding from scratch, different firmware versions, reducing radio power etc. Why does the rc_service daemon keep restarting the wireless 5/6 times a day?:
Apr 4 12:07:45 rc_service: amas_wlcconnect 22852:notify_rc restart_wireless

At this point, I have given up and planning to buy a new system unless somehow here has a clue on how t solve this problem. Thanks in advance. Your help is much appreciated.
Code:
Apr 4 11:58:43 acsd: scan in progress ...

Apr 4 11:58:43 acsd: scan in progress ...

Apr 4 11:58:43 acsd: scan in progress ...

Apr 4 12:06:52 rc_service: watchdog 250:notify_rc start_cfgsync

Apr 4 12:07:45 rc_service: amas_wlcconnect 22852:notify_rc restart_wireless

Apr 4 12:07:51 kernel: dpsta enabled

Apr 4 12:07:52 acsd: scan in progress ...

Apr 4 12:07:52 acsd: scan in progress ...

Apr 4 12:07:52 rc_service: watchdog 250:notify_rc start_amas_bhctrl

Apr 4 12:07:52 rc_service: waitting "restart_wireless" via ...

Apr 4 12:07:52 acsd: scan in progress ...

Apr 4 12:07:52 acsd: scan in progress ...

Apr 4 12:07:53 acsd: scan in progress ...

Apr 4 12:07:53 acsd: scan in progress ...

Apr 4 12:07:53 acsd: scan in progress ...

Apr 4 12:07:53 acsd: scan in progress ...

Apr 4 12:07:54 acsd: scan in progress ...

Apr 4 12:07:54 acsd: scan in progress ...

Apr 4 12:07:54 acsd: scan in progress ...

Apr 4 12:07:54 acsd: selected channel spec: 0x1005 (5)

Apr 4 12:07:54 acsd: Adjusted channel spec: 0x1005 (5)

Apr 4 12:07:54 acsd: selected DFS-exit channel spec: 0x1005 (5)

Apr 4 12:07:54 acsd: selected channel spec: 0x1005 (5)

Apr 4 12:07:54 acsd: Adjusted channel spec: 0x1005 (5)

Apr 4 12:07:54 acsd: selected channel spec: 0x1005 (5)

Apr 4 12:07:55 acsd: scan in progress ...

Apr 4 12:07:55 acsd: scan in progress ...

Apr 4 12:07:55 acsd: scan in progress ...

Apr 4 12:07:55 acsd: scan in progress ...

Should it be scanning if you are using fixed channels?

OE
 
for 5 GHZ, extension channel is set to AUTO (no other option)
channel bandwidth is 20/40/80
 
for 5 GHZ, extension channel is set to AUTO (no other option)
channel bandwidth is 20/40/80

I use:
- set 2.4 WLAN to n-only, 20 MHz, ch 1,6,11 or 1,5,9,13 (non-overlapping, least congested), WPA2-Personal AES
- set 5.0 WLAN to n/ac mixed, 80 MHz, ch 149 or above (US, non-radar, highest Tx power), WPA2-Personal AES

OE
 
I use:
- set 2.4 WLAN to n-only, 20 MHz, ch 1,6,11 or 1,5,9,13 (non-overlapping, least congested), WPA2-Personal AES
- set 5.0 WLAN to n/ac mixed, 80 MHz, ch 149 or above (US, non-radar, highest Tx power), WPA2-Personal AES

OE
I tried the fixed bandwidth 80MHz. Still see the acsd scan log messages. Rest of my configuration is same as yours.
 
I tried the fixed bandwidth 80MHz. Still see the acsd scan log messages. Rest of my configuration is same as yours.

Given it worked for two years and is now acting up, maybe a router is failing.

OE
 
Before you give up on the hardware, see if a full reset helps. :)

Please see the link in my signature below for the M&M Config and the Nuclear Reset guides.

The following links may also be of use to get your router back to a good/known state.

If after following these suggested steps the issue is still present, without any of your specific customizations in place, then a hardware issue is more likely the real problem.

https://www.snbforums.com/threads/ax88-packet-loss.62891/#post-563326

https://www.snbforums.com/threads/order-of-installing-popular-scripts.61854/#post-551865

HTH.
 
Just Fyi, the problem seems to have gone (17 hours so far) after I replaced the power adaptor. Will be able to confirm if and once this is sustained our few days.
 

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top