Wifi client radio0 keeps resetting

Have a Comfast CF-EW71 on 23.05.03 (it's replacing a dead TP-Link N300 that was working great) as Wifi client, connecting to a Ubiquiti IW-AP. Signal strength is -59/-95 dBm. I keep getting this in the logs as soon as any load is placed on the Wifi, low traffic works fine:

Thu Jun 20 09:40:17 2024 daemon.notice netifd: radio0 (4451): sh: out of range
Thu Jun 20 09:40:18 2024 daemon.notice wpa_supplicant[1126]: Set new config for phy phy0
Thu Jun 20 09:40:18 2024 daemon.notice wpa_supplicant[1126]: Update configuration for interface phy0-sta0
Thu Jun 20 09:40:18 2024 daemon.notice netifd: Network device 'phy0-sta0' link is down
Thu Jun 20 09:40:18 2024 daemon.notice netifd: Interface 'wifi0' has link connectivity loss
Thu Jun 20 09:40:18 2024 kern.info kernel: [38161.679085] phy0-sta0: deauthenticating from e0:63:da:34:32:c8 by local choice (Reason: 3=DEAUTH_LEAVING)
Thu Jun 20 09:40:18 2024 daemon.notice wpa_supplicant[1126]: phy0-sta0: CTRL-EVENT-DISCONNECTED bssid=e0:63:da:34:32:c8 reason=3 locally_generated=1
Thu Jun 20 09:40:18 2024 daemon.notice wpa_supplicant[1126]: phy0-sta0: CTRL-EVENT-DSCP-POLICY clear_all
Thu Jun 20 09:40:18 2024 daemon.notice wpa_supplicant[1126]: phy0-sta0: CTRL-EVENT-DSCP-POLICY clear_all
Thu Jun 20 09:40:18 2024 daemon.notice wpa_supplicant[1126]: nl80211: deinit ifname=phy0-sta0 disabled_11b_rates=0
Thu Jun 20 09:40:18 2024 daemon.info avahi-daemon[1519]: Interface phy0-sta0.IPv6 no longer relevant for mDNS.
Thu Jun 20 09:40:18 2024 daemon.info avahi-daemon[1519]: Leaving mDNS multicast group on interface phy0-sta0.IPv6 with address fe80::42a5:efff:fe07:15a8.
Thu Jun 20 09:40:18 2024 daemon.info avahi-daemon[1519]: Interface phy0-sta0.IPv4 no longer relevant for mDNS.
Thu Jun 20 09:40:18 2024 daemon.info avahi-daemon[1519]: Leaving mDNS multicast group on interface phy0-sta0.IPv4 with address 192.168.1.40.
Thu Jun 20 09:40:18 2024 daemon.err wpa_supplicant[1126]: rmdir[ctrl_interface=/var/run/wpa_supplicant]: Permission denied
Thu Jun 20 09:40:18 2024 daemon.info avahi-daemon[1519]: Withdrawing address record for fe80::42a5:efff:fe07:15a8 on phy0-sta0.
Thu Jun 20 09:40:18 2024 daemon.info avahi-daemon[1519]: Withdrawing address record for 192.168.1.40 on phy0-sta0.
Thu Jun 20 09:40:18 2024 daemon.notice hostapd: Set new config for phy phy0:
Thu Jun 20 09:40:18 2024 daemon.notice wpa_supplicant[1126]: Set new config for phy phy0
Thu Jun 20 09:40:18 2024 daemon.notice netifd: wifi0 (2212): udhcpc: SIOCGIFINDEX: No such device
Thu Jun 20 09:40:18 2024 daemon.notice netifd: wifi0 (2212): udhcpc: received SIGTERM
Thu Jun 20 09:40:18 2024 daemon.notice netifd: wifi0 (2212): udhcpc: unicasting a release of 192.168.1.40 to 192.168.1.1
Thu Jun 20 09:40:18 2024 daemon.notice netifd: wifi0 (2212): udhcpc: sending release
Thu Jun 20 09:40:18 2024 daemon.notice netifd: wifi0 (2212): udhcpc: can't bind to interface phy0-sta0: No such device
Thu Jun 20 09:40:18 2024 daemon.notice netifd: wifi0 (2212): udhcpc: bindtodevice: No such device
Thu Jun 20 09:40:18 2024 daemon.notice netifd: wifi0 (2212): udhcpc: entering released state
Thu Jun 20 09:40:18 2024 daemon.notice netifd: wifi0 (2212): Command failed: ubus call network.interface notify_proto { "action": 0, "link-up": false, "keep": false, "interface": "wifi0" } (Permission denied)
Thu Jun 20 09:40:18 2024 daemon.notice netifd: Interface 'wifi0' is now down
Thu Jun 20 09:40:18 2024 daemon.info dnsmasq[1]: reading /tmp/resolv.conf.d/resolv.conf.auto
Thu Jun 20 09:40:18 2024 daemon.info dnsmasq[1]: using nameserver 192.168.1.1#53
Thu Jun 20 09:40:18 2024 daemon.info dnsmasq[1]: using only locally-known addresses for test
Thu Jun 20 09:40:18 2024 daemon.info dnsmasq[1]: using only locally-known addresses for onion
Thu Jun 20 09:40:18 2024 daemon.info dnsmasq[1]: using only locally-known addresses for localhost
Thu Jun 20 09:40:18 2024 daemon.info dnsmasq[1]: using only locally-known addresses for local
Thu Jun 20 09:40:18 2024 daemon.info dnsmasq[1]: using only locally-known addresses for invalid
Thu Jun 20 09:40:18 2024 daemon.info dnsmasq[1]: using only locally-known addresses for bind
Thu Jun 20 09:40:18 2024 daemon.info dnsmasq[1]: using only locally-known addresses for lan
Thu Jun 20 09:40:19 2024 daemon.notice netifd: Wireless device 'radio0' is now up
Thu Jun 20 09:40:20 2024 daemon.info dnsmasq[1]: read /etc/hosts - 12 names
Thu Jun 20 09:40:20 2024 daemon.info dnsmasq[1]: read /tmp/hosts/dhcp.cfg01411c - 5 names
Thu Jun 20 09:40:20 2024 daemon.info dnsmasq-dhcp[1]: read /etc/ethers - 0 addresses
Thu Jun 20 09:40:21 2024 daemon.notice wpa_supplicant[1126]: phy0-sta0: SME: Trying to authenticate with fc:ec:da:f7:b0:02 (SSID='ME' freq=2437 MHz)
Thu Jun 20 09:40:21 2024 kern.info kernel: [38164.734166] phy0-sta0: authenticate with fc:ec:da:f7:b0:02
Thu Jun 20 09:40:21 2024 kern.info kernel: [38164.740124] phy0-sta0: 80 MHz not supported, disabling VHT
Thu Jun 20 09:40:21 2024 kern.info kernel: [38164.758971] phy0-sta0: send auth to fc:ec:da:f7:b0:02 (try 1/3)
Thu Jun 20 09:40:21 2024 kern.info kernel: [38164.867451] phy0-sta0: send auth to fc:ec:da:f7:b0:02 (try 2/3)
Thu Jun 20 09:40:21 2024 kern.info kernel: [38164.987420] phy0-sta0: send auth to fc:ec:da:f7:b0:02 (try 3/3)
Thu Jun 20 09:40:21 2024 kern.info kernel: [38165.107440] phy0-sta0: authentication with fc:ec:da:f7:b0:02 timed out
Thu Jun 20 09:40:21 2024 daemon.warn odhcpd[1300]: No default route present, overriding ra_lifetime!
Thu Jun 20 09:40:22 2024 daemon.notice wpa_supplicant[1126]: phy0-sta0: SME: Trying to authenticate with e0:63:da:34:32:c8 (SSID='ME' freq=2462 MHz)
Thu Jun 20 09:40:22 2024 kern.info kernel: [38166.291926] phy0-sta0: authenticate with e0:63:da:34:32:c8
Thu Jun 20 09:40:22 2024 kern.info kernel: [38166.297887] phy0-sta0: 80 MHz not supported, disabling VHT
Thu Jun 20 09:40:22 2024 kern.info kernel: [38166.316691] phy0-sta0: send auth to e0:63:da:34:32:c8 (try 1/3)
Thu Jun 20 09:40:22 2024 daemon.notice wpa_supplicant[1126]: phy0-sta0: SME: Trying to authenticate with e0:63:da:34:32:c8 (SSID='ME' freq=2462 MHz)
Thu Jun 20 09:40:22 2024 kern.info kernel: [38166.504009] phy0-sta0: authenticate with e0:63:da:34:32:c8
Thu Jun 20 09:40:22 2024 kern.info kernel: [38166.509796] phy0-sta0: send auth to e0:63:da:34:32:c8 (try 1/3)
Thu Jun 20 09:40:22 2024 daemon.notice wpa_supplicant[1126]: phy0-sta0: Trying to associate with e0:63:da:34:32:c8 (SSID='ME' freq=2462 MHz)
Thu Jun 20 09:40:22 2024 kern.info kernel: [38166.518636] phy0-sta0: authenticated
Thu Jun 20 09:40:22 2024 kern.info kernel: [38166.527730] phy0-sta0: associate with e0:63:da:34:32:c8 (try 1/3)
Thu Jun 20 09:40:22 2024 kern.info kernel: [38166.536125] phy0-sta0: RX AssocResp from e0:63:da:34:32:c8 (capab=0x431 status=0 aid=3)
Thu Jun 20 09:40:22 2024 kern.info kernel: [38166.544984] phy0-sta0: associated
Thu Jun 20 09:40:22 2024 daemon.notice wpa_supplicant[1126]: phy0-sta0: Associated with e0:63:da:34:32:c8
Thu Jun 20 09:40:22 2024 daemon.notice netifd: Network device 'phy0-sta0' link is up
Thu Jun 20 09:40:22 2024 daemon.notice netifd: Interface 'wifi0' has link connectivity
Thu Jun 20 09:40:22 2024 daemon.notice netifd: Interface 'wifi0' is setting up now
Thu Jun 20 09:40:22 2024 daemon.notice wpa_supplicant[1126]: phy0-sta0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Thu Jun 20 09:40:22 2024 daemon.notice wpa_supplicant[1126]: phy0-sta0: Unknown event 37
Thu Jun 20 09:40:22 2024 daemon.notice wpa_supplicant[1126]: phy0-sta0: WPA: Key negotiation completed with e0:63:da:34:32:c8 [PTK=CCMP GTK=CCMP]
Thu Jun 20 09:40:22 2024 daemon.notice wpa_supplicant[1126]: phy0-sta0: CTRL-EVENT-CONNECTED - Connection to e0:63:da:34:32:c8 completed [id=1 id_str=]
Thu Jun 20 09:40:23 2024 kern.info kernel: [38166.586668] IPv6: ADDRCONF(NETDEV_CHANGE): phy0-sta0: link becomes ready
Thu Jun 20 09:40:23 2024 daemon.notice wpa_supplicant[1126]: phy0-sta0: Unknown event 37
Thu Jun 20 09:40:23 2024 daemon.notice netifd: wifi0 (4870): udhcpc: started, v1.36.1
Thu Jun 20 09:40:23 2024 daemon.notice netifd: wifi0 (4870): udhcpc: broadcasting discover
Thu Jun 20 09:40:23 2024 daemon.notice netifd: wifi0 (4870): udhcpc: broadcasting select for 192.168.1.40, server 192.168.1.1
Thu Jun 20 09:40:23 2024 daemon.notice netifd: wifi0 (4870): udhcpc: lease of 192.168.1.40 obtained from 192.168.1.1, lease time 3600
Thu Jun 20 09:40:23 2024 daemon.info avahi-daemon[1519]: Joining mDNS multicast group on interface phy0-sta0.IPv4 with address 192.168.1.40.
Thu Jun 20 09:40:23 2024 daemon.info avahi-daemon[1519]: New relevant interface phy0-sta0.IPv4 for mDNS.
Thu Jun 20 09:40:23 2024 daemon.info avahi-daemon[1519]: Registering new address record for 192.168.1.40 on phy0-sta0.IPv4.
Thu Jun 20 09:40:23 2024 daemon.notice netifd: Interface 'wifi0' is now up

Please post the output of

ubus call system board
{
        "kernel": "5.15.134",
        "hostname": "OpenWrt-Pool",
        "system": "Qualcomm Atheros QCA9533 ver 2 rev 0",
        "model": "COMFAST CF-EW72",
        "board_name": "comfast,cf-ew72",
        "rootfs_type": "squashfs",
        "release": {
                "distribution": "OpenWrt",
                "version": "23.05.0",
                "revision": "r23497-6637af95aa",
                "target": "ath79/generic",
                "description": "OpenWrt 23.05.0 r23497-6637af95aa"
        }
}

Flashing incompatible firmware likely did irrepairable damage.
Return to OEM and flash proper EW71 firmware snapshot

According to this: https://openwrt.org/toh/comfast/cf-ew72 the CF-EW71 is identical to CF-EW72 (v1) with just a 2.4Ghz radio. Is there a dedicated CF-EW71 firmware?

Yes, the snapshot. You will need to install LuCI.

Are you saying to flash back to the Comfast OEM firmware, then install LuCl on their custom OpenWRT based image?

Check partition layout in sources. If you re-wrote any system area to be used by 71 then will not be good even with correct firmware.

Tried the snapshot r26730-17099f2760 and same issue. I don't understand how the partition issue could affect the wireless radio...

Correction, the wifi is now rock solid running on the snapshot. Think I'm fixed.

1 Like

You can use auc every now and then waiting for stable release of your router.
The system partitions are very important, they have wifi calibration data, like antenna amplification curve, MAC addresses etc.

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