| 1 |
On Fri, Dec 23, 2016 at 8:57 PM, lee <lee@××××××××.de> wrote: |
| 2 |
> Tom H <tomh0665@×××××.com> writes: |
| 3 |
|
| 4 |
|
| 5 |
>> [1] There's no need to learn/use the udev rules syntax. I use the |
| 6 |
>> following in "/etc/systemd/network/" on a Debian 8 system with |
| 7 |
>> sysvinit-as-pid1: |
| 8 |
>> |
| 9 |
>> [Match] |
| 10 |
>> MACAddress=can't_be_bothered_to_look_it_up |
| 11 |
>> [Link] |
| 12 |
>> Name=en0 |
| 13 |
> |
| 14 |
> Thanks! |
| 15 |
|
| 16 |
You're welcome. |
| 17 |
|
| 18 |
|
| 19 |
> What happens when you replace the card with another one that has a |
| 20 |
> different MAC? Shouldn't an assignment like this rather go by the |
| 21 |
> unrecognisable name? I'd find that more consistent. |
| 22 |
|
| 23 |
AFAIK, you have three possibilities. |
| 24 |
|
| 25 |
1) If you're renaming a NIC via its MAC address, you have to edit the |
| 26 |
config file thatlinks the NIC's names and its MAC address. |
| 27 |
|
| 28 |
2) If you're using udev's predictable names, the NIC'll have the same |
| 29 |
(more or less complex) name if you use the same slot. |
| 30 |
|
| 31 |
3) If you're using the kernel names, you have no guarantee that ethX |
| 32 |
will be assigned to the same NIC at every bot. |
Archives