OK...so I got bored the other day (been sick and havent been to work all week) and decided to see how secure my home network was. I grabbed a few of my Live CDs (Whoppix and BackTrack, which is just a newer release of Whoppix) and booted up the laptop. I have a WPC11 V3 card which uses a Prism chipset. Whoppix sees it as eth0, BT sees it as wlan0. Kismet.conf source for whoppix reads as follows. Source=wlanng,eth0,Prism Kismet will not put the card into monitor mode. If I switch to source=orinoco,eth0,kismet it works fine. I can capture packets all day with airodump as well. When I try to repeat packets with aireplay, the IV count doesnt change at all. If I run iwconfig, it shows the card in Managed model. If I run iwconfig eth0 mode Monitor I get an error. If i try iwpriv eth0 monitor 2 1 it does nothing either. When I insert the card and dmesg | tail, it shows the orinoco_cs driver loading. Why is this? I thought it was a Prism card? Sorry for the long post...i was just rambling. But I'm pretty fed up with it right now and my laptop is about to go through a window. ~Rich
Will these still work even though I cant manually put the card into rfmon?? I was only able to run airodump and aireplay when kismet was running. If I shut it down, airodump quit capturing packets and aireplay quit transmitting packets. Back again to the orinoco drivers being used for a Prism based card. Whats the deal with that? Thanks for the reply. ~Rich
that is an odd problem, airodump-ng and aireplay-ng work out of the box on backtrack for me (on more than 2 laptops and a PC) also just a note.. Backtrack isnt an update of whoppix. its a remake using slax combining tools from auditor and whax ... ANYWAYS... im stuck as to a solution for you at the min.. if i think of anything tho ill definatly post. very odd problem tho..
