DWL-650 & Kismet [was Re: Orinoco Wireless Card and Monitor Mode w/ Kismet - No Longer Working?]

Fish fish at fish-mail.com
Tue May 25 09:17:25 PDT 2004


On Tuesday 25 May 2004 11:06 am, you wrote:
> What I've discovered is the following:
>
*snip*
> Now, my problem.  I have an up-to-date CURRENT system and all seems
> to work well, with one exception.  When started, kismet_server proceeds
> to eat all available CPU without producing the correct located networks.
>
> I ran kismet (from ports) directly on a 5.2.1 (from ISO) install and
> it did not display this behavior (I'm working on putting together
> another system to try to reproduce the problem).
>
> Might anyone have a clue as to where I should start looking to see
> what is going on?
>
> I'd really like to retire my Linux box that I use for wardriving, but...
>
> AlanC

You say you don't see this problem on a freshly-built machine?

Hm, now that IS interesting.  Something, somewhere, seems to have some sort of 
conflict with Kismet.  I'd like to help you track this down, as I'm having 
the exact same problem, and would like to be able to use my system for 
wardriving again as well.

I'll get to backing up my system in preparation to rebuild, and I'll go this 
way: Install from CDs, install Kismet. Test.  CVSUP, rebuild base system, 
rebuild kismet, test.  Start installing ports - X, KDE3, firefox, rebuilding 
kismet and testing after each.

It's heartening to know that I'm not the only person having this problem.  
Thank you, now I know there's a way to track down the problem.

Fish


More information about the freebsd-mobile mailing list