> > Hi! > > Could you please test if you can see packets originating from your > network in Kismet or Wireshark? > Also, did you use the included airmon-ng script to enable monitor > mode, or did you just do "ifconfig wlan0 down; iwconfig wlan0 mode > monitor, ifconfig wlan0 up"? (The two are significantly different, as > airmon-ng uses iw/nl80211 to enable monitor mode on a separate > interface - it would be good if you tried it both ways.) > > Thanks, > Gábor (.NetRolller 3D) > > -- > Vista: [V]iruses, [I]ntruders, [S]pyware, [T]rojans and [A]dware. :-) > A short summary of my first quick test. I use airmon-ng script to enable monitor mode. iw tool is version 0.9.9-nogit. No beacons from wep networks are shown. I've downloaded a couple of so called "security distros", backtrack4 and nubuntu, shipped with rtl8187. Same behaviour about weps. I haven't had the time to investigate the "old way" of enabling monitor mode on those live cd. I've followed your advice about "ifconfig wlan0 down; iwconfig wlan0 mode monitor, ifconfig wlan0 up" on my ubuntu installation. My surprise to see beacons growing from the wep network. Kismet works fine, too. With wlan0 in monitor mode, I've used airmon-ng to create a mon0 monitor interface, just to see what could happen. And the result was mon0 worked fine, too. So I've disconnected the usb dongle and unloaded possible related modules by hand and by "make unload" from compat wireless setup scripts. Then I've reconnected the usb device and created the mon0 interface with airmon-ng, this time without enabling monitor mode on wlan0. mon0 still worked fine. I'll check again after a system reboot. I hope that makes any sense to you. Thanks for your reply -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
