Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.project > #10335
| From | Adam Borowski <kilobyte@angband.pl> |
|---|---|
| Newsgroups | linux.debian.project |
| Subject | Re: What is the problem with eth0 |
| Date | 2019-02-09 18:40 +0100 |
| Message-ID | <xpELE-6Kq-13@gated-at.bofh.it> (permalink) |
| References | <xpEBX-6H7-7@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Sat, Feb 09, 2019 at 06:06:31PM +0100, Ingo von Laer wrote: > Dear Sirs and Ladies, > with the implementation of the NetworkManager the little Problems began. > WFT, "Wired Connection 1" tree blanks an config-file in the etc. > The biggest Problem are the fancy new names for the Ethernet. What is the > problem with eth0? All server tools like isc-dhcp-server or FAI are using > eth0. If you must use the fancy names for the eth0 then implement it so > that other packages can use them too, or simpler leave the name eth0. You want predictable interface names, then. To switch them to predictable, append "net.ifnames=0" to kernel's cmdline; the argument will then be parsed by udev (the on-filesystem way to do so changes quite often). Easiest way to change the cmdline is "dpkg-reconfigure grub-*" where * can be "pc" or "efi" depending on how your machine boots. Meow! -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Remember, the S in "IoT" stands for Security, while P stands ⢿⡄⠘⠷⠚⠋⠀ for Privacy. ⠈⠳⣄⠀⠀⠀⠀
Back to linux.debian.project | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
What is the problem with eth0 Ingo von Laer <ivlaer@gmx.de> - 2019-02-09 18:30 +0100
Re: What is the problem with eth0 Adam Borowski <kilobyte@angband.pl> - 2019-02-09 18:40 +0100
Re: What is the problem with eth0 Geert Stappers <stappers@stappers.nl> - 2019-03-02 12:40 +0100
csiph-web