On Wed, 31 Aug 2005 17:06:19 -0400, Peter Jones wrote: > Not necessarily started "by hotplug", but started by something like > ifplugd or NetworkManager. And that class of programs is already > responsible for things like choosing what AP to associate, so it's an > extra degree of control for them, but not really a hastle for end users, > who shouldn't have to run "ifconfig up" or anything else 99% of the > time.
I apologize if I misunderstood you. We're actually not talking about ifconfig. By "ifconfig up" there is in this thread almost always meant setting IFF_UP flag regardless of actually used program. So "that class of programs" is exactly what we're talking about. And it's not about an extra degree of control, it's about the right way to do this (i.e. no side effects, no unwanted associations, etc.). > You also don't want to "ifconfig down" when you're hopping from AP to AP > with the same ESSID -- you generally want to tell it to reassociate with > the other AP, but leave the connection up the entire time. Sure. And not even that, you want the ieee80211 layer to do this automatically (based on signal strength) if it is told so. -- Jiri Benc SUSE Labs - To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
