rt2x00.serialmonkey.com

Hey all!
I've been googling and reading for the whole day and I'm so tired that I ask you not to ban me if I'm asking something absolutely lame )) Help me please, or give a direction to move)
So, here's the task. I've got D-Link DWL G510 (RaLink RT2561/RT61) and Ubuntu 8.04.1. The kernel is 2.6.24-21-generic. I need to make an ad-hoc network, or (it would be fantastic if possible) make it work in Master mode.
I haven't change anything so everything is running on the default. Here's my lsmod:
# lsmod | grep rt61
rt61pci 25472 0
rt2x00pci 11264 1 rt61pci
rt2x00lib 22528 2 rt61pci,rt2x00pci
mac80211 165652 3 rt61pci,rt2x00pci,rt2x00lib
eeprom_93cx6 3200 1 rt61pci

But when I'm trying Master mode, here's what I see:
# iwconfig wlan0 mode Master
Error for wireless request "Set Mode" (8B06) :
SET failed on device wlan0 ; Invalid argument.
And when I'm trying to make it work in Ad-Hoc mode, I see this:
# iwconfig wlan0 mode Ad-Hoc
# ifconfig wlan0 up
SIOCSIFFLAGS: Operation not supported

But in the Managed mode it works.

So what should I do? Should I compile the latest rt2x00 drivers? Do they support Ad-Hoc? Do they support Master mode on my card? And will they work on my distrib?

Master mode is only available in rt2x00.git or wireless-testing.git, and it must be combined using hostapd (latest version) search this forum for other peoples experience.

As for adhoc mode, that should just work, what is the output of 'dmesg'? and 'ifconfig -a' ? and 'iwconfig'?

Oh... So I guess having Master mode is quite difficult)

About ad-hoc.
# ifconfig -a
eth0 Link encap:Ethernet HWaddr 00:0c:6e:56:67:35
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
Interrupt:20

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:3111 errors:0 dropped:0 overruns:0 frame:0
TX packets:3111 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:177634 (173.4 KB) TX bytes:177634 (173.4 KB)

nas0 Link encap:Ethernet HWaddr 00:a0:c5:78:e5:95
inet6 addr: fe80::2a0:c5ff:fe78:e595/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:3631199 errors:0 dropped:0 overruns:0 frame:0
TX packets:3941274 errors:225 dropped:0 overruns:225 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2655851073 (2.4 GB) TX bytes:1781754863 (1.6 GB)

ppp0 Link encap:Point-to-Point Protocol
inet addr:91.78.247.132 P-t-P:91.78.244.1 Mask:255.255.255.255
UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1492 Metric:1
RX packets:1060907 errors:0 dropped:0 overruns:0 frame:0
TX packets:1555315 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:3
RX bytes:173610202 (165.5 MB) TX bytes:1373871958 (1.2 GB)

wlan0 Link encap:Ethernet HWaddr 00:1b:11:01:71:f5
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

wmaster0 Link encap:UNSPEC HWaddr 00-1B-11-01-71-F5-00-00-00-00-00-00-00-00-00-00
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

# iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

wmaster0 no wireless extensions.

wlan0 IEEE 802.11g ESSID:""
Mode:Managed Frequency:2.462 GHz Access Point: Not-Associated
Tx-Power=27 dBm
Retry min limit:7 RTS thr:off Fragment thr=2346 B
Encryption key:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

nas0 no wireless extensions.

ppp0 no wireless extensions.

And dmesg output is really large, but the last entries are:
phy0 -> rt2x00mac_add_interface: Error - rt2x00 does not support Adhoc or Master mode<3>phy0 -> rt61pci_mcu_request: Error - mcu request error. Request 0x50 failed for token 0xff.
As I can see, they appear after I try to do "ifconfig wlan0 up".

PS: didn't see this before... Seems like the rt2x00 I have actually doesn't support Adhoc or Master mode %) What should I do then?

Ehm, kernel 2.6.24 had master mode and adhoc mode disabled due to various bugs.
It was enabled in a later version, but I am not sure if that was in 2.6.25 or 2.6.26. So you need to at least upgrade your kernel to a more recent version.

Ad-hoc mode seems not to work with current wireless-testing (2.6.28-rc6-wl), too, only setting mode to managed works.



Is the ad-hoc mode buggy at the moment or might my configuration be wrong?

I think you are trying to switch to adhoc mode while the interface is up, that is not allowed.
You must bring the interface down before switching operating modes.

The interface should be down, i am doing "ifconfig wlan0 down" before that.

During the boot-process i get the same error with this configuration in /etc/network/interfaces



The same configuration works when switching to an older kernel image / driver (2.6.27-rc4).

Is there any debug information in the log?

No, there are no output messages with dmesg and syslog. 'Ralink debug output' and most mac80211 debugging options are set. I have a rt73usb device in use, i just noticed the device mentioned in the subject of the thread, but this shouldnt make a difference, or can it?

Is there a way to trigger some debug messages concerning this issue?

rt61 and rt73 should behave the same on this area.

Maybe somebody can reproduce the issue, i did nothing more than pulling the latest wireless-testing and tried to set the device to ad-hoc mode.

Maybe this can help.
I have an RT2500 802.11g Cardbus/mini-PCI in kubuntu 8.04.2 and the same problem "rt2x00 does not support Adhoc or Master mode". The funny is that when I had gutsy (7.10) it worked like a charm, it only needed the "wireless-mode" and "wireless-essid" directives in /etc/network/interfaces to work perfectly. Now, in hardy, is imposible to bring the interface up after switching it to ad-hoc, it looks like:
#iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

wmaster0 no wireless extensions.

wlan0 IEEE 802.11g ESSID:"uni.net"
Mode:Ad-Hoc Frequency:2.412 GHz Cell: Not-Associated
Tx-Power=27 dBm
Retry min limit:7 RTS thr:off Fragment thr=2346 B
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
and a "SIOCSIFFLAGS" error on ifconfig up

I follow the same process than the roginal post and get:
#lsmod | grep rt2
rt2500pci 22656 0
rt2x00pci 12800 1 rt2500pci
rt2x00lib 25344 2 rt2500pci,rt2x00pci
rfkill 10144 1 rt2x00lib
input_polldev 6928 1 rt2x00lib
crc_itu_t 3584 1 rt2x00lib
mac80211 192532 3 rt2500pci,rt2x00pci,rt2x00lib
eeprom_93cx6 3840 1 rt2500pci

can you try running "iwlist wlan0 scan" after you brought up the interface?
some user reported beaconing didn't kick in until a scan command was issued (this is being further investigated).