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

[Mike Tubby]

On 19/09/2019 12:28, Tor Rune Skoglund wrote:
> Hi!
>
> Our company's internal demand was about ip-adresses actually, so we're 
> thinking of adding an optional comma-separated list of addresses to 
> the network option as a quick-fix. Would that be sufficient as first 
> attempt?
>
> We might find some time to add this, but don't expect it too early...! :)

It would, but since interfaces have IP addresses binding to devices 
(network interfaces) would appear to meet both requirements.

Many Unix/Linux services have the ability to specify a list of 
interfaces on which to listen including Exim, Bind/Named, Nginx etc. you 
might borrow some ideas from, them?

Mike

> BR, Tor Rune Skoglund
>
> Den 19.09.2019 10:38, skrev 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.