From: David T Hollis <dhollis@davehollis.com>
To: Aaron Lehmann <aaronl@vitelus.com>
Cc: "Bryan O'Sullivan" <bos@keyresearch.com>,
linux-kernel@vger.kernel.org, netdev@oss.sgi.com
Subject: Re: [ANNOUNCE] netplug, a daemon that handles network cables getting plugged in and out
Date: Thu, 28 Aug 2003 22:11:13 -0400 [thread overview]
Message-ID: <3F4EB641.3040107@davehollis.com> (raw)
In-Reply-To: <20030829003426.GF12249@vitelus.com>
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.
next prev parent reply other threads:[~2003-08-29 2:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-28 21:21 [ANNOUNCE] netplug, a daemon that handles network cables getting plugged in and out Bryan O'Sullivan
2003-08-28 21:35 ` Jeff Garzik
2003-08-28 21:46 ` Christoph Hellwig
2003-08-28 21:50 ` Bryan O'Sullivan
2003-08-28 21:54 ` J.A. Magallon
2003-08-28 22:34 ` Jeff Garzik
2003-08-28 22:45 ` J.A. Magallon
2003-08-28 22:49 ` Bryan O'Sullivan
2003-09-03 8:42 ` Stefan Rompf
2003-08-29 0:34 ` Aaron Lehmann
2003-08-29 2:11 ` David T Hollis [this message]
2003-08-29 17:43 ` Bryan O'Sullivan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3F4EB641.3040107@davehollis.com \
--to=dhollis@davehollis.com \
--cc=aaronl@vitelus.com \
--cc=bos@keyresearch.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).