Bug#676183: Same problem with resolvconf and a bridge

2012-06-22 Thread Andrew Shadura
Hello, On Fri, 22 Jun 2012 04:51:56 +0200 m...@linux.it (Marco d'Itri) wrote: > > 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 > No: the kernel emits events for network interfaces, udev merely

Bug#676183: Same problem with resolvconf and a bridge

2012-06-21 Thread Marco d'Itri
On Jun 21, Andrew Shadura wrote: > 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 No: the kernel emits events for network interfaces, udev merely runs scripts when configured to do so. > is explicit

Bug#676183: Same problem with resolvconf and a bridge

2012-06-21 Thread Andrew Shadura
Hello, On Thu, 21 Jun 2012 16:12:33 +0200 Andrew Shadura 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

Bug#676183: Same problem with resolvconf and a bridge

2012-06-21 Thread Andrew Shadura
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 reassign 676183 udev 172-1 thanks Hello, On Wed, 20 Jun 2012 20:34:57 +0200 Harald Dunkel wrote: > Both timing and boot history might be important here. Instead > of manually starting the resolvconf and networking init scripts > I would suggest t

Bug#676183: Same problem with resolvconf and a bridge

2012-06-20 Thread Harald Dunkel
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 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. For verification I have configured a private network with some fake IP addresses on

Bug#676183: Same problem with resolvconf and a bridge

2012-06-19 Thread Andrew Shadura
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hello, On Tue, 19 Jun 2012 20:33:49 +0200 Harald Dunkel wrote: > Maybe its related to configuring a bridge interface. Andrew, > have you tried a bridge, or was your test on eth0? I've just tried to reproduce it within some test environment... Sur

Bug#676183: Same problem with resolvconf and a bridge

2012-06-19 Thread Harald Dunkel
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Maybe its related to configuring a bridge interface. Andrew, have you tried a bridge, or was your test on eth0? Regards Harri -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAk/gxggACgkQUTlbRTxpHjeD1ACfWP6B2fEDmhqm/iawZw

Bug#676183: Same problem with resolvconf and a bridge

2012-06-18 Thread Jeroen Dekkers
I've got the same problem with resolvconf, after booting the nameserver configured /etc/network/interfaces doesn't end up in /etc/resolv.conf. In my case the dns information is also configured on a bridge and a manual ifdown br0;ifup br0 gives me a correct /etc/resolv.conf. -- To UNSUBSCRIBE, e