Linksys MX5300 USB Ethernet adaptor bug?

Installing and Using OpenWrt
1

Hi I tried to add a USB3 2.5gbps adaptor to MX5300. It works upon adding, but after a reboot, it looks like the DHCP and authentication is messed up for radio2 (2.4Ghz): many devices receive no authentication, connected devices got no DHCP.

The split moment I unplugged the USB adaptor radio2 is fixed.

Log attached:

Sat Mar 22 23:20:15 2025 daemon.notice hostapd: Set new config for phy phy2:
Sat Mar 22 23:20:15 2025 daemon.notice hostapd: Remove interface 'phy2'
Sat Mar 22 23:20:15 2025 daemon.notice hostapd: phy2-ap0: interface state ENABLED->DISABLED
Sat Mar 22 23:20:15 2025 daemon.notice hostapd: phy2-ap0: AP-DISABLED
Sat Mar 22 23:20:15 2025 daemon.notice hostapd: phy2-ap0: CTRL-EVENT-TERMINATING
Sat Mar 22 23:20:15 2025 daemon.err hostapd: rmdir[ctrl_interface=/var/run/hostapd]: Permission denied
Sat Mar 22 23:20:15 2025 daemon.notice hostapd: nl80211: deinit ifname=phy2-ap0 disabled_11b_rates=0
Sat Mar 22 23:20:15 2025 kern.info kernel: [  371.827723] ath11k c000000.wifi phy2-ap0: left allmulticast mode
Sat Mar 22 23:20:15 2025 kern.info kernel: [  371.827787] ath11k c000000.wifi phy2-ap0: left promiscuous mode
Sat Mar 22 23:20:15 2025 kern.info kernel: [  371.832892] br-lan2: port 2(phy2-ap0) entered disabled state
Sat Mar 22 23:20:15 2025 daemon.notice netifd: Network device 'phy2-ap0' link is down
Sat Mar 22 23:20:15 2025 daemon.notice wpa_supplicant[2394]: Set new config for phy phy2
Sat Mar 22 23:20:15 2025 daemon.notice netifd: Wireless device 'radio2' is now down
Sat Mar 22 23:20:15 2025 daemon.notice netifd: radio2 (13019): WARNING: Variable 'data' does not exist or is not an array/object
Sat Mar 22 23:20:15 2025 daemon.notice hostapd: Set new config for phy phy2:
Sat Mar 22 23:20:15 2025 daemon.notice wpa_supplicant[2394]: Set new config for phy phy2
Sat Mar 22 23:20:15 2025 daemon.notice wpa_supplicant[2394]: Set new config for phy phy2
Sat Mar 22 23:20:15 2025 daemon.notice hostapd: Set new config for phy phy2: /var/run/hostapd-phy2.conf
Sat Mar 22 23:20:15 2025 daemon.notice hostapd: Restart interface for phy phy2
Sat Mar 22 23:20:16 2025 daemon.notice hostapd: Configuration file: data: driver=nl80211 logger_syslog=127 logger_syslog_level=2 logger_stdout=127 logger_stdout_level=2 country_code=US ieee80211d=1 hw_mode=g supported_rates=60 90 120 180 240 360 480 540 basic_rates=60 120 240 beacon_int=100 stationary_ap=1 chanlist=11 #num_global_macaddr=1 #macaddr_base= ieee80211n=1 ht_coex=0 ht_capab=[LDPC][SHORT-GI-20][SHORT-GI-40][TX-STBC][RX-STBC1][DSSS_CCK-40] ieee80211ax=1 he_su_beamformer=1 he_su_beamformee=1 he_mu_beamformer=1 he_bss_color=128 he_spr_sr_control=3 he_default_pe_duration=4 he_rts_threshold=1023 he_mu_edca_qos_info_param_count=0 he_mu_edca_qos_info_q_ack=0 he_mu_edca_qos_info_queue_request=0 he_mu_edca_qos_info_txop_request=0 he_mu_edca_ac_be_aifsn=8 he_mu_edca_ac_be_aci=0 he_mu_edca_ac_be_ecwmin=9 he_mu_edca_ac_be_ecwmax=10 he_mu_edca_ac_be_timer=255 he_mu_edca_ac_bk_aifsn=15 he_mu_edca_ac_bk_aci=1 he_mu_edca_ac_bk_ecwmin=9 he_mu_edca_ac_bk_ecwmax=10 he_mu_edca_ac_bk_timer=255 he_mu_edca_ac_vi_ecwmin=5 he_mu_edca_ac_vi_
Sat Mar 22 23:20:16 2025 kern.info kernel: [  372.595646] br-lan2: port 2(phy2-ap0) entered blocking state
Sat Mar 22 23:20:16 2025 kern.info kernel: [  372.595690] br-lan2: port 2(phy2-ap0) entered disabled state
Sat Mar 22 23:20:16 2025 kern.info kernel: [  372.600074] ath11k c000000.wifi phy2-ap0: entered allmulticast mode
Sat Mar 22 23:20:16 2025 kern.info kernel: [  372.606001] ath11k c000000.wifi phy2-ap0: entered promiscuous mode
Sat Mar 22 23:20:16 2025 kern.info kernel: [  372.612215] br-lan2: port 2(phy2-ap0) entered blocking state
Sat Mar 22 23:20:16 2025 kern.info kernel: [  372.618111] br-lan2: port 2(phy2-ap0) entered forwarding state
Sat Mar 22 23:20:16 2025 daemon.notice hostapd: phy2-ap0: interface state UNINITIALIZED->COUNTRY_UPDATE
Sat Mar 22 23:20:16 2025 daemon.notice netifd: Network device 'phy2-ap0' link is up
Sat Mar 22 23:20:16 2025 daemon.notice hostapd: phy2-ap0: interface state COUNTRY_UPDATE->ENABLED
Sat Mar 22 23:20:16 2025 daemon.notice hostapd: phy2-ap0: AP-ENABLED
Sat Mar 22 23:20:16 2025 daemon.notice netifd: Wireless device 'radio2' is now up
Sat Mar 22 23:20:39 2025 daemon.notice hostapd: phy2-ap0: STA 28:**:66:**:f9:** IEEE 802.11: did not acknowledge authentication response
Sat Mar 22 23:20:40 2025 daemon.notice hostapd: phy2-ap0: STA 28:**:66:**:f9:** IEEE 802.11: did not acknowledge authentication response
Sat Mar 22 23:20:40 2025 daemon.notice hostapd: phy2-ap0: STA 28:**:66:**:f9:** IEEE 802.11: did not acknowledge authentication response
Sat Mar 22 23:20:40 2025 daemon.notice hostapd: phy2-ap0: STA 28:**:66:**:f9:** IEEE 802.11: did not acknowledge authentication response
Sat Mar 22 23:20:40 2025 daemon.notice hostapd: phy2-ap0: STA 28:**:66:**:f9:** IEEE 802.11: did not acknowledge authentication response
Sat Mar 22 23:21:18 2025 daemon.notice hostapd: phy2-ap0: STA 28:**:66:**:f9:** IEEE 802.11: did not acknowledge authentication response
Sat Mar 22 23:21:18 2025 daemon.notice hostapd: phy2-ap0: STA 28:**:66:**:f9:** IEEE 802.11: did not acknowledge authentication response
Sat Mar 22 23:21:19 2025 daemon.notice hostapd: phy2-ap0: STA 28:**:66:**:f9:** IEEE 802.11: did not acknowledge authentication response
Sat Mar 22 23:21:19 2025 daemon.notice hostapd: phy2-ap0: STA 28:**:66:**:f9:** IEEE 802.11: did not acknowledge authentication response
Sat Mar 22 23:21:19 2025 daemon.notice hostapd: phy2-ap0: STA 28:**:66:**:f9:** IEEE 802.11: did not acknowledge authentication response
Sat Mar 22 23:21:42 2025 daemon.notice netifd: Network device 'eth0' link is down
Sat Mar 22 23:21:42 2025 kern.info kernel: [  458.792131] r8152-cfgselector 2-1: USB disconnect, device number 2
Sat Mar 22 23:21:42 2025 kern.info kernel: [  458.792912] br-lan: port 1(eth0) entered disabled state
Sat Mar 22 23:21:42 2025 kern.info kernel: [  458.798610] r8152 2-1:1.0 eth0 (unregistering): left allmulticast mode
Sat Mar 22 23:21:42 2025 kern.info kernel: [  458.802556] r8152 2-1:1.0 eth0 (unregistering): left promiscuous mode
Sat Mar 22 23:21:42 2025 kern.info kernel: [  458.808961] br-lan: port 1(eth0) entered disabled state
Sat Mar 22 23:21:53 2025 daemon.info hostapd: phy2-ap0: STA d8:__:c9:__:aa:__ IEEE 802.11: authenticated
Sat Mar 22 23:21:53 2025 daemon.info hostapd: phy2-ap0: STA d8:__:c9:__:aa:__ IEEE 802.11: associated (aid 1)
Sat Mar 22 23:21:53 2025 daemon.notice hostapd: phy2-ap0: AP-STA-CONNECTED d8:__:c9:__:aa:__ auth_alg=open
Sat Mar 22 23:21:53 2025 daemon.info hostapd: phy2-ap0: STA d8:__:c9:__:aa:__ WPA: pairwise key handshake completed (RSN)
Sat Mar 22 23:21:53 2025 daemon.notice hostapd: phy2-ap0: EAPOL-4WAY-HS-COMPLETED d8:__:c9:__:aa:__
Sat Mar 22 23:21:53 2025 daemon.info dnsmasq-dhcp[1]: DHCPDISCOVER(br-lan2) d8:__:c9:__:aa:__
Sat Mar 22 23:21:53 2025 daemon.info dnsmasq-dhcp[1]: DHCPOFFER(br-lan2) 192.168.222.17 d8:__:c9:__:aa:__
Sat Mar 22 23:21:53 2025 daemon.info dnsmasq-dhcp[1]: DHCPREQUEST(br-lan2) 192.168.222.17 d8:__:c9:__:aa:__
Sat Mar 22 23:21:53 2025 daemon.info dnsmasq-dhcp[1]: DHCPACK(br-lan2) 192.168.222.17 d8:__:c9:__:aa:__ Some-Appliance
Sat Mar 22 23:21:55 2025 daemon.info hostapd: phy2-ap0: STA 28:**:66:**:f9:** IEEE 802.11: authenticated
Sat Mar 22 23:21:55 2025 daemon.info hostapd: phy2-ap0: STA 28:**:66:**:f9:** IEEE 802.11: associated (aid 2)
Sat Mar 22 23:21:55 2025 daemon.notice hostapd: phy2-ap0: AP-STA-CONNECTED 28:**:66:**:f9:** auth_alg=open
Sat Mar 22 23:21:55 2025 daemon.info hostapd: phy2-ap0: STA 28:**:66:**:f9:** WPA: pairwise key handshake completed (RSN)
Sat Mar 22 23:21:55 2025 daemon.notice hostapd: phy2-ap0: EAPOL-4WAY-HS-COMPLETED 28:**:66:**:f9:**
Sat Mar 22 23:21:56 2025 daemon.info dnsmasq-dhcp[1]: DHCPREQUEST(br-lan2) 192.168.222.14 28:**:66:**:f9:**
Sat Mar 22 23:21:56 2025 daemon.info dnsmasq-dhcp[1]: DHCPACK(br-lan2) 192.168.222.14 28:**:66:**:f9:** Some-Gadget
Sat Mar 22 23:21:57 2025 kern.info kernel: [  473.658415] nss-dp 3a001600.dp4 lan4: PHY Link up speed: 1000
Sat Mar 22 23:21:57 2025 kern.info kernel: [  473.658477] br-lan: port 5(lan4) entered blocking state
Sat Mar 22 23:21:57 2025 kern.info kernel: [  473.663163] br-lan: port 5(lan4) entered forwarding state
2

