On Saturday 12 December 2020 at 16:06:29, tito via Dng wrote:
> On Sat, 12 Dec 2020 14:15:53 +0100 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.
> >
> > The file didn't exist (although the directory did) on my Beowulf
> > system, so I created one with the appropriate contents, and I now get
> > messages while the kernel is booting:
> >
> > udevd[441]: Error changing net interface name eth2 to eth0: File exists
> > udevd[441]: could not rename interface '4' from 'eth2' to 'eth0': File
> > exists
> > udevd[438]: Error changing net interface name eth1 to eth2: File exists
> > udevd[438]: could not rename interface '3' from 'eth1' to 'eth2': File
> > exists
> > udevd[445]: Error changing net interface name eth0 to eth1: File exists
> > udevd[445]: could not rename interface '2' from 'eth0' to 'eth1': File
> > exists
> > I _have_ tried adding "net.ifnames=0" to the kernel boot line; this
> > makes no difference.
> Hi,
> You can:
>
> 1) delete the persistent net names file and get the interfaces with
> old style names but eventually reordered (with net.ifnames=0).
I do not have a problem with the style of the names.
I am getting eth0 and eth1 on my PCI card and eth2 on the motherboard.
I want eth0 on the motherboard and eth1 and eth2 on the PCI card.
> 2) use a new net persistent names file using mac address or pci bus (use
> lspci to get it):
>
> SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*",
> ATTR{address}=="00:00:00:00:00:ea", ATTR{type}=="1", KERNEL=="?*",
> NAME:="eth0"
> SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*",
> ATTR{address}=="00:00:00:00:00:eb", ATTR{type}=="1", KERNEL=="?*",
> NAME:="eth1"
Sorry, how is that different from what I already did above?
Regards,
Antony.
--
I lay awake all night wondering where the sun went, and then it dawned on me.
Please reply to the list;
please *don't* CC me.
_______________________________________________
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
