AiMesh fine for 2 years, now a mess, advice anyone?

[Nihilim]

Hello,

I can see on the forum that there is a lot of dislike regarding AiMesh. I really want to use it and it worked fine until a week ago.

If anyone has the time and energy, please read my post and see if you can give me any advice.

Mu initial setup was 2 x RT-AC68U and this worked satisfying for 18 months. I wanted to expand my range in my house and bought 1 RT-AC86U in November 2019

The RT-AC86U became AiMesh router and 1 RT-AC68U as a node. This has worked again satisfying with some restarts needed and other minor problems I can read in the forum from November 2019 until last week.

My network just went haywire, drops all connected devices all the time. The SSID disappears for awhile. This goes on non-stop. Thought that my really old RT-AC68U had it. I decided that it's time to upgrade it to another RT-AC86U.

So now i had 2 x RT-AC86U, but the problem persists non-stop. So I took the new RT-AC86U and paired it with the second RT-AC68U that I hadn't used as I thought it might be something wrong with the RT-AC86U that I bought in November 2019. Same problem, So now I have tried every possible combination of 2 routers and I have the same issues.

Don't understand why it has worked for almost 2 years and now I can't use AiMesh at all. I have upgraded the firmware on all routers to the latest after the issues started and that doesn't help.

Any tips, is it a lost cause with AiMesh?

Will upload my log from the router if anyone want's to have a look.
B0:6E:BF:3B:19: D1 is the MAC address of the node.

At the moment I am using media bridge mode as most of the devices are connected through cable on the node.

 

[L&LD]

Have you followed @OzarkEdge's AiMesh notes?

https://www.snbforums.com/threads/o...-supported-products.44375/page-14#post-381537

 

[Nihilim]

Have you followed @OzarkEdge's AiMesh notes?

https://www.snbforums.com/threads/o...-supported-products.44375/page-14#post-381537

No I haven't, that is a lot of configuration to get AiMesh working. I worked fine until a week ago and I just used default configuration, set the mesh up and worked fine.
If you have to do all that to get it to work again, in my opinion sucks.

Will have to see if I have the energy to do all that, media bridge works fine at the moment, I loose a bit of range on the wireless though.

 

[OzarkEdge]

Hello,

I can see on the forum that there is a lot of dislike regarding AiMesh. I really want to use it and it worked fine until a week ago.

If anyone has the time and energy, please read my post and see if you can give me any advice.

Mu initial setup was 2 x RT-AC68U and this worked satisfying for 18 months. I wanted to expand my range in my house and bought 1 RT-AC86U in November 2019

The RT-AC86U became AiMesh router and 1 RT-AC68U as a node. This has worked again satisfying with some restarts needed and other minor problems I can read in the forum from November 2019 until last week.

My network just went haywire, drops all connected devices all the time. The SSID disappears for awhile. This goes on non-stop. Thought that my really old RT-AC68U had it. I decided that it's time to upgrade it to another RT-AC86U.

So now i had 2 x RT-AC86U, but the problem persists non-stop. So I took the new RT-AC86U and paired it with the second RT-AC68U that I hadn't used as I thought it might be something wrong with the RT-AC86U that I bought in November 2019. Same problem, So now I have tried every possible combination of 2 routers and I have the same issues.

Don't understand why it has worked for almost 2 years and now I can't use AiMesh at all. I have upgraded the firmware on all routers to the latest after the issues started and that doesn't help.

Any tips, is it a lost cause with AiMesh?

Will upload my log from the router if anyone want's to have a look.
B0:6E:BF:3B:19: D1 is the MAC address of the node.

At the moment I am using media bridge mode as most of the devices are connected through cable on the node.

You imply one SSID. Assuming your hardware is ok, I would install the latest firmware on the two 86Us, reset both, and install a 2x86U AiMesh per my notes with emphasis on using separate SSIDs and fixed channels. Takes about 15 minutes if you already have the latest firmware installed.

OE

 

[L&LD]

@Nihilim, it always looks daunting when written out.

Even if this takes you one hour of your time, it seems that it will be worth it in the end.

 

[OzarkEdge]

@Nihilim, it always looks daunting when written out.

Even if this takes you one hour of your time, it seems that it will be worth it in the end.

True. It's actually straight forward... nearly a default configuration and without the missteps. It would look much worse if not restricted by the forum character limit!

OE

 

[Nihilim]

True. It's actually straight forward... nearly a default configuration and without the missteps. It would look much worse if not restricted by the forum character limit!

OE

Thanks for the help, will try the setup when I have a bit more time and patience Struggled for almost a week with these problems now.

I have another question, I have set it up with bridge mode at them moment.

Setup:
1 x RT-AC86U as the main router
1 x RT-AC86U as bridge mode with my computer and NAS etc
1 x RT-AC68U as bridge mode to some other peripherals

The setup seems to work fine, however 1 time last night and again just now the main router just shuts itself down completely. I can't start the router with the button on the back, I have to take the wall-plug out and put it in again, then the router restarts.

I will upload my log, it seems really odd, about 30 min before the router shuts of it reverts to an old date and does somethings for 30 min then it shuts down.

From timestamp:
Feb 17 20:58:54 wlceventd: WLCEVENTD wlceventd_proc_event(401): eth6: Disassoc 80:BE:05:183:4A, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
May 5 07:05:09 kernel: klogd started: BusyBox v1.24.1 (2019-11-09 05:26:25 CST)

 