I suspect that this is a power issue... the router may not have enough USB power budget for the ethernet adapter, thus causing the system to brown out.

3

This is a fairly low power adaptor but these ports are usually designed for external drives? DHCP and authentication also works well for two other radios, just not for radio2. Does it still look like a power issue?

If so I may try looking for an external power mod.

4

Grab a powered USB hub and insert it between the router and the USB adapter... if the problem goes away, it was indeed a power issue.

Meanwhile, we can review your config for any signs of issues:

Please connect to your OpenWrt device using ssh and copy the output of the following commands and post it here using the "Preformatted text </> " button:
grafik
Remember to redact passwords, MAC addresses and any public IP addresses you may have:

ubus call system board
cat /etc/config/network
cat /etc/config/wireless
cat /etc/config/dhcp
cat /etc/config/firewall
5

Retrofitting high-speed interfaces (ethernet, wireless, storage) to 'plastic routers' is rarely a sensible solution, as these devices tend to be purpose built with little margins beyond what they're designed for. Especially in this case, the IPQ8072A SOC is designed to rely heavily on NSS hardware offloading to keep up at wirespeed of its internal (offloaded) interfaces, without NSS it has a hard time keeping up with those, it will have an even harder time to cope with high speed USB transfers from your ethernet card on top.

Do yourself a favour, if you are in search on 2.5 GBit/s capable hardware, get some that offers it natively and doesn't require NSS - be it filogic 830 or x86_64 (in the later case your mx5300 can still make a decent AP).

1 Like