Devd event from GEOM?

[Sam Leffler]

Brooks Davis wrote:
> On Tue, Jan 25, 2005 at 05:15:47PM +0000, Robert Watson wrote:
> 
>>On Tue, 25 Jan 2005, Warner Losh wrote:
>>
>>
>>>>It depends a bit on where we sit: we probably want a neteventd that knows
>>>>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. 
>>>
>>>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 :-).
> 
> 
> 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="..." variable to start wpa_supplicant
> independent of dhclient, but I'm not 100% sure yet.

I auto-start wpa_supplicant from the /etc/start_if.foo script.  The only 
trick is you need to force LD_LIBRARY_PATH to collect libdnet.so from 
where ports installs it.

	Sam