@david, new kernel is out, 4.9.45

No changes have been made to the radio firmware in ages, and nothing has changed in the mwlwifi driver that would cause what you are describing.

As was just very recently discussed on the last page, you must enable option noscan '1' for your 2.4GHz radio in the /etc/config/wireless file for 40MHz to work on 2.4GHz.  It has always been this way...

@david, just an update, it appears that setting is now contained in the file

source/package/utils/busybox/Config-defaults.in

starting at line 944.

That commit that I had linked to and got my information from previously is apparently way out of date, and the option is now in the above file.  So if you were having trouble trying to find it, that's why

(Last edited by starcms on 30 Aug 2017, 22:31)

Cool -- thanks

I made another mistake.  The file is now source/package/utils/busybox/Config-defaults.in, but the options are now BUSYBOX_DEFAULT_DIFF and BUSYBOX_DEFAULT_FEATURE_DIFF_DIR that need to be changed from default n to default y.  BUSYBOX_DEFAULT_FEATURE_DIFF_LONG_OPTIONS can be left on default n.

Edit: Since I'm not exactly sure what BUSYBOX_DEFAULT_FEATURE_DIFF_LONG_OPTIONS does, and it's other prereq is already enabled by default, you might as well turn this one to default y too to ensure the diff command works fully as needed in the script.  OR if you find it easier, just skip all of this and just include the package diffutils as we first discussed.

Edit2:  Ah, I see.  We definitely need BUSYBOX_DEFAULT_DIFF and BUSYBOX_DEFAULT_FEATURE_DIFF_DIR as I mentioned previously because the script is using the diff command on two directories. 

What BUSYBOX_DEFAULT_FEATURE_DIFF_LONG_OPTIONS does is enable for example --brief (long option) in addition to -q (short option) which both do the same command.  Since the script only uses diff -q, LONG_OPTIONS isn't required, but since we are enabling the diff command, it seems to be foolish not to enable BUSYBOX_DEFAULT_FEATURE_DIFF_LONG_OPTIONS as well.

(Last edited by starcms on 30 Aug 2017, 23:15)

While searching, this is all I could find:

uci set wireless.radio0.noscan=1
uci commit
reboot

Would this work? I'm also seeing this on the OpenWRT page:

uci set wireless.radio0.htmode=HT40+  # or: HT40- if using channel 11
  uci commit wireless; wifi

Not sure what the best way to do it would be. I'd prefer to be able to open it up in a text editor but I'm not sure how to do that...

(Last edited by BIOHazard87 on 30 Aug 2017, 23:54)

@BIOHazard87

Install MobaXterm and from there just copy the text file over to the PC... Edit, and replace. Just be sure to do it in Notepad.

noscan '1' is now set, and 40mhz still isn't working. I believe I need those other steps.

Thank you that is a great app.

(Last edited by BIOHazard87 on 31 Aug 2017, 04:22)

As I said, on the WRT1900AC V1, I'm not sure if radio0 or radio1 is the 2.4GHz radio. 

If you don't want to use a text editor to edit /etc/config/wireless you use uci set.

uci set will work (I just tested it) and since it doesn't hurt to add noscan=1 to the 5GHz radio, since you don't know which is which enter the following at the SSH prompt, enter after each command:

uci set wireless.radio0.noscan=1
uci set wireless.radio1.noscan=1
uci commit
reboot

Don't use uci to set HT40+ or HT40-, after you reboot, just set it to 40MHz in LuCi.

Edit: Just saw your above post.  You don't need the other step.  Most likely on the 1900AC V1, the 2.4GHz radio is radio1 which is why it didn't work.  Just do the uci set command again but replace radio0 with radio1.  Or just enter all 4 commands as I have them listed above.  Then be sure to go to Wireless settings in LuCi and change your 2.4GHz radio from 20MHz to 40MHz.

(Last edited by starcms on 31 Aug 2017, 04:28)

