On 27/03/2013 14:32, Robert Elz wrote:
| That's the thing - dhcpcd is dynamic by nature, works by default for| hotplugged interfaces such as your usb wireless. Yes, I knew that. But with "denyinterfaces *" I assume it is going to need to be told to start on the new interface - but that's what ifwatchd is good for (or should be).
Sadly yes, but that's because you're abusing the way dhcpcd was designed to work. dhcpcd has grown into a network manager like application which seems to conflict with your setup.
I didn't mean to say that it couldn't be done (I had no idea), but that I don't think it is the right place, almost everything could be dumped into dhcpcd.conf and made to work, but that doesn't mean it is (always) the bestsolution.I know I can have dhcpcd statically configure addresses (etc) but that just seems perverse to me - it is hardly the job of a dhcp client to avoid dhcp after all - it is easier, cleaner, and more in line with tradition (and so with what other people expect to see when they look at the config) to simply configure the addresses with ifconfig, rather than adding config to dhcpcdin order for it to do the job.But in any case, I'm not sure you quite understood what I meant, it isn't that I want to configure the wireless differently when I see one or another ssid on it, rather, I want to use the detected ssid on the wireless interface to change the configuration of other interfaces (when the ssid tells me I am at work, I change the way I configure the wired interface, when the ssid tells me I am at home, I do a different type of wired network config, and when the ssid is at some strange unknown place, I generally don't want thewired network configured (by default) at all.
Well I do have to admin that defining how the wired is configured based on the SSID quite odd. Can you explain why you do this? Maybe dhcpcd can make it easier, or it's just outside its scope.
Thanks Roy