Kismet build in kismetdb_to_wiglecsv exports everything as wifi, hardcoded.
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
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?
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
![Confused :?](./images/smilies/icon_confused.gif)
In the CSV generated, all devices are reported as "WIFI", taking a look at the sourcecode, yes, its hardcoded
![Crying or Very sad :cry:](./images/smilies/icon_cry.gif)
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?
![Image](https://wigle.net/bi/2ZsngqUUff7pC9BaKnNk3Q.png)
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!
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![Confused :?](./images/smilies/icon_confused.gif)
this is marking all as BT, i could not figure out how to make the BT / BLE difference
![Confused :?](./images/smilies/icon_confused.gif)
![Image](https://wigle.net/bi/2ZsngqUUff7pC9BaKnNk3Q.png)
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)
(over at the github there is feedback that this is a issue)
![Image](https://wigle.net/bi/2ZsngqUUff7pC9BaKnNk3Q.png)
it shouldn't be; eventual RSSI/Power logging improvements will only refine the positions of devices.
Hey all. So I dropped my wigle phone and the screen shattered, so I got a raspberry pi 4. I got everything running and collecting wifi and bluetooth. I've figured out everything except for how to implement a pull request (?) to fix this issue where everything exports from the kismetdb as wifi.
I have Kismet 2020-04-R3. I'm pretty sure I have some bluetooth in the log. Can someone please help explain how to implement this fix to correct the bluetooth? I guess I'm a little surprised this is still an issue on a newer kismet release.
Any help would be greatly appreciated.
I have Kismet 2020-04-R3. I'm pretty sure I have some bluetooth in the log. Can someone please help explain how to implement this fix to correct the bluetooth? I guess I'm a little surprised this is still an issue on a newer kismet release.
Any help would be greatly appreciated.
There is now a fix in place: https://github.com/kismetwireless/kisme ... 985afae54e
![Image](https://wigle.net/bi/2ZsngqUUff7pC9BaKnNk3Q.png)
Return to “Net Hugging Hardware and Software”
Who is online
Users browsing this forum: No registered users and 61 guests