Madwifi-NG notes
dr
It seems that if there is an AP or STA vap created AND SET TO 'UP' WITH IFCONFIG, madwifi-ng does funny things (like report no packets) with a monitor vap.

Right now the only solution is to manually take down the other VAPs with ifconfig, destroy them, and recreate the monitor vap (or if you're using kismet-newcore, destroy the other vaps and then start kismet).

This is sub-optimal and I'll try to narrow down the behavior and talk to people, but for now, heads up.