Beta Asuswrt-Merlin 388.1 Beta is available for select models

[Tech9]

But it's outrageous that with 388.x it drops from 2.4Gbps to 1.6Gbps in a glimpse.

1.6Mbps must be still 160MHz wide channel. 1.2Mbps link is the max for 80MHz wide and 2-stream client.

 

[capncybo]

1.6Mbps must be still 160MHz wide channel. 1.2Mbps link is the max for 80MHz wide and 2-stream client.

That's what I was thinking so... @jeton7608 under the Wireless=>Professional section... do you have an entry where you could:
Extended NSS=enable
Perhaps some of the high end phones REQUIRE it ???
My limited understanding is that on the more recent firmware... The 160MHz will switch-off when there is no-longer a suitable client connected.

 

[jeton7608]

I certainly wasn't trying to disagree with your observations... but just to clarify... are you achieving those speeds without enabling 160MHz?

No, that's with AX Only and 160Mhz in channel 36.

 

[jeton7608]

That's what I was thinking so... @jeton7608 under the Wireless=>Professional section... do you have an entry where you could:
Extended NSS=enable
Perhaps some of the high end phones REQUIRE it ???
My limited understanding is that on the more recent firmware... The 160MHz will switch-off when there is no-longer a suitable client connected.

As you can see... no Extended NSS option in Merlin's firmware.

 

[capncybo]

As you can see... no Extended NSS option in Merlin's firmware.

I'm just brainstorming so... thanks for looking.
I had thought maybe the "Extended NSS" option would appear AFTER enabling 160MHz & disappear when 160MHz was turned off.
But perhaps it's a router specific setting.
Anyone know if "Extended NSS" (Under Wireless =>Professional) still exists within latest STOCK firmware ???
Perhaps it's been depreciated or replaced.
But I did read (within the ASUS FAQ) that it was ONCE required for certain hardware.

 

[ColinTaylor]

@capncybo See here: https://www.snbforums.com/threads/r...9260-wifi-in-laptops-160mhz.76909/post-739107

 

[capncybo]

@capncybo See here: https://www.snbforums.com/threads/r...9260-wifi-in-laptops-160mhz.76909/post-739107

Thanks again @ColinTaylor
-I don't know how you keep all this information straight in your head... Data keeps leaking out of mine

 

[ColinTaylor]

-I don't know how you keep all this information straight in your head...

I don't, I've got a memory like a sieve. I use the Better Search function.

 

[skeal]

View attachment 45893

View attachment 45892

As you can see... no Extended NSS option in Merlin's firmware.

I have 160Mhz enabled and channel set to auto. This has been very stable and not far from default settings. To be honest you should just enable 160Mhz and with using n/ac/ax mixed and 20/40/80/160 bandwidth. Don't even set a channel and test to see if the same issue is present. Our settings on the professional tab differ quite a bit also. I'm just saying that the more basic you keep things the more connection time you log.

 

[JGrana]

I don't, I've got a memory like a sieve. I use the Better Search function.

I would say you more have "sage wisdom" ;-)

 

[skeal]

View attachment 45893

View attachment 45892

As you can see... no Extended NSS option in Merlin's firmware.

I thought I would try one of your settings on the 5G proffesional page. My system is otherwise stable at this point using 160Mhz and Auto Channel. The setting I tried is below.

Mine was set to this the default

Right after I applied settings it disabled 160Mhz without it being disabled in the interface. My channel went to 44 from auto channel. No device would connect at 160Mhz. So basically it screwed my 5G 160Mhz settings. I had to disable 160Mhz and reboot to get the router back where it was before. That seems to be a problematic setting.

 

[New2This]

My system is also very stable running same as above with + MU-MIMO enabled with channel set to auto, running channel 60 atm, with the pixel running Graphene OS with NO issues and connecting @ 160Mhz

 

[jeton7608]

