New version of D-Link DWL-AG660 H/W Ver B3 (AR5006X) do not see net packets in monitor mode after some time of work

DWL-AG6600 B3 stopped receiving packets near 12:54:21/12:54:22

The second card (the same model/revision/etc.) have the same problem - after some time it stops receiving packets.

I have the smae problem with a D-Link DWL-g520. There is some solution?

As of my DWL-G520 card I have not noticed this problem, but I use it mostly in AP mode. My DWL-G520 sticker says H/w ver.: B3 F/W Ver.:4.30

#  lspci -nn -v -s 00:0a.0
00:0a.0 Ethernet controller [0200]: Atheros Communications, Inc. AR5212 802.11abg NIC [168c:0013] (rev 01)
        Subsystem: D-Link System Inc D-Link AirPlus DWL-G520 Wireless PCI Adapter(rev.B) [1186:3a13]
        Flags: bus master, medium devsel, latency 168, IRQ 5
        Memory at e7000000 (32-bit, non-prefetchable) [size=64K]
        Capabilities: [44] Power Management version 2

What is your revision of the card? What is the chip of your DWL-G520 (AR5212 or AR5006X). Is the problem exists when sniffing on a single channel?

BTW. in the mean time I've tested r1784 snapshot and still got the problem (with DWL-AG660).

At first, I have to execute the next commands to set my D-Link card in Monitor mode:

# wlanconfig ath26 destroy # wlanconfig ath26 create nounit wlandev wifi0 wlanmode monitor

Also, when I do it, the unit number is incremented by one (yes, with nounit option).

I don't know how to get all the information that you said about my card, but I can execute lspci :)

[root@PC]# lspci -nn -v -s 01:02.0
01:02.0 0200: 168c:0013 (rev 01)
        Subsystem: 1186:3a13
        Flags: bus master, medium devsel, latency 168, IRQ 217
        Memory at cadd0000 (32-bit, non-prefetchable) [size=64K]
        Capabilities: [44] Power Management version 2

The chip of my DWL-G520 card is an AR5212. when I'm sniffing all channels, after 5 or 10 minuts aprox. , my card stop to recieving packets, but the application works. But, when I'm sniffing in a single channel, after 1 minute aprox., the application brokes and I have to kill the process, because the CPU Fan becomes to work a lot.

thanks for all, and please, If you have some solution or you can help me in any way.. I thank you it.

One more time... THANK YOU VERY MUCH!

Version/revision of the card hardware and firmware should be printed on a sticker glued to the box (and probably also on the card) From the lspci data I assume that we have the same DWL-G520 model.

I use DWL-G520 card as an Access Point for the most of the time and have got option 'options ath_pci autocreate=ap' in my /etc/modprobe.conf file (ie. my autocreated ath0 is in ap mode). To enter the monitor mode I simply create ath1 device with:

wlanconfig ath1 create wlandev wifi0 wlanmode monitor 

and then launch airodump with

airodump-ng -w file ath1

My ap on ath0 stops working (the card has only one radio unit), but I can monitor without problems (on DWL-G520), and resume ap connections after monitoring.

Questions: what version of madwifi-ng do you use (dmesg | grep -e ath_hal -e ath_pci -e ath_rate or grep -e ath_hal -e ath_pci -e ath_rate /var/log/kernel), what kernel/arch (uname -a), is ath26 the only ath interface you have got configured (check iwconfig - there are some issues when the first interface is in station mode)? Have you tried other PCI slot or another card (to exclude hardware problem)? lspci tells that your card uses IRQ 217 - you could check cat /proc/interrupts if any other hardware uses the same interrupt. From the number of irq I assume that you have got an APIC enabled kernel/hardware - you could try to disable the feature with noapic kernel parameter (in grub/lilo/... - btw. probably not a good idea, but sometimes could help).

Same thing is happening to me with a WG511T

The problem is still present for madwifi-hal-0.9.30.10-r2249-20070329. The issue shows up even faster - after ~ 3-6 minutes the card stops reveiving any signals when in monitoring mode (and changing chanells).

please! help me for D-Link DWL-AG660 H/W Ver B3 notify me some solution, thanks.

Numbering of units - you have to blame/adjust udev. I don't use it so can't help with that much, take a look at another tickets.

Problem with card not receiving pakets - here famous stuck beacon problem did that recently. Link - AP <-> sta - worked for some minutes, then stopped to work and even hasn't been able to scan, i have tried to destroy and create vap again, to no avail, only reboot helped. So, if you can, check athstats -i wifi0 if there are missed beacon interrupts. Also, check dmesg if there are stuck beacon messages. You could also play - as Marek wrote - with some settings, take a look in interrupts distribution in /proc/interrupts, even you could try to play with kernel - especially apic - parameters.

It looks like problem is gone with the 20080124 snapshot of madwifi-ng:

ath_hal: 0.9.30.13
wlan: svn r3235
ath_pci: svn r3235

Tested with a custom 2.6.24.2 kernel. Now I'm monitoring for 17 hours and 45 minutes and my card (D-Link AirPremier? AG DWL-AG660, H/W Ver.:B3 F/W Ver.:2.20) still gets new frames.

Thanks for the feedback. I'll close this as fixed in trunk. Feel free to reopen the ticket in case the issue reoccurs.