To: linux-kernel@vger.kernel.org
From: mru@users.sourceforge.net (=?iso-8859-1?q?M=E5ns_Rullg=E5rd?=)
Subject: Re: [ANNOUNCE] netplug, a daemon that handles network cables
 getting plugged in and out
Date: Fri, 29 Aug 2003 10:25:48 +0200
Message-ID: <yw1x1xv498fn.fsf@users.sourceforge.net>
References: <1062105712.12285.78.camel@serpentine.internal.keyresearch.com> <20030829003426.GF12249@vitelus.com>
 <3F4EB641.3040107@davehollis.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
User-Agent: Gnus/5.1002 (Gnus v5.10.2) XEmacs/21.4 (Rational FORTRAN, linux)
Cancel-Lock: sha1:HQpJJwbyZwTEDja1pwJo9KKdz/o=
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1209
Lines: 21

David T Hollis <dhollis@davehollis.com> writes:

>>Thank you, thank you, thank you. I was just thinking today how
>>annoying it is that whenever I boot up my laptop, dhclient runs and tries
>>to get an IP address on the ethernet interface until it's ^C'd. Since
>>I often use the Ethernet interface this is not a bad default, but dhclient
>>can't even realize on its own that there's no cable plugged in.
> 
> Hmm, that seems to raise the question - why doesn't dhclient just
> handle that?  On a DHCP interface, it's running anyway.  if it paid
> attention to link status, it would know when to re-request an IP.  If
> you are statically assigned, you don't really care anyway.

Well, sometimes it's better to not have the interface configured UP
when there's no cable connected.  It avoids some very long timeouts
when some program tries to connect to something.  It's better to just
get a host unreachable error immediately.

-- 
M?ns Rullg?rd
mru@users.sf.net

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/