sullen_penguin

OK bit of an update - Talk about jumping through hoops but I found that if you connect to your wireless network, open kismet from the menu, then open kismet from the command line it works - not much use that way out in the field but it leads me to believe kismet is picking the wrong network card or driver on startup by default the normal way - perhaps? Also with Backtrack3 on the Aspire One I've found the WiFi can sometimes be intermittent, at one stage I had to power down (not restart) to get the WiFi back (an old problem I had in XP but that was fixed by a BIOS upgrade)...

Hi all, I am having the same problem here running Backtrack3 on an Acer Aspire One from USB live. My wireless is up and running as I can see and connect to networks in Wireless Assistant. I did manage to get Kismet working once lastnight after many attempts but haven't been able to since. I've tried running Kismet from the command line with the switches as Darren suggested above but still nothing, I have checked in iwconfig and its says wifi0 has no wireless extensions, the entries for ath0 (and ath1 and so on after multiple attempts of opening Kismet) all have info listed. There are also entries for Kis0 (and kis1 etc). Any suggestions would be much appreciated... :) Also - just to add after a few attempts of trying different things I get an error message which is quiet long - The last few lines: FATAL: Unable to create VAP: No such device FATAL: Unable to create monitor-mode VAP WARNING: wifi0 appears to not accept the Madwifi-NG controls. Will attempt to configure it as a standard Madwifi-old interface. If you are using madwifi-ng, be sure to set the source interface to the wifiX control interface, NOT athX FATAL: GetIFFlags: interface wifi0: No such device