Hi all.
Recently set up my first 18.04 server system, and I'm getting used to netplan and associated behavior.
I currently have netplan setup with both bonding and vlans:
The issue I am experiencing is that the MAC address being applied to the bond0 (and, subsequently, the slave interfaces and vlan interfaces) is not persisting. It is sometimes changing at reboot, and (I am not sure, and can't find indication in the logs) I am suspicious it is actually being changed partway through the boot process. Because the MAC address is flapping around like this, it's causing havoc with ARP propagation and breaking the connection.
I've had two different MACs, at least, show up:
42:9b:e9:39:6a:7b (seems to be a variant of actual hardware MACs)
ac:1f:6b:71:86:75 (not sure where this one is coming from)
Does anyone have any idea where this is coming from? Is there a more ideal solution than just hardcoding one of the MACs into the config?
Recently set up my first 18.04 server system, and I'm getting used to netplan and associated behavior.
I currently have netplan setup with both bonding and vlans:
Code:
network:
version: 2
renderer: networkd
ethernets:
eno1:
dhcp4: no
eno2:
dhcp4: no
bonds:
bond0:
interfaces: [eno1, eno2]
parameters:
mode: 802.3ad
mii-monitor-interval: 100
dhcp4: yes
vlans:
vlan30:
id: 30
link: bond0
dhcp4: yes
vlan99:
id: 99
link: bond0
dhcp4: yesI've had two different MACs, at least, show up:
42:9b:e9:39:6a:7b (seems to be a variant of actual hardware MACs)
ac:1f:6b:71:86:75 (not sure where this one is coming from)
Does anyone have any idea where this is coming from? Is there a more ideal solution than just hardcoding one of the MACs into the config?