Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #246900
| From | David Wright <deblis@lionunicorn.co.uk> |
|---|---|
| Newsgroups | linux.debian.user |
| Subject | Re: networking.service fails |
| Date | 2022-04-04 05:50 +0200 |
| Message-ID | <E8lT3-6jTo-1@gated-at.bofh.it> (permalink) |
| References | <BJng5-5q1-5@gated-at.bofh.it> <BJng5-5q1-3@gated-at.bofh.it> <BJv3Y-1wp-9@gated-at.bofh.it> <BJw9I-27K-5@gated-at.bofh.it> <E8kaB-6ivc-9@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
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.
Cheers,
David.
Back to linux.debian.user | Previous | Next — Next in thread | Find similar | Unroll thread
Re: networking.service fails David Wright <deblis@lionunicorn.co.uk> - 2022-04-04 05:50 +0200
Re: networking.service fails Greg Wooledge <greg@wooledge.org> - 2022-04-04 06:00 +0200
Re: networking.service fails Reco <recoverym4n@enotuniq.net> - 2022-04-11 08:20 +0200
Re: networking.service fails Dmitry Katsubo <dma_k@mail.ru> - 2022-04-12 23:30 +0200
csiph-web