Kismet build in kismetdb_to_wiglecsv exports everything as wifi, hardcoded.

The gear needed for wardriving

5 posts • Page 1 of 1
Hello,
to replace my crippled android 9 phone, i jumped on a rpi-zero running kismet. so far so good.

Im also using the onboard bluetooth to capture, so i have a Wifi and a Bluetooth source. It also shows this in the GUI.

As its the latest (right now git state) i can only store in the *.kismet file, what i convert using the kismetdb_to_wiglecsv tool, installed with kismet.

Only to find out that Wigle reports 0 bluetooth, but massive wifi counts from this uploads :?

In the CSV generated, all devices are reported as "WIFI", taking a look at the sourcecode, yes, its hardcoded :cry:

https://github.com/kismetwireless/kisme ... sv.cc#L572

I raised a Bug: https://github.com/kismetwireless/kismet/issues/160

How should Bluetooth devices be named instead of "WIFI" in the CSV?
the supported values are the names (not the character codes) listed in this enumerated type:

https://github.com/wiglenet/wigle-wifi- ... pe.java#L6

cheers, and thanks for helping improve the state of the wireless world!
thanks! i made a pull request to kismet: https://github.com/kismetwireless/kismet/pull/161

this is marking all as BT, i could not figure out how to make the BT / BLE difference :?
kismet shows all the bluetooth devices with a signal power of 0, is this a problem?

(over at the github there is feedback that this is a issue)
it shouldn't be; eventual RSSI/Power logging improvements will only refine the positions of devices.

5 posts • Page 1 of 1

Return to “Net Hugging Hardware and Software”

Who is online

Users browsing this forum: Google [Bot] and 2 guests