On Thu, Jul 20, 2017 at 12:33:49AM +0200, Sven-Haegar Koch wrote:

> > 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.
> 
> Which is a pain to add from custom package postinst scripts without any 
> allowed user-interaction - but I will try that.

Well, you could add a /etc/grub.d/ file maybe, but it's indeed a hassle.

> > It still shouldn't be necessary. What's in your
> > /etc/udev/rules.d/80-ifupdown.rules?
> 
> /etc/udev/rules.d/80-ifupdown.rules does not exist.
> 
> ch-00-sims:~# cat /lib/udev/rules.d/80-ifupdown.rules
[...]

Ah yes, that's the one I meant.

> But the biggest strange this is that now it works, even with disabling 
> all my workarounds!
> 
> Something changed between the initial stretch upgrade with broken 
> network, and now, I don't know what - could even be something timing 
> related.
> 
> Guus, thanks for your help!
> 
> I will close this bug for now as "Unreproduceable".

Well, keep an eye on it. If the problem comes back, let me know!

-- 
Met vriendelijke groet / with kind regards,
      Guus Sliepen <g...@debian.org>

Attachment: signature.asc
Description: PGP signature

Reply via email to