[maemo-developers] Kismet on N800 stops running after 1-2 minutes

From: Ryan Pavlik abiryan at ryand.net
Date: Fri Dec 14 16:26:49 EET 2007
That is a wireless driver error (probably has nothing to do with 
auto-search), and because the driver is closed source, Dragorn can't fix it.

I've found putting the device into offline mode (so that the UI stops 
trying to manage it by connecting, disconnecting, searching for stuff, 
sending beacons, etc), then trying a few times will usually get it 
working.  If I see it stops working, I quit and start it again.  Oddly 
enough if I try enough times it will work, while on my 770 it seems to 
work every time.

Hope this helps!

Ryan

Alex Iliadis wrote:
> I believe it has to do with the wireless driver not working properly in 
> monitoring mode. There are workarounds for it but they require some sort 
> of scripting. Also the wireless driver corrupts packets in monitor mode so 
> you may get inaccurate results sometimes.
>
> Thanks,
> Alex
>
> On Thursday 13 December 2007 08:24:12 pm Jaeyeon Jung wrote:
>   
>> Found that others also encountered a similar problem and as someone
>> suggested, I increased the automatic connection search interval (to 60
>> minutes) and crossed my fingers. Unfortunately, that doesn't fix the
>> problem.
>>
>> Any other suggestions? Basically, Kismet runs fine for a couple of
>> minutes and the packet counter stops increasing (the application is
>> still running and the elapsed time is updated but basically sniffing
>> stops working).
>>
>> jYj

-- 
Ryan Pavlik
AbiWord Win32 Platform Maintainer, Art Lead: www.abisource.com
AbiWord Community Outreach Project: www.cleardefinition.com/oss/abi/blog/

"Optimism is the father that leads to achievement."
 -- Helen Keller

"The folder structure in a modern Linux distribution such as Ubuntu
was largely inspired by the original UNIX foundations that were
created by men with large beards and sensible jumpers."
 -- Jono Bacon, The Ubuntu Guide


More information about the maemo-developers mailing list