Dynalink DL-WRX36 Askey RT5010W IPQ8072A technical discussion

For Developers
2311

To clarify- for $80 with the hardware WRX36 offers, buy it. The issue is with the openwrt software and ath11k driver, they should be straighthen out eventually. The thing is new so we need more users and feedback.

For now unless you're on gigabit and ethernet hardwired I wouldn't use it as a primary wifi device. I myself am using it for tinkering as a hobby, with nightly 'main' builds, which also contribute to the 'wild' performance experience, as expected. Sorry for the confusion of my complaints, if any:D

1 Like
2312

You know what we really need, somewhere to post recomended settings for stability of WiFi.

Could have saved a lot of time in this regard had we a sticky somewhere. I've tried it all now, I'm sure I could contribute meaningfully in this regard.

I just discovered that wifi client isolation reliably brings the WiFi down every time... took me a few hours though to come to this conclusion.

The script I had posted earlier to reboot the router, I've updated it. Now have it writing to the system log as well every 60 seconds. I'm updating it as well to make it more reliable in detecting when the WiFi is down.

But we really should at least have a sticky if possible or recomeded WiFi settings for stability.

Ive got my custom builds going now for this router. Any value in downgrading the kernel at all for greater stability? Anyone have any feedback in this regard?

1 Like
2314

Probably already answered but why can I not set my power to 30 dB, it should be allowed.

Is the GUI just misreporting?

On casual comparison with my EA8500 which reports 30 dB, the range does not seem different (and I know that the client also plays its part) throughput (iperf3) of the DL-WRX36 is higher though (AX vs AC)

iw list
                Frequencies:
                        * 5180 MHz [36] (30.0 dBm)
                        * 5200 MHz [40] (30.0 dBm)
                        * 5220 MHz [44] (30.0 dBm)
                        * 5240 MHz [48] (30.0 dBm)
                        * 5260 MHz [52] (24.0 dBm)
                        * 5280 MHz [56] (24.0 dBm)
                        * 5300 MHz [60] (24.0 dBm)
                        * 5320 MHz [64] (24.0 dBm)
                        * 5500 MHz [100] (24.0 dBm)
                        * 5520 MHz [104] (24.0 dBm)
                        * 5540 MHz [108] (24.0 dBm)
                        * 5560 MHz [112] (24.0 dBm)
                        * 5580 MHz [116] (24.0 dBm)
                        * 5600 MHz [120] (24.0 dBm)
                        * 5620 MHz [124] (24.0 dBm)
                        * 5640 MHz [128] (24.0 dBm)
                        * 5660 MHz [132] (24.0 dBm)
                        * 5680 MHz [136] (24.0 dBm)
                        * 5700 MHz [140] (24.0 dBm)
                        * 5720 MHz [144] (24.0 dBm)
                        * 5745 MHz [149] (30.0 dBm)
                        * 5765 MHz [153] (30.0 dBm)
                        * 5785 MHz [157] (30.0 dBm)
                        * 5805 MHz [161] (30.0 dBm)
                        * 5825 MHz [165] (30.0 dBm)
                        * 5845 MHz [169] (disabled)
                        * 5865 MHz [173] (disabled)
                        * 5885 MHz [177] (disabled)

afbeelding
afbeelding1634×539 50.8 KB

I know @robimarko worked on it and I checked and this patch is still in place

Any other thoughts?

2315

Its a known issue for this board, its capped at 17dBm due to a BDF setting.

I have no idea how to properly fix it, nor is there a need to fix it and there is just amplification out of FW control so they deliberately scaled it down.

3 Likes
2316

I guess this explains the crappy wifi performance/coverage...

1 Like
2317

Of course. I've shared my benchmark results in this thread already - just do a search on my posts. I was careful to keep the comparison as apples to apples as possible since my goal was to select the best of two options (DL-WRX36 or RT3200) for my second floor AP.

1 Like
2318

Great I can use those to compare with my own.

2319

Thing's are stable with the 2.4Ghz radio disable, wifi hasn't dropped at all overnight. Will continue to monitor throughout the day.

2320

Try switching the 2.4 radio to N (instead of AX) if not yet, in addition to enable multicast-to-unicast.

1 Like
2321

Use country: US, this will give you 29dBm for both 5 & 2G...
the Frequencies you posted are similar...