I did what David said,  downloaded the wireless config file, edited in wordpad, then uploaded it, and rebooted. 40mhz still does not work when set in Luci.

config wifi-device 'radio0'
    option type 'mac80211'
    option hwmode '11g'
    option path 'soc/soc:pcie-controller/pci0000:00/0000:00:02.0/0000:02:00.0'
    option country 'US'
    option channel '6'
    option noscan '1'
    option htmode 'HT40'

It appears radio0 is 2.4ghz

EDIT: I added it under radio1 as well, and still no luck after rebooting .

EDIT2:   It seems 40mhz is actually working, but Luci is still showing 20mhz? My iPhone detects the AP as 40mhz now, but like I said the interface shows all devices as 20mhz.

(Last edited by BIOHazard87 on 31 Aug 2017, 04:37)

All that looks good.

You did reboot after adding option noscan '1' and setting 40MHz in luci?

First use the command:

cat /etc/config/wireless

to view the wireless file to ensure the updated file was successfully uploaded to the router and option noscan '1' is there.  If it is then continue.

If 40MHz still isn't working, its because of the regulatory settings.  You will need to apply a "hack" called reghack2 which will disable DFS on all 5GHz channels, enable channels 12 and 13 on 2.4GHz, allow the maximum power to be set to 30dBm on all 2.4 and 5GHz channels, and allow 40MHz to work on 2.4GHz.

Issue the following commands at your SSH prompt:

