5GHz WiFi Missing on Sercomm NA502(mt7621) with Latest Snapshot

gtxent · September 15, 2024, 2:42am

Hello,

I've recently updated to the latest snapshot for OpenWrt and have encountered an issue with the Sercomm NA502. The 5GHz WiFi band is no longer functioning. In addition, both physical interfaces (phy's) are only showing 2.4GHz capabilities in the wireless section and in iw commands.

I've tried forcing the configuration to 5GHz bands, but it doesn't resolve the problem.
Rolling back to 22.03.7 restores device functionality.

Unable to test 23.05.0 to 23.05.2 due to LZMA kernel error which was fixed in 23.05.3
23.05.3, 23.05.4 and snapshot confirmed missing 5ghz.

For more details, I've attached device logs:
na502-logs

If anyone has any suggestions, would love to hear/try them.

lleachii · September 15, 2024, 2:49am

Your configs for both radio0 and radio1 says option band '2g'.

gtxent · September 15, 2024, 3:17am

oops, that's the auto generated config after a fresh install. (2g)
updated the logs with 5g settings, which produces the same result.
logread:

Sat Sep 14 20:19:45 2024 daemon.notice hostapd: Set new config for phy phy1:
Sat Sep 14 20:19:45 2024 daemon.notice wpa_supplicant[1486]: Set new config for phy phy1
Sat Sep 14 20:19:45 2024 daemon.notice netifd: Wireless device 'radio1' is now down
Sat Sep 14 20:19:45 2024 daemon.notice netifd: radio1 (6544): WARNING: Variable 'data' does not exist or is not an array/object
Sat Sep 14 20:19:45 2024 daemon.notice hostapd: Set new config for phy phy1:
Sat Sep 14 20:19:45 2024 daemon.notice wpa_supplicant[1486]: Set new config for phy phy1
Sat Sep 14 20:19:46 2024 daemon.notice wpa_supplicant[1486]: Set new config for phy phy1
Sat Sep 14 20:19:46 2024 daemon.notice hostapd: Set new config for phy phy1: /var/run/hostapd-phy1.conf
Sat Sep 14 20:19:46 2024 daemon.notice hostapd: Restart interface for phy phy1
Sat Sep 14 20:19:46 2024 daemon.notice hostapd: Configuration file: data: driver=nl80211 logger_syslog=127 logger_syslog_level=2 logger_stdout=127 logger_stdout_level=2 hw_mode=a beacon_int=100 chanlist=36 tx_queue_data2_burst=2.0 #num_global_macaddr=1 ieee80211n=1 ht_coex=0 ht_capab=[HT40+][LDPC][SHORT-GI-20][SHORT-GI-40][TX-STBC][RX-STBC1] ieee80211ac=1 vht_oper_chwidth=1 vht_oper_centr_freq_seg0_idx=42 vht_capab=[MAX-A-MPDU-LEN-EXP0] channel=36  interface=phy1-ap0 bssid=e0:60:66:1a:09:42 ctrl_interface=/var/run/hostapd bss_load_update_period=60 chan_util_avg_period=600 disassoc_low_ack=1 skip_inactivity_poll=0 preamble=1 wmm_enabled=1 ignore_broadcast_ssid=0 uapsd_advertisement_enabled=1 utf8_ssid=1 multi_ap=0 auth_algs=1 wpa=0 ssid=OpenWrt5ghz qos_map_set=0,0,2,16,1,1,255,255,18,22,24,38,40,40,44,46,48,56 #default_macaddr nas_identifier=e060661a0942  (phy phy1) --> new PHY
Sat Sep 14 20:19:46 2024 daemon.notice hostapd: Could not determine operating frequency
Sat Sep 14 20:19:46 2024 daemon.notice hostapd: phy1-ap0: interface state UNINITIALIZED->DISABLED
Sat Sep 14 20:19:46 2024 daemon.notice hostapd: phy1-ap0: AP-DISABLED
Sat Sep 14 20:19:46 2024 daemon.err hostapd: phy1-ap0: Unable to setup interface.
Sat Sep 14 20:19:46 2024 daemon.notice hostapd: nl80211: deinit ifname=phy1-ap0 disabled_11b_rates=0
Sat Sep 14 20:19:46 2024 daemon.err hostapd: rmdir[ctrl_interface=/var/run/hostapd]: Permission denied
Sat Sep 14 20:19:46 2024 daemon.notice hostapd: phy1-ap0: CTRL-EVENT-TERMINATING
Sat Sep 14 20:19:46 2024 daemon.err hostapd: hostapd_free_hapd_data: Interface phy1-ap0 wasn't started
Sat Sep 14 20:19:46 2024 daemon.notice hostapd: hostapd.add_iface failed for phy phy1 ifname=phy1-ap0
Sat Sep 14 20:19:46 2024 daemon.notice netifd: Wireless device 'radio1' is now up

