Date: Wed, 10 Jan 2001 15:51:34 +0000 From: Josef Karthauser <joe@tao.org.uk> To: Robert Watson <rwatson@FreeBSD.ORG> Cc: Samuel Tardieu <sam@inf.enst.fr>, hackers@FreeBSD.ORG, n_hibma@freebsd.org Subject: Re: Link up/down events Message-ID: <20010110155134.B524@tao.org.uk> In-Reply-To: <Pine.NEB.3.96L.1010110085515.78872B-100000@fledge.watson.org>; from rwatson@FreeBSD.ORG on Wed, Jan 10, 2001 at 08:57:14AM -0500 References: <2001-01-10-12-03-26%2Btrackit%2Bsam@inf.enst.fr> <Pine.NEB.3.96L.1010110085515.78872B-100000@fledge.watson.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Jan 10, 2001 at 08:57:14AM -0500, Robert Watson wrote: > 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). There's an ongoing discussion about building a generic devd (device daemon) to deal with this kind of thing. Nick Hibma proposed a spec for one, but as far as I'm aware there's been no feedback to him yet. Nick, maybe you should re-propose it via the -arch list. Joe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010110155134.B524>