Ubuntu
netplan.io package

  1. Cosmic (18.10)
  2. Bug #1804861
  3. Comment #8

Comment 8 for bug 1804861

Revision history for this message
Mathieu Trudel-Lapierre (cyphermox) wrote :

I compiled three different cases and their behavior (see attached). In each case, I have included the netplan config, contents of files in /run/systemd/network and the output of 'ip link':

- Case A: MAC is unset in netplan config (I do not think MAAS allows this right now):
 - here, the system behaves correctly. MTUs are correctly set, devices gain a MAC address in b2:31:91:*. I am not sure yet what assigns it that, I think it's the kernel.

- Case B: using a custom MAC address for the new bond interface (possible in MAAS)
 - here, the system again behaves correctly. MTUs are correctly set, and devices all get the same MAC address as defined. I used "52:54:45:be:de:ad"; I believe any MAC under the range for virtualized devices should work (52:54:*), obviously any valid MAC that doesn't already exist on the network is fine to use.

- Case C: using the MAC of the first physical interface (default in MAAS)
 - The VLAN under the bond gets the wrong MTU (9000), due to the imprecise matching. All devices get the same MAC, the one originally set to ens6 in my example (52:54:00:25:ba:4f).