brada4 · September 15, 2024, 4:29am

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:

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

gtxent · September 15, 2024, 4:33am

BusyBox v1.36.1 (2024-09-13 20:17:35 UTC) built-in shell (ash)

  _______                     ________        __
 |       |.-----.-----.-----.|  |  |  |.----.|  |_
 |   -   ||  _  |  -__|     ||  |  |  ||   _||   _|
 |_______||   __|_____|__|__||________||__|  |____|
          |__| W I R E L E S S   F R E E D O M
 -----------------------------------------------------
 OpenWrt SNAPSHOT, r27352-47370eb9ba
 -----------------------------------------------------
root@vera:~# ubus call system board
{
	"kernel": "6.6.50",
	"hostname": "vera",
	"system": "MediaTek MT7621 ver:1 eco:3",
	"model": "SERCOMM NA502",
	"board_name": "sercomm,na502",
	"rootfs_type": "squashfs",
	"release": {
		"distribution": "OpenWrt",
		"version": "SNAPSHOT",
		"revision": "r27352-47370eb9ba",
		"target": "ramips/mt7621",
		"description": "OpenWrt SNAPSHOT r27352-47370eb9ba"
	}
}
root@vera:~# cat /etc/config/network

config interface 'loopback'
	option device 'lo'
	option proto 'static'
	option ipaddr '127.0.0.1'
	option netmask '255.0.0.0'

config globals 'globals'
	option packet_steering '1'
	option ula_prefix 'fd89:49d0:52c6::/48'

config interface 'wan'
	option proto 'dhcp'
	option device 'lan'

config device
	option name 'lan'

config interface 'wan6'
	option proto 'dhcpv6'
	option device 'lan'
	option reqaddress 'try'
	option reqprefix 'no'

config device
	option type '8021q'
	option ifname 'lan'
	option vid '30'
	option name 'lan.30'

config device
	option type 'bridge'
	option name 'nvr-bridge'
	list ports 'lan.30'
	option macaddr 'E0:60:66:1A:09:41'

config interface 'nvr_bridge'
	option device 'nvr-bridge'
	option proto 'dhcpv6'
	option reqprefix 'no'
	option reqaddress 'force'

config interface 'NVR_BRIDGE_IPv4'
	option proto 'dhcp'
	option device 'nvr-bridge'

root@vera:~# cat /etc/config/wireless

config wifi-device 'radio0'
	option type 'mac80211'
	option path '1e140000.pcie/pci0000:00/0000:00:02.0/0000:02:00.0'
	option band '2g'
	option channel '13'
	option htmode 'HT20'
	option country 'PA'
	option cell_density '0'
	option txpower '25'

config wifi-iface 'default_radio0'
	option device 'radio0'
	option mode 'ap'
	option ssid 'nvr-ap'
	option encryption 'psk2'
	option key 'redactedpw'
	option network 'NVR_BRIDGE_IPv4'
	option hidden '1'
	option wpa_disable_eapol_key_retries '1'

config wifi-device 'radio1'
	option type 'mac80211'
	option path '1e140000.pcie/pci0000:00/0000:00:01.0/0000:01:00.0'
	option band '5g'
	option channel '36'
	option htmode 'VHT80'
	option disabled '0'

config wifi-iface 'default_radio1'
	option device 'radio1'
	option network 'lan'
	option mode 'ap'
	option ssid 'OpenWrt5ghz'
	option disabled '1'

root@vera:~# cat /etc/config/dhcp

