Package: rt2500-source Version: 1.1.0+cvs20050530-2 The package generated by rt2500-source depends unnecessarily on rt2500-base. When RT2500STA.dat (from rt2500-base) is present, the kernel module gets confused when wireless settings are also in /etc/network/interfaces.
I used to have a working verstion of the rt2500 module installed (based on the cvs version and installed without a proper debian package), using the standard debian way of setting up the wireless parameters in the interfaces file: auto ra0 iface ra0 inet dhcp wireless_mode Ad-Hoc wireless_essid <myessid> wireless_channel <mychannel> wireless_key restricted <mykey> After installing the packaged version, with the 3 rt2500-related packages (and only changing the module options to use ifname=ra%d), it wouldn't work. At bootup, dhclient wouldn't find anything. I realised that "ifup ra0" didn't actually set up the wireless parameters, in particular, iwconfig ra0 wouldn't show any encryption key. The /etc/Wireless/RT2500STA/RT2500STA.dat file was untouched from the standard installation (and therefore didn't contain my keys). Setting the key manually with iwconfig, whilst dhclient was running, would solve the problem, but only temporarily. After a while, the module would try to load RT2500STA.dat again, and all the iwconfig settings would go away. Deleting RT2500STA.dat seems to solve the problem once and for all. I prefer the debian way (in network/interfaces) of configuring the wireless parameters, it's more consistent with modules for other cards as well. Since RT2500STA.dat is not really necessary, maybe the packaging should be done slighlty differently (I guess it's really required for people who want to use RaConfig2500, in package rt2500). The problem is that the dependency makes it compulsory to install rt2500 and rt2500-base with the module package generated by rt2500-source, whereas in fact, in works well without them. ___________________________________________________________ To help you stay safe and secure online, we've developed the all new Yahoo! Security Centre. http://uk.security.yahoo.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]