Lollifeet

Not sure what do you mean. In any case, I know how to install the missing key. I am just reporting this as a bug to fix in the image/installation process.

I have a somewhat related issue running Rock Pi S: https://forum.armbian.com/topic/18977-changing-mac-address-for-rockpis-21082-focal-linux-5145-rockchip64/
 
In my case all machines have the same MAC address, but I'm still interested to see what you learn?

Hi @TonyB.ca, I have another NanoPi Neo3 and I'm experiencing the same you are, I wonder what could be happening.
 
Right now, I have a stable build on Jammy, but I have another microSD with which I'm making tests to try to see how come the actual MAC from the device isn't picked up. Just now I finished building a current Bookworm based Armbian, but with u-boot being that of 2023.04 instead, same outcome. I know the board was released with u-boot 2017.sth, but I thought, what the hell, perhaps it's a bug in the 2022 versions.
 
In any case, I'm at a loss, I'll try to find other boards that ship with real MACs and see if there's any difference on how they're defined in configuration files or kernel builds. For example, the NanoPi R4S used to ship with a unique MAC, but due to shortage of parts or something they can't guarantee that now unless you place a considerable order; that doesn't happen with the Neo3, even if ordered just one they do come with a unique address.
 
If anyone comes across this thread and knows at least where we should look into, we'd appreciate it! I'm new to this kind of low level stuff.

I am allright with you and i find my MAC Address here
sudo i2cdump 0 0x51
i have a Neo3 with i2c eeprom and the mac is writing inside

and when i go to 
/etc/NetworkManager/system-connections# sudo nano Wired\ connection\ 1.nmconnection

i can see that the MAC is fixed
 
How can we patch this problem?
 

i watch this in u-boot????

si it can help you for a nanopi neo3
you can write a script like 
sudo nano extract_mac.sh
#!/bin/bash # Extraire l'adresse MAC de l'EEPROM mac_address="" mac_address+="$(sudo i2cget -y -f 0 0x51 0xfa c):$(sudo i2cget -y -f 0 0x51 0xfb c)" mac_address+=:"$(sudo i2cget -y -f 0 0x51 0xfc c):$(sudo i2cget -y -f 0 0x51 0xfd c)" mac_address+=:"$(sudo i2cget -y -f 0 0x51 0xfe c):$(sudo i2cget -y -f 0 0x51 0xff c)" # Supprimer les préfixes "0x" mac_address="${mac_address//0x/}" mac_address=$(echo $mac_address | tr '[:lower:]' '[:upper:]') echo "MAC address: $mac_address" # Extraire l'adresse MAC du fichier de configuration NetworkManager configured_mac_address="$(sudo grep "mac-address=" /etc/NetworkManager/system-connections/Wired\ connection\ 1.nmconnection | cut -d "=" -f 2)" # configured_mac_address="${configured_mac_address//:/}" echo "configured mac address: $configured_mac_address" # Comparer les adresses MAC if [[ "$mac_address" != "$configured_mac_address" ]]; then echo "Les adresses MAC sont différentes. Mise à jour nécessaire." # Mettre à jour le fichier de configuration NetworkManager avec la nouvelle adresse MAC sudo sed -i "s/mac-address=.*/mac-address=$mac_address/" /etc/NetworkManager/system-connections/Wired\ connection\ 1.nmconnection # Redémarrer NetworkManager pour prendre en compte les modifications sudo service NetworkManager restart echo "Adresse MAC mise à jour et redémarrage du systeme." # Redémarrer complètement le système pour prendre en compte les modifications sudo reboot else echo "Les adresses MAC sont identiques." fi  and
and to start script

it's working well for me
 
best regards

Greetings All,
 
If I run one of the Friendly distributions, they use the correct (physical) MAC address. My 3 are as follows:

80:34:28:79:4e:5c
80:34:28:79:2e:07
80:34:28:79:20:31
 
From this we can tell that FriendlyElec uses "80:34:28" as their vendor code. The remaining 3 digits compose the individual NIC address. Thanks for providing the script to work around the issue. It does what it needs to do, but it still raises the question as to why this is necessary. The FriendlyElec build does not require that we do this, so it would be great to have a base code fix. At some point I will try simply deleting the directory containing the script to see what happens ( - unless somebody else gets there first - 🙂 - ). For now, this script does what is needed ...

bracka@NanoPi-NEO3b:/etc/NetworkManager/system-connections$ hostnamectl
   Static hostname: NanoPi-NEO3b
         Icon name: computer
        Machine ID: f86b967515a04b7aa4ee086b7ee8f50b
           Boot ID: 7d724c0ff2a544f7959641728cacfe16
  Operating System: Ubuntu 20.04.6 LTS
            Kernel: Linux 5.15.78
      Architecture: arm64
bracka@NanoPi-NEO3b:/etc/NetworkManager/system-connections$ ls -al
total 8
drwxr-xr-x 2 root root 4096 Nov 26  2021 .
drwxr-xr-x 7 root root 4096 Jun 13 20:55 ..
 
Regards & Thank You,
Tony

yes i think they didn't read the i2c eeprom at start

You forgot something that i test, you can launch it directly. 
You just need to add this in the repository /etc/rc.local before the line "exit 0"
/bin/bash /etc/init.d/extract_mac.sh
If you do this, the script will launch automatically if the MAC didn't correspond, and if they correspond then he will don't reboot so you don't have to launch it manually if you had these line.

this is very coded with foot, but its working 
thanx you