config dnsmasq
	option domainneeded '1'
	option boguspriv '1'
	option filterwin2k '0'
	option localise_queries '1'
	option rebind_protection '1'
	option rebind_localhost '1'
	option local '/lan/'
	option domain 'lan'
	option expandhosts '1'
	option nonegcache '0'
	option cachesize '1000'
	option authoritative '1'
	option readethers '1'
	option leasefile '/tmp/dhcp.leases'
	option resolvfile '/tmp/resolv.conf.d/resolv.conf.auto'
	option nonwildcard '1'
	option localservice '1'
	option ednspacket_max '1232'
	option filter_aaaa '0'
	option filter_a '0'

config dhcp 'wan'
	option interface 'wan'
	option ignore '1'

config odhcpd 'odhcpd'
	option maindhcp '0'
	option leasefile '/tmp/hosts/odhcpd'
	option leasetrigger '/usr/sbin/odhcpd-update'
	option loglevel '4'

root@vera:~# cat /etc/config/firewall

config defaults
	option syn_flood '1'
	option input 'ACCEPT'
	option output 'ACCEPT'
	option forward 'REJECT'

config zone
	option name 'lan'
	option input 'ACCEPT'
	option output 'ACCEPT'
	option forward 'ACCEPT'
	list network 'lan'

config zone
	option name 'wan'
	option input 'ACCEPT'
	option output 'ACCEPT'
	option forward 'ACCEPT'
	option masq '1'
	option mtu_fix '1'

config forwarding
	option src 'lan'
	option dest 'wan'

config rule
	option name 'Allow-DHCP-Renew'
	option src 'wan'
	option proto 'udp'
	option dest_port '68'
	option target 'ACCEPT'
	option family 'ipv4'

config rule
	option name 'Allow-Ping'
	option src 'wan'
	option proto 'icmp'
	option icmp_type 'echo-request'
	option family 'ipv4'
	option target 'ACCEPT'

config rule
	option name 'Allow-IGMP'
	option src 'wan'
	option proto 'igmp'
	option family 'ipv4'
	option target 'ACCEPT'

config rule
	option name 'Allow-DHCPv6'
	option src 'wan'
	option proto 'udp'
	option dest_port '546'
	option family 'ipv6'
	option target 'ACCEPT'

config rule
	option name 'Allow-MLD'
	option src 'wan'
	option proto 'icmp'
	option src_ip 'fe80::/10'
	list icmp_type '130/0'
	list icmp_type '131/0'
	list icmp_type '132/0'
	list icmp_type '143/0'
	option family 'ipv6'
	option target 'ACCEPT'

config rule
	option name 'Allow-ICMPv6-Input'
	option src 'wan'
	option proto 'icmp'
	list icmp_type 'echo-request'
	list icmp_type 'echo-reply'
	list icmp_type 'destination-unreachable'
	list icmp_type 'packet-too-big'
	list icmp_type 'time-exceeded'
	list icmp_type 'bad-header'
	list icmp_type 'unknown-header-type'
	list icmp_type 'router-solicitation'
	list icmp_type 'neighbour-solicitation'
	list icmp_type 'router-advertisement'
	list icmp_type 'neighbour-advertisement'
	option limit '1000/sec'
	option family 'ipv6'
	option target 'ACCEPT'

config rule
	option name 'Allow-ICMPv6-Forward'
	option src 'wan'
	option dest '*'
	option proto 'icmp'
	list icmp_type 'echo-request'
	list icmp_type 'echo-reply'
	list icmp_type 'destination-unreachable'
	list icmp_type 'packet-too-big'
	list icmp_type 'time-exceeded'
	list icmp_type 'bad-header'
	list icmp_type 'unknown-header-type'
	option limit '1000/sec'
	option family 'ipv6'
	option target 'ACCEPT'

config rule
	option name 'Allow-IPSec-ESP'
	option src 'wan'
	option dest 'lan'
	option proto 'esp'
	option target 'ACCEPT'

config rule
	option name 'Allow-ISAKMP'
	option src 'wan'
	option dest 'lan'
	option dest_port '500'
	option proto 'udp'
	option target 'ACCEPT'

