From mboxrd@z Thu Jan 1 00:00:00 1970 From: David T Hollis Subject: Re: [ANNOUNCE] netplug, a daemon that handles network cables getting plugged in and out Date: Thu, 28 Aug 2003 22:11:13 -0400 Sender: netdev-bounce@oss.sgi.com Message-ID: <3F4EB641.3040107@davehollis.com> References: <1062105712.12285.78.camel@serpentine.internal.keyresearch.com> <20030829003426.GF12249@vitelus.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: "Bryan O'Sullivan" , linux-kernel@vger.kernel.org, netdev@oss.sgi.com Return-path: To: Aaron Lehmann In-Reply-To: <20030829003426.GF12249@vitelus.com> Errors-to: netdev-bounce@oss.sgi.com List-Id: netdev.vger.kernel.org Aaron Lehmann wrote: >On Thu, Aug 28, 2003 at 02:21:52PM -0700, Bryan O'Sullivan wrote: > > >>Netplug is a daemon that responds to network cables being plugged in or >>out by bringing a network interface up or down. This is extremely >>useful for DHCP-managed systems that move around a lot, such as laptops >>and systems in cluster environments. >> >>For more details and download instructions, see the netplug homepage: >>http://www.red-bean.com/~bos/ >> >> > >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. >- >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/ > > 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.