root@OpenWrt:~# iw reg get
global
country US: DFS-FCC
        (902 - 904 @ 2), (N/A, 30), (N/A)
        (904 - 920 @ 16), (N/A, 30), (N/A)
        (920 - 928 @ 8), (N/A, 30), (N/A)
        (2400 - 2472 @ 40), (N/A, 30), (N/A)
        (5150 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW
        (5250 - 5350 @ 80), (N/A, 24), (0 ms), DFS, AUTO-BW
        (5470 - 5730 @ 160), (N/A, 24), (0 ms), DFS
        (5730 - 5850 @ 80), (N/A, 30), (N/A), AUTO-BW
        (5850 - 5895 @ 40), (N/A, 27), (N/A), NO-OUTDOOR, AUTO-BW, PASSIVE-SCAN
        (5925 - 7125 @ 320), (N/A, 12), (N/A), NO-OUTDOOR, PASSIVE-SCAN
        (57240 - 71000 @ 2160), (N/A, 40), (N/A)

phy#1 (self-managed)
country US: DFS-FCC
        (2402 - 2472 @ 40), (6, 30), (N/A)
        (5170 - 5250 @ 80), (6, 30), (N/A), AUTO-BW
        (5250 - 5330 @ 80), (6, 24), (0 ms), DFS, AUTO-BW
        (5490 - 5730 @ 160), (6, 24), (0 ms), DFS, AUTO-BW
        (5735 - 5895 @ 160), (6, 30), (N/A), AUTO-BW

phy#0 (self-managed)
country US: DFS-FCC
        (2402 - 2472 @ 40), (6, 30), (N/A)
        (5170 - 5250 @ 80), (6, 30), (N/A), AUTO-BW
        (5250 - 5330 @ 80), (6, 24), (0 ms), DFS, AUTO-BW
        (5490 - 5730 @ 160), (6, 24), (0 ms), DFS, AUTO-BW
        (5735 - 5895 @ 160), (6, 30), (N/A), AUTO-BW

root@OpenWrt:~# iwinfo phy0 txpower
   0 dBm (   1 mW)
   1 dBm (   1 mW)
   2 dBm (   1 mW)
   3 dBm (   1 mW)
   4 dBm (   2 mW)
   5 dBm (   3 mW)
   6 dBm (   3 mW)
   7 dBm (   5 mW)
   8 dBm (   6 mW)
   9 dBm (   7 mW)
  10 dBm (  10 mW)
  11 dBm (  12 mW)
  12 dBm (  15 mW)
  13 dBm (  19 mW)
  14 dBm (  25 mW)
  15 dBm (  31 mW)
  16 dBm (  39 mW)
  17 dBm (  50 mW)
  18 dBm (  63 mW)
  19 dBm (  79 mW)
  20 dBm ( 100 mW)
  21 dBm ( 125 mW)
  22 dBm ( 158 mW)
  23 dBm ( 199 mW)
  24 dBm ( 251 mW)
  25 dBm ( 316 mW)
  26 dBm ( 398 mW)
  27 dBm ( 501 mW)
  28 dBm ( 630 mW)
* 29 dBm ( 794 mW)
  30 dBm (1000 mW)
root@OpenWrt:~# iwinfo phy1 txpower
   0 dBm (   1 mW)
   1 dBm (   1 mW)
   2 dBm (   1 mW)
   3 dBm (   1 mW)
   4 dBm (   2 mW)
   5 dBm (   3 mW)
   6 dBm (   3 mW)
   7 dBm (   5 mW)
   8 dBm (   6 mW)
   9 dBm (   7 mW)
  10 dBm (  10 mW)
  11 dBm (  12 mW)
  12 dBm (  15 mW)
  13 dBm (  19 mW)
  14 dBm (  25 mW)
  15 dBm (  31 mW)
  16 dBm (  39 mW)
  17 dBm (  50 mW)
  18 dBm (  63 mW)
  19 dBm (  79 mW)
  20 dBm ( 100 mW)
  21 dBm ( 125 mW)
  22 dBm ( 158 mW)
  23 dBm ( 199 mW)
  24 dBm ( 251 mW)
  25 dBm ( 316 mW)
  26 dBm ( 398 mW)
  27 dBm ( 501 mW)
  28 dBm ( 630 mW)
* 29 dBm ( 794 mW)
  30 dBm (1000 mW)
1 Like
2322

If I didn't also enable multicast-to-unicast on 2.4G, wifi device would disconnect then won't reconnect automatically.

1 Like
2323

So I got this router to play around with openwrt until I can figure out how to get openwrt on my MR7500 and while it is stable on most things on wifi it is a trainwreck, things keep disconnecting or avoiding 5ghz due to how unstable it is, with or without the multicast option.
I get less speed on it on 160 mhz than I get on my mr7500 which has the same chip on 80 mhz in the 5ghz band, less than half, and 80mhz I get 40 mhz or less results of my my mr7500.

on wired I see that the sqm isn't doing too well which is bizarre, the MR7500 as one of linksys undocumented features if you turn on priority(qos) without assigning any client as the top one it first does regular qos and if bandwith gets close to being full use uses fq_codel and it works great in both wifi and ethernet, it is the same chip!

----- QoS info -------

  • syscfg QoS Info
    QoSMacAddrCount=0
    QoSUserDefinedPolicyCount=0
    qos_auto_prioritize_enable=0
    qos_enable=1
    wan_download_speed=940.360000
    wan_upload_speed=940160.000000
  • sysevent QoS info
    committed_bitrate is
  • QoS queues
    -> queues on eth4
    class mq :1 root
    Sent 1250005554 bytes 983008 pkt (dropped 0, overlimits 0 requeues 0)
    backlog 0b 0p requeues 0
    class mq :2 root
    Sent 377303493 bytes 323150 pkt (dropped 0, overlimits 0 requeues 0)
    backlog 0b 0p requeues 0
    class mq :3 root
    Sent 1447762173 bytes 1032039 pkt (dropped 0, overlimits 0 requeues 0)
    backlog 0b 0p requeues 0
    class mq :4 root
    Sent 470565199 bytes 354332 pkt (dropped 0, overlimits 0 requeues 93)
    backlog 0b 0p requeues 93
    class fq_codel :268 parent none
    (dropped 0, overlimits 0 requeues 0)
    backlog 0b 0p requeues 0
    deficit -7570 count 0 lastcount 0 ldelay 209us
    -> queues on br0

I have no idea why this thing is doing so bad versus my mr7500 with same hardware minus the 6ghz. I do wish I could get to building openwrt to my mr7500 after this.

2325

In my case without the muliti-cast option enabled, the WiFi is unpredictable.

I've got 10 WiFi devices connected simultaneously ATM, two on 2G, the rest on 5G, none of which are 160Mhz.

Using AX channel 149 @ 80MHz, and AX & 20MHz for 2.4G, and manually upgraded the wireless driver WLAN.HK.2.9.0.1-01862 and have not had any issues since moving to 23.05.0-rc3, 12 days ago.

1 Like
2326

Okay thanks mate. I've don't that and things are stable. I did try that last night (I thought)

Woo hoo, it's all working well now! Great router!!

2 Likes
2327

Good grief... both radios have gone down again on all 3 routers... I suspect perhaps issue exasperated by 802.11r as they all go down at the same time....(**But, I am only running 802.11r on 5Ghz, not 2.4Ghz.) perhaps even isolated to 802.11r use case scenarios only? But my WiFi Smart Switches/Power Points seem to be randomly knocking both radios down if 2.4Ghz radio is enabled (this is happening BTW when they are not even connected to the network...)

If I disable the 2.4Ghz radio completely on the router than the WiFi 6 radio stays up 24hrs+.

Anyways, I bought the router for WiFi 6 mainly. I do have an existing solution for 2.4Gh on other hardware. so.... not the end of the world. But, I do hope things improve. For now however, I'm going to disable 2.4Ghz entirely.

Sat Sep 9 20:33:36 2023 kern.warn kernel: [54201.404723] ath11k_warn: 104 callbacks suppressed Sat Sep 9 20:33:36 2023 kern.warn kernel: [54201.404741] ath11k c000000.wifi: failed to send WMI_PDEV_BSS_CHAN_INFO_REQUEST cmd Sat Sep 9 20:33:36 2023 kern.warn kernel: [54201.408427] ath11k c000000.wifi: failed to send pdev bss chan info request Sat Sep 9 20:33:36 2023 kern.warn kernel: [54201.416127] ath11k c000000.wifi: failed to send WMI_PDEV_SET_PARAM cmd Sat Sep 9 20:33:36 2023 kern.warn kernel: [54201.422749] ath11k c000000.wifi: Failed to set beacon mode for VDEV: 0 Sat Sep 9 20:33:36 2023 kern.warn kernel: [54201.429316] ath11k c000000.wifi: failed to send WMI_BCN_TMPL_CMDID Sat Sep 9 20:33:36 2023 kern.warn kernel: [54201.435796] ath11k c000000.wifi: failed to submit beacon template command: -108 Sat Sep 9 20:33:36 2023 kern.warn kernel: [54201.441931] ath11k c000000.wifi: failed to update bcn template: -108 Sat Sep 9 20:33:36 2023 kern.warn kernel: [54201.449177] ath11k c000000.wifi: failed to send WMI_VDEV_SET_PARAM_CMDID Sat Sep 9 20:33:36 2023 kern.warn kernel: [54201.455763] ath11k c000000.wifi: failed to set BA BUFFER SIZE 256 for vdev: 0 Sat Sep 9 20:33:36 2023 kern.warn kernel: [54201.462426] ath11k c000000.wifi: failed to send WMI_VDEV_SET_PARAM_CMDID Sat Sep 9 20:33:42 2023 kern.warn kernel: [54207.473312] ath11k_warn: 104 callbacks suppressed Sat Sep 9 20:33:42 2023 kern.warn kernel: [54207.473331] ath11k c000000.wifi: failed to send WMI_PDEV_BSS_CHAN_INFO_REQUEST cmd Sat Sep 9 20:33:42 2023 kern.warn kernel: [54207.477017] ath11k c000000.wifi: failed to send pdev bss chan info request Sat Sep 9 20:33:42 2023 kern.warn kernel: [54207.484770] ath11k c000000.wifi: failed to send WMI_PDEV_SET_PARAM cmd Sat Sep 9 20:33:42 2023 kern.warn kernel: [54207.491342] ath11k c000000.wifi: Failed to set beacon mode for VDEV: 0 Sat Sep 9 20:33:42 2023 kern.warn kernel: [54207.497909] ath11k c000000.wifi: failed to send WMI_BCN_TMPL_CMDID Sat Sep 9 20:33:42 2023 kern.warn kernel: [54207.504392] ath11k c000000.wifi: failed to submit beacon template command: -108 Sat Sep 9 20:33:42 2023 kern.warn kernel: [54207.510523] ath11k c000000.wifi: failed to update bcn template: -108 Sat Sep 9 20:33:42 2023 kern.warn kernel: [54207.517761] ath11k c000000.wifi: failed to send WMI_VDEV_SET_PARAM_CMDID Sat Sep 9 20:33:42 2023 kern.warn kernel: [54207.524357] ath11k c000000.wifi: failed to set BA BUFFER SIZE 256 for vdev: 0 Sat Sep 9 20:33:42 2023 kern.warn kernel: [54207.531018] ath11k c000000.wifi: failed to send WMI_VDEV_SET_PARAM_CMDID Sat Sep 9 20:33:48 2023 kern.warn kernel: [54213.543902] ath11k_warn: 104 callbacks suppressed Sat Sep 9 20:33:48 2023 kern.warn kernel: [54213.543919] ath11k c000000.wifi: failed to send WMI_PDEV_BSS_CHAN_INFO_REQUEST cmd Sat Sep 9 20:33:48 2023 kern.warn kernel: [54213.547605] ath11k c000000.wifi: failed to send pdev bss chan info request Sat Sep 9 20:33:48 2023 kern.warn kernel: [54213.555337] ath11k c000000.wifi: failed to send WMI_PDEV_SET_PARAM cmd Sat Sep 9 20:33:48 2023 kern.warn kernel: [54213.561929] ath11k c000000.wifi: Failed to set beacon mode for VDEV: 0 Sat Sep 9 20:33:48 2023 kern.warn kernel: [54213.568496] ath11k c000000.wifi: failed to send WMI_BCN_TMPL_CMDID Sat Sep 9 20:33:48 2023 kern.warn kernel: [54213.574976] ath11k c000000.wifi: failed to submit beacon template command: -108 Sat Sep 9 20:33:48 2023 kern.warn kernel: [54213.581110] ath11k c000000.wifi: failed to update bcn template: -108 Sat Sep 9 20:33:48 2023 kern.warn kernel: [54213.588344] ath11k c000000.wifi: failed to send WMI_VDEV_SET_PARAM_CMDID Sat Sep 9 20:33:48 2023 kern.warn kernel: [54213.594942] ath11k c000000.wifi: failed to set BA BUFFER SIZE 256 for vdev: 0 Sat Sep 9 20:33:48 2023 kern.warn kernel: [54213.601605] ath11k c000000.wifi: failed to send WMI_VDEV_SET_PARAM_CMDID Sat Sep 9 20:33:54 2023 kern.warn kernel: [54219.614598] ath11k_warn: 104 callbacks suppressed Sat Sep 9 20:33:54 2023 kern.warn kernel: [54219.614617] ath11k c000000.wifi: failed to send WMI_PDEV_BSS_CHAN_INFO_REQUEST cmd Sat Sep 9 20:33:54 2023 kern.warn kernel: [54219.618306] ath11k c000000.wifi: failed to send pdev bss chan info request Sat Sep 9 20:33:54 2023 kern.warn kernel: [54219.626039] ath11k c000000.wifi: failed to send WMI_PDEV_SET_PARAM cmd Sat Sep 9 20:33:54 2023 kern.warn kernel: [54219.632628] ath11k c000000.wifi: Failed to set beacon mode for VDEV: 0 Sat Sep 9 20:33:54 2023 kern.warn kernel: [54219.639195] ath11k c000000.wifi: failed to send WMI_BCN_TMPL_CMDID Sat Sep 9 20:33:54 2023 kern.warn kernel: [54219.645677] ath11k c000000.wifi: failed to submit beacon template command: -108 Sat Sep 9 20:33:54 2023 kern.warn kernel: [54219.651810] ath11k c000000.wifi: failed to update bcn template: -108 Sat Sep 9 20:33:54 2023 kern.warn kernel: [54219.659046] ath11k c000000.wifi: failed to send WMI_VDEV_SET_PARAM_CMDID Sat Sep 9 20:33:54 2023 kern.warn kernel: [54219.665645] ath11k c000000.wifi: failed to set BA BUFFER SIZE 256 for vdev: 0 Sat Sep 9 20:33:54 2023 kern.warn kernel: [54219.672305] ath11k c000000.wifi: failed to send WMI_VDEV_SET_PARAM_CMDID Sat Sep 9 20:34:00 2023 kern.warn kernel: [54225.681318] ath11k_warn: 104 callbacks suppressed Sat Sep 9 20:34:00 2023 kern.warn kernel: [54225.681335] ath11k c000000.wifi: failed to send WMI_PDEV_BSS_CHAN_INFO_REQUEST cmd Sat Sep 9 20:34:00 2023 kern.warn kernel: [54225.685041] ath11k c000000.wifi: failed to send pdev bss chan info request Sat Sep 9 20:34:00 2023 kern.warn kernel: [54225.692759] ath11k c000000.wifi: failed to send WMI_PDEV_SET_PARAM cmd Sat Sep 9 20:34:00 2023 kern.warn kernel: [54225.699385] ath11k c000000.wifi: Failed to set beacon mode for VDEV: 0 Sat Sep 9 20:34:00 2023 kern.warn kernel: [54225.705905] ath11k c000000.wifi: failed to send WMI_BCN_TMPL_CMDID Sat Sep 9 20:34:00 2023 kern.warn kernel: [54225.712363] ath11k c000000.wifi: failed to submit beacon template command: -108 Sat Sep 9 20:34:00 2023 kern.warn kernel: [54225.718546] ath11k c000000.wifi: failed to update bcn template: -108 Sat Sep 9 20:34:00 2023 kern.warn kernel: [54225.725776] ath11k c000000.wifi: failed to send WMI_VDEV_SET_PARAM_CMDID Sat Sep 9 20:34:00 2023 kern.warn kernel: [54225.732330] ath11k c000000.wifi: failed to set BA BUFFER SIZE 256 for vdev: 0 Sat Sep 9 20:34:00 2023 kern.warn kernel: [54225.739040] ath11k c000000.wifi: failed to send WMI_VDEV_SET_PARAM_CMDID Sat Sep 9 20:34:06 2023 kern.warn kernel: [54231.751860] ath11k_warn: 104 callbacks suppressed

2328

That really sucks, man, I feel for you. I'm doing HT80 802.11ax psk2+ccmp with 3ms latency at ~490/420 of the ISP's 300-500 on my WRX36 (wired through an old trusty TL-WR1043ND). Granted, I'm not using any sort of traffic shaping. Aaaaand I'm still on stock. Waiting for OW to stabilize, having read this thread.

Edit: for clarification, the latency/bandwidth numbers is my laptop conversing with the server hosted by my ISP that speedtest(dot)net uses. Connections to other peers are likely to perform worse.

2329

I am running 23.05. firmware 1835, using 80 Mhz AX on channel 36 my wifi is stable runs for more than a week now, with better range and throughput than my Linksys EA8500 but that is an older AC router.

I just use more or less standard wifi settings other than setting my country code (PA) and highest possible TX power, I do not have Multicast to Unicast enabled but have only three modern Samsung clients running on the 5 GHz band, so probably not a representative sample.

1 Like
2330

thank you! I updated the driver on a new snapshot and it runs flawless now

1 Like
2331

Good to hear!

I have no issues with WiFi 5Ghz either, just 2.4Ghz

2332

Tank you, I'll give it a go.

Has the updated driver been merged yet?