portmap(8) [opendarwin man page]

PORTMAP(8)						    BSD System Manager's Manual 						PORTMAP(8)

NAME

     portmap -- RPC program,version to DARPA port mapper

SYNOPSIS

     portmap [-d] [-v] [-h bindip]

DESCRIPTION

     Portmap is a server that converts RPC program numbers into DARPA protocol port numbers.  It must be running in order to make RPC calls.

     When an RPC server is started, it will tell portmap what port number it is listening to, and what RPC program numbers it is prepared to
     serve.  When a client wishes to make an RPC call to a given program number, it will first contact portmap on the server machine to determine
     the port number where RPC packets should be sent.

     Portmap must be started before any RPC servers are invoked.

     Portmap uses hosts_access(5) access control by default.  Access control patterns may only reference IP addresses.

     Normally portmap forks and dissociates itself from the terminal like any other daemon.  Portmap then logs errors using syslog(3).

     The following options are available:

     -d      Prevent portmap from running as a daemon, and causes errors and debugging information to be printed to the standard error output.

     -v      Enable verbose logging of access control checks.

     -h      Specify specific ip addresses to bind to for UDP requests.  This option may be specified multiple times and is typically necessary
	     when running portmap on a multi-homed host.  If no -h option is specified, portmap will bind to INADDR_ANY, which could lead to prob-
	     lems on a multi-homed host due to portmap returning a udp packet from a different IP address then it was sent to.	Note that when
	     specifying ip addresses with -h, portmap will automatically add 127.0.0.1 to the list so you don't have to.

SEE ALSO

     hosts_access(5), inetd.conf(5), inetd(8), rpcinfo(8)

BUGS

     If portmap crashes, all servers must be restarted.

HISTORY

     The portmap command appeared in 4.3BSD

4.3 Berkeley Distribution					   June 6, 1993 					 4.3 Berkeley Distribution

RPCBIND(8)						    BSD System Manager's Manual 						RPCBIND(8)

NAME

     rpcbind -- universal addresses to RPC program number mapper

SYNOPSIS

     rpcbind [-dilLs]

DESCRIPTION

     rpcbind is a server that converts RPC program numbers into universal addresses.  It must be running on the host to be able to make RPC calls
     on a server on that machine.

     When an RPC service is started, it tells rpcbind the address at which it is listening, and the RPC program numbers it is prepared to serve.
     When a client wishes to make an RPC call to a given program number, it first contacts rpcbind on the server machine to determine the address
     where RPC requests should be sent.

     rpcbind should be started before any other RPC service.  Normally, standard RPC servers are started by port monitors, so rpcbind must be
     started before port monitors are invoked.

     When rpcbind is started, it checks that certain name-to-address translation-calls function correctly.  If they fail, the network configura-
     tion databases may be corrupt.  Since RPC services cannot function correctly in this situation, rpcbind reports the condition and terminates.

     rpcbind can only be started by the super-user.

     Access control is provided by /etc/hosts.allow and /etc/hosts.deny, as described in hosts_access(5) with daemon name rpcbind.

OPTIONS

     -d      Run in debug mode.  In this mode, rpcbind will not fork when it starts, will print additional information during operation, and will
	     abort on certain errors.  With this option, the name-to-address translation consistency checks are shown in detail.

     -i      ``insecure'' mode.  Allows calls to SET and UNSET from any host.  Normally rpcbind accepts these requests only from the loopback
	     interface for security reasons.  This change is necessary for programs that were compiled with earlier versions of the rpc library
	     and do not make those requests using the loopback interface.

     -l      Turns on libwrap connection logging.

     -s      Causes rpcbind to change to the user daemon as soon as possible.  This causes rpcbind to use non-privileged ports for outgoing con-
	     nections, preventing non-privileged clients from using rpcbind to connect to services from a privileged port.

     -L      Allow old-style local connections over the loopback interface.  Without this flag, local connections are only allowed over a local
	     socket, /var/run/rpcbind.sock

NOTES

     All RPC servers must be restarted if rpcbind is restarted.

FILES

     /var/run/rpcbind.sock
     /etc/hosts.allow	    explicit remote host access list.
     /etc/hosts.deny	    explicit remote host denial of service list.

SEE ALSO

     rpcbind(3), hosts_access(5), hosts_options(5), netconfig(5), rpcinfo(8)

BSD
								 October 19, 2008							       BSD