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

[cco12]

After run Version 3.0.0.4.384.81858 for 2-3 days,
1.Have big ping problems on WIFI 2.4G that increase to 1000ms to 3000ms that can't use internet.

-So i go back to Version 3.0.0.4.384.45713 and wifi 2.4G normal stable

 

[OzarkEdge]

i've never used sc. would you help me understand:

1. why you limit the 2.4 g radio to 20 and the 5g to 80 instead of the defaults?
   
2. is 153 a non dfs channel?
   
3. in general, why one should use sc?

been running fine without it disabled but if it helps , i'll adjust.
thanks

1. The 2.4 signal travels off-site and can interfere with off-site signals. Limiting the bandwidth to 20 MHz is a courtesy to others to limit radio frequency spectrum usage to share the spectrum with others. Reducing the bandwidth reduces the data capacity in time (speed) but that's ok... I have enough speed for my 2.4 clients.

If there is no other 2.4 WiFi around you, max out your bandwidth for the most throughput.

I force 5.0 to max bandwidth of 80 MHz to keep it there no matter what.

Knowing how your clients are connected can help you to interpret their behaviors with less variables in play and with more certainty.

2. My router Wireless Log lists these 5.o GHz channels:
Channel 36 A Band
Channel 40 A Band
Channel 44 A Band
Channel 48 A Band
Channel 52 A Band, RADAR Sensitive, Passive
Channel 56 A Band, RADAR Sensitive, Passive
Channel 60 A Band, RADAR Sensitive, Passive
Channel 64 A Band, RADAR Sensitive, Passive
Channel 100 A Band, RADAR Sensitive, Passive
Channel 104 A Band, RADAR Sensitive, Passive
Channel 108 A Band, RADAR Sensitive, Passive
Channel 112 A Band, RADAR Sensitive, Passive
Channel 116 A Band, RADAR Sensitive, Passive
Channel 132 A Band, RADAR Sensitive, Passive
Channel 136 A Band, RADAR Sensitive, Passive
Channel 140 A Band, RADAR Sensitive, Passive
Channel 149 A Band
Channel 153 A Band
Channel 157 A Band
Channel 161 A Band
Channel 165 A Band

I believe DFS allows WiFi to use radar channels 52 to 140. So, 153 could be considered a non-DFS channel.

If you use a radar sensitive channel, and DFS senses radar and decides to change channels, your clients my notice.

3. Smart Connect encourages a wireless client to connect to the better band/SSID when both bands advertise identical SSIDs. You would use SC if you want to use same SSIDs, configure your client for only one connection/SSID, and have that connection 'magically' connect to the best band/signal/SSID for various roaming locations/distances. Plus, configuring for and broadcasting only one SSID name is more sexy, if it works, and if you don't need to segregate clients to a particular band/WLAN.

OE

 

[tallytr]

I leave 5GHz to Auto myself and not just 80, works well...

 

[bbunge]

i've never used sc. would you help me understand:

1. why you limit the 2.4 g radio to 20 and the 5g to 80 instead of the defaults?
   
2. is 153 a non dfs channel?
   
3. in general, why one should use sc?

been running fine without it disabled but if it helps , i'll adjust. btw, i use different ssids for each radio. perhaps that's why it would not be useful for me.
thanks

1. Limit 2.4 to 20 Mhz because 40 Mhz spreads across too many channels and causes interference. Also use channel 1, 6 or 11 depending on neighborhood wifi congestion.
2. Non DFS ch 36-48, 149-161
3. I was not sold on SmaartConnect until the early April release for the AC86U. That release was pulled back for some reason but several of us kept using it anyway. I found that with the dual band SmartConnect enabled with the same SSID for both bands that my clients seemed to be happy. By that I mean they performed very well. My Roku sometimes ends up on the 2.4 band but still streams online content and from my NAS with no buffering. OK, so I don't give a hoot about ping. But my wife, daughter and myself can stream video at the same time no problem. I have also worked outside with the iPod and have maintained streaming 200 ft from the house!
It would be great if DoT were built into Asus like Merlin and John's Fork but there are other ways to enable DNS security.

 

[128bit]

1. Limit 2.4 to 20 Mhz because 40 Mhz spreads across too many channels and causes interference. Also use channel 1, 6 or 11 depending on neighborhood wifi congestion.
2. Non DFS ch 36-48, 149-161
3. I was not sold on SmaartConnect until the early April release for the AC86U. That release was pulled back for some reason but several of us kept using it anyway. I found that with the dual band SmartConnect enabled with the same SSID for both bands that my clients seemed to be happy. By that I mean they performed very well. My Roku sometimes ends up on the 2.4 band but still streams online content and from my NAS with no buffering. OK, so I don't give a hoot about ping. But my wife, daughter and myself can stream video at the same time no problem. I have also worked outside with the iPod and have maintained streaming 200 ft from the house!
It would be great if DoT were built into Asus like Merlin and John's Fork but there are other ways to enable DNS security.

much appreciated. i too could care less about a ping. we have several tv's and at least 2 are always streaming. my only issue is wiht a lacrosse weather device that constantly gets wlcevents. i just put up with it and am happy with the overall phenomenal performance of the 86u!
is there any advantage to using 1 ssid for both frequencies? if not, i may stay the course since 81858 is so stable?
i've also read read that disabling samba is helpful. may try that later but i thought it was necessary to "see" my network shares on networked 'puters. i'll play with that later.

thanks

 

[tallytr]

