SOLVED: WRT3200ACM on 19.07.4 DFS not Working

Installing and Using OpenWrt
1

I went to the Stable Build 19.07.4 for my WRT3200ACM that I built using the Image Builder.

I cannot get the 5GHz Radio to work on any DFS Channels. It did work fine on the snapshot image before so is not the hardware.

The errors I get are below.

Can some one point me in the right direction to get this fixed as I think it should work on DFS channels?

My build packages are:

make image PROFILE=linksys_wrt3200acm PACKAGES="luci-ssl-openssl luci-app-advanced-reboot block-mount kmod-usb-storage luci-app-samba4 luci-app-ddns luci-app-uhttpd luci-app-openvpn openvpn-openssl libopenssl-devcrypto luci-app-statistics collectd-mod-sensors collectd-mod-thermal vsftpd-tls ca-certificates -dnsmasq dnsmasq-full hostapd-common wpad-basic wireguard luci-app-wireguard kmod-btmrvl mwifiex-sdio-firmware mwlwifi-firmware-88w8964 luci-app-vpn-policy-routing wget curl -libustream-wolfssl ppp -ppp-mod-pppoe"

Fri Sep 18 15:49:25 2020 daemon.notice hostapd: wlan0: DFS-CAC-START freq=5540 chan=108 sec_chan=0, width=0, seg0=0, seg1=0, cac_time=60s
Fri Sep 18 15:49:25 2020 daemon.err hostapd: DFS start_dfs_cac() failed, -1
Fri Sep 18 15:49:25 2020 daemon.err hostapd: Interface initialization failed
Fri Sep 18 15:49:25 2020 daemon.notice hostapd: wlan0: interface state DFS->DISABLED
Fri Sep 18 15:49:25 2020 daemon.notice hostapd: wlan0: AP-DISABLED
Fri Sep 18 15:49:25 2020 daemon.notice hostapd: wlan0: interface state DISABLED->DISABLED
Fri Sep 18 15:49:25 2020 daemon.notice hostapd: wlan0: AP-DISABLED
Fri Sep 18 15:49:25 2020 daemon.notice hostapd: wlan0: CTRL-EVENT-TERMINATING
Fri Sep 18 15:49:25 2020 daemon.err hostapd: hostapd_free_hapd_data: Interface wlan0 wasn't started
Fri Sep 18 15:49:25 2020 daemon.notice hostapd: nl80211: deinit ifname=wlan0 disabled_11b_rates=0
Fri Sep 18 15:49:25 2020 kern.info kernel: [ 1261.263773] device wlan0 left promiscuous mode
Fri Sep 18 15:49:25 2020 kern.info kernel: [ 1261.268281] br-lan: port 2(wlan0) entered disabled state
Fri Sep 18 15:49:25 2020 daemon.notice hostapd: ELOOP: remaining socket: sock=22 eloop_data=0xb6f58c60 user_data=0 handler=0x84c50
Fri Sep 18 15:49:25 2020 daemon.notice netifd: radio0 (29679): WARNING (wireless_add_process): executable path /usr/sbin/wpad does not match process 28225 path ()
Fri Sep 18 15:49:25 2020 kern.debug kernel: [ 1261.511811] ieee80211 phy0: change: 0xffffffff

2

Hi if you would like the driver fixt pleas sign here: https://www.change.org/p/belkin-linksys-to-release-the-drivers-for-their-wrt-routers-for-better-open-source-support/share_for_starters?just_created=true

3

The BLOB update is not in 19.x, and a few other mwlwifi commits; I never found DFS to be anythings other than a big fail with mwlwifi though.

4

Signed petition

5

The DFS worked OK in the Snapshot builds but other issues with loss of IP and other issues too complicated for me to figure out, pushed me to the Stable Build 19.07.4. I was surprised when the Stable Build is not fully stable.

6

Should be able to do this if you want to see if that FW makes any difference on 19.x.

7

I dont think a petition will help, the only solution will be to reverse engineer the firmware and drivers and go from there.

8

Tried this but no change, still get the DFS error.

9

Fixed! DFS passes and I can use the DFS channels.

Solution can be found here: https://github.com/kaloz/mwlwifi/issues/173#issuecomment-695320073

1 Like
10

There is a bug on initial setting of the corrrect CC on the rango, but FR is the only option on a EU unit, and if you have the third radio in use they all have to be in agreement, or you will have problems; the mwlwifi read recommends not setting CC, or removal of driver. PR2397 may be of interest.

1 Like
11

Excellent read. Lets hope there is some progress. Thanks.

12

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.