FS#4068 - ath9k: Placeholder MAC address set on wireless device on Lantiq XRX200 (AVM FRITZ!Box 7430) #9051
Labels
flyspray
kernel
pull request/issue with Linux kernel related changes
release/21.02
pull request/issue targeted (also) for OpenWrt 21.02 release
doesnotcompete:
I am encountering issues with the wifi device on AVM FRITZ!Box 7430. The MAC address of the adapter is set to a placeholder value:
ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP qlen 1000
link/ether [REDACTED] brd ff:ff:ff:ff:ff:ff
4: br-lan: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP qlen 1000
link/ether [REDACTED] brd ff:ff:ff:ff:ff:ff
5: eth0.1@eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-lan state UP qlen 1000
link/ether [REDACTED] brd ff:ff:ff:ff:ff:ff
7: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-lan state UP qlen 1000
link/ether 00:02:03:04:05:06 brd ff:ff:ff:ff:ff:ff
This issue was reproducable on two separate devices, both with the 21.0.2 release (no matter whether the image was pre-built or self-compiled) and the latest SNAPSHOT image.
fritz_tffs_nand -d /dev/mtd1 -n macwlan
is able to read the correct MAC address from flash however. Attempts to reconfigure the MAC address during runtime with "ip" or by adding the "macaddr" option to /etc/config/wireless were not successful.I am trying to built a mesh network with multiple FRITZ!Box 7430 devices and the identical BSSID used by them seems to cause on the client network. I have no experience in developing drivers, but am comfortable in compiling OpenWrt from source. Does anyone have an idea on where I could start looking into this issue? I am not sure how the wireless device is configured with its MAC address during boot-up, but would be glad to try any suggestions on how this placeholder value could be overriden. I've attached a log showing the boot process.
The text was updated successfully, but these errors were encountered: