Kismet Wireless

Kismet Forums

 

Posted by:KristoferBeck
Subject:Sirfmon III gps, no CGPS, and no coordinates in .gps file
Date:14:17:28 16/07/2008

> checking netinet/in.h presence... yes
> checking for netinet/in.h... yes
> checking netinet/tcp.h usability... yes
> checking netinet/tcp.h presence... yes
> checking for netinet/tcp.h... yes
> checking for netinet/ip.h... no
> checking termios.h usability... yes
> checking termios.h presence... yes
> checking for termios.h... yes
> checking for strings.h... (cached) yes
> checking ncurses.h usability... yes
> checking ncurses.h presence... yes
> checking for ncurses.h... yes
> checking getopt.h usability... yes
> checking getopt.h presence... yes
> checking for getopt.h... yes
> checking netdb.h usability... yes
> checking netdb.h presence... yes
> checking for netdb.h... yes
> checking for round... no
> checking for strlcpy... no
> checking for strlcat... no
> checking for strtonum... no
> checking for setlocale... yes
> checking whether time.h and sys/time.h may both be included... yes
> checking whether struct tm is in sys/time.h or time.h... time.h
> checking for struct tm.tm_zone... yes
> checking for timezone variable... yes
> checking for daylight external... yes
> checking for gethostbyname in -lnsl... yes
> checking for socket in -lsocket... no
> checking for rint in -lm... yes
> checking for open in -lc... yes
> checking for pthread_setcancelstate in -lpthread... yes
> checking X11/xpm.h usability... yes
> checking X11/xpm.h presence... yes
> checking for X11/xpm.h... yes
> checking xpm.h usability... no
> checking xpm.h presence... no
> checking for xpm.h... no
> checking for X... libraries , headers
> checking for gethostbyname... yes
> checking for connect... yes
> checking for remove... yes
> checking for shmat... yes
> checking for IceConnectionNumber in -lICE... yes
> checking for XtToolkitInitialize in -lXt... yes
> checking X11/Xaw/Label.h usability... yes
> checking X11/Xaw/Label.h presence... yes
> checking for X11/Xaw/Label.h... yes
> checking for XawInitializeWidgetSet in -lXaw... yes
> checking for XShapeQueryVersion in -lXext... yes
> checking for XpmCreatePixmapFromXpmImage in -lXpm... yes
> checking for XpSelectInput in -lXp... no
> checking for XmInternAtom in -lXm... no
> checking for ncurses.h... (cached) yes
> checking for initscr in -lncurses... yes
> checking for NMEA support... yes
> checking for SiRF support... yes
> checking for Trimble TSIP support... yes
> checking for FV-18 support... yes
> checking for Tripmate support... yes
> checking for EarthMate support... yes
> checking for iTrax support... yes
> checking for Ashtech support... yes
> checking for Navcom support... yes
> checking for Garmin support... yes
> checking for Garmin Simple Text support... no
> checking for True North support... no
> checking for UBX support... yes
> checking for EverMore support... yes
> checking for GPSClock support... yes
> checking for rtcm104 support... yes
> checking for NTRIP support... yes
> checking for profiling support... no
> checking for NTP time hinting support... yes
> checking for PPS time syncing support... yes
> checking for PPS pulse on CTS rather than DCD... no
> checking privilege revokation user... nobody
> checking for fixed port speed... no
> checking for DBUS support... no
> checking for limited max clients... no
> checking for max devices... no
> checking if device reconfiguration is allowed... yes
> checking for disabled logging... no
> checking for xsltproc... yes
> checking whether xsltproc knows about docbook xsl...
> ^[[B^[[yes
>
> ==========================================
> gpsd 2.37
> ------------------------------------------
> Protocols
> ---------
> Ashtech : yes
> Earthmate : yes
> EverMore : yes
> FV-18 : yes
> Garmin : yes
> Garmin Simple Text : no
> iTrax : yes
> NMEA : yes
> NTRIP : yes
> Navcom : yes
> RTCM104 : yes
> SiRF : yes
> Trimble TSIP : yes
> Tripmate : yes
> True North : no
> UBX : yes
> GPSclock : yes
> Daemon Features
> ---------------
> NTP SHM : yes
> NTP PPS : yes
> PPS input on : DCD
> Fixed port speed : no
> Priv-drop user : nobody
> Enable shared libraries : yes
> Enable DBUS support : no
> Enable X11 support : yes
> Enable Python support : yes
> Limited max clients : no
> Limited max devices : no
> Allow device reconfig : yes
> Squelch logging/hexdump : no
> Build ncurses programs : yes
> ------------------------------------------
> configure: creating ./config.status
> config.status: creating Makefile
> config.status: creating gpsd.spec
> config.status: creating libgps.pc
> config.status: creating libgpsd.pc
> config.status: creating gpsd_config.h
> config.status: gpsd_config.h is unchanged
> config.status: executing depfiles commands
> Configure finished, type 'make' to build.
> [root@localhost gpsd-2.37]#
> [root@localhost gpsd-2.37]# gmake
> gmake all-am
> gmake[1]: Entering directory `/root/gpsd-2.37'
> gmake[1]: Leaving directory `/root/gpsd-2.37'
> [root@localhost gpsd-2.37]# nc localhost 2947
> r=1
> GPSD,R=1
>
> [root@localhost gpsd-2.37]# nc localhost 2947
> r
> GPSD,R=1
>
> Here is my output when compiling and running gpsd 2.37
>
> Nothing happens...
>
> > > Hi,
> > >
> > > I'm having trouble using my navibe gps unit with kismet. I have the gpsd running and can see output using sirfmon /dev/ttyUSB0. However, when I run kismet - there is no GPS information showing and the .gps files are empty. I do have the gps=true and gpshost=localhost:2947 set in the kismet.conf file. Oddly, CGPS does not work neither does nc localhost 2947 r. Any help would be appreciated.
> >
> > I don't know what CGPS is.
> >
> > Netcat/telnet to your gpsd server implies gpsd is borked (not terribly surprising).
> >
> > Your best bet is to first try to get gpsd working to the point where you can telnet to it, type R=1, and get debug output from it... until then, Kismet won't be able to do much (obviously).
> >
> > Make sure you're running the latest kismet (stable or newcore) since a bunch of workarounds for gpsd got checked in recently on both, one of the biggest issues is recent gpsd versions don't respond correctly to multiple commands w/in an unknown period of time (most likely, multiple commands received w/in a single read() of their socket) so if you set too many options at once (J=1 and W=1 for example) commands are silently ignored. Depending how you're trying to configure gpsd, you might hit this.
> >
> > -m

As dumb as this sounds, I think unplugging the gps unit and repluggin it in until cgps sees it is the only work around. The sirfmon sees it and gives coordinates but for some reason kismet won't take the gps data until cgps works.


Reply to this message