Kismet Wireless

Kismet Forums


Posted by:FreierRadikaler
Subject:On-the-fly PPI-processing
Date:15:37:19 29/05/2013

> > Hi@all,
> >
> > is there a possibility to process the PPI-header on the fly while capturing pakets from multiple drones?
> > As the tap interface doesn't provide this header, there is only the possibility to get those data by processing the *.pcapdump file, right? I read, that there was the possibility in the past to get this header by a fifo named pipe but this feature was removed long ago.
> > My aim is to get somthing like this after processing:
> >
> > [Sender-Mac];[CaptureDroneName e.g. Drone1];RSSI-Value1;RSSI-Value2;...;RSSI-ValueN;
> >
> > The problem is that this processing should be an on going process without interruption like:
> > Kismet_start -> wait some time-> kismet stop -> processing -> delete old pcapfile-> kismet start -> wait some time -> kismet stop -> processing -> and so on ...
> >
> > The problem with this basic approach is that the pcap file will grow unlimited as long as the kismet_server runs; but I don't need the package data anymore after processing...
> >
> > I need this data for a RSSI based localisation system.
> You could modify tuntap to export a PPI header, just set the DLT properly. It would be a bit broken in terms of network device, but it'd work.

This would be one possibility. But I think this way would be better:

I just connect directly to the drone with my own script and parse the tcp stream by myself. This reduces the overhead of the kismet_server that is redundant for my purposes in fact. But now I've got the next problem: How do I have to interpret the bits of the tcp stream that i get from the drones? Is there a documentation? I can recognise the pakages itself by connecting via telnet to one of the drones, but the ppi header seems to be a little bit different!?

Is there a documentation?

Edit: Easiest solution is telnet the kismet_server and type:
!0 ENABLE CLIENT mac,signal_dbm,noise_dbm,minsignal_dbm,minnoise_dbm,maxsignal_dbm,maxnoise_dbm,signal_rssi,noise_rssi,minsignal_rssi,minnoise_rssi,maxsignal_rssi,maxnoise_rssi,freqmhz,channel

Reply to this message