Re: gpsfake usage

[Владимир Калачихин]

Hi Gary!
27.04.2020 20:49, Gary E. Miller пишет:
> You need more thrust to make this pig fly.

You right.

In one lan it works fine with start slave gpsd as
./gpsd -N gpsd://192.168.10.10

Via NAT - ERROR Unrecognized request '' :

gpsd -N -D 4 gpsd://192.168.10.10
gpsd:INFO: launching (Version 3.17)
gpsd:INFO: listening on port gpsd
gpsd:PROG: NTP: shmat(0,0,0) succeeded, segment 0
gpsd:PROG: NTP: shmat(32769,0,0) succeeded, segment 1
gpsd:PROG: NTP: shmat(65538,0,0) succeeded, segment 2
gpsd:PROG: NTP: shmat(98307,0,0) succeeded, segment 3
gpsd:PROG: NTP: shmat(131076,0,0) succeeded, segment 4
gpsd:PROG: NTP: shmat(163845,0,0) succeeded, segment 5
gpsd:PROG: NTP: shmat(196614,0,0) succeeded, segment 6
gpsd:PROG: NTP: shmat(229383,0,0) succeeded, segment 7
gpsd:PROG: shmget(0x47505344, 8928, 0666) for SHM export succeeded
gpsd:PROG: shmat() for SHM export succeeded, segment 262152
gpsd:INFO: stashing device gpsd://192.168.10.10 at slot 0
gpsd:INFO: running with effective group ID 20
gpsd:INFO: running with effective user ID 65534
gpsd:INFO: startup at 2020-04-28T15:01:55.000Z (1588086115)
gpsd:CLIENT: => client(0): 
{"class":"VERSION","release":"3.17","rev":"3.17","proto_major":3,"proto_minor":12}\x0d\x0a
gpsd:PROG: checking client(0)
gpsd:CLIENT: <= client(0): ?WATCH={"enable":true,"json":true};\x0a
gpsd:PROG: no /etc/gpsd/device-hook present, skipped running ACTIVATE hook
gpsd:INFO: opening remote gpsd feed at 192.168.10.10, port 2947.
gpsd:INFO: gpsd_activate(2): activated GPS (fd 6)
gpsd:CLIENT: => client(0): 
{"class":"DEVICES","devices":[{"class":"DEVICE","path":"gpsd://192.168.10.10","activated":"2020-04-28T15:02:02.430Z"}]}\x0d\x0a{"class":"WATCH","enable":true,"json":true,"nmea":false,"raw":0,"scaled":false,"timing":false,"split24":false,"pps":false}\x0d\x0a
gpsd:PROG: switching to match packet type 18: 
{"class":"VERSION","release":"3.20.1~dev","rev":"release-3.20-489-g5d52e5e63","proto_major":3,"proto_minor":14}
gpsd:PROG: switch_driver(JSON slave driver) called...
gpsd:PROG: selecting JSON slave driver driver...
gpsd:INFO: gpsd://192.168.10.10 identified as type JSON slave driver, 0 
sec @ 0bps
gpsd:PROG: JSON, passing through 
{"class":"VERSION","release":"3.20.1~dev","rev":"release-3.20-489-g5d52e5e63","proto_major":3,"proto_minor":14,"remote":"gpsd://192.168.10.10"}
gpsd:PROG: device 0 (fd=6, path gpsd://192.168.10.10) already active.
gpsd:CLIENT: => client(0): 
{"class":"DEVICE","path":"gpsd://192.168.10.10","driver":"JSON slave 
driver","activated":"2020-04-28T15:02:02.433Z"}\x0d\x0a
gpsd:CLIENT: => client(0): 
{"class":"VERSION","release":"3.20.1~dev","rev":"release-3.20-489-g5d52e5e63","proto_major":3,"proto_minor":14,"remote":"gpsd://192.168.10.10"}\x0d\x0a
gpsd:PROG: JSON, passing through 
{"class":"ERROR","message":"Unrecognized request ''"}
gpsd:CLIENT: => client(0): {"class":"ERROR","message":"Unrecognized 
request ''"}\x0d\x0a
gpsd:PROG: checking client(0)
gpsd:INFO: detaching ::1 (sub 0, fd 5) in detach_client
gpsd:PROG: device 0 (fd 6) released


If I start slave gpsd via NAT as
./gpsd -b -N gpsd://192.168.10.10
- after ?WATCH get DEVICES and infinitely wait for WATCH.



Владимир Калачихин