public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "David L. Parsley" <parsley@roanoke.edu>
To: Andi Kleen <ak@suse.de>
Cc: Stefan Rompf <srompf@isg.de>, linux-kernel@vger.kernel.org
Subject: Re: Interface operative status detection
Date: Tue, 12 Feb 2002 09:52:12 -0500	[thread overview]
Message-ID: <3C692C1C.7090107@roanoke.edu> (raw)
In-Reply-To: <3C498CC9.6FAED2AF@isg.de.suse.lists.linux.kernel> <p73g0525je4.fsf@oldwotan.suse.de>

Andi,

> In short - Linux doesn't have this feature because it's not needed.
> If your routing protocol relies on link state checking without other
> probing it's broken. Zebra isn't. 

Link state checking _would_ be nice, though, for stuff like laptops 
using dhcp.  Right now, if I start my laptop without being plugged into 
the network, I have to wait for DHCP to time out before it'll finish 
booting - about 1 minute.  (yech!)

Is there a good way for a dhcp daemon to find out whether the laptop is 
connected to the network or not?  It'd be really sweet if dhcpcd could:

- down the interface and remove routes whenever the network cable was 
unplugged
- wait for the interface to get link beat again, and send a new request

This would greatly enhance desktop usability.  I'd be happy to do the 
dhcpcd hacking if the right kernel interfaces were available.

regards,
	David

-- 
David L. Parsley
Network Administrator, Roanoke College
"If I have seen further it is by standing on ye shoulders of Giants."
--Isaac Newton


  parent reply	other threads:[~2002-02-12 14:52 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <3C498CC9.6FAED2AF@isg.de.suse.lists.linux.kernel>
2002-01-19 17:40 ` Interface operative status detection Andi Kleen
2002-01-20  0:51   ` Stefan Rompf
2002-02-12 14:52   ` David L. Parsley [this message]
2002-02-12 15:58     ` Chris Friesen
2002-02-12 16:08       ` Stefan Rompf
2002-01-19 15:12 Stefan Rompf
2002-01-19 15:29 ` Jeff Garzik
2002-01-19 18:34 ` Roberto Nibali
2002-02-08 10:16 ` Jeff Garzik

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=3C692C1C.7090107@roanoke.edu \
    --to=parsley@roanoke.edu \
    --cc=ak@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=srompf@isg.de \
    /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