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

[K-2SO]

Only problem is that I can't find this 00:15:99:79:2C:07 device.

Samsung Electronics Co.

 

[semigator]

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

Interesting. I'm on AIMesh with RT-86u as main router and 3 RT-1900P as nodes. After Roaming Assistant crashed 36 times in an hour yesterday on this version, I disabled it. The consequence is I have some devices (usually IoT things) that like to hop around to different nodes even if they are right next to one. So now I have some joining and dropping relatively frequently. The advantage of roamast in my setup is it keeps them on the best node. The only thread I've been able to ever find about Roaming Assistant crashing was this one over on Merlin: https://www.snbforums.com/threads/b...ta-is-now-available.60037/page-10#post-526848 but it doesn't provide a solution. On previous new firmware versions I did a full wipe, but I did a dirty upgrade here because I assumed roamast would fail the same way. I may try a complete wipe at this level unless I see enough other issues (like what is listed above) for me to downgrade back to 45717 which has been rock solid.

 

[OzarkEdge]

Interesting. I'm on AIMesh with RT-86u as main router and 3 RT-1900P as nodes. After Roaming Assistant crashed 36 times in an hour yesterday on this version, I disabled it. The consequence is I have some devices (usually IoT things) that like to hop around to different nodes even if they are right next to one. So now I have some joining and dropping relatively frequently. The advantage of roamast in my setup is it keeps them on the best node. The only thread I've been able to ever find about Roaming Assistant crashing was this one over on Merlin: https://www.snbforums.com/threads/b...ta-is-now-available.60037/page-10#post-526848 but it doesn't provide a solution. On previous new firmware versions I did a full wipe, but I did a dirty upgrade here because I assumed roamast would fail the same way. I may try a complete wipe at this level unless I see enough other issues (like what is listed above) for me to downgrade back to 45717 which has been rock solid.

I suspect the issue is unique to your equipment. And if it's been around since forever, a clean install now won't make a difference. So, time to think outside the box.

I would use fixed channels. And I would suspect and shed some IoT clients to see if they are involved in 'crashing' the router/network.

What is the sq footprint area you are covering with 4 nodes?

OE

 

[semigator]

I suspect the issue is unique to your equipment. And if it's been around since forever, a clean install now won't make a difference. So, time to think outside the box.

I would use fixed channels. And I would suspect and shed some IoT clients to see if they are involved in 'crashing' the router/network.

What is the sq footprint area you are covering with 4 nodes?

OE

I use fixed channels and a single SSID across 2.4 and 5 Ghz for the main network. Another thing I've done for a while is use guest networks on the main router for the devices I don't want to roam. This works well for the ones that have quality signal, but not all of them do. My house has a lot of concrete and other material that blocks signal, which is the reason for the multiple nodes.

Again, roamast works perfectly at 45717. Something changed beyond that level.

 

[OzarkEdge]

My house has a lot of concrete and other material that blocks signal, which is the reason for the multiple nodes.

Again, roamast works perfectly at 45717. Something changed beyond that level.

After 45717, RA 2.4/5.0 defaults changed from -55/-70 to -70/-70 dBm.

OE

 

[scajjr2]

Been running 81858 all week ( dirty update from 81792 which I had no issues with) and no issues at all on either 86U (router, access point).

Sam

 

[semigator]

After 45717, RA 2.4/5.0 defaults changed from -55/-70 to -70/-70 dBm.

OE

I have always used custom RA settings that work in my environment -73/-77. I also used Roaming Block List for clients that did better roaming on their own - that list grew over time. I think what I'm going to do is stay at this firmware for a bit, leave RA off, and see if I get stable.

 

[KevTech]

Even clicking on the online status icon leads to a total crash within Google Chrome for the display at times.

Perhaps this is a chrome issue.

I use Firefox and the GUI is just as fast as ever and never crashes.

 

[tallytr]

I use fixed channels and a single SSID across 2.4 and 5 Ghz for the main network. Another thing I've done for a while is use guest networks on the main router for the devices I don't want to roam. This works well for the ones that have quality signal, but not all of them do. My house has a lot of concrete and other material that blocks signal, which is the reason for the multiple nodes.

Again, roamast works perfectly at 45717. Something changed beyond that level.

I use smart connect with one SSID but also > Wireless - Wireless MAC Filter.
I set a couple notebooks 5GHz so they will be rejected on 2.4GHz, pretty good feature.

 

[semigator]

I use smart connect with one SSID but also > Wireless - Wireless MAC Filter.
I set a couple notebooks 5GHz so they will be rejected on 2.4GHz, pretty good feature.

Thanks - I hadn't thought of using the Wireless MAC Filter that way. One of my cameras is dual band and it likes to pick 5 GHz, but I want to force it 2.4, so I will be using this.

 

[tallytr]

Thanks - I hadn't thought of using the Wireless MAC Filter that way. One of my cameras is dual band and it likes to pick 5 GHz, but I want to force it 2.4, so I will be using this.

I use it with my Apple TV, usually connects to 2.4GHz after a router reboot but now sticking to much faster 5Ghz...

 

[Neil62]

Perhaps this is a chrome issue.

I use Firefox and the GUI is just as fast as ever and never crashes.

ON trying Firefox (latest Version), I have this issue appearing randomly on applying client changes, in this case a client name and standard icon to standard icon:

 

[OzarkEdge]

ON trying Firefox (latest Version), I have this issue appearing randomly on applying client changes

Seems odd that the issue is random.

I'm not seeing that here using the new Microsoft Edge based on Chromium... Chrome built-in and without Google.

This firmware, like 81792, is working fine for me (same SSIDs, fixed channels, Auto wireless mode). Memory consumption has not budged. Wireless backhauls are very good considering the distance and path (not much congestion here):

2.4 Yes Yes -60dBm ac No Yes Yes Yes 3 234M 216.7M
5.0 Yes Yes -70dBm ac No Yes Yes Yes 4 975M 780M

2.4 TuneIn test while circling the AiMesh at distance on a riding mower for hours was flawless (ear buds under ear muffs).

Time for a mike drop and to look forward to the next ordeal... tri-band WiFi6e AiMesh.

OE

 

[podkaracz]

What is the risk of using 45717 in 2020 security wise?

 

[K-2SO]

What is the risk of using 45717 in 2020 security wise?

As per changelog, someone may DDoS or Kr00k you.

 

[podkaracz]

As per changelog, someone may DDoS or Kr00k you.

Yea im using latest firmware since many months but the more i read how 45717 stable is i would like to back to it since i used it and remember it was the only firmware with decent performance.

 

[OzarkEdge]

Yea im using latest firmware since many months but the more i read how 45717 stable is i would like to back to it since i used it and remember it was the only firmware with decent performance.

My impression is that there is one user here who posts their faith in 45717.

OE

 

[K-2SO]

My impression is that there is one user here who posts their faith in 45717.

I remember two.

 

[Smedley]

I remember two.

I'll make it three!

 

[K-2SO]

I'll make it three!

No. One of the others upgraded.