1 .\" Copyright (c) 1987 Sun Microsystems
2 .\" Copyright (c) 1990, 1991 The Regents of the University of California.
3 .\" All rights reserved.
5 .\" Redistribution and use in source and binary forms, with or without
6 .\" modification, are permitted provided that the following conditions
8 .\" 1. Redistributions of source code must retain the above copyright
9 .\" notice, this list of conditions and the following disclaimer.
10 .\" 2. Redistributions in binary form must reproduce the above copyright
11 .\" notice, this list of conditions and the following disclaimer in the
12 .\" documentation and/or other materials provided with the distribution.
13 .\" 3. All advertising materials mentioning features or use of this software
14 .\" must display the following acknowledgement:
15 .\" This product includes software developed by the University of
16 .\" California, Berkeley and its contributors.
17 .\" 4. Neither the name of the University nor the names of its contributors
18 .\" may be used to endorse or promote products derived from this software
19 .\" without specific prior written permission.
21 .\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
22 .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
23 .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
24 .\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
25 .\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
26 .\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
27 .\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
28 .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
29 .\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
30 .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
33 .\" from: @(#)portmap.8 5.3 (Berkeley) 3/16/91
34 .\" $Id: portmap.8,v 1.2 2004/04/03 09:30:21 herbert Exp $
60 is a server that converts
64 protocol port numbers.
65 It must be running in order to make
71 server is started, it will tell
73 what port number it is listening to, and what
75 program numbers it is prepared to serve.
76 When a client wishes to make an
78 call to a given program number,
81 on the server machine to determine
84 packets should be sent.
87 must be started before any
93 forks and dissociates itself from the terminal
94 like any other daemon.
96 then logs errors using
100 records all current mapping in the file
101 .Nm /var/run/portmap_mapping
102 so that if it gets killed and restarted, it can reload the mapping for
103 currently active services.
108 Display version number and exit.
112 from running as a daemon,
113 and causes errors and debugging information
114 to be printed to the standard error output.
116 (foreground) prevents
118 from running as a daemon,
119 and causes log messages
120 to be printed to the standard error output.
122 (foreground) same as -f, but logging as usual
131 should be empty, not writeable by the daemon user, and preferably on a
132 filesystem mounted read-only, noexec, nodev, and nosuid.
134 (mapfile) specify an alternative mapping
138 Set the user-id and group-id of the running process to those given,
139 rather than the compiled-in defaults of DAEMON_UID/DAEMON_GID.
141 If neither are set, then
143 will look up the user
145 and use the uid and gid of that user.
150 run under this user (uid/gid) rather than compiled-in defaults of DEAMON_UID/DAEMON_GID.
158 to address. If you specify 127.0.0.1 it will bind to the loopback
163 to the loop-back address 127.0.0.1. This is a shorthand for
164 specifying 127.0.0.1 with -i.
168 to a non-standard port
173 version is protected by the
175 library. You have to give the clients access to
177 if they should be allowed to use it.
178 .if 'USE_DNS'yes' .ig
179 To allow connects from clients of the network 192.168. you could use
180 the following line in /etc/hosts.allow:
184 In order to avoid deadlocks, the
186 program does not attempt to look up the remote host name or user name, nor will
187 it try to match NIS netgroups. As a consequence only network number patterns
188 (or IP addresses) will work for portmap access control, do not use hostnames.
189 Notice that localhost will always be allowed access to the portmapper.
191 You have to use the daemon name
193 for the daemon name (even if the binary has a different name). For the
194 client names you can only use the keyword ALL or IP addresses (NOT
195 host or domain names).
197 .if !'USE_DNS'yes' .ig
198 To allow connects from clients of
199 the .bar.com domain you could use the following line in /etc/hosts.allow:
203 You have to use the daemon name
205 for the daemon name (even if the binary has a different name). For the
206 client names you can use the keyword ALL, IP addresses, hostnames or domain
207 names. Using netgroup names will likely cause
210 Note that localhost will always be allowed access to the portmapper.
213 For further information please have a look at the
235 manual page was changed by
236 .An Anibal Monsalve Salazar
237 for the Debian Project.