From owner-freebsd-hackers Wed Jan 10 5:57:55 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id 5CDF437B400 for ; Wed, 10 Jan 2001 05:57:35 -0800 (PST) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.11.1/8.11.1) with SMTP id f0ADvE778982; Wed, 10 Jan 2001 08:57:15 -0500 (EST) (envelope-from robert@fledge.watson.org) Date: Wed, 10 Jan 2001 08:57:14 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org To: Samuel Tardieu Cc: hackers@freebsd.org Subject: Re: Link up/down events In-Reply-To: <2001-01-10-12-03-26+trackit+sam@inf.enst.fr> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 10 Jan 2001, Samuel Tardieu wrote: > Is there a way to be warned about ethernet link up/down events? I have a > laptop with an internal fxp0 interface, and I'd like to launch/kill > dhclient whenever the link goes up/down. I've been wondering about this also -- Darwin has this, and it's pretty cool to watch dhclient run as soon as the ethernet cable is stuck in, and not have to dig around to find out how to pursuade the system to make the change. Windows 2000 also appears to do this for appropriate ethernet cards. The traditional means of notifying userland processes of interface/network events has been the routing socket -- presumably we want to notify on interface arrive / depart, as well as for condition changes, including a link up / down (differentiated from administrative up / down). Robert N M Watson FreeBSD Core Team, TrustedBSD Project robert@fledge.watson.org NAI Labs, Safeport Network Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message