Thanks! Any idea on how to check which channels are actually available, and whether my device (the 1900ACS V2) supports 160 Mhz channels? It feels like Luci channel selection is incomplete somehow, I only see 20 Mhz channels:
I have the same issue. From what I understand, a 40-80Mhz band does not increase the speeds to much unless you ive in a remote area (but I'm far from an expert).
Also, my router only gets decent speeds when using band 36. All other bands result in very slow speeds and some of my devices fail to connect at all.
Using band 36 the speeds are excellent, though this band is quite crowded, so the range might increase by going to another band.....
I don't use Luci, but this is the interface I have seen previously (just the picture, not interested in the issue):
The width should be selectable near the frequency.
On the command line you can do
iw phy0 info
To see the channels.
Your device can't do 160MHz.
Someone else would need to give Luci specific advice. But obviously if you have 2x 20MHz together, you can use 40MHz there. If you have 4, you can use 80.
Exactly the same problem here: 36 works indeed but two neighbours use it too and their signal is excellent in my house, so I guess a lot of interference is going on when I'm on 36 too.
Excellent, thanks for the tip on iw phy0 info (I'm still finding my way around OpenWrt).
I thought that 80 Mhz on any other channel than 36 would be good for my network, but I'm unsure how to set it up (via command line, as Luci doesn't seem to provide all the options).
Perhaps I should mention that I also have a wireless range extender (Linksys RE7000, connected via wifi only) and another router configured as access point and connected via ethernet (Linksys EA9500). My idea was to somehow configure those devices so that I have maximum speed and seamless roaming enabled (802.11r?).
Can somebody please look at my output and tell me what config would be optimal for my situation? Any tips on how to get those 3 devices to play nicely are greatly appreciated!
root@OpenWrt:~# iw phy0 info
Wiphy phy0
max # scan SSIDs: 4
max scan IEs length: 2247 bytes
max # sched scan SSIDs: 0
max # match sets: 0
max # scan plans: 1
max scan plan interval: -1
max scan plan iterations: 0
Retry short limit: 7
Retry long limit: 4
Coverage class: 0 (up to 0m)
Device supports AP-side u-APSD.
Device supports T-DLS.
Available Antennas: TX 0 RX 0
Supported interface modes:
* managed
* AP
* AP/VLAN
* monitor
* mesh point
Band 2:
Capabilities: 0x106f
RX LDPC
HT20/HT40
SM Power Save disabled
RX HT20 SGI
RX HT40 SGI
No RX STBC
Max AMSDU length: 3839 bytes
DSSS/CCK HT40
Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
Minimum RX AMPDU time spacing: 4 usec (0x05)
HT TX/RX MCS rate indexes supported: 0-23, 32
VHT Capabilities (0x33837930):
Max MPDU length: 3895
Supported Channel Width: neither 160 nor 80+80
RX LDPC
short GI (80 MHz)
SU Beamformer
SU Beamformee
RX antenna pattern consistency
TX antenna pattern consistency
VHT RX MCS set:
1 streams: MCS 0-9
2 streams: MCS 0-9
3 streams: MCS 0-9
4 streams: not supported
5 streams: not supported
6 streams: not supported
7 streams: not supported
8 streams: not supported
VHT RX highest supported: 0 Mbps
VHT TX MCS set:
1 streams: MCS 0-9
2 streams: MCS 0-9
3 streams: MCS 0-9
4 streams: not supported
5 streams: not supported
6 streams: not supported
7 streams: not supported
8 streams: not supported
VHT TX highest supported: 0 Mbps
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] (27.0 dBm) (radar detection)
* 5520 MHz [104] (27.0 dBm) (radar detection)
* 5540 MHz [108] (27.0 dBm) (radar detection)
* 5560 MHz [112] (27.0 dBm) (radar detection)
* 5580 MHz [116] (27.0 dBm) (radar detection)
* 5600 MHz [120] (27.0 dBm) (radar detection)
* 5620 MHz [124] (27.0 dBm) (radar detection)
* 5640 MHz [128] (27.0 dBm) (radar detection)
* 5660 MHz [132] (27.0 dBm) (radar detection)
* 5680 MHz [136] (27.0 dBm) (radar detection)
* 5700 MHz [140] (27.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)
valid interface combinations:
* #{ AP } <= 16, #{ mesh point } <= 1, #{ managed } <= 1,
total <= 16, #channels <= 1, radar detect widths: { 20 MHz (no HT), 20 MHz, 40 MHz, 80 MHz, 160 MHz }
HT Capability overrides:
* MCS: ff ff ff ff ff ff ff ff ff ff
* maximum A-MSDU length
* supported channel width
* short GI for 40 MHz
* max A-MPDU length exponent
* min MPDU start spacing
Supported extended features:
* [ RRM ]: RRM
* [ CONTROL_PORT_OVER_NL80211 ]: control port over nl80211
Maybe this is of help?
I'm unsure if you meant this as reply to my post, but in that case: no, it didn't help, unfortunately. Please clarify if possible.
Hello davidc502 ,
You can implement in your version of firmware and the option of wifi schedule, in order to be able to suspend the activity on the side of the wifi during the nights or on certain days?...
Or how can I add this option in this version?
Thx
Take a look at luci-app-wifischedule.
2 Likes
Ive been waiting for this to come to openwrt for a while now.
1 Like
Hi David and all
Ive just upgraded to r12833.
How to I get dnscrypt v2 working, I see the package is present as part of the built but cant see where to go next?
all the best
wayne
Can you verify where all of your devices go for DNS resolution? All clients should be pointed to the router Gateway IP address for DNS resolution. That is the first step.
2nd Step is to look at your dnscrypt-proxy.toml file. The 2 most important lines are the following examples:
server_names = ['cloudflare']
listen_addresses = ['127.0.0.1:5300']
doh_servers = trueOnce the following has been verified you can restart the service.
The 3rd step is to start proxying the dns queries from your clients.
Under your network configurations add the following line under 'Config Interface WAN'
option dns '127.0.0.1#5300'Those 3 steps should get you up and running.
1 Like
Hello i have install on my wrt3200acm a last firmware of openwrt 19.07.2 r10947-65030d81f3.
I'm trying to use the davidc502 build, what i have to do ..
Update the firmware from a factury file or sysupdate file.
From the factory firmware if you have only installed OpenWrt 1 time, then you need to use the OpenWrt .img file the second time. You do not have to update from factory, and do not update from the openwrt .bin file. If this isn't clear let me know.
That part i don't understand,
To use your build "openwrt-mvebu-cortexa9-linksys_wrt3200acm-squashfs-sysupgrade.bin" only need to update from http://192.168.1.1/cgi-bin/luci/admin/system/flash
I'll just try asking once more in case somebody looked over my primary question.
Can somebody please give me some input on optimal Wifi config for my situation/devices?
Large single-story house and 3 potential wifi points:
- Linksys WRT1900ACS (OpenWRT, primary router)
- Linksys EA9500 (stock FW, wired to primary router)
- Linksys RE7000 (stock FW, currently not wired wireless range extender).
Not much to do about the stock firmware devices so my config options are mainly on the primary router. Should I set it as AP or AP (WDS)? Should I go for 802.11r or not? I should also mention that the goal here is to have seamless roaming and I have some legacy (G-only devices that will connect to the 2.4 Ghz band). Any tips on how to get those 3 devices to play nicely are greatly appreciated, thanks!
1 Like
Take a look at the difference between .bin and .img -> #2 https://dc502wrt.org/faq/
The 3200acm has 2 partitions, and each time flashed uses the other partition. So, if flashed OpenWrt from factory, then OpenWrt is on the 2nd partition and Factory FW is on the 1st partition. The factory FW is still on your router right now, so to over-write it, be sure to use the OpenWrt .img file.
HI here
i just installed the last build - all good except few small stuff
1/ the screen for advanced reboot, has back square and can see properly the different buttons - i use firefox - tested also on safari - same
2/
in the tab DHCP and DNS, i can not add or modify existing dns forwardings as i get a message 'expecting valid hostname' even when i just want to put 127.0.0.1#5300 which is valid or 9.9.9.9
the point 2 is particularly annoying - can you help here please?
with the 19.07.2 release, i dont have this behavior
hi David
sorry for delay i nreplying....I tried this and the DNS is still coming from my ISP. The relevant sections of the toml file show
# server_names = ['scaleway-fr', 'google', 'yandex', 'cloudflare']
server_names ['cloudflare']
## listen_addresses = ['127.0.0.1:53', '[::1]:53']
listen_addressess ['127.0.0.1:5300']
while in /etc/config/network we have
config interface 'wan'
option ifname 'eth1.2'
option proto 'pppoe'
option username 'xxxxxxxx@skydsl'
option password 'xxxxxxxx'
option ipv6 'auto'
option dns '127.0.0.1#5300'