I thought I would try one of your settings on the 5G proffesional page. My system is otherwise stable at this point using 160Mhz and Auto Channel. The setting I tried is below.
View attachment 45901
Mine was set to this the default
View attachment 45902
Right after I applied settings it disabled 160Mhz without it being disabled in the interface. My channel went to 44 from auto channel. No device would connect at 160Mhz. So basically it screwed my 5G 160Mhz settings. I had to disable 160Mhz and reboot to get the router back where it was before. That seems to be a problematic setting.

I won't dispute your settings. That configuration works and it's stable even with a fixed 36 channel. All AX devices connect at 2.4Gbps or 1.2Gbps initially.

In my opinion, if you leave settings to Auto, the system may change channels or frequencies when it's not necessary and it's better to force it.

My ISP is 1Gbps with static IP and Fullcone.

 

[Morris]

That was a very simple (but fair) point... So in trying to help others I looked within the GUI for the support Links & noticed the FAQ in the footer.
Curiously I typed in... 160MHz which led me to... How to ensure compatibility of 160MHz and device with RT-AX89X
(Perhaps the info is outdated & definitely not all routers are the same)
But it pointed out something I had never paid much attention to... It suggested having to enable:
Extended NSS=enable
(Hmmmmmm... It can't be something that simple, could it?)

What is extended NSS?

Extended NSS: Enable this option to allow devices that support NSS to maintain stable connection when the channel width is 160 MHz or 80 + 80 MHz. 802.11r: Enable this option for fast roaming between different Wi-Fi points.

 

[raven-au]

Cosmetic problem.
On my GT-AX6000, on the WAN page assigning DNS addresses I see two Clean Browsing options , one for the Family filter and one for the Adult filter.
If I select the Adult filter the resulting WAN page shows it as "Filter Mode: Family" when it should be "Filter Mode: Adult".

 

[skeal]

In my opinion, if you leave settings to Auto, the system may change channels or frequencies when it's not necessary and it's better to force it.

We'll agree to disagree here, I don't see it the same way. Your opinion is not based on facts. The system makes an adjustment because there is a need to, not for any other reason.

 

[skeal]

Cosmetic problem.
On my GT-AX6000, on the WAN page assigning DNS addresses I see two Clean Browsing options , one for the Family filter and one for the Adult filter.
If I select the Adult filter the resulting WAN page shows it as "Filter Mode: Family" when it should be "Filter Mode: Adult".

RMerlin only supports the DNS over TLS not the individual DNS providers include within. You need to talk to the Clean Browsing team themselves.

 

[Ripshod]

I have to agree with @skeal. For a long while I was forcing just the 160MHz option thinking that was the only way to get it to even operate that bandwidth. But, with reading these forums I've learned to just leave it on automatic and once PRE-ISM is done I'm given a 160MHz channel that will drop back to 80MHz if it's not actually needed. So when I'm not using the laptop it'll drop back to 80MHz for my phone etc, but as soon as my laptop connects the channel seamlessly changes to 160MHz. That is what I believe to be the way it should work, and indeed the way it actually does.
Don't force 160. There's a reason your radio isn't enabling it.

 

[Damit1]

So, IPv6 with DDNS works good, it seems my shirtty ISP has crappy bandwidth over v6. WIll just cancel it for time being... stick to what works

 

[jeton7608]

I have to agree with @skeal. For a long while I was forcing just the 160MHz option thinking that was the only way to get it to even operate that bandwidth. But, with reading these forums I've learned to just leave it on automatic and once PRE-ISM is done I'm given a 160MHz channel that will drop back to 80MHz if it's not actually needed. So when I'm not using the laptop it'll drop back to 80MHz for my phone etc, but as soon as my laptop connects the channel seamlessly changes to 160MHz. That is what I believe to be the way it should work, and indeed the way it actually does.
Don't force 160. There's a reason your radio isn't enabling it.

I also agree to disagree with you but that may be ok with a 300Mbps ISP connection which I used to have. But having 1Gbps is what makes me force 160Mhz. Remember this mini thread started because an 800Mbps slowdown with a S22 Ultra which is A LOT and with 80Mhz it would be even worse, which ASUS (or Samsung?) didn't resolve.