Same NIC name to MAC mapping on FreeBSD

[Willem Jan Withagen]

On 01/07/2015 05:42, Julian Elischer wrote:
> On 7/1/15 6:56 AM, Adrian Chadd wrote:
>> Hi,
>>
>> If we don't support this as part of the interface renaming stuff, it
>> would certainly be good to.
>>
>>
>> a-
>>
>>
>> On 29 June 2015 at 21:36, Wei Hu <weh at microsoft.com> wrote:
>>>> -----Original Message-----
>>>> From: owner-freebsd-net at freebsd.org [mailto:owner-freebsd-
>>>> net at freebsd.org] On Behalf Of Paul S.
>>>> Sent: Monday, June 29, 2015 7:53 PM
>>>> To: freebsd-net at freebsd.org
>>>> Subject: Re: Same NIC name to MAC mapping on FreeBSD
>>>>
>>>> On my production systems, I've never seen it deviate without hardware
>>>> changes.
>>>>
>>>> Are you seeing otherwise?
>>>>
>>> In Hyper-V, if say three NICs were assigned to the VM, I got
>>> following mapping
>>> Initially:
>>>
>>> Hn0 -> MAC 0
>>> Hn1 -> MAC 1
>>> Hn2 -> MAC2
>>>
>>> Then if I remove the NIC with MAC 1 and reboot, I want the other two
>>> interfaces to keep the same
>>> Names instead of reassigning hn1 to MAC2. This is a requirement from
>>> virtual appliance
>>> Vendor to retain such mappings.  I am wondering if there is any way
>>> to do this without
>>> Asking customer or manually editing any config files.
> do interface arrivals show up in devd? if so they could be renamed on
> arrival
> I vaguely remember being able to do this some years ago but I can't
> remember the details.

This sounds horribly like the Linux solution, where I always have to
refind eth0 and eth1 because the assignments in the devd config.
Swapping a disk to another system, changes MACs and looses the devices. :(

But I've been bitten so often now, that I do know where to look.

Bhyve virtualisation and disk image replication is one of the cases
where this comes into play.

--WjW