Re: [DNG] ethernet interface name swap (WAS: what has gone wrong with networking in ascii?
Rick Moen wrote on 16/07/18 07:44: Quoting Hendrik Boom (hend...@topoi.pooq.com): But I wold like to be able to run wheezy very occasionally -- there's an application I have that suffered the end-of-days in wheezy -- so I'd like to find another solution. http://www.enterprisenetworkingplanet.com/netos/article.php/3586546/Nail-Down-Network-Interface-Names-with-ifrename.htm Yes, "ifrename" is capable and easy to use for this purpose. However, one must make sure it runs before interfaces are configured, which unfortunately is not the default case for a choice of using "eudev" for configuration. (Primarily because "e" is before "i" in the natural ordering of startup script invocations). Thus, if your "/etc/network/interfaces" declares "allow-hotplug" for the interface(s) concerned, you need to take extra steps. For example, you can add "ifrename" as a required facility in "/etc/init/eudev" before enabling it. In other words, it's the four steps of a) disabling ifrename, b) do the edit, c) enable ifrenam, and d) update initramfs. (There are many other ways to achieve the same result of course) On the other hand, if your "interfaces" file declares "auto" for the interface(s) concerned, you don't need to correct anything, but it would suffice with steps c and d. Also, if your "interfaces" file is quiet about the interface(s) concerned, typically because you use one of the handy network management daemons, you still need to ensure that the ifrename facility is started before the network management daemon. This is likely to also be the default setting, so steps c and d would suffice. Ralph. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] ethernet interface name swap (WAS: what has gone wrong with networking in ascii?
Quoting Hendrik Boom (hend...@topoi.pooq.com): > But I wold like to be able to run wheezy very occasionally -- there's an > application I have that suffered the end-of-days in wheezy -- so I'd > like to find another solution. http://www.enterprisenetworkingplanet.com/netos/article.php/3586546/Nail-Down-Network-Interface-Names-with-ifrename.htm ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
[DNG] ethernet interface name swap (WAS: what has gone wrong with networking in ascii?
On Sat, Jul 14, 2018 at 07:03:13PM +0200, Stefan Krusche wrote: > Am Samstag, 14. Juli 2018 schrieb Hendrik Boom: > > (2) How should I go about tracking down the problem? > > > > I might add that ifconfig reports the usual interfaces of eth0, eth1, > > Have you checked they also have the same MAC address like before? The MAC addresses got swapped. Or rather, I suppose, the deignation eth0 and eth1 got swapped. I seem to remember somethign like that happened to me ten or fifteen years ago. Long enough ago that I forgot that this was a thing that might happen. That time I swapped the ethernet cables. But I wold like to be able to run wheezy very occasionally -- there's an application I have that suffered the end-of-days in wheezy -- so I'd like to find another solution. I suppose I'll have to find a way to define new device names for the physical ports and use those in all my configurations. Finding all explicit references to eth0 and eth1 in /etc is probably the esy part. I'm not sure how to time interfaces to physical ports. Some black magic incolcing udev? or vdev? or any of Devuan's udev replacements? -- hendrik > > Kind regards, > Stefan > > ___ > Dng mailing list > Dng@lists.dyne.org > https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
