Score:0

Persistent interface naming configuration not working anymore

om flag
Ror

I have multiple public cloud instances at OVH. Each one as a public interface and one or multiple private interfaces. All intances are on Debian 9. Since the naming is done automatically and I don't want to change the IP configuration every time the servers reboot, I used to set the private interfaces names persistently in

/etc/udev/rules.d/70-persistent-net.rules

like so

SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="MAC ADDRESS", NAME="interface_name"

But on my most recent installations, I noticed that this configuration does not work anymore (On reboot the servers get the automatic naming like ens4 or eth1). Is there any alternative so that I can persistently name the interfaces ?

mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.