[OzarkEdge]

Thanks for the help, will try the setup when I have a bit more time and patience Struggled for almost a week with these problems now.

I have another question, I have set it up with bridge mode at them moment.

Setup:
1 x RT-AC86U as the main router
1 x RT-AC86U as bridge mode with my computer and NAS etc
1 x RT-AC68U as bridge mode to some other peripherals

The setup seems to work fine, however 1 time last night and again just now the main router just shuts itself down completely. I can't start the router with the button on the back, I have to take the wall-plug out and put it in again, then the router restarts.

I will upload my log, it seems really odd, about 30 min before the router shuts of it reverts to an old date and does somethings for 30 min then it shuts down.

From timestamp:
Feb 17 20:58:54 wlceventd: WLCEVENTD wlceventd_proc_event(401): eth6: Disassoc 80:BE:05:183:4A, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
May 5 07:05:09 kernel: klogd started: BusyBox v1.24.1 (2019-11-09 05:26:25 CST)

The old date in the log is likely the OEM default date seen when the router reboots.... sounds like the router is rebooting and then shutting down. Not healthy.

My approach would be to re-install the router only, following all of the usual advice... firmware install, firmware webUI reset/restore with initialize, minimal config from scratch... and then use it to see how it behaves. If if seems solid after a period of reliable use, then add a piece of your network to it, one step at a time to give yourself time to evaluate each new configuration.

OE

 

[Nihilim]

The old date in the log is likely the OEM default date seen when the router reboots.... sounds like the router is rebooting and then shutting down. Not healthy.

My approach would be to re-install the router only, following all of the usual advice... firmware install, firmware webUI reset/restore with initialize, minimal config from scratch... and then use it to see how it behaves. If if seems solid after a period of reliable use, then add a piece of your network to it, one step at a time to give yourself time to evaluate each new configuration.

OE

Hello again,

I went and returned the AC86U as I thought something might be wrong with the router. The gave me a new one, installed it yesterday. Lasted a bit more than 24 hours until 20:05. The router shut it self down, could there really be something connected in the network that makes the router shutdown?

I will attach the full log as well. I will disconnect my two other routers that are set up as a media bridge and let it run for 2 days and see if it happens again.

Any other advice?

Feb 22 20:12:04 wlceventd: WLCEVENTD wlceventd_proc_event(430): eth6: ReAssoc 80:BE:05:183:4A, status: 0, reason: d11 RC reserved (0)
Feb 22 20:12:55 acsd: eth6: NONACSD channel switching to channel spec: 0xe03a (52/80)
Feb 22 20:20:35 wlceventd: WLCEVENTD wlceventd_proc_event(420): eth6: Auth 74:9E:AF:80:B9:86, status: 0, reason: d11 RC reserved (0)
Feb 22 20:20:35 wlceventd: WLCEVENTD wlceventd_proc_event(449): eth6: Assoc 74:9E:AF:80:B9:86, status: 0, reason: d11 RC reserved (0)
Feb 22 20:31:50 wlceventd: WLCEVENTD wlceventd_proc_event(401): eth6: Disassoc 80:BE:05:183:4A, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Feb 22 20:54:45 wlceventd: WLCEVENTD wlceventd_proc_event(420): eth6: Auth 44:8A:5B5:EC:AE, status: 0, reason: d11 RC reserved (0)
Feb 22 20:54:45 wlceventd: WLCEVENTD wlceventd_proc_event(449): eth6: Assoc 44:8A:5B5:EC:AE, status: 0, reason: d11 RC reserved (0)
Feb 22 19:57:57 miniupnpd[1333]: upnp_event_process_notify: connect(192.168.1.3:2869): Connection timed out
Feb 22 19:57:57 miniupnpd[1333]: upnp_event_process_notify: connect(192.168.1.3:2869): Connection timed out
Feb 22 20:05:02 miniupnpd[1333]: upnp_event_process_notify: connect(192.168.1.3:2869): Connection timed out
Feb 22 20:05:02 miniupnpd[1333]: upnp_event_process_notify: connect(192.168.1.3:2869): Connection timed out
Feb 22 20:05:10 miniupnpd[1333]: upnp_event_process_notify: connect(192.168.1.3:2869): Connection timed out
Feb 22 20:05:11 miniupnpd[1333]: upnp_event_process_notify: connect(192.168.1.3:2869): Connection timed out
May 5 07:05:09 kernel: klogd started: BusyBox v1.24.1 (2019-11-09 05:26:25 CST)
May 5 07:05:09 kernel: Linux version 4.1.27 (jenkins@asuswrt-build-server) (gcc version 5.3.0 (Buildroot 2016.02) ) #2 SMP PREEMPT Sat Nov 9 06:08:20 CST 2019
May 5 07:05:09 kernel: CPU: AArch64 Processor [420f1000] revision 0
May 5 07:05:09 kernel: Kernel command line: coherent_pool=1M cpuidle_sysfs_switch
May 5 07:05:09 kernel: Virtual kernel memory layout:
May 5 07:05:09 kernel: vmalloc : 0xffffff8000000000 - 0xffffffbdffff0000 ( 247 GB)
May 5 07:05:09 kernel: vmemmap : 0xffffffbe00000000 - 0xffffffbfc0000000 ( 7 GB maximum)

 

[Grisu]

yes such things may be possible, but as well it could be your power source having the router to reboot!

 

[Salles]

Do you need UPnP? Otherwise I would deactivate that and see what happens.