From owner-freebsd-current@FreeBSD.ORG Tue Jan 25 23:01:54 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1396C16A4CE for ; Tue, 25 Jan 2005 23:01:54 +0000 (GMT) Received: from pi.codefab.com (pi.codefab.com [199.103.21.227]) by mx1.FreeBSD.org (Postfix) with ESMTP id B225343D58 for ; Tue, 25 Jan 2005 23:01:53 +0000 (GMT) (envelope-from cswiger@mac.com) Received: from localhost (localhost [127.0.0.1]) by pi.codefab.com (Postfix) with ESMTP id 195765EF6; Tue, 25 Jan 2005 18:01:53 -0500 (EST) Received: from pi.codefab.com ([127.0.0.1]) by localhost (pi.codefab.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 54002-02; Tue, 25 Jan 2005 18:01:50 -0500 (EST) Received: from [192.168.1.3] (pool-68-160-236-186.ny325.east.verizon.net [68.160.236.186]) by pi.codefab.com (Postfix) with ESMTP id 5C4245E93; Tue, 25 Jan 2005 18:01:50 -0500 (EST) Message-ID: <41F6CFC7.3020305@mac.com> Date: Tue, 25 Jan 2005 18:01:27 -0500 From: Chuck Swiger Organization: The Courts of Chaos User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041217 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Sam Leffler References: <20050125.101021.41686898.imp@harmony.village.org> <20050125175022.GA8667@odin.ac.hmc.edu> <20050125205142.GA8930@webcom.it> <41F6BD98.3040402@errno.com> <41F6C684.2050403@mac.com> <41F6C8E0.6030103@errno.com> In-Reply-To: <41F6C8E0.6030103@errno.com> X-Enigmail-Version: 0.90.0.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-new at codefab.com cc: current@freebsd.org Subject: Re: Devd event from GEOM? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Jan 2005 23:01:54 -0000 Sam Leffler wrote: > Chuck Swiger wrote: [ ... ] >> I'm not surprised. Zeroconf/Rendezvous is intended for people who >> don't know about or manage networks. :-) > > 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. Zeroconf is highly interested in the results of such activities, as 'network up' and 'network down' events from interfaces as they change state are the most significant events that it needs to deal with. When you said "What's presently missing is: background scanning, proper roaming,...", presumably this meant that something which provides "proper roaming" is something that you care about. Rendezvous between a Mac and a bunch of Airports is supposed to provide proper roaming without special user intervention. Did it not work because Rendezvous expects open access to AP's? Did it not work because of bugs with Tiger? Did it not work because of other issues? I don't know: you haven't supplied enough data. ----- As to whether this is on topic for the thread, consider Message-id: : "> We don't neet yet another daemon around for that. 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. 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 :-)." "Setting up WPA and 802.1x" doesn't help Grandma print from her laptop to her printer via wireless connectivity. Zeroconf would. -- -Chuck