JRD McLAREN Posted April 7, 2022 Share Posted April 7, 2022 Hello... after last update, I'm got this issue .. MAC address for wifi changed after reboot ... (and dhcp reservation does not work .. of course) It happen on all 5.15.x 5.16.x kernels .. Armbian 22.02.1 with Linux 5.16.11-sunxi - has problem Armbian 22.02.1 with Linux 5.15.25-sunxi - has problem downgrade to 5.10 works Armbian 22.02.1 with Linux 5.10.60-sunxi - Is OK .. Have anybody same problem ..?? is any way, how can I solve this issue ..? thanks ... for answer(s)... 0 Quote Link to comment Share on other sites More sharing options...
Werner Posted April 7, 2022 Share Posted April 7, 2022 Moved to P2P help. 0 Quote Link to comment Share on other sites More sharing options...
ManoftheSea Posted April 7, 2022 Share Posted April 7, 2022 A simple way to mask this problem is to set the mac address in the systemd.network or NetworkManager configuration files. 0 Quote Link to comment Share on other sites More sharing options...
remov-b4-flight Posted April 8, 2022 Share Posted April 8, 2022 Hi all , I have same issue. in dmesg, xradio_wlan mmc1:0001:1: no mac address provided, using random. It’s No due to NetworkManager. 0 Quote Link to comment Share on other sites More sharing options...
prkl Posted April 8, 2022 Share Posted April 8, 2022 12 hours ago, ManoftheSea said: A simple way to mask this problem is to set the mac address in the systemd.network or NetworkManager configuration files. How does one do that? I have this very same problem and it's annoying to use PiHole since macaddress is always changing 0 Quote Link to comment Share on other sites More sharing options...
JRD McLAREN Posted April 8, 2022 Author Share Posted April 8, 2022 short log from 5.15.25 kernel: Apr 6 22:22:03 opizerompd kernel: [ 14.085917] [drm] Initialized lima 1.2.0 20200215 for 1c40000.gpu on minor 0 Apr 6 22:22:03 opizerompd kernel: [ 14.381026] cfg80211: Loading compiled-in X.509 certificates for regulatory database Apr 6 22:22:03 opizerompd kernel: [ 14.386092] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7' Apr 6 22:22:03 opizerompd kernel: [ 14.443927] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2 Apr 6 22:22:03 opizerompd kernel: [ 14.443968] platform regulatory.0: Falling back to sysfs fallback for: regulatory.db Apr 6 22:22:03 opizerompd kernel: [ 14.445797] cfg80211: failed to load regulatory.db Apr 6 22:22:03 opizerompd kernel: [ 14.771399] xradio: XR819 device discovered Apr 6 22:22:03 opizerompd kernel: [ 14.772207] xradio_wlan mmc1:0001:1: no mac address provided, using random Apr 6 22:22:03 opizerompd kernel: [ 15.018782] xradio: hardware vers. 7.9 Apr 6 22:22:03 opizerompd kernel: [ 15.018816] xradio: firmware vers. 8 (WSM), build 5258, api 1060, cap 0x0003 Apr 6 22:22:03 opizerompd kernel: [ 15.018831] xradio: Config USE_EXTENSIONS Apr 6 22:22:03 opizerompd kernel: [ 15.024541] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht' Apr 6 22:22:03 opizerompd kernel: [ 15.615404] EXT4-fs (sda2): and shortlog from 5.10.60 kernel .. Apr 7 21:48:56 opizerompd kernel: [ 13.477921] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7' Apr 7 21:48:56 opizerompd kernel: [ 13.490193] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2 Apr 7 21:48:56 opizerompd kernel: [ 13.490224] platform regulatory.0: Falling back to sysfs fallback for: regulatory.db Apr 7 21:48:56 opizerompd kernel: [ 13.495445] cfg80211: failed to load regulatory.db Apr 7 21:48:56 opizerompd kernel: [ 13.697443] xradio: XR819 device discovered Apr 7 21:48:56 opizerompd kernel: [ 13.945300] xradio: hardware vers. 7.9 Apr 7 21:48:56 opizerompd kernel: [ 13.945314] xradio: firmware vers. 8 (WSM), build 5258, api 1060, cap 0x0003 Apr 7 21:48:56 opizerompd kernel: [ 13.945319] xradio: Config USE_EXTENSIONS Apr 7 21:48:56 opizerompd kernel: [ 13.950696] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht' Apr 7 21:48:56 opizerompd kernel: [ 14.948195] EXT4-fs (sda2): mou and something about NM .. Apr 7 21:51:27 opizerompd systemd[1]: Started WPA supplicant. Apr 7 21:51:28 opizerompd NetworkManager[1002]: <info> [1649361088.5341] NetworkManager (version 1.14.6) is starting... (for the first time) Apr 7 21:51:28 opizerompd NetworkManager[1002]: <info> [1649361088.5348] Read config: /etc/NetworkManager/NetworkManager.conf (lib: no-mac-addr-change.conf) (etc: 10-override-wifi-random-mac-disable.conf, 20-override-wifi-powersave-disable.conf) Apr 7 21:51:28 opizerompd NetworkManager[1002]: <info> [1649361088.5522] wifi-nl80211: (wlan0): using nl80211 for WiFi device control Apr 7 21:51:28 opizerompd systemd[1]: Started Network Manager. Apr 7 21:51:28 opizerompd NetworkManager[1002]: <info> [1649361088.6020] bus-manager: acquired D-Bus service "org.freedesktop.NetworkManager" Apr 7 21:51:28 opizerompd NetworkManager[1002]: <info> [1649361088.6193] manager[0xb5b020]: monitoring kernel firmware directory '/lib/firmware'. Apr 7 21:51:28 opizerompd NetworkManager[1002]: <info> [1649361088.6199] monitoring ifupdown state file '/run/network/ifstate'. Apr 7 21:51:28 opizerompd systemd[1]: Starting Network Manager Wait Online... Apr 7 21:51:28 opizerompd dbus-daemon[984]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.4' (uid=0 pid=1002 comm="/usr/sbin/NetworkManager --no-daemon ") Apr 7 21:51:28 opizerompd systemd[1]: Reached target Network. where is stored mac address for xradio ..? it is generated ..?? dtb or module patch is needed ..?? 0 Quote Link to comment Share on other sites More sharing options...
ManoftheSea Posted April 8, 2022 Share Posted April 8, 2022 https://askubuntu.com/questions/1121523/how-do-i-get-networkmanager-to-assign-a-fixed-mac-address-to-eth0 Set the "cloned mac address" in the profile https://unix.stackexchange.com/questions/501928/systemd-set-mac-address-and-ip-address Set the MACAddress property in the [link] section Note that only one of the above is needed, depending on what is managing your network devices. 0 Quote Link to comment Share on other sites More sharing options...
prkl Posted April 10, 2022 Share Posted April 10, 2022 I tried following the 1st link by running the sudo nmcli con modify command modified to my needs I'm using OrangePi over wifi and tried to make it a static macaddress. Ended up messing up the whole wifi connection 😅 So I had to remove the wifi from nmcli to remove whatever broke it. I'm curious now to know if it's just the command I did wrong. When I only modified the network name in the command it output: Quote Error: invalid or not allowed setting '802-3-ethernet': '802-3-ethernet' not among [connection, 802-11-wireless (wifi), 802-11-wireless-security (wifi-sec), 802-1x, ethtool, match, ipv4, ipv6, tc, proxy]. So since I'm on wifi I adapted it to sudo nmcli con modify NetworkName 802-11-wireless.cloned-mac-address 00:12:34:56:78:9a Is there a specific macaddress rule we must follow or something? 0 Quote Link to comment Share on other sites More sharing options...
egzumer Posted June 26, 2022 Share Posted June 26, 2022 I have the same problem. I installed Armbian 21.08.1 Focal with Linux 5.10.60-sunxi, it all worked as it should, then I run an "apt upgrade" which upgrades to Armbian 22.05.3 Focal with Linux 5.15.48-sunxi. It then switches to a new random wifi mac address on each reboot. The cable connection has permanent mac address. I tried to set cloned-mac-address but it then fails to connect with an error: "Activation: (wifi) association took too long, failing activation" 0 Quote Link to comment Share on other sites More sharing options...
JRD McLAREN Posted June 27, 2022 Author Share Posted June 27, 2022 (edited) Try to downgrade kernel via armbian-config to 5.10.60 armbian-config > System > Other >> MAC Address clone not work (I'm guess why ... ) another thread: Edited June 27, 2022 by JRD McLAREN 1 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.