GPS in Version 6.3.5 How to Use it?

[TheOneBananaMan]

First of all: I love this tool! It's the most powerful tool for fully automated capturing of 3-way handshakes AND PMKIDs simultaneously, and for processing this data later with hashcat.

But if I manage to get this tool working with GPS enabled it would be a huge benefit for me:
When I looked at the man page it says --use_gpsd should gather the GPS data from GPSD and write it to pcapng or separate nmea file. But every time I try to use it this error shows:

even with --use_gps_device:

Is the man page just outdated or am I doing something wrong?

In other discussions I heard the whole GPS functionality moved to an other tool called hcxnmealog.
But how do I use this tool if I want to upload the data to tools like WiGLE to connect SSIDs with GPS? Is there any documentation how to use this tool with hcxdumptool at the same time?
I am using this tool on a Raspberry Pi 4 8g with Kali 2025 Rolling on it.

I appreciate any Help!

[ZerBea]

I don't know who wrote this man page, but it wasn't me.
Please take a look at my man page here:
https://github.com/ZerBea/hcxdumptool/blob/master/man/hcxdumptool.1
It refers to the help menu of each tool, which should be the first to read.

hcxnmealog shows an information about the usage and the output file (which is a standard tabulator separated file containing all information retrieved from the GPS device).

$ hcxnmealog -h
hcxnmealog 6.3.5-147-g6cb43de (C) 2025 ZeroBeat
usage:
hcxnmealog <options>

options:
-n <file>      : output nmea 0183 track to file
                  track append to file: filename
                  use gpsbabel to convert to other formats:
                   gpsbabel -w -t -i nmea -f in_file.nmea -o gpx -F out_file.gpx
                   gpsbabel -w -t -i nmea -f in_file.nmea -o kml -F out_file.kml
                  time = UTC (in accordance with the NMEA 0183 standard)
-t <file>      : output separated by tabulator (tsv)
                  clolumns:
                   LINUX EPOCH (seconds that have passed since the date January 1st, 1970)
                    use date -d @epoch_value to convert to human readable time
                   BSSID (MAC ACCESS POINT)
                   ESSID (network name)
                   COUNTRY CODE (ISO / IEC 3166 alpha2 country code)
                   ENCRYPTION (encrypted / open)
                   RSN INFORMATION ELEMENT (WPA2/WPA3)
                    bitmask (--help for more information)
                   WPA INFORMATION ELEMENT (WPA1)
                    bitmask (--help for more information)
                   FREQUENCY (interface frequency in MHz)
                   CHANNEL
                   RSSI (signal strength in dBm)
                   lATITUDE (decimal degrees)
                   LONGITUDE (decimal degrees)
                   ALTITUDE (decimal degrees)
                   SPEED (knots)
                   PDOP (position -3D- dilution of precision)
                   HDOP (horizontal dilution of precision)
                   VDOP (vertical dilution of precision)
-d <device>    : GPS source
                  use gpsd: gpsd
                  use device: /dev/ttyACM0, /dev/tty/USBx, ...
                  get more information: https://en.wikipedia.org/wiki/NMEA_0183
                  depending on the device it can take a while to get a fix
-b <digit>     : baudrate of GPS device
                  default: 9600
-i <INTERFACE> : name of INTERFACE to be used
-h             : show this help
-v             : show version

--bpf=<file>   : input Berkeley Packet Filter (BPF) code (maximum 4096 instructions) in tcpdump decimal numbers format
                  see --help for more information
--help         : show additional help
--version      : show version

Some more information how to convert the standard (tsv) output file to a wigle compatible file is here.
#157
I don't provide conversion tools for third party tools like wigle (which uses its own format specification). The reason is explained here:
#157 (comment)

You can always run hcxnmealog in parallel with hcxdumptool. Therefore start hcxdumptool followed by hcxnmelog (either in the same terminal:)
or in a separate terminal).
There is no extra documentation, because this is Linux basic knowledge.

BTW:
I moved this to discussions, because it isn't really an issue.