airodump-ng doesn't work with ipw3945

[misterx]

airodump-ng doesn't work with ipw3945

[JMF]

I don't know what issue made this ticket to be opened, but I know that Intel pro wireless 3945 cards work well with airodump-ng.

When ipw3945 driver is used with monitor mode enabled, airodump-ng works using rtap interface. About ipwraw driver, sometime ago configuring channels was quite different from most other drivers, but now that I added wireless extensions that's not a problem anymore. With this driver, both rtapX and wifiX interfaces can be used, and wifiX even supports channel hopping... (the modified driver is being discussed in the aircrack-ng forum, in the drivers section). The last driver available for these cards, iwlwifi, I have never tested. Most surely it will be the best choice in the future because it's the one being actively developed, but for now I don't know if it works with airodum-ng or any of the tools in aircrack-ng suite.

-- I think this ticket can be closed --

[misterx]

I had some issue with ipw3945 driver and airodump-ng.
If you confirm that latest version in trunk work (0.9.1), I'll cose the ticket (I don't have such device here, I tried once on a friend's laptop).

[anonymous]

I use aircrack-ng 0.9.1 and airodump don't work fully : Using the program on one channel isn't faster than on all channels. And when I ask to dump channel 1, it dump other channels (ch 10 for example).

[JMF]

I did some testing with Intel Pro Wireless 3945 card (I don't know if this ticket refers to the card or a driver that can be used with it, both are usually called "ipw3945"). I used aircrack-ng versions 0.9.1 and 1.0-dev, both of them with the changes made until changeset [710]

These are the results:

DRIVER: iwlwifi 0.1.16 + mac80211 10.0.0 (both from intellinuxwireless.org)
INTERFACE: wlan0
Both versions work well for capturing packets and both report PWR value 0.
With 0.9.1 injection doesn't seem to work; when trying to inject using 1.0-dev
 the computer hanged.

DRIVER: ipwraw-ng 2.0.0
INTERFACE: wifi0
0.9.1 reports PWR -1 and 1.0-dev reports PWR 0, but besides that both versions
 work well for capturing packets.
Both also allow injection, but aireplay-ng --test only worked with 0.9.1.

INTERFACE: rtap0
Aireplay-ng injection doesn't work with this interface, neither does 
channel hopping on airodump-ng. Nevertheless it captures packets
 on the channel set for wifi0 interface.
Reported PWR 0 with version 0.9.1 and a variable value around 170 with 1.0-dev

DRIVER: ipw3945 1.2.2 (MONITOR, RADIOTAP and PROMISCUOUS enabled in Makefile)
*Injection isn't supposed to work with this driver so I didn't even bother to 
 test it.
INTERFACE: eth1
0.9.1 reports PWR 0 and 1.0-dev reports a variable number around 170; both
 versions work well for capturing packets.

INTERFACE: rtap0
Channel hopping doesn't work with this interface on airodump-ng. Version 0.9.1
reports PWR 0 but captures packets.
Version 1.0-dev shows a variable value around 170 for PWR and HAS A PROBLEM.
It seems to capture packets but does it very slowly.
After doing "airodump-ng rtap0" and stopping it, airodump-ng will always
 work slow, independent of which interface is specified (rtap0 or eth1) and of
 which version is used (0.9.1 or 1.0-dev).

I know this msg is BIG, but I hope it's clear... The owner of an ipw3945 card has 3 options regarding drivers and all of them work for packet capturing. Anything can be chosen, just the config airodump-ng 1.0-dev + rtap interface from ipw3945 driver must be avoided. I don't know it it's worth the time fixing this in airodump-ng 1.0-dev, because the driver will be made obsolete by iwlwifi. Unfortunately for now there seems to be only one option for injection, but I guess iwlwifi will soon allow it too.

---

With these results and suggestions, maybe this ticket can be closed. WORKSFORME :)