1. Limit 2.4 to 20 Mhz because 40 Mhz spreads across too many channels and causes interference. Also use channel 1, 6 or 11 depending on neighborhood wifi congestion.
2. Non DFS ch 36-48, 149-161
3. I was not sold on SmaartConnect until the early April release for the AC86U. That release was pulled back for some reason but several of us kept using it anyway. I found that with the dual band SmartConnect enabled with the same SSID for both bands that my clients seemed to be happy. By that I mean they performed very well. My Roku sometimes ends up on the 2.4 band but still streams online content and from my NAS with no buffering. OK, so I don't give a hoot about ping. But my wife, daughter and myself can stream video at the same time no problem. I have also worked outside with the iPod and have maintained streaming 200 ft from the house!
It would be great if DoT were built into Asus like Merlin and John's Fork but there are other ways to enable DNS security.

Your Roku: Did you consider Wireless - Wireless MAC Filter so it gets rejected on 2.4GHz? Took me a while but I put my stationary clients and some where I know 5GHz works best (Apple TV, Amazon Echo, notebooks) on the reject list and this works really well...

 

[bbunge]

Your Roku: Did you consider Wireless - Wireless MAC Filter so it gets rejected on 2.4GHz? Took me a while but I put my stationary clients and some where I know 5GHz works best (Apple TV, Amazon Echo, notebooks) on the reject list and this works really well...

Tried the wireless MAC filter and it worked. But the way I have it now the Roku and Dish boxes all have switched to the 5 GHZ. I don't use static IP's. Let the DHCP server assign addresses to all devices but do have several (printer, NAS, Cam server) on Manual Assignment in the LAN - DHCP Server area. As I've said before, my goal is to make this as simple as possible if, for some reason, something happens to me. Old guys need to be careful these days... Tonight is bad as I had an eye exam this afternoon and things are still blurry. Can't wait for the cataract surgery!
Getting old is not for the faint of heart...

 

[tallytr]

Tried the wireless MAC filter and it worked. But the way I have it now the Roku and Dish boxes all have switched to the 5 GHZ. I don't use static IP's. Let the DHCP server assign addresses to all devices but do have several (printer, NAS, Cam server) on Manual Assignment in the LAN - DHCP Server area. As I've said before, my goal is to make this as simple as possible if, for some reason, something happens to me. Old guys need to be careful these days... Tonight is bad as I had an eye exam this afternoon and things are still blurry. Can't wait for the cataract surgery!
Getting old is not for the faint of heart...

What works best for me with printers for example, I set them to DHCP first, then in the router Network Map > Clients > Client Status, I click on the client, printer for example and simply bind MAC to IP Address, that way the IP never changes and the configuration
is manual so basically static, then I set the TCP/IP Boot method to Static in the printer menu so when the printer re-boots its still the same IP...

 

[OzarkEdge]

What works best for me with printers for example, I set them to DHCP first, then in the router Network Map > Clients > Client Status, I click on the client, printer for example and simply bind MAC to IP Address, that way the IP never changes and the configuration
is manual so basically static, then I set the TCP/IP Boot method to Static in the printer menu so when the printer re-boots its still the same IP...

If the printer permits it, set a static IP on the printer... I use 192.168.1.2... and then install the printer driver. This will stick when the router configuration doesn't. And enable network discovery on Windows, of course.

OE

 

[podkaracz]

I tested a lot and in my case mostly my internet is utterly bad because its jumping most of the time so its not that much of a router fault . The setup process of this router is really messy and without "nuclear resets" often is not working at intended but in my case internet plays the biggest bad part not the router.

 

[OzarkEdge]

I tested a lot and in my case mostly my internet is utterly bad because its jumping most of the time so its not that much of a router fault . The setup process of this router is really messy and without "nuclear resets" often is not working at intended but in my case internet plays the biggest bad part not the router.

The WAN equipment/service being unstable makes more sense.

I've never done a 'nuclear reset'. A simple reset w/initialization always works for me, if required by a significant change in firmware code/features... or by firmware-in-development like AiMesh has been. AiMesh has been a different experience, but it's been worth it for me and provides a viable path forward, imo.

OE

 

[ryan806]

Is it worth upgrading from 45717?

 

[OzarkEdge]

Is it worth upgrading from 45717?

It could make you more manly.

OE

 

[bbunge]

Is it worth upgrading from 45717?

In a word, YES! Might not change you but your network will be happy. I also recommend trying the Dual Band Smart Connect with fixed channels. Also may be best to do a factory reset and reconfigure although my upgrade has worked well.

 

[ryan806]

In a word, YES! Might not change you but your network will be happy. I also recommend trying the Dual Band Smart Connect with fixed channels. Also may be best to do a factory reset and reconfigure although my upgrade has worked well.

Yeah I've done that working well so far cheers

 

[OzarkEdge]

Might not change you but your network will be happy.

A happy network changed you!

OE

 

[bbunge]

Yeah I've done that working well so far cheers

By my count that is three happy campers today with AC86U and 384_81858! Whoopee!!!

 

[DarkKnight75]

Going on 20+ days, so rock solid release coming from 45717.

 

[DarkKnight75]

Just got notification via router GUI, new firmware 81918 is out..who's going to beta test it, lol

 

[SeeSawSam]

Just got notification via router GUI, new firmware 81918 is out..who's going to beta test it, lol

Anyone see actual release notes? Mine never load. Just says "Loading release notes, please wait..." and thats what I"m doing... waiting.