Recent content by lala_cai

Forgot to mention that I was coming from 388.2 The blink sync module was connected via 2.4GHz without any issues. The strange part is the sync module can connect to my mesh node RT-AC86U without any issues as well. I assume the mesh node have the same wifi settings inherit from the RT-AX86S...

Just if anyone have this issue. I have RT-AX86S running on 388.6_2. I have a old Blink sync module unable to connect to 2.4GHz at all. There is no association logs at all. When I turn on my RT-AC86U (386.7_2) as mesh node, the Blink sync module automatically connects without any issues. The...

Which firmware are you currently in now? I’m facing this issue with the newer firmwares which started from 384.18.

Normally I’ll just fixed to channel 1 after the initial reset. Will try to fixed it to other channel and see if this is still happening.

Nope, it will not work again as I have camera which reports to the cloud which will notify me it has been disconnected for 30 minutes. On the 384.19, it will still happen once maybe in weeks but not as frequent as 386 (in days).

Hi, I'm not talking about the debugging code. I'm facing an issue whereby 2.4GHz disconnect all the clients and no longer allow connection even though I can see the SSID I attached the logs to see if there are better ways to troubleshoot the issue. thanks

I'm facing a problem with RT-AC86U where the devices is unable to connect to 2.4GHz after a certain time (from days to weeks). I can see the SSID but it just refused to connect. I have no problem with 5GHz. This issues seems to begin from 384.18 onwards and now I'm on 386.1_2 and it's still...

Hi @ColinTaylor , Yes, that was the problem. Thanks again. I changed it to use all google DNS now instead. I'm not sure why the 1.1.1.1 is not resolving accordingly

Hi, My setup is as follows - Rt-ac86u with 384.12 - Initiated reset with Initialize. - configured only stock WAN, wifi, DDNS and swap memory. - no DNSFilter, no AiProtection Encounter some very strange problem. I start noticing some sites some images not loading accordingly. I did some...

Require some help. Here is the procedure which I have done when flash to Merlin 384.8_2. - Flash to 384.8_2 from stock asus firmware 3.0.0.4.384.32799 - did Initialize on the 86u and reconfigure from scratch for all configurations. - configuration done was only wireless, IPTV, enable...

A quick check, just flashed my ac86u to 384.8_2. I did an initialize after flashing and configured from scratch. All seems working well but I’m getting a lot of this error from time to time. Dec 17 23:51:52 kernel: protocol 0800 is buggy, dev eth5 Dec 17 23:51:58 kernel: protocol 0800 is...

So far using the stock Asus 3.0.0.4.384.21140 firmware and having 21 days uptime. Same HW ver 1.5 and 2018 production. I'll wait for the merlin 384.7 stable release before trying to flash again.

I did not have this issue when I was on 384.4_2 with more than 2 months uptime. No new devices have been added to the network so far. The memory utilization on the 86u have always been 90+% without any issues. The issue only started when I flash to 384.6. And the same, I can't see any error...

I have updated from 384.4_2 to 384.6 and I started experiencing random reboots from matter of hours to days. Tried to downgrade back but the issue seems to persist. The logs doesn’t show anything other than booting up. Anybody managed to solve the issue?

I upgrade from 384.4_2 to 384.6 faced the same problem of random reboot issue for 86U I tried downgrading back to 384.4_2 and the issue still persist. Did the initialize every time after flashing the firmware still have the random reboot issue. Any advise on what item i can check also? Now i try...