cd /sbin
wget https://files.fm/down.php?i=v4faj68x&n=reghack2
Press enter to get back to a command prompt after download completes.
mv down.php?i=v4faj68x reghack2
chmod 755 reghack2
/sbin/reghack2 /lib/modules/*/cfg80211.ko
reboot

That combined with noscan will enable 40MHz at 2.4GHz for you.

(Last edited by starcms on 31 Aug 2017, 04:55)

Great advice and very detailed, as usual my friend!

I did everything you suggested, but one thing... I'm using the dnscrypt.nl-ns0 resolver, and my 2nd one is cisco-familyshield, as I assume that one will filter (return an error) for sites that are not suitable for my kids... Is my assumption correct? And if it is correct, reading your email about dnscrypt picking one and the other sequentally, I'll lose the "family protection"...

LUCI shows connection statuses, not interface status. So, if you device can only connect router to 20 - it will be shown as 20 (however, it also decreased at inactivity).
Use any kind of wifi scanner (f.e. Acrylic Wi-Fi for windows, Wifi analyzer for Android) to check what do you have around.

For reghack it's also needed to set US as a county in settings.

He can also set BM or BO as a country _without_ reghack for 30db 2.4.

According to Wifi Explorer on iOS, 40mhz is working with noscan 1 on just the 2.4ghz. However, it seemed to degrade my long-range 5ghz performance when noscan 1 was set on the 5ghz band as well. I was getting around 5Mbps through multiple tests compared to 15-20Mbps.

I'm not using reghack and my country is set to US, yet Luci says my 2.4 is at 30dB while set to Auto, is this true or no?

Mode: Master | SSID: -------
BSSID: ----------- | Encryption: WPA2 PSK (CCMP)
Channel: 6 (2.437 GHz) | Tx-Power: 30 dBm
Signal: -67 dBm | Noise: -85 dBm
Bitrate: 104.7 Mbit/s | Country: US

(Last edited by BIOHazard87 on 31 Aug 2017, 05:18)

Actually dnsmasq seems to use the [dns] servers listed in /etc/config/dhcp (meaning your dnscrypt resolvers) at random.  It doesn't use them in any particular order I have found out from experience.  Also, I have recently began highly recommending adding the line:

option allservers '1'

to the config dnsmasq section of /etc/config/dhcp because sometimes (without that option) dnsmasq won't automatically use the other resolver if one goes down.  The allservers options forces dnsmasq to always try to use all servers and use the one that responds first.  This guarantees if one of your revolvers goes down, your entire DNS won't go down.

So unfortunately for your question, no, there is no way to force dnsmasq to only use cisco-familyshield unless it goes down and then switch to your other resolver.  So sometimes it would use cisco-familyshield and block offensive content and other times it would use your other resolver and not. 

My only suggestion is to use adblock for your content filtering.  I believe it has a few block lists included dedicated to blocking sites not friendly to kids.  Plus you can always find a kid-friendly blocklist and add it to adblock.  And you might even be able to find the list of websites that cisco-familyshield uses to block and add it to adblock to get identical protection.

Edit: Or, since cisco's (OpenDNS) servers are sooooo reliable, you could probably get away with only using cisco-familyshield without a second resolver and never have an issue.

(Last edited by starcms on 31 Aug 2017, 05:40)

So an app on your iPhone detects the AP as 40MHz, but no devices connect using 40MHz?  It's very possible your devices do not support 40MHz on 2.4GHz.  Or there is too much interference for them to connect using 40MHz.

I didn't think reghack2 was required for 2.4GHz 40MHz to work, only the noscan '1' option, but @T-Troll had mentioned it a long time ago.

I wouldn't recommend using noscan '1' on the 5GHz radio, only the 2.4GHz radio.  It is only needed on the 2.4GHz radio for 40MHz 2.4GHz to work.

Also, yes 30dBm is allowed on all channels on 2.4GHz in the US.  On 5GHz, most channels are limited to 23dBm, with only channels 149, 153, 157, and 161 allowed to use up to 30dBm in the US.

I HIGHLY recommend not leaving any settings set to AUTO.

(Last edited by starcms on 31 Aug 2017, 05:24)

Strangely I've never heard of the fact that I need to add this option added speed increased 2 times thanks for the tip and help sorry people if I was too emotionally.

Just wanted to chime in. Here is my current setup:

Build: R4707
Router: WRT3200ACM
Setup/Customizations:

• Disabled adblock

• Enabled SSH over LAN

• 2.4GHz: Channel 1, N only, 40MHz

• 5.0GHz: Channel 153, AC only, 80MHz

• SQM QoS Enabled using Cake

Everything has been working really well. Download speeds have been steady and conistent, and QoS has worked well. One weird thing I have noticed - sometimes after turning on a laptop or desktop, it takes 10-15 seconds before the DNS resolution works. In some rare cases I have had to disconnect and reconnect before it works.

Keep up the great work!

Try setting option nonwildcard to '0' in /etc/config/dhcp.  You'll see it towards the very top in the config dnsmasq section. Save and reboot.  Hopefully that will help!

Long time lurker, first time caller.

I cannot get my 2.4 @ 20Mhz over 72.2mbps MCS 7. Added all the "extras" for radio1 trying to get over 72mbps.

Here is my wireless config.

config wifi-device 'radio0'
        option type 'mac80211'
        option hwmode '11a'
        option path 'soc/soc:pcie-controller/pci0000:00/0000:00:01.0/0000:01:00.0'
        option txpower '23'
        option htmode 'VHT80'
        option channel '36'
        option country 'US'

config wifi-iface 'default_radio0'
        option device 'radio0'
        option network 'lan'
        option mode 'ap'
        option key PASSWORD HERE
        option macaddr '00:E0:5E:56:DD:99'
        option noscan '1'
        option encryption 'psk2+ccmp'
        option ssid 'Obsidian Networks 5Ghz'

config wifi-device 'radio1'
        option type 'mac80211'
        option hwmode '11g'
        option path 'soc/soc:pcie-controller/pci0000:00/0000:00:02.0/0000:02:00.0'
        option noscan '1'
        option txpower '30'
        option bursting '1'
        option ff '1'
        option compression '1
        list ht_capab SHORT-GI-40
        list ht_capab TX-STBC
        list ht_capab RX-STBC1
        list ht_capab DSSS_CCK-40'
        option country 'US'
        option channel '1'
        option htmode 'HT20'

config wifi-iface 'default_radio1'
        option device 'radio1'
        option network 'lan'
        option mode 'ap'
        option encryption 'psk2+ccmp'
        option key PASSWORD HERE
        option macaddr '00:E0:5E:56:DD:98'
        option ssid 'Obsidian Networks 2.4Ghz'

(Last edited by PolarisX on 1 Sep 2017, 06:59)

First, there's a typo, there's no close quote on: option compression '1

However, I highly don't recommend any of those options (those list ht_capab lines aren't even valid the way they are entered, plus your 2.4GHz radio already has SHORT-GI-40 and DSSS_CCK-40 enabled by default, and doesn't even support the other two options, so most definitely remove all 4 of those lines; plus ff, compression, and bursting are also in the wrong section and not even supported on our devices (only on atheros based devices)), except noscan '1' and that only matters if you are using 40MHz, which you aren't (You would need to change htmode to HT40 as shown below).  I would recommend changing your config back to default (except for noscan '1') and trying 40MHz as shown:

config wifi-device 'radio1'
        option type 'mac80211'
        option hwmode '11g'
        option path 'soc/soc:pcie-controller/pci0000:00/0000:00:02.0/0000:02:00.0'
        option noscan '1'
        option txpower '30'
        option country 'US'
        option channel '1'
        option htmode 'HT40'

You most likely aren't getting above MCS 7 simply because your device(s) don't support it.  Those options you added wouldn't help at all with getting above MCS 7 (those options such as bursting, ff, and compression are meant to increase the real-world speed when connected via a theoretical max speed such as 72.2mbps).  MCS 7 (72.2mbps) is the fastest speed for a device at 20MHz that supports only 1 spacial stream.  So most likely your old 2.4GHz device(s) only support 1 spacial stream; however they may support 40MHz, but if they do support 40MHz, then you would still be at MCS 7, but the speed would be 150mbps.

(Last edited by starcms on 1 Sep 2017, 09:08)

@all,

I remember a while back someone asking how to set the 5GHz radio to 802.11ac ONLY mode (he was coming from DD-WRT where they had such a mode (as does the stock Linksys firmware); as I'm sure most of you know, if in LuCi you have the 5GHz radio set to AC, N devices can still connect).

I just happened to stumble across a setting that will allow you to set your 5GHz radio/AP to 802.11ac ONLY mode.

In your /etc/config/wireless file under the config wifi-device 'radio0' section (if you have a mamba, WRT1900AC V1, it would go under config wifi-device 'radio1') add the following line and reboot:

option require_mode 'ac'

It's that simple.  Hopefully whoever originally asked that question about a month or two ago sees this

Taken from https://wiki.openwrt.org/doc/uci/wireless

option require_mode: (ap mode) Set the minimum mode that connecting clients need to support to be allowed to connect. Supported values: g = 802.11g, n = 802.11n, ac = 802.11ac

So it could also be used on the 2.4GHz radio to only allow N devices to connect (because if you have your 2.4GHz set to N in LuCi, 802.11g (and maybe 802.11b) devices can still connect -- similar to above with 5GHz and AC mode in LuCi.  So in that case for the 2.4GHz radio, the setting option require_mode 'n' would go under config wifi-device 'radio1' (except for the mamba, 1900AC V1, where it would go under config wifi-device 'radio0').

(Last edited by starcms on 1 Sep 2017, 16:25)

@all,

For those of you who have suffered from slow DNS resolution issues, and option nowildcard '0' did not work, I believe the problem may have finally been fixed (although I believe this now affects very, very few people since option nonwildcard '0' seemed to help the few experiencing it). 

A new version of dnsmasq was released (v. 2.77-10) which fixes issues with the answer_request() function.  It will be included in @david's next build.  Of course if you have changed your distros to point to LEDE's servers, you can upgrade to the latest version of dnsmasq right now.

Commit is here for those interested: https://github.com/lede-project/source/ … d929cbee48