severity 675372 normal thanks On Thu, May 31, 2012 at 06:35:29PM +0200, Vincent wrote: > Package: isc-dhcp-client > Version: 4.2.2.dfsg.1-5 > Severity: important > > Hello, > > Recently (corresponding to the installation of 4.2.2.dfsg.1-5), my > boot time went fromn 15 s to more than 1 minute because dhcp is trying > hard to get an IP address from an interface with nothing plugged > into. This looks a bit like #615532, but it happened only very > recently. > > In addition, the method mentioned in #615532 doesn't work: I > installed ifplugd but nothing changes. > > This is the contents of my interfaces file, which hasn't changed > since the installation: > > ~ cat /etc/network/interfaces > # This file describes the network interfaces available on your system > # and how to activate them. For more information, see interfaces(5). > > # The loopback network interface > auto lo > iface lo inet loopback > > # The primary network interface > allow-hotplug eth0 > iface eth0 inet dhcp > > Any idea/workaround ? This is pretty painful ! > > Cheers, > > Vincent > > > -- System Information: > Debian Release: wheezy/sid > APT prefers testing > APT policy: (500, 'testing'), (500, 'stable'), (1, 'experimental') > Architecture: amd64 (x86_64) > > Kernel: Linux 3.2.0-2-amd64 (SMP w/2 CPU cores) > Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8) > Shell: /bin/sh linked to /bin/dash > > Versions of packages isc-dhcp-client depends on: > ii debianutils 4.3 > ii iproute 20120319-1 > ii isc-dhcp-common 4.2.2.dfsg.1-5 > ii libc6 2.13-32 > > isc-dhcp-client recommends no packages. > > Versions of packages isc-dhcp-client suggests: > pn avahi-autoipd <none> > pn resolvconf <none> > > -- no debconf information > >
On Tue, Jun 05, 2012 at 08:02:30AM -0700, rimo...@gmail.com wrote: > i can confirm the problem on a similar configuration > a.l.e > > I've found the culprit: it's 0.7~rc1+experimental of ifupdown. Sounds like you folks must have the ifupdown from experimental installed. Also Cc'ing the ifupdown maintainer (whoa, it's not aj any more?) I'll have to review #420784 and try to understand what problem is trying to be solved with adding the -1 flag to dhclient, but that's the cause. In the meantime, you can work around this by adding timeout 10; to your dhclient.conf. Adjust 10 up or down to taste.
signature.asc
Description: Digital signature
