Dynalink DL-WRX36 Askey RT5010W IPQ8072A technical discussion

can't replicate any of these issues ... the cac_time is just over 1m

Channel 128 160mhz

Mon Oct  2 06:33:47 2023 daemon.notice hostapd: phy0-ap0: DFS-CAC-START freq=5640 chan=128 sec_chan=-1, width=2, seg0=114, seg1=0, cac_time=60s
Mon Oct  2 06:33:47 2023 kern.info kernel: [  450.317396] br-lan: port 6(phy0-ap0) entered disabled state
Mon Oct  2 06:33:48 2023 daemon.notice hostapd: phy0-ap0: DFS-PRE-CAC-EXPIRED freq=5260 ht_enabled=0 chan_offset=0 chan_width=0 cf1=5260 cf2=0
Mon Oct  2 06:33:48 2023 daemon.notice hostapd: phy0-ap0: DFS-PRE-CAC-EXPIRED freq=5280 ht_enabled=0 chan_offset=0 chan_width=0 cf1=5280 cf2=0
Mon Oct  2 06:33:48 2023 daemon.notice hostapd: phy0-ap0: DFS-PRE-CAC-EXPIRED freq=5300 ht_enabled=0 chan_offset=0 chan_width=0 cf1=5300 cf2=0
Mon Oct  2 06:33:48 2023 daemon.notice hostapd: phy0-ap0: DFS-PRE-CAC-EXPIRED freq=5320 ht_enabled=0 chan_offset=0 chan_width=0 cf1=5320 cf2=0

Mon Oct  2 06:34:52 2023 daemon.notice hostapd: phy0-ap0: DFS-CAC-COMPLETED success=1 freq=5640 ht_enabled=0 chan_offset=0 chan_width=5 cf1=5570 cf2=0
Mon Oct  2 06:34:52 2023 kern.info kernel: [  515.112611] IPv6: ADDRCONF(NETDEV_CHANGE): phy0-ap0: link becomes ready
Mon Oct  2 06:34:52 2023 kern.info kernel: [  515.112789] br-lan: port 6(phy0-ap0) entered blocking state
Mon Oct  2 06:34:52 2023 kern.info kernel: [  515.118045] br-lan: port 6(phy0-ap0) entered forwarding state
Mon Oct  2 06:34:52 2023 daemon.notice netifd: Network device 'phy0-ap0' link is up
Mon Oct  2 06:34:52 2023 daemon.notice hostapd: phy0-ap0: interface state DFS->ENABLED

Channel 36 160MHZ

Mon Oct  2 06:35:40 2023 daemon.notice hostapd: phy0-ap0: DFS-CAC-START freq=5180 chan=36 sec_chan=1, width=2, seg0=50, seg1=0, cac_time=60s
Mon Oct  2 06:35:40 2023 kern.info kernel: [  563.198869] br-lan: port 6(phy0-ap0) entered disabled state
Mon Oct  2 06:35:41 2023 daemon.notice hostapd: phy0-ap0: DFS-PRE-CAC-EXPIRED freq=5500 ht_enabled=0 chan_offset=0 chan_width=0 cf1=5500 cf2=0
Mon Oct  2 06:35:41 2023 daemon.notice hostapd: phy0-ap0: DFS-PRE-CAC-EXPIRED freq=5520 ht_enabled=0 chan_offset=0 chan_width=0 cf1=5520 cf2=0
Mon Oct  2 06:35:41 2023 daemon.notice hostapd: phy0-ap0: DFS-PRE-CAC-EXPIRED freq=5540 ht_enabled=0 chan_offset=0 chan_width=0 cf1=5540 cf2=0
Mon Oct  2 06:35:41 2023 daemon.notice hostapd: phy0-ap0: DFS-PRE-CAC-EXPIRED freq=5560 ht_enabled=0 chan_offset=0 chan_width=0 cf1=5560 cf2=0
Mon Oct  2 06:35:41 2023 daemon.notice hostapd: phy0-ap0: DFS-PRE-CAC-EXPIRED freq=5580 ht_enabled=0 chan_offset=0 chan_width=0 cf1=5580 cf2=0
Mon Oct  2 06:35:41 2023 daemon.notice hostapd: phy0-ap0: DFS-PRE-CAC-EXPIRED freq=5600 ht_enabled=0 chan_offset=0 chan_width=0 cf1=5600 cf2=0
Mon Oct  2 06:35:41 2023 daemon.notice hostapd: phy0-ap0: DFS-PRE-CAC-EXPIRED freq=5620 ht_enabled=0 chan_offset=0 chan_width=0 cf1=5620 cf2=0
Mon Oct  2 06:35:41 2023 daemon.notice hostapd: phy0-ap0: DFS-PRE-CAC-EXPIRED freq=5640 ht_enabled=0 chan_offset=0 chan_width=0 cf1=5640 cf2=0
Mon Oct  2 06:36:39 2023 daemon.warn odhcpd[2576]: No default route present, overriding ra_lifetime!
Mon Oct  2 06:36:44 2023 daemon.notice hostapd: phy0-ap0: DFS-CAC-COMPLETED success=1 freq=5180 ht_enabled=0 chan_offset=0 chan_width=5 cf1=5250 cf2=0

1 Like

So why is 48 working while 36 is not?

