On Mon, Sep 20, 2010 at 08:18:32PM +0200, Antoni Grzymala wrote: > Does that support configurations where I set static addresses > (including ipv6) and routes (also including ipv6) based on the SSID as > is allowed by the oldnet scheme of things? I (and probably lots other > ???power users???) rely on those features extensively and I thank whoever > came up with the idea of actually configuring that in a pretty simple > way (compared to other distros and OS'es where it is more complicated > or plain impossible sometimes).
Things like this are why I wanted to bring up this discussion. I personally haven't had a reason to set things up based on a ssid, so I've never tried to do that. wpa_supplicant doesn't assign addresses or routes to interfaces; it just handles the wireless portion of the setup. In my setup, dhcpcd handles assigning the route and address to the interface. For a setup involving static routes and addresses on wireless, you would still need to use a network script to configure the routes or addresses, just like you do for static addresses on a wired interface, you just wouldn't want it to run wpa_supplicant since wpa_supplicant would already be running. I guess these are the questions I'm asking in this thread: dhcpcd and wpa_supplicant, in particular, are able to manage any network interfaces they find on a system independently of what we are doing in the network scripts. The oldnet scheme runs one instance of these for each network interface instead of running one instance and allowing that instance to manage all of the interfaces. What is the reason we do that? Is it possible to rework things so that the oldnet scheme uses system wide instances of services instead of running multiple copies of them on multiple interfaces where possible? William
pgp4BqO2U4dBd.pgp
Description: PGP signature
