[ANNOUNCE] netplug, a daemon that handles network cables getting plugged in and out

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/

	<b

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/

Does it make use of the link status notification stuff in 2.6.x?  ;-)

	Jeff

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.

Aaron Lehmann wrote:

On Thu, Aug 28, 2003 at 02:21:52PM -0700, Bryan O'Sullivan wrote:
 

quoted

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.

On Thu, 2003-08-28 at 19:11, David T Hollis wrote:

Hmm, that seems to raise the question - why doesn't dhclient just handle 
that?

Because it has as little knowledge of how the OS works as possible. 
It's intended to run on all kinds of Unix platforms, not just Linux.

On a DHCP interface, it's running anyway.  if it paid attention 
to link status, it would know when to re-request an IP.

There are no cross-platform standards for this kind of thing, so they'd
need modules for Linux, FreeBSD, Solaris, AIX, etc., etc.  I'm sure
they'd be happy to accept patches.

	<b