WiGLE.net

The new kismet log format stores all data in a sqlite database instead of dumping the data into nettxt and netxml. Could Wigle support this format directly?

https://api.wigle.net/api/v2/file/kml/20180514-01128

Probably not, that's not a great format for transport and incremental diffs. But they do have a new file format we keep meaning to add a parser for.
https://github.com/kismetwireless/kisme ... gging.conf

So the "kismet" log type from the conf file above appears to be producing sqlite output files:

root@zero2:~# file Kismet-20180804-12-02-38-1.kismet
Kismet-20180804-12-02-38-1.kismet: SQLite 3.x database, last written using SQLite version 3024000
root@zero2:~#

The others are pcapppi and pcapng. Does wigle currently support any of these or are there any plans to add support for any of them?
Or as an alternative is there an easy way to convert them to something that wigle is able to parse?

Also noticed they provide scripts to convert to json, kml and pcap:
https://github.com/kismetwireless/kisme ... /log_tools
Guess the only option currently would be kml, unless Wigle adds support for the json output?

So I'm finally starting to upgrade the first of my several snifferkits to a RasPi 3B+ with the Kismet 2018-0-BETA1 code, and of course just discovered the same issue... sqlite file instead of gpsxml or netxml output.

Really would like to see some type of support for data import from the new system.

Kthxbai!

Also noticed they provide scripts to convert to json, kml and pcap:
https://github.com/kismetwireless/kisme ... /log_tools
Guess the only option currently would be kml, unless Wigle adds support for the json output?

Just tried to upload converted new .kismet to .kml file to wigle with no success. https://api.wigle.net/api/v2/file/kml/20181216-00760 - shows zero Wi-Wi GPS lines, but there are 3465 coordinates.

I posted in this thread about why it is not possible with the current beta of 2018 Kismet is at.

viewtopic.php?f=3&t=2585

Basically, if you check the sqllite file it uses now for its logs you will notice it is missing a lot of data that used to be in the netxml. Heck, some of the data is even needed for wigle like wifi strength and ESSID. Until they import all the other data collection that 2016 pulls in, you will not get all the useful data you need, namely the name of the access point.

AWESOME news: Dragorn and co. over at kismet have added WiGLE CSV export as a tool!!

https://github.com/kismetwireless/kisme ... 73ab0f48b4

Woot!!