Scanning on 5 GHz might not work:
- if currently tuned into a DFS channel
- at all (depending on your regulatory domain and its requirements)
that isn't necessarily a bug.
For the images I provided, I created a default configuration and selected LuCI as an additional package. It was not done by the firmware selector, I built them manually.
For the problem I reported above, I used the firmware selector with additional packages LuCI, relayd and the LuCI relayd plugin.
I’ll try to reduce the problem to a specific commit.
I understand, but my expectation was that there would be either a message indicating the problem or that scanning the 5Ghz network won’t show any results at all. Showing the 2,4 GHz networks when scanning 5GHz was confusing for me.
Somebody is having problems too. Not sure if actually related: Belkin RT1800 snapshot r21950 - mt7915e fail to load
I was neither able to find r21599, nor the r21950 commit. Would be nice, if people would actually provide links to the commit.
Wait, maybe it is this issue: ubus call iwinfo scan '{"device": "radio1"}' get wrong output?
ubus call iwinfo scan '{"device": "radio1"}'get all 2.4G wifi resaults
butiwinfo phy1-ap0 scanget the correct 5.8G wifi resaults.tested on mt7915
device: wax202also tested on RT-ACRH17 no issue
After some rounds of git bisect, builds and flashing:
f3d8de73988a79440d183050dc9711bb29d2a5e1 is the first bad commit
commit f3d8de73988a79440d183050dc9711bb29d2a5e1
Author: Christian Marangi <ansuelsmth@gmail.com>
Date: Sat Jan 21 01:23:22 2023 +0100
iwinfo: update to latest Git HEAD
If somebody wants to reproduce the issue:
Log of git bisect:
git bisect start
# status: waiting for both good and bad commits
# bad: [d02d4556789f59f472c3134569a341a48f18c1ec] kernel: make it possible for packages to select page pool support
git bisect bad d02d4556789f59f472c3134569a341a48f18c1ec
# status: waiting for good commit(s), bad commit known
# good: [26c095cb4d27428acedf1b738507a585f1585fe4] ipq807x: add Dynalink DL-WRX36
git bisect good 26c095cb4d27428acedf1b738507a585f1585fe4
# bad: [183bad664167f73a6798980faab5d9b5bba06b5a] CI: tools: add gnu-getopt to macOS CI
git bisect bad 183bad664167f73a6798980faab5d9b5bba06b5a
# good: [00f1463df7e690862403208082f71fb4741baf02] mbedtls: move source modification to patch
git bisect good 00f1463df7e690862403208082f71fb4741baf02
# bad: [f183ce35b8ea2fd991ac489fb223b09a1ecb4db0] kernel: mtk-bmt: fix usage of _oob_read
git bisect bad f183ce35b8ea2fd991ac489fb223b09a1ecb4db0
# good: [84ee3436a44dac3809b05a1c900e34dbebf030c1] ipq806x: Point to externally compiled dtbs in recipes
git bisect good 84ee3436a44dac3809b05a1c900e34dbebf030c1
# good: [bd0f9d8ffcd1dc169fb66f9d7ddb335abbe49d37] fstools: bump to latest Git HEAD
git bisect good bd0f9d8ffcd1dc169fb66f9d7ddb335abbe49d37
# bad: [f3d8de73988a79440d183050dc9711bb29d2a5e1] iwinfo: update to latest Git HEAD
git bisect bad f3d8de73988a79440d183050dc9711bb29d2a5e1
# good: [ef649b0b14814a84a480e9b7805e4a401e9e06b6] ipq806x: Initial TP-Link and ASUS OnHub support
git bisect good ef649b0b14814a84a480e9b7805e4a401e9e06b6
# first bad commit: [f3d8de73988a79440d183050dc9711bb29d2a5e1] iwinfo: update to latest Git HEAD
So in the archive, there are
- good: 02, 04, 05,
- bad: 01, 03, 06, 07
While looking at older commits, two commits later there was:
commit b61404a6ad100b1e8305a84dbeacc2cae9d66ccf
Author: Christian Marangi <ansuelsmth@gmail.com>
Date: Sun Jan 22 19:51:39 2023 +0100
rssileds: bump PKG_RELEASE due to libiwinfo ABI change
Has anyone recently built an image and checked whether rssileds is now working?
// edit: ok this does probably not affect the naming of the interfaces, just resolves an issue introduced i the commit mentioned earlier (ABI change with new iinfo version).
iperf3 -c 10.20.10.212 -p 5201 -P 4 -t 60 -i 10:
Connecting to host 10.20.10.212, port 5201
[ 5] local 10.20.10.29 port 51043 connected to 10.20.10.212 port 5201
[ 7] local 10.20.10.29 port 51044 connected to 10.20.10.212 port 5201
[ 9] local 10.20.10.29 port 51045 connected to 10.20.10.212 port 5201
[ 11] local 10.20.10.29 port 51046 connected to 10.20.10.212 port 5201
[ ID] Interval Transfer Bitrate
[ 5] 0.00-10.00 sec 74.6 MBytes 62.6 Mbits/sec
[ 7] 0.00-10.00 sec 83.1 MBytes 69.7 Mbits/sec
[ 9] 0.00-10.00 sec 55.9 MBytes 46.9 Mbits/sec
[ 11] 0.00-10.00 sec 37.3 MBytes 31.3 Mbits/sec
[SUM] 0.00-10.00 sec 251 MBytes 211 Mbits/sec
- - - - - - - - - - - - - - - - - - - - - - - - -
[ 5] 10.00-20.00 sec 67.4 MBytes 56.5 Mbits/sec
[ 7] 10.00-20.00 sec 67.8 MBytes 56.9 Mbits/sec
[ 9] 10.00-20.00 sec 46.4 MBytes 38.9 Mbits/sec
[ 11] 10.00-20.00 sec 71.9 MBytes 60.3 Mbits/sec
[SUM] 10.00-20.00 sec 253 MBytes 213 Mbits/sec
- - - - - - - - - - - - - - - - - - - - - - - - -
[ 5] 20.00-30.00 sec 62.2 MBytes 52.2 Mbits/sec
[ 7] 20.00-30.00 sec 78.3 MBytes 65.7 Mbits/sec
[ 9] 20.00-30.00 sec 47.7 MBytes 40.0 Mbits/sec
[ 11] 20.00-30.00 sec 65.1 MBytes 54.6 Mbits/sec
[SUM] 20.00-30.00 sec 253 MBytes 212 Mbits/sec
- - - - - - - - - - - - - - - - - - - - - - - - -
[ 5] 30.00-40.00 sec 57.8 MBytes 48.5 Mbits/sec
[ 7] 30.00-40.00 sec 61.5 MBytes 51.6 Mbits/sec
[ 9] 30.00-40.00 sec 67.5 MBytes 56.7 Mbits/sec
[ 11] 30.00-40.00 sec 61.8 MBytes 51.8 Mbits/sec
[SUM] 30.00-40.00 sec 249 MBytes 209 Mbits/sec
- - - - - - - - - - - - - - - - - - - - - - - - -
[ 5] 40.00-50.00 sec 50.6 MBytes 42.5 Mbits/sec
[ 7] 40.00-50.00 sec 71.7 MBytes 60.1 Mbits/sec
[ 9] 40.00-50.00 sec 54.1 MBytes 45.4 Mbits/sec
[ 11] 40.00-50.00 sec 89.5 MBytes 75.1 Mbits/sec
[SUM] 40.00-50.00 sec 266 MBytes 223 Mbits/sec
- - - - - - - - - - - - - - - - - - - - - - - - -
[ 5] 50.00-60.00 sec 54.4 MBytes 45.6 Mbits/sec
[ 7] 50.00-60.00 sec 59.3 MBytes 49.8 Mbits/sec
[ 9] 50.00-60.00 sec 56.8 MBytes 47.7 Mbits/sec
[ 11] 50.00-60.00 sec 81.8 MBytes 68.6 Mbits/sec
[SUM] 50.00-60.00 sec 252 MBytes 212 Mbits/sec
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bitrate
[ 5] 0.00-60.00 sec 367 MBytes 51.3 Mbits/sec sender
[ 5] 0.00-60.05 sec 367 MBytes 51.2 Mbits/sec receiver
[ 7] 0.00-60.00 sec 422 MBytes 59.0 Mbits/sec sender
[ 7] 0.00-60.05 sec 421 MBytes 58.9 Mbits/sec receiver
[ 9] 0.00-60.00 sec 328 MBytes 45.9 Mbits/sec sender
[ 9] 0.00-60.05 sec 328 MBytes 45.8 Mbits/sec receiver
[ 11] 0.00-60.00 sec 407 MBytes 57.0 Mbits/sec sender
[ 11] 0.00-60.05 sec 407 MBytes 56.8 Mbits/sec receiver
[SUM] 0.00-60.00 sec 1.49 GBytes 213 Mbits/sec sender
[SUM] 0.00-60.05 sec 1.49 GBytes 213 Mbits/sec receiver
iperf Done.
iperf3 -c 10.20.10.212 -p 5201 -P 4 -t 60 -i 10 -R:
Connecting to host 10.20.10.212, port 5201
Reverse mode, remote host 10.20.10.212 is sending
[ 5] local 10.20.10.29 port 51071 connected to 10.20.10.212 port 5201
[ 7] local 10.20.10.29 port 51072 connected to 10.20.10.212 port 5201
[ 9] local 10.20.10.29 port 51073 connected to 10.20.10.212 port 5201
[ 11] local 10.20.10.29 port 51074 connected to 10.20.10.212 port 5201
[ ID] Interval Transfer Bitrate
[ 5] 0.00-10.00 sec 167 MBytes 140 Mbits/sec
[ 7] 0.00-10.00 sec 89.8 MBytes 75.3 Mbits/sec
[ 9] 0.00-10.00 sec 171 MBytes 144 Mbits/sec
[ 11] 0.00-10.00 sec 182 MBytes 153 Mbits/sec
[SUM] 0.00-10.00 sec 610 MBytes 512 Mbits/sec
- - - - - - - - - - - - - - - - - - - - - - - - -
[ 5] 10.00-20.00 sec 145 MBytes 122 Mbits/sec
[ 7] 10.00-20.00 sec 117 MBytes 98.5 Mbits/sec
[ 9] 10.00-20.00 sec 189 MBytes 158 Mbits/sec
[ 11] 10.00-20.00 sec 165 MBytes 139 Mbits/sec
[SUM] 10.00-20.00 sec 617 MBytes 517 Mbits/sec
- - - - - - - - - - - - - - - - - - - - - - - - -
[ 5] 20.00-30.00 sec 85.3 MBytes 71.6 Mbits/sec
[ 7] 20.00-30.00 sec 8.41 MBytes 7.06 Mbits/sec
[ 9] 20.00-30.00 sec 15.4 MBytes 12.9 Mbits/sec
[ 11] 20.00-30.00 sec 92.2 MBytes 77.4 Mbits/sec
[SUM] 20.00-30.00 sec 201 MBytes 169 Mbits/sec
- - - - - - - - - - - - - - - - - - - - - - - - -
[ 5] 30.00-40.00 sec 216 MBytes 181 Mbits/sec
[ 7] 30.00-40.00 sec 135 MBytes 113 Mbits/sec
[ 9] 30.00-40.00 sec 21.9 MBytes 18.4 Mbits/sec
[ 11] 30.00-40.00 sec 214 MBytes 179 Mbits/sec
[SUM] 30.00-40.00 sec 587 MBytes 493 Mbits/sec
- - - - - - - - - - - - - - - - - - - - - - - - -
[ 5] 40.00-50.00 sec 167 MBytes 140 Mbits/sec
[ 7] 40.00-50.00 sec 234 MBytes 196 Mbits/sec
[ 9] 40.00-50.00 sec 30.7 MBytes 25.7 Mbits/sec
[ 11] 40.00-50.00 sec 166 MBytes 139 Mbits/sec
[SUM] 40.00-50.00 sec 597 MBytes 501 Mbits/sec
- - - - - - - - - - - - - - - - - - - - - - - - -
[ 5] 50.00-60.00 sec 11.2 MBytes 9.42 Mbits/sec
[ 7] 50.00-60.00 sec 15.9 MBytes 13.4 Mbits/sec
[ 9] 50.00-60.00 sec 2.66 MBytes 2.23 Mbits/sec
[ 11] 50.00-60.00 sec 11.4 MBytes 9.54 Mbits/sec
[SUM] 50.00-60.00 sec 41.2 MBytes 34.5 Mbits/sec
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-60.00 sec 794 MBytes 111 Mbits/sec 2290 sender
[ 5] 0.00-60.00 sec 791 MBytes 111 Mbits/sec receiver
[ 7] 0.00-60.00 sec 605 MBytes 84.5 Mbits/sec 1885 sender
[ 7] 0.00-60.00 sec 601 MBytes 84.0 Mbits/sec receiver
[ 9] 0.00-60.00 sec 434 MBytes 60.7 Mbits/sec 2464 sender
[ 9] 0.00-60.00 sec 431 MBytes 60.2 Mbits/sec receiver
[ 11] 0.00-60.00 sec 835 MBytes 117 Mbits/sec 3116 sender
[ 11] 0.00-60.00 sec 831 MBytes 116 Mbits/sec receiver
[SUM] 0.00-60.00 sec 2.61 GBytes 373 Mbits/sec 9755 sender
[SUM] 0.00-60.00 sec 2.59 GBytes 371 Mbits/sec receiver
iperf Done.
1 Like
Was thinking about upgrading to newest master snapshot, as the buildbot has recently finished its build for the ramips/mt7621 target. @RolandoMagico, do you still experience scanning issues? - iwinfo: bump to latest git HEAD (2023-02-06) has been merged, which was supposed to fix
- Transmit Power incorrect in snapshot #11902 and
- ubus call iwinfo scan '{"device": "radio1"}' get wrong output #735
but dhewg still experienced issues with mt76: https://github.com/openwrt/openwrt/issues/11902#issuecomment-1416870934, so not sure, if it is actually advised to upgrade 
If we can still reproduce issues with newest snapshot, we probably should report them over there...
Wifi scanning is working with 2.4GHz and 5GHz in the latest snapshot
3 Likes
Can confirm. Retained my configuration and all is working fine so far. Gotta do some iperf tests tomorrow 
2 Likes
Today I got two slightly used DAP-X1860 from amazon for 30€ a piece. Flashed the latest snapshot, used Win11 edge, everything went smoothly. Using 802.11s meshes with both radios without hickups. Thank you all. Nice small router.
2 Likes
Just saw this post
D-Link DAP-X1860
--------------------------------------------------------
OpenWrt SNAPSHOT, r22071-3c66ac7e22
--------------------------------------------------------
root@AP_Varasto:~# iperf3 -s -D && iperf3 -c 127.0.0.1
Connecting to host 127.0.0.1, port 5201
[ 5] local 127.0.0.1 port 47342 connected to 127.0.0.1 port 5201
[ ID] Interval Transfer Bitrate Retr Cwnd
[ 5] 0.00-1.01 sec 76.1 MBytes 635 Mbits/sec 0 1023 KBytes
[ 5] 1.01-2.01 sec 76.1 MBytes 633 Mbits/sec 0 1023 KBytes
[ 5] 2.01-3.00 sec 75.0 MBytes 637 Mbits/sec 0 1023 KBytes
[ 5] 3.00-4.00 sec 65.0 MBytes 544 Mbits/sec 0 1023 KBytes
[ 5] 4.00-5.01 sec 68.8 MBytes 572 Mbits/sec 0 1023 KBytes
[ 5] 5.01-6.01 sec 76.0 MBytes 639 Mbits/sec 0 1023 KBytes
[ 5] 6.01-7.01 sec 78.8 MBytes 658 Mbits/sec 0 1023 KBytes
[ 5] 7.01-8.01 sec 72.4 MBytes 611 Mbits/sec 0 1023 KBytes
[ 5] 8.01-9.01 sec 67.5 MBytes 562 Mbits/sec 0 1023 KBytes
[ 5] 9.01-10.01 sec 67.5 MBytes 572 Mbits/sec 0 1023 KBytes
[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-10.01 sec 723 MBytes 606 Mbits/sec 0 sender
[ 5] 0.00-10.01 sec 723 MBytes 606 Mbits/sec receiver
Does this mean that the dap x1860 is bottlenecked by RAM?
This looks like the same result that other devices with MT7621 have achieved, not sure if iperf3 is indeed running single-threaded as some suggested, but it's a lot faster than qca9563 for example.
It looks like iperf3 uses mostly one processor which peeks.
1 Like
If somebody is looking for this device, it’s again available for 15€ at Mediamarkt/Saturn in Germany
5 Likes
I just installed the latest snapshot and it's working well, the only thing I miss is 160MHz support. Is it theoretically possible?
no not possible
Since this type of information is indeed missing, maybe we should add further information to the table of hardware. Docs are here about how to do it.