ASUS RT-AC86U - 4th May - New Firmware version 3.0.0.4.384_81858 (04.05.2020)

[Lutek]

The WiFi analyzer gives ambiguous results so I am looking for a more practical mechanism because there are several dozen Wlan access points around my estate that reach my apartment. In this localization there are complicated conditions in the 2.4Ghz band.

 

[OzarkEdge]

The WiFi analyzer gives ambiguous results so I am looking for a more practical mechanism because there are several dozen Wlan access points around my estate that reach my apartment.

Works for me.

Feel free to move your router and let it respond, and let us know how that works for you.

What is the dBm level of your WiFi signal on the balcony? Maybe it's not strong enough to compete with surrounding signals.

OE

 

[tallytr]

Works for me.

Feel free to move your router and let it respond, and let us know how that works for you.

What is the dBm level of your WiFi signal on the balcony? Maybe it's not strong enough to compete with surrounding signals.

OE

I had big success with moving the router to the top floor, basement is the worst, move it to central location for good coverage....

 

[DarkKnight75]

I'll will wait for it to mature and then i may upgrade (beast quad-core 1.8 with 1gb ram)
https://www.asus.com/Networking/RT-AX86U/

 

[Lutek]

I'll will wait for it to mature and then i may upgrade (beast quad-core 1.8 with 1gb ram)
https://www.asus.com/Networking/RT-AX86U/

But it isn't the same as AC86U !

 

[DarkKnight75]

But it isn't the same as AC86U !

Some features, but a bump in hardware specs (check out the specs)...will have to wait to insure no major issues with it as it was just released.

 

[Lutek]

I just wanted to warn you that the firmware probably doesn't fit and you should be careful not to damage the router.

 

[DarkKnight75]

I just wanted to warn you that the firmware probably doesn't fit and you should be careful not to damage the router.

Of course it wont work, they are diff routers..

 

[K-2SO]

This is something new:

 

[bitsbytes]

I'll will wait for it to mature and then i may upgrade (beast quad-core 1.8 with 1gb ram)
https://www.asus.com/Networking/RT-AX86U/

the only wifi 6 capable device i have right now is my galaxy S10 plus and looking forward it looks like it'll be the only one for at least another year.

 

[DarkKnight75]

This is something new:

View attachment 23310

I had this appear 2 days ago and disappeared today after i rebooted to do some final tests before letting my unit settle..

 

[OzarkEdge]

Of course it wont work, they are diff routers..

So, be sure not to install this firmware on it!

OE

 

[semigator]

I have been stuck on 45717 for a long time. I installed this version today and it seems pretty stable, but one of the reasons I stayed at 45717 was roamast crashes on any version newer. I just saw it crash on this version - anyone else having this issue?

May  7 20:10:39 roamast: determine candidate node [70:8B:CD:xx:xx:xx](rssi: -56dbm) for client [B4:AE:2B:xx:xx:xx](rssi: -79dbm) to roam
May  7 20:10:39 kernel: pgd = ffffffc011ff2000
May  7 20:10:39 kernel: [00000000] *pgd=0000000011f88003, *pud=0000000011f88003, *pmd=0000000011058003, *pte=0000000000000000
May  7 20:10:39 kernel: CPU: 1 PID: 9625 Comm: roamast Tainted: P           O    4.1.27 #2
May  7 20:10:39 kernel: Hardware name: Broadcom-v8A (DT)
May  7 20:10:39 kernel: task: ffffffc017379480 ti: ffffffc014de0000 task.ti: ffffffc014de0000
May  7 20:10:39 kernel: PC is at 0x100420
May  7 20:10:39 kernel: LR is at 0xf6b687d4
May  7 20:10:39 kernel: pc : [<0000000000100420>] lr : [<00000000f6b687d4>] pstate: 60070010
May  7 20:10:39 kernel: sp : 00000000f6b36308
May  7 20:10:39 kernel: x12: 00000000f6c73c40
May  7 20:10:39 kernel: x11: 0000000000000000 x10: 0000000000000001
May  7 20:10:39 kernel: x9 : 000000000015b88c x8 : 0000000000000000
May  7 20:10:39 kernel: x7 : 0000000000000001 x6 : 00000000f71f8ce0
May  7 20:10:39 kernel: x5 : 00000000f6b36380 x4 : 00000000f6b3633c
May  7 20:10:39 kernel: x3 : 0000000000000000 x2 : 0000000000000001
May  7 20:10:39 kernel: x1 : 0000000000000020 x0 : 0000000000000000

 

