On Tue, Jul 18, 2017 at 05:15:06PM +0200, Sven-Haegar Koch wrote: > The VM is a VirtualBox (from Debian Unstable) with two virtual e1000 > network interfaces, both connected to different host-only adapters.
What about eth1, eth3 and idrac?
> Could this related to my "ln -s /dev/null
> /etc/systemd/network/99-default.link" trying to get rid of that ugly
> enFOO interface renaming introduced in Stretch?
I tried that and the only result of that was that network interfaces
added to the VM after booting were not renamed, the ones at boot time
still were. The only thing that prevented everything from being renamed
was to add net.ifnames=0 to the kernel command line.
It seems initramfs has some ideas of its own, and it was starting DHCP
on an interface even though this was disabled in
/etc/network/interfaces. I guess it did this because I had a NFS mount
in my VM, and it just copied ifupdown's config into the VM. Or at least,
that's what it looked like. If this is out of sync with the actual
/etc/network/interfaces, that might explain some things.
> Right now I am using the attached networking-hotplug.service /
> networking-hotplug-ifup.sh combo to work around it, practically
> extracted the --allow=hotplug part of the /etc/init.d/networking script.
It still shouldn't be necessary. What's in your
/etc/udev/rules.d/80-ifupdown.rules?
--
Met vriendelijke groet / with kind regards,
Guus Sliepen <[email protected]>
signature.asc
Description: PGP signature
