kismet icon indicating copy to clipboard operation
kismet copied to clipboard

Kismet out of memory raspberry pi 3

Open arifainchtein opened this issue 6 years ago • 8 comments

Hello, I installed kismet on the pi 3 using the file:

wget http://kismetwireless.net/code/kismet-2016-07-R1.tar.xz

and i got it to work ok. I am using a usb dongle with the 5370 chipset. The problem was that i need to export the data into json and it seems that the version i installed does not support that. I decided to install a release version following the instructions in : https://www.kismetwireless.net/docs/readme/packages/

The problem now is that when i start kismet it quits immediately, and the only error i been able to see is a messgae relating to out of memory:

Kismet error

arifainchtein avatar Jun 18 '19 22:06 arifainchtein

That version is pretty ancient and unsupported. I'd suggest the latest stable release, 2019.05.02.

It doesn't surprise me the old code doesn't work; the drivers have evolved over time.

The pi3 isn't an optimal platform but you'll have some success.

On Tue, Jun 18, 2019, 6:43 PM arifainchtein [email protected] wrote:

Hello, I installed kismet on the pi 3 using the file:

wget http://kismetwireless.net/code/kismet-2016-07-R1.tar.xz

and i got it to work ok. I am using a usb dongle with the 5370 chipset. The problem was that i need to export the data into json and it seems that the version i installed does not support that. I decided to install a release version following the instructions in : https://www.kismetwireless.net/docs/readme/packages/

The problem now is that when i start kismet it quits immediately, and the only error i been able to see is:

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/kismetwireless/kismet/issues/150?email_source=notifications&email_token=AFKJYY6H4SVSGTLD5WJTJH3P3FQIHA5CNFSM4HZENSS2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4G2IL63Q, or mute the thread https://github.com/notifications/unsubscribe-auth/AFKJYY6MHCLLMRESVM4E43DP3FQIHANCNFSM4HZENSSQ .

kismetwireless avatar Jun 18 '19 22:06 kismetwireless

i accidentally clicked the submit message before fuinishing the post.

i am trying to get the latest release to work, but It just dies with that out of memory message Is there something i can do? Would loe to be able to run it in the pi, because i am creating an embedded system.

thanks

arifainchtein avatar Jun 18 '19 22:06 arifainchtein

Stable should handle 15000 to 30000 devices on a pi3.

Compiling it is another matter; you'll either need a lot of swap and a lot of time, or use one of the packages that's precompiled.

You'll also need to not be running a desktop environment, etc on the pi if you expect usable performance.

On Tue, Jun 18, 2019, 6:48 PM arifainchtein [email protected] wrote:

i accidentally clicked the submit message before fuinishing the post.

i am trying to get the latest release to work, but It just dies with that out of memory message Is there something i can do? Would loe to be able to run it in the pi, because i am creating an embedded system.

thanks

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/kismetwireless/kismet/issues/150?email_source=notifications&email_token=AFKJYY7ZWLZYJWFMTJ4ZSXTP3FQ3RA5CNFSM4HZENSS2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYAFYBY#issuecomment-503340039, or mute the thread https://github.com/notifications/unsubscribe-auth/AFKJYYZMCKOWEYREVSCW6KDP3FQ3RANCNFSM4HZENSSQ .

kismetwireless avatar Jun 18 '19 22:06 kismetwireless

i just installed it, so no compiling. Any ideas why I cant get it to start? Any changes to kismet_memory.conf i should make?

thanks

arifainchtein avatar Jun 18 '19 23:06 arifainchtein

oh, yes, i forgot to mention that the pi is running headless.

arifainchtein avatar Jun 18 '19 23:06 arifainchtein

Are you attempting to run it from /etc/kismet ? Your screenshot makes it seem so - the pi user can't write to that directory.

digitallyelite avatar Jul 02 '19 21:07 digitallyelite

I have similar problem when running Kismet for several days. Memory usage grows and eventually, the swap file fills and systems gets terribly slow. If you run with --no-logging, this will help allow kismet to run much longer. Also, I haven't tested this yet, but configuring logging.conf to create new log files may help with memory as well

MyProjectExpert avatar Jan 14 '20 15:01 MyProjectExpert

The more kismet sees, the more ram it needs - so this is expected.

You can tune kismets memory use:

https://www.kismetwireless.net/docs/readme/performance_and_memory/

and should definitely do so if you're attempting to run it on very small hw like a pi3.

On Tue, Jan 14, 2020 at 10:18 AM Michael Wharton [email protected] wrote:

I have similar problem when running Kismet for several days. Memory usage grows and eventually, the swap file fills and systems gets terribly slow. If you run with --no-logging, this will help allow kismet to run much longer. Also, I haven't tested this yet, but configuring logging.conf to create new log files may help with memory as well

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/kismetwireless/kismet/issues/150?email_source=notifications&email_token=AFKJYY4VJ5OQ4HMTBR7NTF3Q5XJULA5CNFSM4HZENSS2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEI47OKQ#issuecomment-574224170, or unsubscribe https://github.com/notifications/unsubscribe-auth/AFKJYY23MBRWTOQIQQNGKADQ5XJULANCNFSM4HZENSSQ .

kismetwireless avatar Jan 14 '20 15:01 kismetwireless