1.\" @(#)rpcbind.1m 1.19 92/09/14 SMI; from SVr4 2.\" Copyright 1989 AT&T 3.\" Copyright 1991 Sun Microsystems, Inc. 4.\" $FreeBSD: src/usr.sbin/rpcbind/rpcbind.8,v 1.10 2007/04/23 07:09:25 matteo Exp $ 5.\" $DragonFly$ 6.Dd April 23, 2007 7.Dt RPCBIND 8 8.Os 9.Sh NAME 10.Nm rpcbind 11.Nd universal addresses to RPC program number mapper 12.Sh SYNOPSIS 13.Nm 14.Op Fl 6adiLls 15.Op Fl h Ar bindip 16.Sh DESCRIPTION 17The 18.Nm 19utility is a server that converts 20.Tn RPC 21program numbers into 22universal addresses. 23It must be running on the host to be able to make 24.Tn RPC 25calls 26on a server on that machine. 27.Pp 28When an 29.Tn RPC 30service is started, 31it tells 32.Nm 33the address at which it is listening, 34and the 35.Tn RPC 36program numbers it is prepared to serve. 37When a client wishes to make an 38.Tn RPC 39call to a given program number, 40it first contacts 41.Nm 42on the server machine to determine 43the address where 44.Tn RPC 45requests should be sent. 46.Pp 47The 48.Nm 49utility should be started before any other RPC service. 50Normally, standard 51.Tn RPC 52servers are started by port monitors, so 53.Nm 54must be started before port monitors are invoked. 55.Pp 56When 57.Nm 58is started, it checks that certain name-to-address 59translation-calls function correctly. 60If they fail, the network configuration databases may be corrupt. 61Since 62.Tn RPC 63services cannot function correctly in this situation, 64.Nm 65reports the condition and terminates. 66.Pp 67The 68.Nm 69utility can only be started by the super-user. 70.Sh OPTIONS 71.Bl -tag -width indent 72.It Fl 6 73Bind to AF_INET6 (IPv6) addresses only. 74.It Fl a 75When debugging 76.Pq Fl d , 77do an abort on errors. 78.It Fl d 79Run in debug mode. 80In this mode, 81.Nm 82will not fork when it starts, will print additional information 83during operation, and will abort on certain errors if 84.Fl a 85is also specified. 86With this option, the name-to-address translation consistency 87checks are shown in detail. 88.It Fl h Ar bindip 89Specify specific IP addresses to bind to for TCP and UDP requests. 90This option 91may be specified multiple times and is typically necessary when running 92on a multi-homed host. 93If no 94.Fl h 95option is specified, 96.Nm 97will bind to 98.Dv INADDR_ANY , 99which could lead to problems on a multi-homed host due to 100.Nm 101returning a UDP packet from a different IP address than it was 102sent to. 103Note that when specifying IP addresses with 104.Fl h , 105.Nm 106will automatically add 107.Li 127.0.0.1 108and if IPv6 is enabled, 109.Li ::1 110to the list. 111.It Fl i 112.Dq Insecure 113mode. 114Allow calls to SET and UNSET from any host. 115Normally 116.Nm 117accepts these requests only from the loopback interface for security reasons. 118This change is necessary for programs that were compiled with earlier 119versions of the rpc library and do not make those requests using the 120loopback interface. 121.It Fl L 122Allow old-style local connections over the loopback interface. 123Without this flag, local connections are only allowed over a local socket, 124.Pa /var/run/rpcbind.sock . 125.It Fl l 126Turn on libwrap connection logging. 127.It Fl s 128Cause 129.Nm 130to change to the user daemon as soon as possible. 131This causes 132.Nm 133to use non-privileged ports for outgoing connections, preventing non-privileged 134clients from using 135.Nm 136to connect to services from a privileged port. 137.El 138.Sh NOTES 139All RPC servers must be restarted if 140.Nm 141is restarted. 142.Sh FILES 143.Bl -tag -width /var/run/rpcbind.sock -compact 144.It Pa /var/run/rpcbind.sock 145.El 146.Sh SEE ALSO 147.Xr rpcbind 3 , 148.Xr netconfig 5 , 149.Xr rpcinfo 8 150