Hello, On Thu, 21 Jun 2012 16:12:33 +0200 Andrew Shadura <bugzi...@tut.by> wrote:
> > Both timing and boot history might be important here. Instead > > of manually starting the resolvconf and networking init scripts > > I would suggest to boot a _real_ system. > Yes, boot history is important indeed. I've traced it down. > The problem is that udev emits events for network interfaces as a part > of a boot sequence, and its scripts call ifup for those interfaces. lo > is explicitly blacklisted there, eth0 isn't present in your > configuration file, and br0 is ifup'ed before resolvconf had a chance > to set things up. I guess, udev should somehow detect this situation > and block these events. Oh, forgot the rest of the story. The interface gets up before resolvconf is ready, so this doesn't result in dns-* options applied. Afterwards, when networking init script finally runs (after resolvconf has prepared all the things!), ifup -a ignores br0 as it's already brought up. This bug hasn't occured before you upgraded because previously ifupdown's init script was clearing /etc/networking/run/ifstate. However, recently this file migrated under /run/networking, which is tmpfs, so it should be clean at boot by definition, so that code has been dropped somewhere around ifupdown 0.7~alpha4. -- WBR, Andrew
signature.asc
Description: PGP signature
