Re: [gpsd-users] Binding gpsd to a specific ip address/port only?

[Mike Tubby]

Hi Tor,

I would be interested in a patch to do this too as we have a use case.

Cay make sure that you handle primary interface names like "eth0" as 
well as aliases like "eth0:17" and VLAN interfaces like "eth0.144".

Regards

Mike


On 19/09/2019 07:57, Gary E. Miller wrote:
> Yo Tor!
>
> On Thu, 19 Sep 2019 08:39:33 +0200
> Tor Rune Skoglund <address@hidden> wrote:
>
> > Am I right in concluding that gpsd by itself cannot be limited to
> > bind to specific ip addresses (e.g. similar to apache's Listen
> > <ipaddress> directive and sshd's ListenAddress <ipaddress:port>), but
> > always grabs all ips when making it available for network access ?
> Yeah.  This has been annoying people for a while...
>
> > What is the correct procedure to suggest a patch or to add this
> > feature?
> Post a patch on this list, or make a Merge Request on GitLab.
>
> Past time to get this fixed, so patches welcome.  I would guess
> a new command line option for what IPs to bind to.
>
> > (My use case is two-fold for this: Firstly; to limit the access to
> > gpsd on specific LAN(s) or interface(s) only - could have used
> > iptables, or course, but that creates an unwanted additional
> > management step. Secondly, we use a container-based systems which
> > disallows the use of the same port number in the container if the
> > host binds to 0.0.0.0 . So in this latter case we just want to bind
> > gpsd to the host's LAN address.)
> Good reasons.
>
> RGDS
> GARY
> ---------------------------------------------------------------------------
> Gary E. Miller Rellim 109 NW Wilmington Ave., Suite E, Bend, OR 97703
>         address@hidden  Tel:+1 541 382 8588
>
>             Veritas liberabit vos. -- Quid est veritas?
>      "If you can't measure it, you can't improve it." - Lord Kelvin