On Tue, Jan 25, 2005 at 09:09:45PM -0800, Sandy Rutherford wrote:
> > But the question is how to get rpcbind to use tcp-wrappers
> > in the first place!
>
> > Because even with this in hosts.allow, sockstat -46l still
> > shows:
>
> > root rpcbind10188 7 udp4 127.0.0.1:111
> On Wed, 26 Jan 2005 10:02:00 +0100,
> cpghost <[EMAIL PROTECTED]> said:
> But the question is how to get rpcbind to use tcp-wrappers
> in the first place!
> Because even with this in hosts.allow, sockstat -46l still
> shows:
> root rpcbind10188 7 udp4 127.0.0.1:111
Chuck Swiger wrote:
cpghost wrote:
how can one configure NFS daemons (esp. mountd and rpcbind) so that
they listen only on one IP address (e.g. on 192.168.1.1)?
While some of the daemons are growing flags to bind only to specified
addresses, it turns out to be unwise to depend on that capability
Sandy Rutherford wrote:
> Hello,
> how can one configure NFS daemons (esp. mountd and rpcbind) so that they
> listen
> only on one IP address (e.g. on 192.168.1.1)?
This isn't quite what you are asking about, but it may do the job
none-the-less. With tcp-wrappers you can restrict the IP numbers
> On Tue, 25 Jan 2005 13:51:06 +0100,
> cpghost <[EMAIL PROTECTED]> said:
> Hello,
> how can one configure NFS daemons (esp. mountd and rpcbind) so that they
> listen
> only on one IP address (e.g. on 192.168.1.1)?
This isn't quite what you are asking about, but it may do the job
no
cpghost wrote:
how can one configure NFS daemons (esp. mountd and rpcbind) so that they
listen only on one IP address (e.g. on 192.168.1.1)?
While some of the daemons are growing flags to bind only to specified
addresses, it turns out to be unwise to depend on that capability alone to
protect a
Hello,
how can one configure NFS daemons (esp. mountd and rpcbind) so that they
listen
only on one IP address (e.g. on 192.168.1.1)?
1. nfsd's -h flag works great.
2. rpcbind's -h flag doesn't seem to work. rpcbind listens on the interfaces
specified by -h, but, according to 'sockstat -4l' also o
