On Sun, 2007-11-25 at 13:47 +0100, Piotr Roszatycki wrote: > 2007/11/25, Ben Hutchings <[EMAIL PROTECTED]>: > > Now it looks like the Ralink drivers do not allow setting most wireless > > parameters while they are down (though rt2500 alone seems to be more > > flexible). Unfortunately, when using ifupdown and wireless-tools, this > > is exactly what is attempted - see bug #403983. Is this what you were > > trying to work around, Piotr? > > Yes, it is a workaround for this bug. Please, notice that udev rule is > required also for i.e. rutilt and other similar utilities. I was very > disappointed that rutilt didn't work after I plugged the wi-fi dongle.
I patched rutilt to work around this (018_up_and_down.diff). I believe this has been applied upstream. > > I think a better workaround would be include a pre-up script that does > > something like: > > > > if [ x"$(basename "$(readlink /sys/class/net/"$IFACE"/device/driver)")" = > > x"rt73" ]; then > > ifconfig "$IFACE" up > > fi > > I think the pre script for ifupdown should be created even if udev > rule is existing. This should replace the udev rule. I know it's simpler to do this as soon as the device is plugged in, but no other network interface is brought up automatically like this, and we know the rule is likely to break in future udev versions. Ben. -- Ben Hutchings Computers are not intelligent. They only think they are.
signature.asc
Description: This is a digitally signed message part
