On Mon, 2015-05-11 at 12:16 +0200, Josselin Mouette wrote: > Ben Hutchings <ben@decadent.org.uk> wrote: > > The NM configuration is based on MAC addresses and doesn’t care about > > the interface name at all. This is the exact opposite of “handling > > dynamic names ungracefully”. > > Well, that's assuming hardware that has a permanent MAC address. What > does it do for virtual or cheap hardware that gets a different locally- > assigned address at each boot or hotplug? > > In most situations, the default behavior (starting a DHCP connection > when the first adapter is plugged on) is what you want. > > When you use manual configuration, the daemon’s default is to write > MAC-based configuration files, but you can change them to remove the > 802-3-ethernet/mac-address setting and use connection/interface-name > instead. > > See https://developer.gnome.org/NetworkManager/unstable/ref-settings.html I think you missed a point: permanent and locally-assigned MAC addresses are distinguishable, so Network Manager can and should avoid matching on the basis of a locally-assigned MAC address. Ben. -- Ben Hutchings For every action, there is an equal and opposite criticism. - Harrison
Attachment:
signature.asc
Description: This is a digitally signed message part