[DarkKnight75]

I have been stuck on 45717 for a long time. I installed this version today and it seems pretty stable, but one of the reasons I stayed at 45717 was roamast crashes on any version newer. I just saw it crash on this version - anyone else having this issue?

May  7 20:10:39 roamast: determine candidate node [70:8B:CD:xx:xx:xx](rssi: -56dbm) for client [B4:AE:2B:xx:xx:xx](rssi: -79dbm) to roam
May  7 20:10:39 kernel: pgd = ffffffc011ff2000
May  7 20:10:39 kernel: [00000000] *pgd=0000000011f88003, *pud=0000000011f88003, *pmd=0000000011058003, *pte=0000000000000000
May  7 20:10:39 kernel: CPU: 1 PID: 9625 Comm: roamast Tainted: P           O    4.1.27 #2
May  7 20:10:39 kernel: Hardware name: Broadcom-v8A (DT)
May  7 20:10:39 kernel: task: ffffffc017379480 ti: ffffffc014de0000 task.ti: ffffffc014de0000
May  7 20:10:39 kernel: PC is at 0x100420
May  7 20:10:39 kernel: LR is at 0xf6b687d4
May  7 20:10:39 kernel: pc : [<0000000000100420>] lr : [<00000000f6b687d4>] pstate: 60070010
May  7 20:10:39 kernel: sp : 00000000f6b36308
May  7 20:10:39 kernel: x12: 00000000f6c73c40
May  7 20:10:39 kernel: x11: 0000000000000000 x10: 0000000000000001
May  7 20:10:39 kernel: x9 : 000000000015b88c x8 : 0000000000000000
May  7 20:10:39 kernel: x7 : 0000000000000001 x6 : 00000000f71f8ce0
May  7 20:10:39 kernel: x5 : 00000000f6b36380 x4 : 00000000f6b3633c
May  7 20:10:39 kernel: x3 : 0000000000000000 x2 : 0000000000000001
May  7 20:10:39 kernel: x1 : 0000000000000020 x0 : 0000000000000000

Im not..mine is error free so far.

 

[Neil62]

This is something new:

View attachment 23310

I have also had that screen appear on more than one occasion. I am using google chrome latest version. Closing the tab down and opening a new login again and it gone. And just as I am typing this the auto logout kicks in and this...

 

[OzarkEdge]

I have been stuck on 45717 for a long time. I installed this version today and it seems pretty stable, but one of the reasons I stayed at 45717 was roamast crashes on any version newer. I just saw it crash on this version - anyone else having this issue?

May  7 20:10:39 roamast: determine candidate node [70:8B:CD:xx:xx:xx](rssi: -56dbm) for client [B4:AE:2B:xx:xx:xx](rssi: -79dbm) to roam
May  7 20:10:39 kernel: pgd = ffffffc011ff2000
May  7 20:10:39 kernel: [00000000] *pgd=0000000011f88003, *pud=0000000011f88003, *pmd=0000000011058003, *pte=0000000000000000
May  7 20:10:39 kernel: CPU: 1 PID: 9625 Comm: roamast Tainted: P           O    4.1.27 #2
May  7 20:10:39 kernel: Hardware name: Broadcom-v8A (DT)
May  7 20:10:39 kernel: task: ffffffc017379480 ti: ffffffc014de0000 task.ti: ffffffc014de0000
May  7 20:10:39 kernel: PC is at 0x100420
May  7 20:10:39 kernel: LR is at 0xf6b687d4
May  7 20:10:39 kernel: pc : [<0000000000100420>] lr : [<00000000f6b687d4>] pstate: 60070010
May  7 20:10:39 kernel: sp : 00000000f6b36308
May  7 20:10:39 kernel: x12: 00000000f6c73c40
May  7 20:10:39 kernel: x11: 0000000000000000 x10: 0000000000000001
May  7 20:10:39 kernel: x9 : 000000000015b88c x8 : 0000000000000000
May  7 20:10:39 kernel: x7 : 0000000000000001 x6 : 00000000f71f8ce0
May  7 20:10:39 kernel: x5 : 00000000f6b36380 x4 : 00000000f6b3633c
May  7 20:10:39 kernel: x3 : 0000000000000000 x2 : 0000000000000001
May  7 20:10:39 kernel: x1 : 0000000000000020 x0 : 0000000000000000