It's working for me and I can't guess what is happening in your case.
The only thing you can do is try to find if there is any message in syslog relevant to your issue.
It's not clear to me if the router radio doesn't go up or if your wifi client just can't see the AP.

3236@160Mhz works for others, so it can only be a difference in router settings (including a different country code), a different openwrt version or DFS doing radar detection in your location.
It could also be some kind of interference from some wifi client you have, some people reported some IOT devices would crash the router radio, but that will give a message in the syslog (search the thread for IOT or crash).

If you can't find the cause and because it works for others, I would:

  • Flash the latest snapshot and reset the router settings (do not use attended sysupgrade this time).
    Then then try with minimal WIFI settings:
  • Set the same country code for both radios.
  • WPA2-PSK/CCMP (AES)
  • channel 3236@160Mhz

If you can't see the AP after a few minutes, look in the syslog for DFS msgs. or other error msgs.

If it solves the problem, then go from there.
If not you can always reload your old config if you wish.

I believe you meant 36 instead of 32.

Anyway, since 48 is working, I see no reason to further spend time on figuring out why 36 stopped.1

1 Like

How's everyone luck with DFS channels?

I had an Asus AP on chan 100 so I wanted the Dynalink on 128. Never worked so I swapped them.

The Dynalink will work 100 @ 80 MHz but only with certain country codes. US doesn't work. Lax country codes don't work. European ones like AT work but since you have to match country codes in newer snapshots the 2.4 GHz interface will lose tx power.

Encryption: mixed WPA2/WPA3 PSK, SAE (CCMP)
Channel: 100 (5.500 GHz)
Tx-Power: 24 dBm
Signal: -60 dBm | Noise: -108 dBm
Bitrate: 436.3 Mbit/s | Country: AT

Encryption: mixed WPA2/WPA3 PSK, SAE (CCMP)
Channel: 1 (2.412 GHz)
Tx-Power: 20 dBm
Signal: -50 dBm | Noise: -102 dBm
Bitrate: 39.2 Mbit/s | Country: AT

Not sure what I did but it seems to work again. I have 5 GHz set to AT and 2.4 GHz set to US.

Encryption: mixed WPA2/WPA3 PSK, SAE (CCMP)
Channel: 100 (5.500 GHz)
Tx-Power: 24 dBm
Signal: -56 dBm | Noise: -108 dBm
Bitrate: 693.3 Mbit/s | Country: AT

Encryption: mixed WPA2/WPA3 PSK, SAE (CCMP)
Channel: 1 (2.412 GHz)
Tx-Power: 27 dBm
Signal: -52 dBm | Noise: -102 dBm
Bitrate: 55.3 Mbit/s | Country: AT

@aparcar

Hi, any ETA regarding updates via auc being functional again ? (they're still broken afaict as of this morning)

And thanks for all your hard work!

1 Like

You can always use the Firmware Selector if you do not want to set up your own build environment.

The link is about to expire. Given the good results so far from it, can it be incorporated into the actual firmware?
I could also host the file if you like in the meantime.

I'm not sure if we should use old board file. Internal regdb is outdated.
@robimarko @Ansuel Can we add a second board file for the same router to the repository?

Is that BDF used in the stock FW?

In the stock firmware there are 3 BDF files that do not differ significantly in binary (comparison):

5f796aae812e2b922393f950a2838c895949d68707f3e31e9c3d6fdf88e53be2	GoldenBin_20210323.bin
7527e6be57b3e8cd40b03b1dbdfdee18dce78a6e18a3b70c81a55749dfedaf8d	BDF_20210412.bin
61ce8046ad281342f12eb6d27435907679ff37b266d8b9018b12b334b9edf719	BDF_20210705.bin
61ce8046ad281342f12eb6d27435907679ff37b266d8b9018b12b334b9edf719	bdwlan.rt5010w-d350_rev0

bdwlan.rt5010w-d350_rev0 is used in stock firmware (and it is the same file as BDF_20210705.bin).

I think these are the 3 revisions of the BDF files for this board:

  1. GoldenBin_20210323.bin
  2. BDF_20210412.bin
  3. BDF_20210705.bin

So, which one of these are you trying to include in OpenWrt?

If its just a newer BDF that the stock FW is actually using then I am fine with that, just the regulatory info needs to be updated.

Slightly better results in txpower are with the GoldenBin_20210323.bin file: https://forum.openwrt.org/t/dynalink-dl-wrx36-askey-rt5010w-ipq8072a-technical-discussion/110454/2367

1 Like

I second @lytr 's BDF. With it I'm currently running 28dbm in channel 36 and 30 dbm in 2.4GHz. Very well within the reg domain limits and gives amazing coverage and speed.

I am going to repeat my question, does the stock FW use it?

If not, then there is a reason for it, just because its giving you higher power doesn't mean that its correct

Anyway to bypass this when trying to install the ipk?

Not downgrading package ipq-wifi-dynalink_dl-wrx36 on root from 2023-09-16-57aa1b15-1 to 2023-09-15-cd9c30ca-2.

It is not used.
Is it possible to create a package with an alternative BDF in the official repository?

Add: --force-downgrade.

1 Like

Well, that then answers your question.
Why would OpenWrt ship and use a BDF that is not used in the OEM FW?

As you know, there is a problem with txpower on this board. Using the older BDF improves this situation somewhat.

1 Like