aboutsummaryrefslogtreecommitdiffstats
path: root/target/linux/ramips
diff options
context:
space:
mode:
authorDavid Bauer <mail@david-bauer.net>2023-03-21 05:07:30 +0100
committerDavid Bauer <mail@david-bauer.net>2023-03-21 05:10:03 +0100
commitd52870125d57d39e73e6c305dd36fad44fe4a773 (patch)
tree37467f46ed7c1820473008bdce791bc40a3afe00 /target/linux/ramips
parentca330cac92240a882711cbe2fbf02f7231e47e9a (diff)
downloadupstream-d52870125d57d39e73e6c305dd36fad44fe4a773.tar.gz
upstream-d52870125d57d39e73e6c305dd36fad44fe4a773.tar.bz2
upstream-d52870125d57d39e73e6c305dd36fad44fe4a773.zip
ramips: fix Archer AX23 WiFi MAC address conflict
The original claim about conflicting MAC addresses is wrong. mac80211 does increment the first octet and sets the LA bit. This means our "workaround" actually leads to the issue while incrementing the last octet is safe. Signed-off-by: David Bauer <mail@david-bauer.net>
Diffstat (limited to 'target/linux/ramips')
-rw-r--r--target/linux/ramips/mt7621/base-files/etc/hotplug.d/ieee80211/10_fix_wifi_mac5
1 files changed, 1 insertions, 4 deletions
diff --git a/target/linux/ramips/mt7621/base-files/etc/hotplug.d/ieee80211/10_fix_wifi_mac b/target/linux/ramips/mt7621/base-files/etc/hotplug.d/ieee80211/10_fix_wifi_mac
index ffc643f42b..bf6c55a8fe 100644
--- a/target/linux/ramips/mt7621/base-files/etc/hotplug.d/ieee80211/10_fix_wifi_mac
+++ b/target/linux/ramips/mt7621/base-files/etc/hotplug.d/ieee80211/10_fix_wifi_mac
@@ -149,10 +149,7 @@ case "$board" in
;;
tplink,archer-ax23-v1)
hw_mac_addr="$(mtd_get_mac_binary config 0x8)"
- # 2.4 GHz MAC is MAC in EEPROm while 5GHz is EEPROM_MAC -1
- # However, mac80211 assigns consecutive addresses for each VAP
- # Which leads to conflicting addresses. Set the LA bit for 5Ghz instead.
- [ "$PHYNBR" = "1" ] && macaddr_setbit_la "$hw_mac_addr" > "/sys${DEVPATH}/macaddress"
+ [ "$PHYNBR" = "1" ] && macaddr_add "$hw_mac_addr" -1 > "/sys${DEVPATH}/macaddress"
;;
tplink,eap615-wall-v1)
hw_mac_addr="$(mtd_get_mac_binary product-info 0x8)"