Never. And I've endured AiMesh firmware since 3/2018:
o 3.0.0.4.384.21140 ok
x 32797,9 remote node client connection/speed degrades
x 45149 Trend Micro crashes
o 45713,7 ok, excessive Auto ch scanning, TM consumes memory
x 81039 excessive Auto ch scanning, webUI lock up, erratic CPU, new RA defaults, PULLED
o 81049 ok, excessive Auto ch scanning
o 81351,2 ok
o 81369 ok
o 81792 ok, SC allows fixed channels! PULLED
o 81858 ok

OE

 

[Andy1932]

I get the occasional pgd crash. Nothing to worry about.

 

[KevTech]

I have been stuck on 45717 for a long time. I installed this version today and it seems pretty stable, but one of the reasons I stayed at 45717 was roamast crashes on any version newer.

That stands for roaming assistant (roamast).

Have you tried disabling it?

 

[rwijnhov]

I am getting these:
proc_event(510): eth5: ReAssoc 00:15:99:79:2C:07, status: Successful (0)
May 8 08:52:35 wlceventd: WLCEVENTD wlceventd_proc_event(466): eth5: Deauth_ind 00:15:99:79:2C:07, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
May 8 08:52:36 wlceventd: WLCEVENTD wlceventd_proc_event(500): eth5: Auth 00:15:99:79:2C:07, status: Successful (0)
May 8 08:52:36 wlceventd: WLCEVENTD wlceventd_proc_event(510): eth5: ReAssoc 00:15:99:79:2C:07, status: Successful (0)
May 8 08:52:36 wlceventd: WLCEVENTD wlceventd_proc_event(466): eth5: Deauth_ind 00:15:99:79:2C:07, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
May 8 08:52:40 wlceventd: WLCEVENTD wlceventd_proc_event(466): eth5: Deauth_ind 00:15:99:79:2C:07, status: 0, reason: Class 3 frame received from nonassociated station (7)
May 8 08:52:40 wlceventd: WLCEVENTD wlceventd_proc_event(466): eth5: Deauth_ind 00:15:99:79:2C:07, status: 0, reason: Class 3 frame received from nonassociated station (7)
May 8 08:52:40 wlceventd: WLCEVENTD wlceventd_proc_event(500): eth5: Auth 00:15:99:79:2C:07, status: Successful (0)
May 8 08:52:40 wlceventd: WLCEVENTD wlceventd_proc_event(510): eth5: ReAssoc 00:15:99:79:2C:07, status: Successful (0)
May 8 08:52:40 wlceventd: WLCEVENTD wlceventd_proc_event(466): eth5: Deauth_ind 00:15:99:79:2C:07, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)

Only problem is that I can't find this 00:15:99:79:2C:07 device. It doesn't show up in the wireless list and it doesnt show up in my dhcp list in my pfsense router. How do I found out what device is causing this?

And in my wireless log this device also show as not associated
Stations List
----------------------------------------
idx MAC Associated Authorized RSSI PHY PSM SGI STBC MUBF NSS Tx rate Rx rate Connect Time
00:15:99:79:2C:07 Yes -76dBm n No Yes No No 1 1M 00:00:00

I have my mesh setup with ethernet not wireless.

I just dropped the mesh and still the same log items so it's not the mesh setup.

 

[Neil62]

The GUI in this version is a little sick. From my perspective at least, it seems less responsive from the previous version. Even clicking on the online status icon leads to a total crash within Google Chrome for the display at times. I constantly get this problem with the client list, see image. Running latest chrome. Logging out and back into the router resolves the problem. See my post#95 for another problem occuring on an ad hoc basis. WIFI and AiMesh stability, no worse and no better from last firmware release before it was pulled.