D-Link WUA-1340 (RaLink 2571) promiscuous mode is flakey?

Live forum: http://rt2x00.serialmonkey.com/viewtopic.php?t=5106

thermowax

02-12-2008 19:52:18

I have read. I have googled. I have read some more. I'm baffled.

Platform Dell Latitude 610, SuSe 11.0 (2.6.25.5-1.1) virgin install, D-Link WUA-1340 (RaLink 2571) WiFi usb adapter.

According to this site, the rt2x00 driver in the kernel is buggy. I tried the rt73legacy driver, only to discover that it doesn't support promiscuous mode at all. I then downloaded and installed the (current? v.2.1.8) rt2x00 suite from linuxwireless.org (just because they build the tarball for you- I didn't want to have to deal with the whole git mess).

Everything works great... except promiscuous mode. Rfmon is fine, Kismet works nicely, I can switch between managed and monitor mode without re-inserting the adapter, I can connect to and use open and WEP-encrypted APs, but promiscuous mode has worked exactly once. I guess I hit some weird sequence of events. Other points of note

- The laptop's internal WiFi is disabled.
- Yes, I'm associated when I try to go promisc.
- Oddly, if I use wireshark, a log message is generated claiming the adapter is in promisc mode- but ifconfig says it's not. I have to do it manually with "ifconfig wlan1 promisc". It still doesn't work, though.
- I've verified the new drivers are what's being loaded, or at least appear to be rt73usb with rt2x00* from the new location.
- No suspicious log messages (errors, warnings) are generated

So, I ask
1. Is the 2.1.8 version I got from linuxwireless current? It's a lot newer than the kernel version (1.0.14 or so).
2. Iwpriv shows no private ioctls. Is this correct??
3. Should I deal with the git mess and get the version hosted here before asking questions? (

Any other ideas? I've been working on this for a while and I'm stumped. I've learned a whole lot about linux module manipulation, though, so it hasn't been a total loss...

Thanks!
Jim

IvD

02-12-2008 19:59:41


1. Is the 2.1.8 version I got from linuxwireless current? It's a lot newer than the kernel version (1.0.14 or so).
[/quote2evq7o7f]

Latest rt2x00 version is 2.2.3 (released today)


2. Iwpriv shows no private ioctls. Is this correct??
[/quote2evq7o7f]

Yes. Private ioctls are ugly. The latest wireless handling in the kernel works without them.


3. Should I deal with the git mess and get the version hosted here before asking questions? (
[/quote2evq7o7f]

Not in your case. promisc mode should just work, regardless of which version.

Please download http//kernel.org/pub/linux/kernel/peop ... regdump.sh
and enable debugfs support in your kernel/driver. With the script you should be able
to create a complete register dump of your device. Please attach the output as attachment
to this topic.

thermowax

04-12-2008 05:49:07

Thanks for the response! Sorry about my delay- I now know much more about kernel compilation/grub/mkinitrd than I did before. That was a bit of a learning curve.

Attached is the output of your script and a screen dump. At the time, I was associated with my WEP-encrypted network and able to ping google but unable to sniff a continuous ping off a machine sitting next to me. I was also able to replicate the behavior that, despite log messages stating tcpdump and wireshark placed the adapter in promisc, ifconfig reported that it was not. Using ifconfig to go promisc changed the ifconfig output to say promisc was on, but still no traffic captured (other than broadcasts and to/from the local machine, of course).

I also experienced some strange problems with "privacy configuration mismatch" and "mixed rate disabled" but those stopped after I un/replugged the adapter.

Thanks again for the help!

Jim

Spy84464

04-12-2008 18:10:43

You forgot the attachments!

thermowax

04-12-2008 19:26:10

Argh- it uploaded them, what did it do with them? Let's try again...

Oh, I see, it doesn't like them without extensions. Strange.

Thanks-
Jim

thermowax

09-12-2008 17:35:23

I've continued to work with this and still getting nowhere- I've verified that the correct 802.11 stack is being loaded, not really sure what to look at next. I don't see any kernel parameters that look like they need to be on for promisc...

Any ideas, anyone? I'm at a loss. I guess I'll start looking at the most current version of the drivers, but that's about all I can think of at this point...

Thanks!
Jim

thermowax

15-12-2008 14:54:49

Followup

I groaned and gitted the entire mess to get the latest version of the drivers and tried to compile them alone- that didn't work, so I went ahead and tried to compile the whole kernel. (I was apprehensive about running a non-Suse-patched kernel, as I couldn't find anything in the documentation that described anything about that kernel- version, pactches, etc.) It wouldn't compile.

Next step I installed Fedora 10.0 (which has the 2.6.27.something kernel) and downloaded the appropriate driver set from linuxwireless.org which happily contained the current rt2x00 drivers. I compiled and installed them and... no luck. In fact, it was worse than under Suse. I couldn't connect to an ap running WEP at all. Every time I tried to assign the ap address it wiped the WEP key.

Thursday (12/18/08) Suse 11.1 will be released and I'll try with that (new kernel and current driver) but I don't have a lot of optimism at this point. I'm starting to wonder if there's something up with Dlink's implementation of the RaLink chipset.

Can anyone recommend a USB adapter that actually works 100%? I don't mind buying another one, I just want to stop screwing with it and move on- I have some other things I want to do that are waiting on this... or even a PCMCIA adapter? I want to run USB so I can put it in a high-gain antenna, but if I have to build a pigtail I will... Argh.

Thanks-
Jim