On Saturday 12 December 2020 at 14:15:53, Antony Stone wrote:
> Historically, I've been used to udev and /etc/udev/rules.d/70-persistent-
> net.rules doing this, where I can specify the name I want for each
> interface according to its MAC address.
> 1. how can I get 70-persistent-net.rules to carry on working under Beowulf?
>
> 2. what's the "correct" way to get my interfaces named the way I want,
> according to their MAC addresses, under Beowulf?
So, I have found a workaround:
1. Create /etc/udev/rules.d/70-persistent-net.rules containing a set of rules
such as:
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*",
ATTR{address}=="78:ac:c0:f7:89:f7", ATTR{dev_id}=="0x0", ATTR{type}=="1",
KERNEL=="eth*", NAME="xeth0"
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*",
ATTR{address}=="00:e0:4c:80:21:6b", ATTR{dev_id}=="0x0", ATTR{type}=="1",
KERNEL=="eth*", NAME="xeth1"
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*",
ATTR{address}=="00:e0:4c:80:21:6c", ATTR{dev_id}=="0x0", ATTR{type}=="1",
KERNEL=="eth*", NAME="xeth2"
The names are in the order I want them, but prefixed with "x" so they don't
conflict with what the kernel decided to call them as it booted.
2. Add some sections to /etc/network/interfaces:
auto xeth0 xeth1 xeth2
iface xeth0 inet manual
up ip link set xeth0 down
up ip link set xeth0 name eth0
iface xeth1 inet manual
up ip link set xeth1 down
up ip link set xeth1 name eth1
iface xeth2 inet manual
up ip link set xeth2 down
up ip link set xeth2 name eth2
That re-renames the (already pseudo-renamed) interfaces to what I really want.
I can then follow that with the standard:
auto eth0
iface eth0 inet static
address 192.168.36.9
netmask 255.255.255.0
gateway 192.168.36.5
etc.
I would still *really like* to know:
1. how can I get 70-persistent-net.rules to carry on working as it used to,
under Beowulf? (I never had to do this sort of workaround in Jessie or
before.)
2. what's the "correct" way to get my interfaces named the way I want,
according to their MAC addresses, under Beowulf, and therefore also Chimaera?
Thanks,
Antony.
--
These clients are often infected by viruses or other malware and need to be
fixed. If not, the user at that client needs to be fixed...
- Henrik Nordstrom, on Squid users' mailing list
Please reply to the list;
please *don't* CC me.