On 06.09.17 15:04, Andrew Pam via luv-main wrote: > On 06/09/17 14:52, Erik Christiansen via luv-main wrote: > > Now eth0 is eth0, and wlan0 is wlan0, a la established *nix usage, > > free of any crappy /dev/urandom-inspired Poetterwank, like > > enx0c5b8f279a64. (Or whatever it comes up as next week)
> On the other hand, you now revert to the problem this change was > introduced to address: Your network interfaces may change names > arbitrarily if you make any hardware changes - for example, inserting or > removing USB devices that provide a network interface (such as a mobile > phone in tethering mode), or a new PCI network adapter. You may then > need to use the udev MAC address based network interface renaming to > avoid issues. If device replacement should ever happen, then either that or I just install ifrename, and have it automatically handled by e.g.: $ more /etc/iftab # This file assigns persistent names to network interfaces. See iftab(5). eth0 mac 00:40:e0:83:e9:97 eth1 mac 00:15:00:30:82:17 OK, ifrename has to run before the interfaces come up, but it's worth delving into init scripts once or twice a decade, just for familiarity. In any event, interface names chosen by me are the non-negotiable requirement. A little effort to achieve that is amusing, and the opportunity to repel linux saboteurs is a bonus. At two companies I've looked after 12 - 20 hosts each, never replacing a NIC in over 2 decades, but adding two. Fiddling with interface names was bog standard sysadmin fare. Once done, recognisable names remained. Simples. Erik _______________________________________________ luv-main mailing list [email protected] https://lists.luv.asn.au/cgi-bin/mailman/listinfo/luv-main
