:: Re: [DNG] Ethernet names revisited
Top Page
Delete this message
Reply to this message
Author: Steve Litt
Date:  
To: dng
Subject: Re: [DNG] Ethernet names revisited
On Sat, 12 Dec 2020 16:06:03 +0100
Antony Stone <Antony.Stone@???> wrote:

> On Saturday 12 December 2020 at 15:27:08, dng@??? wrote:
>
> > On 12-12-2020 14:15, Antony Stone wrote:
> > >
> > > According to https://wiki.debian.org/NetworkInterfaceNames the
> > > old 70- persistent-net.rules system _should_ still work in Buster
> > > / Beowulf, but I can't work out how to get it to do so.
> >
> > From what I understand after some research you need an additional
> >
> > /etc/udev/rules.d/10-network.rules as follows:
> > SUBSYSTEM=="net", ATTR{address}=="90:e6:ba:01:00:01", NAME="eth0"
> > SUBSYSTEM=="net", ATTR{address}=="90:e6:ba:01:00:02", NAME="eth1"
> > SUBSYSTEM=="net", ATTR{address}=="90:e6:ba:01:20:01", NAME="eth2"
>
> Thanks, but no - it makes no difference.
>
> I tried:
>
> 1. Adding that file and keeping 70-persistent-net.rules as well
>
> 2. Adding that file and removing 70-persistent-net.rules
>
> 3. Both the above both with and without net.ifnames=0 in the kernel
> boot parameters.
>
> In every case I continue to get eth0 and eth1 as my PCI card, and the
> motherboard interface as eth2.
>
>
> Anyone else got any useful ideas?


You can create one or a few very simple shellscripts to turn stuff like
eno01y0u5uck02 into eth0, as long as the device isn't moved around,
which ports on a pci card wouldn't be. Another Devuaner and I wrote the
basics of such a script and posted it on this mailing list, several
years ago.

Sorry, but I'm on a tight deadline and can't research
anything more than this memory. Perhaps somebody else knows.

SteveT

Steve Litt
Autumn 2020 featured book: Thriving in Tough Times
http://www.troubleshooters.com/thrive