David, I'm looking forward to trying the new build out with dnscrypt-proxy v2 baked in. As I understand, the only change from how it is currently handled is that the config file will be in the new location.
Could you share your config files, please?
Correct, just move the .toml file out of /etc/config/ over to /etc/dnscrypt-proxy2/ then restart dnscrypt-proxy2 like so --- /etc/init.d/dnscryp-proxy restart
Once that is done you should have DNS again.
For any people using dnscrypt-proxy2 and you want to give it a try -- https://dc502wrt.org/snapshots/r11266/targets/mvebu/cortexa9/
I'm going to be in and out all day, and after 3 will be out of town. However, I'm interested in your experience and if moving the .toml file to the new directory fixes the issue. It should, but I can't just go by my set up or figure it works for me so it will work for everyone else.
2 Likes
Does someone explain the layout of the powertable in the dts files?
For reference here is the patch adding the powertables:
https://git.openwrt.org/?p=openwrt/openwrt.git;a=blob;f=target/linux/mvebu/patches-4.19/002-add_powertables.patch;h=c2fb748d5d076403abab3316bf801938de646490;hb=HEAD
Column:
1: channel number
2: ?
3 - 16: Possible power levels? Why so many?
17: ?
18: ?
Which row does indicate if a channel is a DFS channel?
I tried to add a new reg domain with lower power levels (6dbm for 2.4Ghz and 12dbm for 5Ghz)
The kernel log shows that the new regdomain and powerlevels were recognized by mwlwifi.
But there was no actual difference.
@T-Troll
160Mhz almost uses the entire available spectrum,
so maybe it is best to always use channel 36 (centered to channel 50 and 114?) for 160Mhz?
Do your 80Mhz devices support all 5Ghz channels?
160Mhz also only seems useful in a place where no other 5Ghz Wifis interference with your wifi.
When you use 160Mhz channel width your AP can create interference almost along the entire spectrum.
So only use 160Mhz when necessary and/or use adequate power levels.
Unfortunately mwlwifi doesn't allow to lower the output power levels 
You've overcome
power table loaded from dts: no
or is this a non-restricted device,
This is an unrestricted device (WRT1200AC v1):
cat /sys/kernel/debug/ieee80211/phy0/mwlwifi/info
driver name: mwlwifi
chip type: 88W8864
hw version: 7
driver version: 10.3.8.0-20181210
firmware version: 0x0702091a
power table loaded from dts: yes
firmware region code: 0x0
mac address: 00:25:9c:13:ca:bb
2g: disable
5g: enable
antenna: 2 2
irq number: 73
ap macid support: 0000ffff
sta macid support: 00010000
macid used: 00000001
radio: enable
iobase0: c47fdfd2
iobase1: 28d76619
tx limit: 768
rx limit: 64
qe trigger number: 4004846
Kernel Log:
[ 17.215257] ieee80211 phy1: regdomain: DE
[ 17.219332] ieee80211 phy1: Channel: 1: 0x0 0x0 0xf
[ 17.224247] ieee80211 phy1: 6 6 6 6 6 6 6 6 6 6 6 6 0 0 0 0
[ 17.230044] ieee80211 phy1: Channel: 2: 0x0 0x0 0xf
[ 17.234958] ieee80211 phy1: 6 6 6 6 6 6 6 6 6 6 6 6 0 0 0 0
[ 17.240672] ieee80211 phy1: Channel: 3: 0x0 0x0 0xf
[ 17.245584] ieee80211 phy1: 6 6 6 6 6 6 6 6 6 6 6 6 0 0 0 0
[ 17.251301] ieee80211 phy1: Channel: 4: 0x0 0x0 0xf
[ 17.256219] ieee80211 phy1: 6 6 6 6 6 6 6 6 6 6 6 6 0 0 0 0
[ 17.261948] ieee80211 phy1: Channel: 5: 0x0 0x0 0xf
[ 17.266867] ieee80211 phy1: 6 6 6 6 6 6 6 6 6 6 6 6 0 0 0 0
[ 17.272573] ieee80211 phy1: Channel: 6: 0x0 0x0 0xf
[ 17.277508] ieee80211 phy1: 6 6 6 6 6 6 6 6 6 6 6 6 0 0 0 0
[ 17.283206] ieee80211 phy1: Channel: 7: 0x0 0x0 0xf
[ 17.288133] ieee80211 phy1: 6 6 6 6 6 6 6 6 6 6 6 6 0 0 0 0
[ 17.293829] ieee80211 phy1: Channel: 8: 0x0 0x0 0xf
[ 17.298762] ieee80211 phy1: 6 6 6 6 6 6 6 6 6 6 6 6 0 0 0 0
[ 17.304457] ieee80211 phy1: Channel: 9: 0x0 0x0 0xf
[ 17.309397] ieee80211 phy1: 6 6 6 6 6 6 6 6 6 6 6 6 0 0 0 0
[ 17.315103] ieee80211 phy1: Channel: 10: 0x0 0x0 0xf
[ 17.320128] ieee80211 phy1: 6 6 6 6 6 6 6 6 6 6 6 6 0 0 0 0
[ 17.325823] ieee80211 phy1: Channel: 11: 0x0 0x0 0xf
[ 17.330842] ieee80211 phy1: 6 6 6 6 6 6 6 6 6 6 6 6 0 0 0 0
[ 17.336539] ieee80211 phy1: Channel: 12: 0x0 0x0 0xf
[ 17.341560] ieee80211 phy1: 6 6 6 6 6 6 6 6 6 6 6 6 0 0 0 0
[ 17.347268] ieee80211 phy1: Channel: 13: 0x0 0x0 0xf
[ 17.352281] ieee80211 phy1: 6 6 6 6 6 6 6 6 6 6 6 6 0 0 0 0
[ 17.358019] ieee80211 phy0: regdomain: DE
[ 17.362058] ieee80211 phy0: Channel: 36: 0x0 0x0 0xf
[ 17.367058] ieee80211 phy0: c c c c c c c c c c c c c c c c
[ 17.374173] ieee80211 phy0: Channel: 40: 0x0 0x0 0xf
[ 17.379213] ieee80211 phy0: c c c c c c c c c c c c c c c c
[ 17.386307] ieee80211 phy0: Channel: 44: 0x0 0x0 0xf
[ 17.391327] ieee80211 phy0: c c c c c c c c c c c c c c c c
[ 17.398442] ieee80211 phy0: Channel: 48: 0x0 0x0 0xf
[ 17.403445] ieee80211 phy0: c c c c c c c c c c c c c c c c
[ 17.410563] ieee80211 phy0: Channel: 52: 0x0 0x0 0xf
[ 17.415565] ieee80211 phy0: c c c c c c c c c c c c c c c c
[ 17.422677] ieee80211 phy0: Channel: 56: 0x0 0x0 0xf
[ 17.427701] ieee80211 phy0: c c c c c c c c c c c c c c c c
[ 17.434794] ieee80211 phy0: Channel: 60: 0x0 0x0 0xf
[ 17.439811] ieee80211 phy0: c c c c c c c c c c c c c c c c
[ 17.446904] ieee80211 phy0: Channel: 64: 0x0 0x0 0xf
[ 17.451925] ieee80211 phy0: c c c c c c c c c c c c c c c c
[ 17.459036] ieee80211 phy0: Channel: 100: 0x0 0x0 0xf
[ 17.464138] ieee80211 phy0: c c c c c c c c c c c c c c c c
[ 17.471248] ieee80211 phy0: Channel: 104: 0x0 0x0 0xf
[ 17.476339] ieee80211 phy0: c c c c c c c c c c c c c c c c
[ 17.483458] ieee80211 phy0: Channel: 108: 0x0 0x0 0xf
[ 17.488563] ieee80211 phy0: c c c c c c c c c c c c c c c c
[ 17.495658] ieee80211 phy0: Channel: 112: 0x0 0x0 0xf
[ 17.500779] ieee80211 phy0: c c c c c c c c c c c c c c c c
[ 17.507887] ieee80211 phy0: Channel: 116: 0x0 0x0 0xf
[ 17.512987] ieee80211 phy0: c c c c c c c c c c c c c c c c
[ 17.520110] ieee80211 phy0: Channel: 120: 0x0 0x0 0xf
[ 17.525198] ieee80211 phy0: c c c c c c c c c c c c c c c c
[ 17.532310] ieee80211 phy0: Channel: 124: 0x0 0x0 0xf
[ 17.537425] ieee80211 phy0: c c c c c c c c c c c c c c c c
[ 17.544518] ieee80211 phy0: Channel: 128: 0x0 0x0 0xf
[ 17.549626] ieee80211 phy0: c c c c c c c c c c c c c c c c
[ 17.556720] ieee80211 phy0: Channel: 132: 0x0 0x0 0xf
[ 17.561828] ieee80211 phy0: c c c c c c c c c c c c c c c c
[ 17.568954] ieee80211 phy0: Channel: 136: 0x0 0x0 0xf
[ 17.574051] ieee80211 phy0: c c c c c c c c c c c c c c c c
[ 17.581168] ieee80211 phy0: Channel: 140: 0x0 0x0 0xf
[ 17.586257] ieee80211 phy0: c c c c c c c c c c c c c c c c
So the new values got read by the mwlwifi driver.
I also removed all short range channels (140+ ?)
iw info shows:
Frequencies:
* 5180 MHz [36] (23.0 dBm)
* 5200 MHz [40] (23.0 dBm)
* 5220 MHz [44] (23.0 dBm)
* 5240 MHz [48] (23.0 dBm)
* 5260 MHz [52] (20.0 dBm) (radar detection)
* 5280 MHz [56] (20.0 dBm) (radar detection)
* 5300 MHz [60] (20.0 dBm) (radar detection)
* 5320 MHz [64] (20.0 dBm) (radar detection)
* 5500 MHz [100] (26.0 dBm) (radar detection)
* 5520 MHz [104] (26.0 dBm) (radar detection)
* 5540 MHz [108] (26.0 dBm) (radar detection)
* 5560 MHz [112] (26.0 dBm) (radar detection)
* 5580 MHz [116] (26.0 dBm) (radar detection)
* 5600 MHz [120] (26.0 dBm) (radar detection)
* 5620 MHz [124] (26.0 dBm) (radar detection)
* 5640 MHz [128] (26.0 dBm) (radar detection)
* 5660 MHz [132] (26.0 dBm) (radar detection)
* 5680 MHz [136] (26.0 dBm) (radar detection)
* 5700 MHz [140] (26.0 dBm) (radar detection)
* 5720 MHz [144] (disabled)
* 5745 MHz [149] (13.0 dBm)
* 5765 MHz [153] (13.0 dBm)
* 5785 MHz [157] (13.0 dBm)
* 5805 MHz [161] (13.0 dBm)
But iw uses values from the wireless-regdb, I guess?
mwlwifi also has no TPC support, right?
Hmm if it is not possible to reduce power levels through software/driver methods, I'm thinking to get some attenuators and physically reduce the signal.
Someone like kaloz might be able to assist with the format of the DTS power table, but I expect it is NDA.
I'd be also interested in the format of the wrt32x ones that are unrestricted (e.g. AU) because they are a slightly different format.
I expect the middle numbers are a series of numbers which go into a register to tune the power.
I think someone asked about the dts layout on the mwlwifi github issue tracker before and kaloz replied that he can't answer this question, so yes you are right and it is under NDA.
Why do some tables have different values in the same row?
I have some other question about the automatic channel selection.
To exclude dfs channels from the automatic channel selection:
acs_exclude_dfs option doesn't me to work with mwlwifi.
acs_chan_bias '36:0.8 44:0.8' sometimes seems to work but is not reliable enough.
channels '36 44' seems to work best but sometimes hostapd gives this message:
hostapd: Switch own primary and secondary channel to get secondary channel with no Beacons from other BSSes
In this case ACS has selected channel 44 (+48 as secondary) but then switches those channels.
48 primary and 44 as secondary but then my devices can't connect anymore.
Using the noscan option fixes this but is there are a better solution?
//edit
Nevermind, works fine.
When using channel 48 with a channel width of 40 Mhz,channel 52 will be used as secondary channel?
If yes, this can cause DFS to trigger because channel 52 requires DFS?
This new build with dnscrypt-proxy v2 works well in my configuration (Linksys WRT1900ACS V2, ~50 devices, most wireless, added wireguard and vpn-policy-routing packages, 300 Mbs / 100 Mbs fiber connection).
1 Like
Good to know -- Thanks @slim0287
When I get back from work tomorrow evening, I'll make sure everything is available on the download page.
This is my configuration so far:
config wifi-device 'radio0'
option type 'mac80211'
option hwmode '11g'
option noscan '1'
option ht_coex '1'
option bursting '1'
option path 'soc/soc:pcie/pci0000:00/0000:00:02.0/0000:02:00.0'
option channel '6'
option htmode 'HT40'
option legacy_rates '0'
option country 'US'
option __toggle 'Enable'
config wifi-iface 'default_radio0'
option device 'radio0'
option mode 'ap'
option ssid 'HouseOfTTrols'
option powersave '0'
option key 'XXXXXXXXXXXXXX'
option network 'lan'
option disassoc_low_ack '0'
option short_preamble '0'
option encryption 'psk2+ccmp'
config wifi-device 'radio1'
option type 'mac80211'
option hwmode '11a'
option path 'soc/soc:pcie/pci0000:00/0000:00:01.0/0000:01:00.0'
option mu_beamformer '1'
option su_beamformer '1'
option beacon_int '50'
option country 'US'
option legacy_rates '0'
option htmode 'VHT160'
option channel '116'
config wifi-iface 'default_radio1'
option device 'radio1'
option mode 'ap'
option ssid 'HouseOfTTrols5'
option key 'XXXXXXXXXXXXXX'
option network 'lan'
option disassoc_low_ack '0'
option encryption 'psk2+ccmp'
option short_preamble '0'
1 Like
No, 36 is not working for me, seems like channel should be in the center of the spectrum.
Yes, my 80MHz devices support all channels. But seems like Killer (=Atheros) can not be bug-free. It also have a problem with more, then 100 AP visible, for example.
For old firmware, there was a hack for 1900 (maybe 1200 as well) - you can set up power in config after it as well as disable radar detection. I use it for my old 1900v1, until sell it.
1 Like
Hi, my 5ghz network doesn't work as good as it did before I upgraded to the latest build.
I have a Linksys WRT1900ACS running
Firmware Version OpenWrt SNAPSHOT r11159-27bf8abe69 / LuCI Master (git-19.278.57548-95ea1e6)
Kernel Version 4.19.76
I've moved my clients to the 2,4ghz network to be able to stream iptv, netflix etc..
Is there any settings changed from previous version, drivers, anything?
edit: maybe disregard this, deleted and added a new 5ghz network and I will have to do some testing..
edit2: still have issues with 5ghz, very bad streaming quality on my apple tv (better quality on 2.4 ghz)
If you are happy with OpenWRT buy something from ubiquiti for Wifi. Asus firmwares can be a pain in the '* too.
Hello,
I am running OpenWrt SNAPSHOT r11266-34939711a5 / LuCI Master (git-19.292.31773-cc35194) and am having some issues.
-
I cannot connect to my HP wireless printer. The problem started with the last snapshot and was unable to print from my Windows computer but from my macOS. Now I cannot print from either computer. Any ideas?
-
It seems I am still using my ISP's DNS and not Clouldflare DNS. What did I do wrong?
Thanks!
#2 - Did you set up dnscrypt-proxy? Otherwise it will not work and it will continue to use the ISP's DNS.
#1 - Are you printing by hostname? Example printer.lan ? Or by IP address?
David
@davidc502 I always owned this 3200ACM. After checking /etc/fw_env.config it matched the expected content. I went with @ParanoidZoid 's advice. The boot_part was set to 1, I did the manual set to 2, rebooted. Before the reboot the Luci had this rosy theme. I never switched themes or anything, I prefer to stay with the built-in settings unless I must change something.
After the reboot to boot_part 2 I was faced with a more plain light blue OpenWRT logo theme, and from the logs I saw I was booted into a firmware of 2018 October. I performed the Flash on that UI with latest build (released on 10/06/2019). That Flash seemed to be successful, because after reboot, I faced with a different theme, also not the rosy Luci, but one with light blue OpenWRT logo and white on black left menu panel. That newest firmware is:
- OpenWrt SNAPSHOT r11159-27bf8abe69 / LuCI Master (git-19.278.57548-95ea1e6)
- Kernel: Linux version 4.19.76 (davidc502@Ryzen-3900x) (gcc version 9.2.0 (OpenWrt GCC 9.2.0 r11159-27bf8abe69)) #0 SMP Fri Oct 4 18:42:26 2019
We'll see if the next release will Flash without any manual fiddling. Thanks for all the help @davidc502, @ParanoidZoid and T-Troll as well!
1 Like
Testing snapshot r11266 on 1900ac v1. dnscrypt-proxy2 works great. had to manually configure as was coming from old version of firmware. The only issue is that I had a unexplained reboot. will setup logging to flash drive to try and catch error if it happens again