Dynalink DL-WRX36 Askey RT5010W IPQ8072A technical discussion

Just adding a report that I've been running a WRX-36 for ~2.5 days as an AP on SNAPSHOT r23580-b993a00b82 with WLAN.HK.2.9.0.1-01837-QCAHKSWPL_SILICONZ-1. No issues noted.

Nothing complicated in the setup. A few VLANs with SSID's for each and our home NAS connected to an Ethernet port. No noticeable change in performance for the better or worse.

I compared 802.11ax 80MHz throughput with iperf3 against an identically configured and placed RT3200 (both AP's using Channel 149) at longish range (AP located a floor above the client) and the RT3200 still performed a bit better, consistent with my past experience.

1 Like

I tried r23583-58c498247b recently too w/ an apple 13 pro. iperf3 speeds bounced around quite a bit while in the same room with AP. HE modulation level shifts up and down constantly.

Sounds similar to my experience.

DL-WRX36 wireless iperf3 throughput to an intel ax200 2x2 desktop a floor below with 80MHz ax connecting with HE MCS 5/6 up/down varied within a wide range of 90-150/65-190 Mbps up/down with more retries than usual. With the Belkin RT3200 swapped into the same AP location I see more consistent 160/350 up/down throughput with few to zero retries, also connecting with HE MCS 5/6 up/down.

Debug logs:

  1. wifi up
[ 5705.071309] ath11k c000000.wifi: txpower from firmware NaN, reported -2147483648 dBm
[ 5705.071350] ath11k c000000.wifi: txpower from firmware NaN, reported -2147483648 dBm
[ 5705.083249] ath11k c000000.wifi: txpower from firmware NaN, reported -2147483648 dBm
[ 5705.083343] ath11k c000000.wifi: txpower from firmware NaN, reported -2147483648 dBm
[ 5705.083825] ath11k c000000.wifi: txpower from firmware NaN, reported -2147483648 dBm
[ 5705.084330] ath11k c000000.wifi: txpower from firmware NaN, reported -2147483648 dBm
[ 5705.084629] ath11k c000000.wifi: mac add interface id 0 type 1 subtype 0 map 3ffffffff
[ 5705.084653] ath11k c000000.wifi: vdev a4:97:33:df:a3:38 created, vdev_id 0
[ 5705.114670] ath11k c000000.wifi: mac stop soc 11d scan
[ 5705.114740] ath11k c000000.wifi: defer protection mode setup, vdev is not ready yet
[ 5705.114751] ath11k c000000.wifi: Set slottime: 1 for VDEV: 0
[ 5705.114765] ath11k c000000.wifi: Set preamble: 1 for VDEV: 0
[ 5705.115935] br-lan: port 5(phy0-ap0) entered blocking state
[ 5705.115972] br-lan: port 5(phy0-ap0) entered disabled state
[ 5705.120525] device phy0-ap0 entered promiscuous mode
[ 5705.125985] br-lan: port 5(phy0-ap0) entered blocking state
[ 5705.131080] br-lan: port 5(phy0-ap0) entered forwarding state
[ 5705.136872] br-lan: port 5(phy0-ap0) entered disabled state
[ 5705.530150] ath11k c000000.wifi: txpower from firmware 48, reported 24 dBm
[ 5705.530393] ath11k c000000.wifi: mac chanctx add freq 5500 width 3 ptr 00000000f0a0b2d2
[ 5705.530411] ath11k c000000.wifi: mac chanctx assign ptr 00000000f0a0b2d2 vdev_id 0
[ 5705.530423] ath11k c000000.wifi: mac vdev 0 start center_freq 5500 phymode 11ax-he80
[ 5705.547404] ath11k c000000.wifi: vdev a4:97:33:df:a3:38 started, vdev_id 0
[ 5705.547426] ath11k c000000.wifi: mac vdev_id 0 txpower 30
[ 5705.547436] ath11k c000000.wifi: txpower to set in hw 30
[ 5705.547449] ath11k c000000.wifi: mac chanctx change freq 5500 width 3 ptr 00000000f0a0b2d2 changed 2
[ 5705.547462] ath11k c000000.wifi: mac chanctx change freq 5500 width 3 ptr 00000000f0a0b2d2 changed 4
[ 5705.547788] ath11k c000000.wifi: vdev a4:97:33:df:a3:38 stopped, vdev_id 0
[ 5705.547800] ath11k c000000.wifi: mac vdev 0 start center_freq 5500 phymode 11ax-he80
[ 5705.563283] ath11k c000000.wifi: vdev a4:97:33:df:a3:38 started, vdev_id 0
[ 5705.563309] ath11k c000000.wifi: Beacon interval: 100 set for VDEV: 0
[ 5705.563322] ath11k c000000.wifi: Set staggered beacon mode for VDEV: 0
[ 5705.563347] ath11k c000000.wifi: Set BA BUFFER SIZE 256 for VDEV: 0
[ 5705.563358] ath11k c000000.wifi: DTIM period: 2 set for VDEV: 0
[ 5705.563381] ath11k c000000.wifi: mac vdev 0 up
[ 5705.563389] ath11k c000000.wifi: mac vdev_id 0 txpower 30
[ 5705.563397] ath11k c000000.wifi: txpower to set in hw 30
[ 5705.563409] ath11k c000000.wifi: mac obss pd sr_ctrl 3 non_srg_thres 0 srg_max 0
[ 5705.563430] ath11k c000000.wifi: bss color param 0xa000000 set on vdev 0
[ 5705.563484] IPv6: ADDRCONF(NETDEV_CHANGE): phy0-ap0: link becomes ready
[ 5705.563651] br-lan: port 5(phy0-ap0) entered blocking state
[ 5705.568926] br-lan: port 5(phy0-ap0) entered forwarding state
[ 5705.574672] ath11k c000000.wifi: Set CTS prot: 0 for VDEV: 0
[ 5705.574688] ath11k c000000.wifi: Set slottime: 2 for VDEV: 0
[ 5705.574699] ath11k c000000.wifi: Set preamble: 2 for VDEV: 0
[ 5705.574853] ath11k c000000.wifi: mac tx mgmt frame, buf id 0
[ 5705.574871] ath11k c000000.wifi: mac tx mgmt frame, vdev_id 0
  1. iwinfo
[ 5708.129682] ath11k c000000.wifi: txpower from firmware 48, reported 24 dBm
[ 5708.130652] ath11k c000000.wifi: txpower from firmware 48, reported 24 dBm
[ 5708.131296] ath11k c000000.wifi: txpower from firmware 48, reported 24 dBm
[ 5708.131869] ath11k c000000.wifi: txpower from firmware 48, reported 24 dBm
[ 5708.132400] ath11k c000000.wifi: txpower from firmware 48, reported 24 dBm
[ 5708.132943] ath11k c000000.wifi: txpower from firmware 48, reported 24 dBm
[ 5708.133471] ath11k c000000.wifi: txpower from firmware 48, reported 24 dBm
[ 5708.134492] ath11k c000000.wifi: txpower from firmware 48, reported 24 dBm
[ 5708.135282] ath11k c000000.wifi: txpower from firmware 48, reported 24 dBm
[ 5708.137168] ath11k c000000.wifi: txpower from firmware 48, reported 24 dBm
[ 5708.138676] ath11k c000000.wifi: txpower from firmware 48, reported 24 dBm
[ 5708.139209] ath11k c000000.wifi: txpower from firmware 48, reported 24 dBm
[ 5708.145733] ath11k c000000.wifi: txpower from firmware NaN, reported -2147483648 dBm
[ 5708.146715] ath11k c000000.wifi: txpower from firmware NaN, reported -2147483648 dBm
[ 5708.147140] ath11k c000000.wifi: txpower from firmware NaN, reported -2147483648 dBm
[ 5708.147495] ath11k c000000.wifi: txpower from firmware NaN, reported -2147483648 dBm
[ 5708.147811] ath11k c000000.wifi: txpower from firmware NaN, reported -2147483648 dBm
[ 5708.148385] ath11k c000000.wifi: txpower from firmware NaN, reported -2147483648 dBm
[ 5708.148700] ath11k c000000.wifi: txpower from firmware NaN, reported -2147483648 dBm
[ 5708.149268] ath11k c000000.wifi: txpower from firmware NaN, reported -2147483648 dBm
[ 5708.149575] ath11k c000000.wifi: txpower from firmware NaN, reported -2147483648 dBm
[ 5708.149838] ath11k c000000.wifi: txpower from firmware NaN, reported -2147483648 dBm
[ 5708.150190] ath11k c000000.wifi: txpower from firmware NaN, reported -2147483648 dBm
[ 5708.150463] ath11k c000000.wifi: txpower from firmware NaN, reported -2147483648 dBm
[ 5708.151955] ath11k c000000.wifi: txpower from firmware NaN, reported -2147483648 dBm
[ 5708.152890] ath11k c000000.wifi: txpower from firmware NaN, reported -2147483648 dBm
[ 5708.153236] ath11k c000000.wifi: txpower from firmware NaN, reported -2147483648 dBm
[ 5708.153496] ath11k c000000.wifi: txpower from firmware NaN, reported -2147483648 dBm
[ 5711.535514] ath11k c000000.wifi: Set staggered beacon mode for VDEV: 0
[ 5711.535559] ath11k c000000.wifi: Set BA BUFFER SIZE 256 for VDEV: 0
[ 5711.535570] ath11k c000000.wifi: DTIM period: 2 set for VDEV: 0
[ 5711.535633] ath11k c000000.wifi: Set CTS prot: 0 for VDEV: 0
[ 5711.535646] ath11k c000000.wifi: Set preamble: 2 for VDEV: 0

Is it possible that WMI_PDEV_PARAM_TXPOWER_LIMIT5G is not setting the value correctly?
Here is a patch where in the case of 6GHz txpower is set with WMI_VDEV_SET_TPC_POWER_CMDID: https://patchwork.kernel.org/project/linux-wireless/patch/20220913051518.23051-14-quic_wgong@quicinc.com/

2 Likes

It looks like you can no longer run split country codes on the two radios. If they don't match the radios randomly go down.

anyone tried to put a fan in this router, what fan do you use?

How hot does it run?

mine is running 50-60 degrees

Mine is running well below 60 Degrees Celsius so that should be fine, no need to put a fan on it I think.

It would be nice if the commit with the newer firmware WLAN.HK.2.9.0.1-01837-QCAHKSWPL_SILICONZ-1 could also be backported to 23.05

No need for a fan on this router. If you look at the internal images provided on the device's wiki, you'll see the generous heatsink that is pre-installed from the factory. Normal temps should be 60-degreesC or less depending on ambient. Maybe more if there's a sustained load on the processors. I had a Zyxel NBG6817 that would run around 90-degreesC even during idle... so that one I did add a fan platform below which helped immensely.

2 Likes

Help, when doing the ubiformat I receive this error only for mtd20:

ubiformat: error!: please, first detach mtd20 (/dev/mtd20) from ubi0

search this thread for first detach.

Turned out I was referencing generic snapshots instead of Qualcomm. Everything went without a hitch otherwise, well until I rebooted it. Now it's just blinking purple every two seconds with no connection. Unsure what I could have done wrong, I made sure I understood each step and executed it well aside from the Qualcomm slipup. Now what to do? F.

What did you exactly?

I think your router is soft-bricked.

To undo this you need a serial console on the router. Consisting of a USB Apdater (in my case ch340g) and a cable (4-pin JST-PH with 2 mm pin spacing), nothing needs to be soldered.

All in one picture:
https://forum.openwrt.org/uploads/default/original/3X/d/3/d3914562aff0408c71a3858eb8246ec49e16f2d4.jpeg

1 Like

It had to have been from typing generic instead of Qualcomm, which I thought I corrected but the damage must have been done. I bought this last night, but looking at your picture the jumpers might not fit.

Quoting from the Openwrt Wiki:
"The connector is a 4-pin JST-PH with 2 mm pin spacing."
A standard jumper connector has 2.54 mm. If I am not wrong.

Yep, the standard/normal patch cable ends do not fit into the connector. I tried :frowning:

One needs a 4-pin JST-PH connector with 2 mm pin spacing.

I heard that an old flopy disk connector would fit?

You mean the 3.5 inch floppy power connector?
Likely not, too wide spacing...