Your message dated Sat, 9 Jan 2016 19:25:51 +0100
with message-id <[email protected]>
and subject line Re: Bug#521708: unplugged ethernet interfaces shouldn't be
brought up on boot
has caused the Debian Bug report #521708,
regarding unplugged ethernet interfaces shouldn't be brought up on boot
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
521708: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=521708
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: netbase
Version: 4.34
Severity: wishlist
Hi,
currently /etc/init.d/networking attempts to bring up ethernet interfaces even
when the cable is unplugged. This can be very annoying with DHCP,
because the user has to wait a long time for timeout. I think the
default behaviour should be that interfaces are brought up only
if the cable is plugged (or information is not available).
Regards
Anton Khirnov
-- System Information:
Debian Release: squeeze/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (300, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.29-zohar.b (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages netbase depends on:
ii lsb-base 3.2-22 Linux Standard Base 3.2 init scrip
Versions of packages netbase recommends:
ii ifupdown 0.7~alpha3 high level tools to configure netw
netbase suggests no packages.
-- debconf information excluded
--- End Message ---
--- Begin Message ---
Not all interfaces support monitoring whether a cable is plugged in,
some cards react very slow and may take a while after poweron before
they detect that a cable is plugged in, most cards won't detect a cable
until after they are brought up, and I'm sure there are buggy cards out
there that always report that they don't see a cable.
Some people might have services installed that might depend on the
interfaces having a DHCP address, and they don't want ifupdown to abort
at boot because it thinks no cable is plugged in.
The patch from Jordi is even worse because if you boot without a cable,
it will never start a DHCP daemon, so you'd need to manually call ifup
if you plugged in a cable later. It also depends on the ifplugd package,
when you use that it's just better to have ifplugd call ifup/ifdown
itself.
So I will not implement this functionality in ifupdown itself. With
current versions of ifupdown, you can just add a pre-up line like this:
pre-up ifplugstatus --quiet $IFACE || test $? -eq 2
--
Met vriendelijke groet / with kind regards,
Guus Sliepen <[email protected]>
signature.asc
Description: Digital signature
--- End Message ---
