Bind RPC Services to a special interface
From: Alexander Block (Alexander.Block_at_fernuni-hagen.de)
Date: 01/27/05
- Next message: Stan Goodman: "Re: HAVE YOU HEARD THE GOOD NEWS!"
- Previous message: Tim McCoy: "Re: modem install, how to do, start with the basics"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Thu, 27 Jan 2005 12:00:14 +0100
Hello newsgroup,
I am wondering how to prevent RPC services (I don't know if this is exactly the thing I want to do) from binding to all interfaces available in the computer. For example, I don't need a nfs server listening on a dynamic interface like ippp0 (I am using nmap to verfiy which ports are visible). In fact, the services I want to bind to only one interface (eth0) are: a nis server and a nfs server (and perhaps some other portmapped-/tcpwrapped-/rpc-services in the future). I didn't use inetd or xinetd. I had a look on the man pages of tcpd, rpc.mountd and much others but the only thing I can do, is to change the port but not the interface. Setting restrictions in hosts.allow and hosts.deny didn't have any effect. Does somebody know good literature to get some information about this topic?
Thanks in advance,
Alex
- Next message: Stan Goodman: "Re: HAVE YOU HEARD THE GOOD NEWS!"
- Previous message: Tim McCoy: "Re: modem install, how to do, start with the basics"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]