search for: dummyopt

...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...

...ng 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...

Hello all, hoping someone can help me out here. I cannot get dummy interfaces on a new Cent8 build to persist across reboots. On Cent7 - this is the process I use: Create Dummies: # cat /etc/modules-load.d/dummy.conf dummy # cat /etc/modprobe.d/dummyopts.conf options dummy numdummies=4 # ip link add dummy0 type dummy ## - repeating a/ ascending dummyN adapters for as many needed # service network start # dracut -f Now this was different than even how 6 handled it, forget how I finally dug that up (possible I even asked here). I've applied...

...> > Hello all, hoping someone can help me out here. > > I cannot get dummy interfaces on a new Cent8 build to persist across reboots. > > On Cent7 - this is the process I use: > > Create Dummies: > # cat /etc/modules-load.d/dummy.conf > dummy > # cat /etc/modprobe.d/dummyopts.conf > options dummy numdummies=4 > # ip link add dummy0 type dummy > ## - repeating a/ ascending dummyN adapters for as many needed > # service network start > # dracut -f > > Now this was different than even how 6 handled it, forget how I > finally dug that up (possibl...

...> > Hello all, hoping someone can help me out here. > > I cannot get dummy interfaces on a new Cent8 build to persist across reboots. > > On Cent7 - this is the process I use: > > Create Dummies: > # cat /etc/modules-load.d/dummy.conf > dummy > # cat /etc/modprobe.d/dummyopts.conf > options dummy numdummies=4 > # ip link add dummy0 type dummy > ## - repeating a/ ascending dummyN adapters for as many needed > # service network start > # dracut -f > > Now? this? was? different than even how 6 handled it, forget how I > finally dug that up (possibl...

...me out here. > > > > I cannot get dummy interfaces on a new Cent8 build to persist across reboots. > > > > On Cent7 - this is the process I use: > > > > Create Dummies: > > # cat /etc/modules-load.d/dummy.conf > > dummy > > # cat /etc/modprobe.d/dummyopts.conf > > options dummy numdummies=4 > > # ip link add dummy0 type dummy > > ## - repeating a/ ascending dummyN adapters for as many needed > > # service network start > > # dracut -f > > > > Now this was different than even how 6 handled it, forget how...

...me out here. > > > > I cannot get dummy interfaces on a new Cent8 build to persist across reboots. > > > > On Cent7 - this is the process I use: > > > > Create Dummies: > > # cat /etc/modules-load.d/dummy.conf > > dummy > > # cat /etc/modprobe.d/dummyopts.conf > > options dummy numdummies=4 > > # ip link add dummy0 type dummy > > ## - repeating a/ ascending dummyN adapters for as many needed > > # service network start > > # dracut -f > > > > Now? this? was? different than even how 6 handled it, forget how...

...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 us...