Re: networking.service fails
On Sun, Apr 03, 2022 at 10:48:31PM -0500, David Wright wrote:
> On Mon 04 Apr 2022 at 02:38:39 (+0200), Dmitry Katsubo wrote:
> > On 2021-02-17 14:21, Henning Follmann wrote:
> >
> > > Are you using eth0, eth1?
> > > Or are you using predictable network names?
> > > https://wiki.debian.org/NetworkInterfaceNames
> > Well, I use eth0/eth1 as I have renamed them from predictable network names via /etc/udev/rules.d/70-persistent-net.rules:
> >
> > ACTION=="add", SUBSYSTEM=="net", ATTR{address}=="00:17:e8:92:b7:77", KERNEL=="eth*", NAME="eth0"
> > ACTION=="add", SUBSYSTEM=="net", ATTR{address}=="00:17:20:53:44:58", KERNEL=="eth*", NAME="eth1"
>
> That is a really bad idea. If you're going to rename interfaces
> yourself, then choose different names from anything that's already
> used or could potentially be used.
It's also worth pointing out that /etc/udev/rules.d/70-persistent-net.rules
was deprecated in buster (Debian 10). According to the release notes,
it *may* work, or it may not. Users were instructed to migrate away
from it.
It would not surprise me one bit if there's a race condition which causes
the renaming done by 70-persistent-net.rules to occur at the wrong time,
if it even happens at all.
Reply to: