11-23-2023, 11:21 PM
(This post was last modified: 11-23-2023, 11:22 PM by Kevin Kofler.)
Check your NetworkManager MAC address randomization settings:
https://wiki.archlinux.org/title/Network...domization
If randomization is disabled, but you still get everchanging MAC addresses, most likely the hardware does not store a fixed MAC address, or U-Boot fails to read it, so the kernel (or the hardware itself) ends up generating a random one at every boot. (The PinePhone had the same issue in early U-Boot versions, until they fixed U-Boot.) As a workaround, try configuring the NetworkManager MAC address randomization mode (see the link above) to "stable" instead of entirely disabled. Then NetworkManager will ignore the broken hardware MAC address and generate one per connection as a hash of the connection name and/or metadata instead.
Alternatively, you can also hardcode a specific MAC address to use in the NetworkManager configuration.
https://wiki.archlinux.org/title/Network...domization
If randomization is disabled, but you still get everchanging MAC addresses, most likely the hardware does not store a fixed MAC address, or U-Boot fails to read it, so the kernel (or the hardware itself) ends up generating a random one at every boot. (The PinePhone had the same issue in early U-Boot versions, until they fixed U-Boot.) As a workaround, try configuring the NetworkManager MAC address randomization mode (see the link above) to "stable" instead of entirely disabled. Then NetworkManager will ignore the broken hardware MAC address and generate one per connection as a hash of the connection name and/or metadata instead.
Alternatively, you can also hardcode a specific MAC address to use in the NetworkManager configuration.