Re: Devd event from GEOM?

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: 
<Pine.NEB.3.96L.1050125171149.3036J-100000_at_fledge.watson.org>:

"> 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