Feature request: "Full" extract of timestamp / amplitude / SSID info
This is either a feature request or something that already exists that I'm just doing wrong
I'm new to inSSIDer, and am trying to export what I see on the screen. (timestamp, list of SSIDs and signal strength of each access point at that time).
Unfortuantely, I'm not currently able to use a GPS with the tool [because i need to task other people to visit locations and take measurements, who do not have GPS capability].
When I've exported .ns1 files into Netstumbler, I can see each access point that I saw during my scan, but i am not getting the time/amplitude information (and based on the small size of the .ns1 files, I suspect it's not in there).
Am i doing something wrong, or is this a feature that I can request?
I'm not able to code, but may be able to pay for this specific feature to be added if it's not already there - as it would be very useful to me as I could then further manipulate and report on the data outside of the tool.
Yes, NS1 would be great (and probably easier). Agree that being able to do it within inSSIDer would be cool (but probably more work).
On a related note, my NS1 extracts are showing the vendor as (Fake), but if I snap a screenshot at the same time from inSSIDer, I can see some of the AP vendor names.
(see screenshots). Would be good if this could be fixed too :-)
The vendor showing up as (fake) is a limitation of NetStumbler, there's nothing I can do about it. The reason being that the OUI lookup table inside of NetStumbler is outdated, so newer mac address allocations don't show up.
Also, note that inSSIDer's internal data buffer currently only holds 8 minutes of data. This means that only 8 minutes of data will get exported to the NS1 file. The buffer size (like many other things) will adjustable in a future version.
-- edit --
I've attached a built version of inSSIDer with the NS1 change.
The 8 minute limit is good to know, but shouldn't affect my planned use case.
Makes sense about the OUI lookup table being outdated. For the moment I'll have to kludge that bit of information into my dataset where inSSIDer finds something interesting, but that's easy enough to do.
I really appreciate your responsiveness to my request, and look forwards to having the functionality "native" within inSSIDer at some point down the road :-)
Bookmarks