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