You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I recently started using Kismet Wireless on my Raspberry Pi 5, and everything works fine excluding the GPS. When I first tested it using my MediaTek wifi card and u-blox 7 GPS dongle, it connected fine. Once I set up a script to automatically launch Kismet on startup (since I don't have a monitor for my Pi in my car), the GPS doesn't connect, and hangs with the error "No readable data from GPSD in the last 30 seconds, reconnecting."
Full error:
(GPS) Connected to a JSON-enabled GPSD (3.22), enabling JSON mode
(GPS) Connected to gpsd server [::1]:2947
(GPS) Connecting to GPSD on localhost:2947
(GPS) No usable data from gpsd in over 30 seconds, reconnecting...
The startup script contains the following:
sudo airmon-ng start wlan1
sudo gpsd /dev/ttyACM0
kismet -c wlan1mon
It's very possible there's something I'm missing, but in case I'm not I wanted to make an issue report.
The text was updated successfully, but these errors were encountered:
I recently started using Kismet Wireless on my Raspberry Pi 5, and everything works fine excluding the GPS. When I first tested it using my MediaTek wifi card and u-blox 7 GPS dongle, it connected fine. Once I set up a script to automatically launch Kismet on startup (since I don't have a monitor for my Pi in my car), the GPS doesn't connect, and hangs with the error "No readable data from GPSD in the last 30 seconds, reconnecting."
Full error:
(GPS) Connected to a JSON-enabled GPSD (3.22), enabling JSON mode
(GPS) Connected to gpsd server [::1]:2947
(GPS) Connecting to GPSD on localhost:2947
(GPS) No usable data from gpsd in over 30 seconds, reconnecting...
The startup script contains the following:
sudo airmon-ng start wlan1
sudo gpsd /dev/ttyACM0
kismet -c wlan1mon
It's very possible there's something I'm missing, but in case I'm not I wanted to make an issue report.
The text was updated successfully, but these errors were encountered: