I always set network mode (AC/N-Mixed), save; channel width, save; extension channel(s), save; then channel. That is how the UI seems to want to play nice, as I have previously stated, I think, quoting Per Yngve Berg (?)...
I will tell you this, though, you may have to test non-recommended settings for things like beamforming. I will have to pull out my R7000P and check the settings I have, which were done by way of the previous wikis when it was strictly for Broadcom only. _________________ "Life is but a fleeting moment, a vapor that vanishes quickly; All is vanity"
Contribute To DD-WRT Pogo - A minimal level of ability is expected and needed... DD-WRT Releases 2023 (PolitePol)
DD-WRT Releases 2023 (RSS Everything)
----------------------
Linux User #377467 counter.li.org / linuxcounter.net
Thank you. I did miss the first link and need to test the recommended settings, although it seems a bit strange to work with a lower fragmentation threshold and with max transmit powers. For sure it extend the range, but it might be counterproductive if you are working in confined spaces such as corridors.
That being said, the issue with the channel might be specifically linked to the RT5300 but it is definitely not a GUI issue. The channels are unavailable regardless of the country and I did try all possible combinations of GUI setting step-by-step.
CH13 and 14 appress w/o problem when you set USA. But there is no sign of CH100-144. Anywhere.
It might be interesting to try and set this channel via command line. I tried but not sure which is the correct command to be used.
Anyway, I confirm that using N/AC-mixed instead of AC-only did improve of ~10% transmission. Although it should have been the other way around. Perhaps just a better implementation of the wl drivers for this freq.mode?
Joined: 08 May 2018 Posts: 14242 Location: Texas, USA
Posted: Wed Feb 24, 2021 2:15 Post subject:
I just noticed something. Are you using the regular or experimental driver firmware image? If you aren't using the experimental driver firmware image, that might be part of your problem...
I did try both experimental firmware r45820 and r45767. Neither of them is stable in terms of wifi settings.
Yes I do see all the channels (regardless of the application of the nvram workaround), but after selecting the wanted channel (any channel really) and applying such settings, but the time the page comes back up, some settings cut as the channel are missing and channel width also is changed. An empty list may also appear in the GUI for the channel selection field.
Joined: 08 May 2018 Posts: 14242 Location: Texas, USA
Posted: Thu Feb 25, 2021 4:13 Post subject:
Considering that the 5GHz band is NOT a penetrator (you'd be lucky if it covers a large room well), I don't see why the focus is on channel 100, but I digress. _________________ "Life is but a fleeting moment, a vapor that vanishes quickly; All is vanity"
Contribute To DD-WRT Pogo - A minimal level of ability is expected and needed... DD-WRT Releases 2023 (PolitePol)
DD-WRT Releases 2023 (RSS Everything)
----------------------
Linux User #377467 counter.li.org / linuxcounter.net
My focus is on ch100 because:
a/ there are so little 80mhz frequencies without radar in my house/area, and ch100 seems to work best of them all - I've also tested the area with a MikroTik router and that channels works best.
b/ the same Asus router I'm using with dd-wrt in the exact same location and position (and cable, etc). was yielding better results on ch100 on stock firmware
Since I switched to dd-wrt to implement vian and a bit of more refined networking (I'm in love with the firmware overall btw), I would like to understand the reason behind not being able to select a channel that is a standard and available on stock firmware - I find this a quite base functionality compared to all the advance features that dd-wrt offers.
Thanks.
PS: All my tests have been conducted in comparable scenarios taking into considerations walls/router positioning and environmental factors (e.g. number of devices connect the AP simultaneously, etc).
for those trying to get dd-wrt on a newer router where the firmware upgrade process is locked .. the instructions here were not clear to me.. this is what i did.
1. the newer firmwares will not allow flashing dd-wrt.trx file or even an older asus stock firmware that did allow it.
2. the recovery partition on the router also will not allow it.. you can get to recovvery by long holding the reset and you will be in recovery when the one light is flashing slowly... do not reboot..
just hard code your ip on your pc plugged into the router to something on 192.168.1.x
ie 192.168.1.12 the router should be at 192.168.1.1
now the built in recovery as i said if you open a web browser to 192.168.1.1 also will not allow the firmware upgrade. it must also have checks.. it doesnt tell you that the submit or whatever button just does nothing..
3. you need to have previously downloaded and setup a version of asus firmware recovery i used this version
once it boots up you should be good to go.. i have had problems getting it to take the new username password.. i think you need to do a reset first and then the second time it took it.
Joined: 31 Jul 2021 Posts: 2146 Location: All over YOUR webs
Posted: Fri Jun 03, 2022 16:50 Post subject:
You need seriously old builds of stock that arent locked, something going back 3 years should be OK. But dont hold me to that, I never flashed a locked stock build so they may even prevent downgrading to an older stock even via recovery, dont know.
While debugging aspects of configuration on my AC5300 and R8000, I encountered the lack of DFS channels on the AC5300, as well. Wanted to just document this:
Available channels (usually) depend on regulatory domain selected. _________________ "The woods are lovely, dark and deep,
But I have promises to keep,
And miles to go before I sleep,
And miles to go before I sleep." - Robert Frost
"I am one of the noticeable ones - notice me" - Dale Frances McKenzie Bozzio
Yes. Both are currently set to Singapore / non 802.11d/h mode (default).
As previous posters have mentioned, it doesn’t matter the domain specified, the AC5300 doesn’t respond with any available DFS channels.
This may be related to how the radios are initialized and capabilities of the way different firmwares operate. Radios certified after 2015 may require to use GPS, adjacent APs, local cellular frequencies and radar detection to verify operating locale and subsequently enable all frequencies / capabilities. If not, only the most basic capabilities are enabled.
Also could be the encrypted CFE is detecting an unsigned / invalidly signed firmware and ensures compliance by disabling the advanced features. I don’t have a console connection to verify either assumption.