bonded network MAC keeps changing

[ricostuart]

I've got my unraid server running balance-alb (6) as it has 4 integrated network ports. Its a QNAP device, so its not using an addon network card. eth 1 - eth 4 have correct sequential MAC showing, however the bonded address keeps changing to something random each reboot.

EG: qnap MAC: 24:5E:BE:23:8F:00, 24:5E:BE:23:8E:FF,  24:5E:BE:23:8F:01, 24:5E:BE:23:8F:02. The MAC currently being used is : 66:59:F1:DF:48:F7 showing on eth1  (for some reason). eth0 is showing on unraid as 24:5E:BE:23:8F:02. 

After a reboot and plugging in all 4 connections, its now using mac : 82:72:39:55:CF:C5

 

Is there a way of getting Unraid to just use one mac and stick with it? I know i can do static ip on unraid which will solve alot of problems, but I'd prefer to set static ip via my router so its easier for me to adjust things such as my dns, etc.

 

Thanks

server-diagnostics-20230929-1325.zip

[Mainfrezzer]

"r8169 0000:05:00.0: can't read MAC address, setting random one"

thats your issue most likely.

If i remember correctly its based on the sysnic, which in your case is the r8169. (which should probably be r8168) you should probably get the driver from the app section and blacklist that driver and see if that fixes the random mac story

Edited September 29, 2023 by Mainfrezzer

[ricostuart]

I've instaled the drivers (thanks for that!) and I've rebooted, but still the mac isnt right?

 

 

server-diagnostics-20230929-1422.zip

[Mainfrezzer]

mhmm, from the logs and what i can see it looks right

 

Sep 29 14:11:21 server rc.inet1: ip link set eth0 master bond0 up type bond_slave
Sep 29 14:11:21 server kernel: eth0: 0xffffc90000149000, 9e:b0:39:a4:e8:d2, IRQ 49
Sep 29 14:11:21 server kernel: bond0: (slave eth0): Enslaving as a backup interface with a down link
Sep 29 14:11:21 server rc.inet1: ip link set eth1 down
Sep 29 14:11:21 server rc.inet1: ip link set eth1 master bond0 up type bond_slave
Sep 29 14:11:21 server kernel: bond0: (slave eth1): Enslaving as a backup interface with a down link
Sep 29 14:11:21 server rc.inet1: ip link set eth2 down
Sep 29 14:11:21 server rc.inet1: ip link set eth2 master bond0 up type bond_slave
Sep 29 14:11:21 server kernel: bond0: (slave eth2): Enslaving as a backup interface with a down link
Sep 29 14:11:21 server rc.inet1: ip link set eth3 down
Sep 29 14:11:21 server rc.inet1: ip link set eth3 master bond0 up type bond_slave
Sep 29 14:11:21 server kernel: bond0: (slave eth3): Enslaving as a backup interface with a down link
Sep 29 14:11:21 server rc.inet1: ip link set eth4 down
Sep 29 14:11:21 server rc.inet1: ip link set eth4 master bond0 up type bond_slave
Sep 29 14:11:21 server kernel: bond0: (slave eth4): Enslaving as a backup interface with a down link
Sep 29 14:11:21 server rc.inet1: ip link set name bond0 type bond primary eth0

 

br0: received packet on bond0 with own address as source address (addr:9e:b0:39:a4:e8:d2, vlan:0)

If that MAC isnt stable, i can only guess that its still randomly generated because the driver is loaded later, in that case, you would have to change the master of the bond to be eth1 or eth2 and let eth0 be a slave.
 

[ricostuart]

So after much testing, i figured it out! Thankfully that driver addon helped me out by showing how to blacklist a kernel driver. So, it seems my 4 main network ports are actually intel based. Now the realtek one (which has no serial showing when using lspci -vv) I have no idea what that is! There isnt a sneaky 5th network port! I do wonder if its got something to do with the front usb micro-b port? Thinking about it I believe it must as i think its ment to have direct link connection with a laptop, etc. Not somehting I've ever done......

Anyway, so I uninstalled the realtek addon, and under the system drivers I blacklisted the realtek driver. And its now showing as 4 ethernet ports correctly!

Thank you!