@elbertmai , does the phy macadress fix in userspace work for you?
I upgraded my U6+ a couple of days ago. This time from main without any local changes. Today I noticed that the advertiesed BSSID wasn't what I expected.
Looking closer I see that the hotplug script has run and set the correct phy addresses, but the AP interfaces are stll using the bogus default adress:
root@u6plus:~# grep . /sys/class/ieee80211/phy*/macaddress
/sys/class/ieee80211/phy0/macaddress:e6:38:83:e5:85:d4
/sys/class/ieee80211/phy1/macaddress:e6:38:83:e5:85:d5
root@u6plus:~# grep . /sys/class/net/phy*/address
/sys/class/net/phy0-ap0/address:00:0c:43:26:60:00
/sys/class/net/phy1-ap0/address:82:0c:43:26:60:00
Guessing the problem is that the hotplug script is running too late at boot?
Restarting wifi, e.g, by running "/sbin/wifi", fixes the issue. So it's only a boot time problem.
But sitll, I don't think that's good enough? We should have the correct and stable BSSIDs from boot. That's the ones that will be actually used.
I believe we need https://github.com/openwrt/mt76/pull/817 or another solution allowing the driver to fetch the correct macaddress.
(this issue is probably not unique to the U6+ - I assume the same affects all devices named in target/linux/mediatek/filogic/base-files/etc/hotplug.d/ieee80211/11_fix_wifi_mac. And similar files for other targets)