kismete_drone over SSH tunnel

[imported_cybrsnpr]

I would change that port. I used to get thousands of brute force attempts over port 22, daily.

Agree 100%...my snort logs will attest to that as well! Just wanted to keep it simple for testing purposes.

Next up, doing the same thing with gpsd.

[imported_cybrsnpr]

Next up, doing the same thing with gpsd.

Since I mentioned previously about running the same ssh tunnel setup with gpsd, figured I would follow up and post the results/syntax:

So: works great with kismet_drone remote configuration. No changes to any .conf file is needed. Just open another ssh shell to the remote drone that is running gpsd:
#>ssh -L 2947:127.0.0.1:2947 <useracct>@<remote DRONE IP>

When you open kismet on your local box, you should have your Lat/Long info on your kismet server.

Cheers...