I know there are a few other posts out there like this, however, I've followed them all and I still have no results. I was hoping someone might be able to shed some light on this headache!
For starters, I'm running FC5 (Kernel version 2.6.15-1.2054_FC5). I recently purchased a like new Cisco Aironet 350 wireless card and installed it into my box. Once plugged in, Linux seemed to pick it right up, however, everyone around me has WEP encryptions and the
complex I'm living in is still squeeking by on dial up. To resolve this issue, I downloaded Airsnort and its components and everything seemed to install just fine. However, now that I'm running Airsnort, the problems seem to be popping up.
First, I open up Airsnort, select my network device (eth0) and click "Start". At this point, a dialog box opens, telling me that my card needs to be put into "monitor mode".
After a little bit of research (on Airsnort's FAQ), I learned that apparently Airsnort does not automatically put Cisco cards into "monitor" mode and that this can be done simply by typing the following into the terminal:
echo 'Mode: y' > /proc/driver/aironet/eth0/Config
This, however, did not seem to do anything.
After more research, I fell upon another way to put the card into monitor mode. It involved typing the following into the terminal:
iwconfig eth0 mode monitor
However, after trying "iwconfig eth0" again, it still shows that the card is in "managed" mode...not monitor mode.
At this point I've run out of ideas and my research keeps leading me in circles with the same or variations of the same commands. Is there anyone who has an idea what could be the problem?