Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.os.linux.networking > #4032
| From | Pascal Hambourg <pascal@plouf.fr.eu.org> |
|---|---|
| Newsgroups | comp.os.linux.networking |
| Subject | Re: Fixed IP addreses on network. |
| Date | 2017-04-01 09:41 +0200 |
| Organization | Plouf ! |
| Message-ID | <obnlk4$24mb$1@saria.nerim.net> (permalink) |
| References | <fcRCA.432076$Tb4.251145@fx03.fr7> <objbri$e95$1@dont-email.me> <bni0rd-0if.ln1@minas-tirith.valinor> <obkh5h$s49$1@dont-email.me> <1873rd-pm7.ln1@minas-tirith.valinor> |
Le 01/04/2017 à 02:01, Carlos E. R. a écrit : >> >> <https://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/> > > For one thing, it is not really systemd, but udev which is involved. It > comes now in the same package, that's true. The udev version introducing predictable network interface names is a part of the systemd package. So yes, it is systemd. > Now read this paragraph right at the start: > > "The classic naming scheme for network interfaces applied by the kernel > is to simply assign names beginning with "eth0", "eth1", ... to all > interfaces as they are probed by the drivers. As the driver probing is > generally not predictable for modern technology "Modern technology" actually standing for "systemd/udev". > The kernel does not create the interfaces always in the same order, so > what one day is eth0 on the next boot could become eth1, if you have > more than one interface. That's the big problem, and it comes right from > the kernel. Actually the problem comes from the asynchronous way "modern technology" probes hardware and loads drivers. > First they tried to use the MAC address to fix the name, but did not > work well. It has worked pretty well here, except on a Sun SPARC workstation where all interfaces have the same MAC address by design, which got udev confused. > So the problem originates from the kernel. I beg to differ. I have perfectly stable kernel-defined interface names on a machine *not* running udev. > systemd/udev simply corrects the issue. I'd rather say systemd/udev corrects the issue it created itself.
Back to comp.os.linux.networking | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Fixed IP addreses on network. Doug Laidlaw <laidlaws@hotkey.net.au> - 2017-03-30 03:23 +1100
Re: Fixed IP addreses on network. Pascal Hambourg <pascal@plouf.fr.eu.org> - 2017-03-29 20:57 +0200
Re: Fixed IP addreses on network. Doug Laidlaw <laidlaws@hotkey.net.au> - 2017-03-30 06:20 +1100
Re: Fixed IP addreses on network. William Unruh <unruh@invalid.ca> - 2017-03-29 21:01 +0000
Re: Fixed IP addreses on network. Doug Laidlaw <laidlaws@hotkey.net.au> - 2017-03-30 23:32 +1100
Re: Fixed IP addreses on network. Pascal Hambourg <pascal@plouf.fr.eu.org> - 2017-03-30 20:28 +0200
Re: Fixed IP addreses on network. Gordon <Gordon@clear.net.nz> - 2017-03-31 05:23 +0000
Re: Fixed IP addreses on network. robert.wolfe@wildcat.uuhec.net (Robert Wolfe) - 2017-03-30 13:27 +0000
Re: Fixed IP addreses on network. robert.wolfe@wildcat.uuhec.net (Robert Wolfe) - 2017-03-30 13:28 +0000
Re: Fixed IP addreses on network. Pascal Hambourg <pascal@plouf.fr.eu.org> - 2017-03-30 20:34 +0200
Re: Fixed IP addreses on network. Richard Kettlewell <invalid@invalid.invalid> - 2017-03-30 20:20 +0100
Re: Fixed IP addreses on network. Gordon <Gordon@clear.net.nz> - 2017-03-31 05:44 +0000
Re: Fixed IP addreses on network. "Jonathan N. Little" <lws4art@gmail.com> - 2017-03-30 16:56 -0400
Re: Fixed IP addreses on network. Pascal Hambourg <pascal@plouf.fr.eu.org> - 2017-03-31 00:18 +0200
Re: Fixed IP addreses on network. "Jonathan N. Little" <lws4art@gmail.com> - 2017-03-30 18:52 -0400
Re: Fixed IP addreses on network. Pascal Hambourg <pascal@plouf.fr.eu.org> - 2017-03-31 19:38 +0200
Re: Fixed IP addreses on network. ray carter <ray@zianet.com> - 2017-03-30 14:04 +0000
Re: Fixed IP addreses on network. "Jonathan N. Little" <lws4art@gmail.com> - 2017-03-30 12:33 -0400
Re: Fixed IP addreses on network. "Carlos E. R." <robin_listas@es.invalid> - 2017-03-31 01:59 +0200
Re: Fixed IP addreses on network. "Jonathan N. Little" <lws4art@gmail.com> - 2017-03-30 23:10 -0400
Re: Fixed IP addreses on network. Gordon <Gordon@clear.net.nz> - 2017-03-31 05:34 +0000
Re: Fixed IP addreses on network. "Jonathan N. Little" <lws4art@gmail.com> - 2017-03-31 08:43 -0400
Re: Fixed IP addreses on network. Jorgen Grahn <grahn+nntp@snipabacken.se> - 2017-03-31 14:10 +0000
Re: Fixed IP addreses on network. "Jonathan N. Little" <lws4art@gmail.com> - 2017-03-31 11:02 -0400
Re: Fixed IP addreses on network. Pascal Hambourg <pascal@plouf.fr.eu.org> - 2017-03-31 19:45 +0200
Re: Fixed IP addreses on network. "Carlos E. R." <robin_listas@es.invalid> - 2017-04-01 02:01 +0200
Re: Fixed IP addreses on network. Pascal Hambourg <pascal@plouf.fr.eu.org> - 2017-04-01 09:41 +0200
Re: Fixed IP addreses on network. "Carlos E. R." <robin_listas@es.invalid> - 2017-04-01 12:50 +0200
Re: Fixed IP addreses on network. Pascal Hambourg <pascal@plouf.fr.eu.org> - 2017-04-02 00:17 +0200
Re: Fixed IP addreses on network. "Carlos E. R." <robin_listas@es.invalid> - 2017-04-02 01:22 +0200
Re: Fixed IP addreses on network. Pascal Hambourg <pascal@plouf.fr.eu.org> - 2017-04-02 11:41 +0200
Re: Fixed IP addreses on network. Jerry Peters <jerry@example.invalid> - 2017-04-02 20:00 +0000
Re: Fixed IP addreses on network. Jerry Peters <jerry@example.invalid> - 2017-04-02 19:57 +0000
Re: Fixed IP addreses on network. William Unruh <unruh@invalid.ca> - 2017-04-03 00:07 +0000
Re: Fixed IP addreses on network. Pascal Hambourg <pascal@plouf.fr.eu.org> - 2017-04-06 23:58 +0200
Re: Fixed IP addreses on network. John Carter <me@mymailsvr.org> - 2017-03-31 04:51 +0000
Re: Fixed IP addreses on network. Dave <noone$$@llondel.org> - 2017-04-02 14:39 -0700
csiph-web