I have no idea what that last command is supposed to do. It looks rather Suse specific, maybe you should ask on Suse forums?
No, it's not Suse specific. "ip" replaced "ipconfig" in Linux kernel 2.2 and "ipconfig" is only a partial interface to the ip functionality since then. In ifconfigs notation the last command line would be "ifconfig wlan0 up".
Same with "BUG nil ifname", vanilla "iwconfig" never produces that kind of output.
That output came from an "ip monitor all" running concurrently in another window. I don't really know, what it does, but it's a kind of kernel message dumping for changes in the network. Google gave some hints in 2004 or 2005 there have been problems with misinterpreted kernel messages related to wireless interfaces, which produced such outputs. I've also seen patches for that but I don't know the current state.
Well, I don't know. Usually, legacy drivers have to be configured after the interface has been brought up.[/quote1rmmg4r0]
So here are some experiences/recipes for using the rt61 under suse 10.3 (Working with an openvpn tunnel through an unencrypted ad-hoc connection)
The kernel sources should be installed.
Whenever you have a new kernel ([b1rmmg4r0]after[/b1rmmg4r0] rebooting, before compiling any kernel-modules ) do
The file /etc/modprobe.d/unsupported.blacklist should end with the line
The "##" are sometimes missing after an update -- AFAIK this is not correct -- add them. (Otherwise the loading of the rt61 kernel module will not be done automatically.)
Suse 10.3 contains an rt2x00 package -- it did not work for me. If it is installed and you dont want to try it -- remove it.
The SUSE scripts in 10.3 emit all of the iwconfig-commands before the interface is brought up. But at least the ESSID vanishes when the interface is brought up. So I've added a line
to the file /etc/sysconfig/network/ifcfg-wlan0
and created an executable file
containing the lines
iwconfig wlan0 essid WHATEVERITIS