Date: Tue, 25 Jan 2005 09:50:22 -0800 From: Brooks Davis <brooks@one-eyed-alien.net> To: Robert Watson <rwatson@freebsd.org> Cc: imp@bsdimp.com Subject: Re: Devd event from GEOM? Message-ID: <20050125175022.GA8667@odin.ac.hmc.edu> In-Reply-To: <Pine.NEB.3.96L.1050125171149.3036J-100000@fledge.watson.org> References: <20050125.101021.41686898.imp@harmony.village.org> <Pine.NEB.3.96L.1050125171149.3036J-100000@fledge.watson.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--IS0zKkzwUGydFO0o Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Jan 25, 2005 at 05:15:47PM +0000, Robert Watson wrote: >=20 > On Tue, 25 Jan 2005, Warner Losh wrote: >=20 > > > It depends a bit on where we sit: we probably want a neteventd that k= nows > > > about this sort of thing and performs unified network interface > > > management. In the mean time, I just want dhclient launched, because > > > dhclient already knows about ssid's, link state, etc.=20 > >=20 > > We don't neet yet another daemon around for that. >=20 > Ah, but we do, because whatever daemon it is needs to provide unified > management of routing in the presence of multiple DHCP and link locally > configured network interfaces. I.e., when I'm switching between wireless > and wired networks, Useful Things Should Happen, and this can't currently > be properly managed by today's dhclient. Likewise, I want to always have > link local addresses configured for every network interface, and not have > things like dhclient step on them. This requires dhclient to become > substantially more mature and/or grow a lot, or it requires a new daemon.= =20 > Having many daemons is just asking for them all to step on each other's > toes, adding and removing addresses and routes in ways that leaves me with > nothing useful to network with, requiring user intervention. If you've > ever used a FreeBSD box in this scenario, followed by a Mac OS X box, > you'll know what I mean. Neither is perfect, but the one with centralized > configuration management does a much better job :-). FWIW, Sam's got a port of openbsd's dhclient in perforce. It's apparently significantly less foobar then ours. Unfortunatly, dhclient isn't enough because we also need wpa_supplication for modern wireless networks (it also provides basic 802.1x support for wired interfaces in linux and we'll probably want that too.) I think we'll be able to simply add a wpa_supplicant_ifs=3D"..." variable to start wpa_supplicant independent of dhclient, but I'm not 100% sure yet. -- Brooks --=20 Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --IS0zKkzwUGydFO0o Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFB9obdXY6L6fI4GtQRAiRHAKDMj/tEepdbOmc/ORYPK1T865xjDgCfTBrC vnBl6H6NaakEnGXV48xWS1w= =QPGc -----END PGP SIGNATURE----- --IS0zKkzwUGydFO0o--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050125175022.GA8667>