tl;dr - a renamed dummy interface is not persisting across reboots on Cent6. I have a situation where I need to rename a dummy interface on my system. I have a total of 3 dummy interfaces: dummy0 dummy1 adummy0 I've been doing some puppet testing in a vbox VM to get this all sorted out to deploy to a group of boxes. Every time I reboot my VM, it comes up WITHOUT adummy0, but I notice there is now an unconfigured dummy2. I've tried everything from adding aliases to /etc/modprobe.d/dummyopts.conf to renaming the interface via "ip" (ip link set dummy2 name adummy0). This is all fine during use, even during a network restart. But as soon as I restart the VM, it comes back up broken. I for the life of me have been unable to figure out why. I could use some help in narrowing down why this won't persist across reboots. I can write a startup script to deal with it, but it doesn't seem like a good solution. Thanks, Frank
On Wed, May 27, 2015 at 1:37 AM, Frank Even <lists+centos.org at elitists.org> wrote:> tl;dr - a renamed dummy interface is not persisting across reboots on Cent6. > > I have a situation where I need to rename a dummy interface on my system. > > I have a total of 3 dummy interfaces: > > dummy0 > dummy1 > adummy0 > > I've been doing some puppet testing in a vbox VM to get this all > sorted out to deploy to a group of boxes. Every time I reboot my VM, > it comes up WITHOUT adummy0, but I notice there is now an unconfigured > dummy2. > > I've tried everything from adding aliases to > /etc/modprobe.d/dummyopts.conf to renaming the interface via "ip" (ip > link set dummy2 name adummy0). This is all fine during use, even > during a network restart. But as soon as I restart the VM, it comes > back up broken. > > I for the life of me have been unable to figure out why. I could use > some help in narrowing down why this won't persist across reboots. I > can write a startup script to deal with it, but it doesn't seem like a > good solution. > > Thanks, > FrankAnybody have any insights?
Frank Even wrote:> On Wed, May 27, 2015 at 1:37 AM, Frank Even > <lists+centos.org at elitists.org> wrote: >> tl;dr - a renamed dummy interface is not persisting across reboots on >> Cent6. >> >> I have a situation where I need to rename a dummy interface on my >> system. >> >> I have a total of 3 dummy interfaces: >> >> dummy0 >> dummy1 >> adummy0 >> >> I've been doing some puppet testing in a vbox VM to get this all >> sorted out to deploy to a group of boxes. Every time I reboot my VM, >> it comes up WITHOUT adummy0, but I notice there is now an unconfigured >> dummy2. >> >> I've tried everything from adding aliases to >> /etc/modprobe.d/dummyopts.conf to renaming the interface via "ip" (ip >> link set dummy2 name adummy0). This is all fine during use, even >> during a network restart. But as soon as I restart the VM, it comes >> back up broken. >> >> I for the life of me have been unable to figure out why. I could use >> some help in narrowing down why this won't persist across reboots. I >> can write a startup script to deal with it, but it doesn't seem like a >> good solution. >> > > Anybody have any insights?What's in /etc/udev/rules.d/70-persistant-net.rules? mark
Reasonably Related Threads
- dummy interface shenanigans - CentOS6
- dummy interface shenanigans - CentOS6
- Unable to get dummy interfaces to persist across reboots in CentOS 8
- Unable to get dummy interfaces to persist across reboots in CentOS 8
- Unable to get dummy interfaces to persist across reboots in CentOS 8