brada4 · September 15, 2024, 4:37am

Reset your device and look for signs of compromise in your home.
Accept all wan means whole world was rhere
And you are not in Panamá

This is not auto detected or default config. It is messed up to unfixable.

gtxent · September 15, 2024, 4:48am

I'm currently debugging the unit, which is why WAN is configured to accept all traffic (as the unit is functioning as an AP downstream from another router). I also have UART connected, and there’s nothing unusual in U-Boot.

After extensive testing and experimenting with various configurations (which is why the current config is modified), I've determined that the issue is that phy1 is not detected as 5GHz capable, as mentioned in my original post. Phy0, which operates at 2.4GHz, works fine.

I uploaded the logs to Gist immediately after the installation, as noted in the first post.

I'm uncertain whether this problem is related to the kernel, the driver, or the WiFi firmware, which is why I'm seeking assistance here. I plan to compare the differences in kernel versions, WiFi drivers, etc., between 22.03.5 and the current setup.

@andyboeh, are you no longer using this unit?

Any advice or tips from anyone would be greatly appreciated!

brada4 · September 15, 2024, 6:23am

Run wifi config to detect wireless then log out and log in to luci and check again. power limit + Panama is not "default"
You absolutely have to use real country code to get any connectivity.

brada4 · September 15, 2024, 6:25am

between 22.03.5 and the current setup

dsa got enabled on switch most likely, so all /etc/config/network is inoperable.

JustMashingKeys · September 15, 2024, 6:38am

I'm encountering the same problem with the latest killing 5g/6g for me with a AW7916 (mt7916), I haven't figured out the issue yet.

brada4 · September 15, 2024, 7:21am

Worth reporting with versions via github. Before that:

Backup configuration
flash same image resetting configuration -> either confirm or acknowledge issue is fixed
23.05-SNAPSHOT and 23.05.4 - if any bug slipped into stable releases it becomes high priority
Next time make config backup before flashing bleeding edge code.

JustMashingKeys · September 15, 2024, 9:54am

I have a backup somewhere that's only a few weeks old, I'm just hoping to get this version working as I need a driver only available in it for installing the BE14 wifi card that I have sitting around and hope to install soon.

I'll report if it turns out to not be something I did stupid as most errors I encounter usually are. I didn't actually "flash" the image, I used the OWUT tool (same idea, I know).

brada4 · September 15, 2024, 12:47pm

So builtin 5ghz radio works fine?

gtxent · September 15, 2024, 5:14pm

just some cursory testing:
OpenWrt 22.03.7 5ghz works
to be continued...

gtxent · September 15, 2024, 6:16pm

logs from 22.03.7, 5ghz working:

gist.github.com

https://gist.github.com/gtxaspec/ecd6bd5f4429288a7d1d73dd356e5300

gistfile1.txt

root@OpenWrt:/# dmesg
[    0.000000] Linux version 5.10.221 (builder@buildhost) (mipsel-openwrt-linux-musl-gcc (OpenWrt GCC 11.2.0 r20341-591b7e93d3) 11.2.0, GNU ld (GNU Binutils) 2.37) #0 SMP Mon Jul 15 22:25:54 2024
[    0.000000] SoC Type: MediaTek MT7621 ver:1 eco:3
[    0.000000] printk: bootconsole [early0] enabled
[    0.000000] CPU0 revision is: 0001992f (MIPS 1004Kc)
[    0.000000] MIPS: machine is SERCOMM NA502
[    0.000000] Initrd not found or empty - disabling initrd
[    0.000000] VPE topology {2} total 2
[    0.000000] Primary instruction cache 32kB, VIPT, 4-way, linesize 32 bytes.
[    0.000000] Primary data cache 32kB, 4-way, PIPT, no aliases, linesize 32 bytes

This file has been truncated. show original

andyboeh · September 15, 2024, 7:13pm

No, I got rid of them in favor of ceiling-mounted APs. I desoldered the Z-Wave module and attached it to an ESP32. I've kept some spare devices, but I have no use for them.

gtxent · October 9, 2024, 6:07am

still experiencing this on latest master, no 5ghz. @Soro i see you are also using this, are you able to use the 5ghz radio?