On Tue, Jan 25, 2005 at 09:50:22AM -0800, Brooks Davis wrote: > > 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. And than you want howl for Zeroconf/Rendezvous... If people agreed to have it in the base system, some scripting would tie everything together seamlessly to give the same level of functionality as Mac OS X or better. Bye, Andrea -- ...and that is how we know the Earth to be banana-shaped.Received on Tue Jan 25 2005 - 19:51:44 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:38:26 UTC