Kismet Wireless

Kismet Forums


Posted by:thirteen37 quirks
Date:22:04:17 02/10/2007

I'm writing a program that reports location data using the gpsd protocol. I've tried it with Kismet and noticed some weirdness.

Admittedly, there's some ambiguity in the gpsd protocol documentation (about midway at, but Kismet also seems to make some strange assumptions in

Firstly, is the use of nulls to mark line endings. gpsd docs says the input lines are delimited by a newline and responses are delimited by CR/LF, yet Kismet sends a null-terminated string and expects one back.

Secondly, Kismet uses 'H' but the closest command which gives the intended values (heading) is 'T' (track made good). Could this be due to an older protocol?

Finally, gpsd recommends using the "watcher" mode instead of polling like Kismet does. Again, this could be due to some differences in protocol versions.

I'm basing this off a quick look at the source from Kismet version 2007-01-R1b.

Reply to this message