Date: Wed, 26 Jan 2005 10:01:53 +0100 From: Andrea Campi <andrea+freebsd_current@webcom.it> To: Sam Leffler <sam@errno.com> Cc: current@freebsd.org Subject: Re: Devd event from GEOM? Message-ID: <20050126090152.GC8930@webcom.it> In-Reply-To: <41F6C8E0.6030103@errno.com> References: <20050125.101021.41686898.imp@harmony.village.org> <Pine.NEB.3.96L.1050125171149.3036J-100000@fledge.watson.org> <20050125175022.GA8667@odin.ac.hmc.edu> <20050125205142.GA8930@webcom.it> <41F6BD98.3040402@errno.com> <41F6C684.2050403@mac.com> <41F6C8E0.6030103@errno.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Jan 25, 2005 at 02:32:00PM -0800, Sam Leffler wrote:
> I know what zeroconf is. The original discussion was not (I thought)
> about setting up "zero configuration" pieces of the network. The
> discussion was about finding AP's. neighbor nodes in an IBSS network,
> setting up WPA and 802.1x, etc. For this zeroconf doesn't get you very far.
You're wrong, that's not what the original thread was about. I was responding
to Robert:
> 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.
While he did mention wireless, the discussion you joined late was about
"every network interface".
Just to get records straight...
--
Give a man a fish and you feed him for a day;
teach him to use the Net and he won't bother you for weeks.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050126090152.GC8930>