Search found 11 matches

Re: is there any reason to upload more than the legacy 2016 kismet .nettxt?

Thank you @arkasha - sadly, it's worse - I've raised my concerns on https://github.com/kismetwireless/kismet/issues/135 - problem is beside "source failed', kismet is no helping much. Tough situation when the alternatives are either window based or the wiggle app (which is fantastic, but because of ...

Re: is there any reason to upload more than the legacy 2016 kismet .nettxt?

The adventure continues ... so far every git pull from my past messages to the most recent april (compiled from source) release has given me trouble with one of my card (the rtl88xxau) locking to 'nill' channel ,with the workaround to restart kismet 3-5 times until it 'accepts' to switch back to hop...

Re: is there any reason to upload more than the legacy 2016 kismet .nettxt?

Ok! wish there was a way to batch process all this, but we got there in the end. IDs are: 20190318-01339 20190318-01334 20190318-01333 20190318-01329 20190318-01328 20190318-01324 20190318-01302 20190318-01287 20190318-01286 ... with 334 and 339 being new files and containing new wifi data, the rest...

Re: is there any reason to upload more than the legacy 2016 kismet .nettxt?

Ok... currently reprocessing my older wiggle files and will upload all of them tonight to report back. We're getting there :)

Re: is there any reason to upload more than the legacy 2016 kismet .nettxt?

Thank you very much Ark, wouldn't have noticed without you. Quick question: is there a point for me to continue wardriving until the patch is in? I wouldn't want to collect endless points only to not see them appear on the map... thank you!

Re: is there any reason to upload more than the legacy 2016 kismet .nettxt?

Ark, regarding 20190305-00008 (and for that matter all my kismet-based uploads), it's a standard csv file generated by kismet_to_wiglecsv. It's really frustrating to hear that it doesn't seem to 'work' - because inside it looks like this: 86:2A:A8:3B:54:0C,ECCI_AGORA,[WPA2-PSK-CCMP][ESS],2019-Mar-04...

Re: is there any reason to upload more than the legacy 2016 kismet .nettxt?

Hi Ash, so I upgraded to Kismet latest and I'm using their CSV output option to upload to wiggle. I'm satisfied the file contains all the information needed, effectively removing the need to upload the 3 large output files from the 2016 version. Unfortunately, there is also what appears to be a majo...

Re: is there any reason to upload more than the legacy 2016 kismet .nettxt?

Thank you very much Ark. I'll upgrade to 2019 r2 and will report back based on direct ssid querying.

Re: is there any reason to upload more than the legacy 2016 kismet .nettxt?

Update: even worse, not only wiggle ignores the signal data in the nettxt file, it doesn't even try to associate it with the matching ssids in the other two files.... Ok, at the risk of talking to myself, i took the time to upload 3 files i knew i had run a perfect square round the block and downloa...

Re: is there any reason to upload more than the legacy 2016 kismet .nettxt?

Actually, it's worse than that. I'm now getting concerned if wigle even tries to dedupe invalid ssids contained in gpsxml and netxml vs the 'clean' info contained in nettxt. If not, then it seems it would be trivial to cheat wigle by uploading junk data. IMHO gpsxml contains such junk data - see the...

is there any reason to upload more than the legacy 2016 kismet .nettxt?

I've searched these forums and found posts dated 2016-2017 on the topic. As of 2019 however, and having gone through each field in the 2016 legacy edition of kismet, I cannot find any 'odd' field in either the gpsxml or netxml not present already in the nettxt (which evidently is much smaller in siz...

Go to advanced search