1 - 2 - 3 - 8 - A - B - C - D - E - F - G - H - I - K - L - M - N - O - P - Q - R - S - T - U - V - W - X - Z
port
Click on the red underlined text to get to the source
... (used in some routing protocols), protocol numbers,
port numbers, management information base object identifiers,
...
...
Requests for parameter assignments (protocols, ports, etc.) should be
sent to <iana@isi.edu>.
...
... use of a link, socket, port, protocol, etc., please contact the IANA
to receive a number assignment.
...
... WELL KNOWN PORT NUMBERS ...
...
The Well Known Ports are controlled and assigned by the IANA and on
most systems can only be used by system (or root ...
... services to unknown callers, a service contact port is
defined. This list specifies the port used by the server ...
... service contact port is
defined. This list specifies the port used by the server process as
its contact port ...
... port used by the server process as
its contact port. The contact port is sometimes called the
"well-known port ...
... by the server process as
its contact port. The contact port is sometimes called the
"well-known port".
...
...
The assigned ports use a small portion of the possible port numbers.
For many years the assigned ports ...
...
The assigned ports use a small portion of the possible port numbers.
For many years the assigned ports were in the range 0-255 ...
... ports use a small portion of the possible port numbers.
For many years the assigned ports were in the range 0-255. Recently,
the range ...
... range 0-255. Recently,
the range for assigned ports managed by the IANA has been expanded to
the range ...
...
Port Assignments:
Keyword Decimal Description References
...
... 0/udp Reserved
# Jon Postel <postel@isi.edu>
tcpmux 1/tcp TCP Port Service Multiplexer
tcpmux 1/udp TCP Port ...
... TCP Port Service Multiplexer
tcpmux 1/udp TCP Port Service Multiplexer
# Mark Lottor <MKL@nisc.sri.com>
...
... # Ed Barron <---none--->
synotics-relay 391/tcp SynOptics SNMP Relay Port
synotics-relay 391/udp SynOptics SNMP Relay Port ...
... Port
synotics-relay 391/udp SynOptics SNMP Relay Port
synotics-broker 392/tcp SynOptics Port Broker Port ...
... SNMP Relay Port
synotics-broker 392/tcp SynOptics Port Broker Port
synotics-broker 392/udp SynOptics Port ...
... Port
synotics-broker 392/tcp SynOptics Port Broker Port
synotics-broker 392/udp SynOptics Port Broker Port ...
... Port Broker Port
synotics-broker 392/udp SynOptics Port Broker Port
# Illan Raab <iraab@synoptics.com>
...
... Port
synotics-broker 392/udp SynOptics Port Broker Port
# Illan Raab <iraab@synoptics.com>
dis 393/tcp Data Interpretation System
...
... MT Protocol
# Peter Eriksson <pen@lysator.liu.se>
synoptics-trap 412/tcp Trap Convention Port
synoptics-trap 412/udp Trap Convention Port
...
... synoptics-trap 412/tcp Trap Convention Port
synoptics-trap 412/udp Trap Convention Port
# Illan Raab <iraab@synoptics.com>
smsp 413/tcp SMSP
...
... # automatic authentication performed
# based on priviledged port numbers
# and distributed data bases which
# identify "authentication domains ...
... # use link protocol (this is actually
# just a rendezvous port from which a
# tcp connection is established)
...
... # use link protocol (this is actually
# just a rendezvous port from which a
tcp connection is established)
...
... REGISTERED PORT NUMBERS ...
...
The Registered Ports are not controlled by the IANA and on most
systems can be used by ordinary user processes or programs executed by
...
... services to unknown callers, a service contact port is
defined. This list specifies the port used by the server ...
... service contact port is
defined. This list specifies the port used by the server process as
its contact port ...
... port used by the server process as
its contact port. While the IANA can not control uses of these ports
...
... its contact port. While the IANA can not control uses of these ports
it does register or list uses of these ports ...
...
Port Assignments:
Keyword Decimal Description References
...
... # Peter Liu <--none--->
timbuktu-srv1 1417/tcp Timbuktu Service 1 Port
timbuktu-srv1 1417/tcp Timbuktu Service 1 Port ...
... Port
timbuktu-srv1 1417/tcp Timbuktu Service 1 Port
timbuktu-srv2 1418/tcp Timbuktu Service 2 Port ...
... Port
timbuktu-srv2 1418/tcp Timbuktu Service 2 Port
timbuktu-srv2 1418/udp Timbuktu Service 2 Port ...
... Port
timbuktu-srv2 1418/udp Timbuktu Service 2 Port
timbuktu-srv3 1419/tcp Timbuktu Service 3 Port ...
... Port
timbuktu-srv3 1419/tcp Timbuktu Service 3 Port
timbuktu-srv3 1419/udp Timbuktu Service 3 Port ...
... Port
timbuktu-srv3 1419/udp Timbuktu Service 3 Port
timbuktu-srv4 1420/tcp Timbuktu Service 4 Port ...
... Port
timbuktu-srv4 1420/tcp Timbuktu Service 4 Port
timbuktu-srv4 1420/udp Timbuktu Service 4 Port ...
... Port
timbuktu-srv4 1420/udp Timbuktu Service 4 Port
# Marc Epard <marc@waygate.farallon.com>
gandalf-lm 1421/tcp Gandalf License ...
... tr-rsrb-p3 1989/udp cisco RSRB Priority 3 port
#PROBLEMS!===================================================
mshnet 1989/tcp MHSnet system
...
... cisco STUN Priority 3 port
#PROBLEMS!===================================================
ipsendmsg 1992/tcp IPsendmsg
...
... # Bob Kummerfeld <bob@sarad.cs.su.oz.au>
#PROBLEMS!===================================================
snmp-tcp-port 1993/tcp cisco SNMP TCP port ...
... dlswpn 2067/udp Data Link Switch Write Port Number
ats 2201/tcp Advanced Training System Program
ats 2201/udp Advanced Training System Program
...
... ftp://ftp.isi.edu/in-notes/iana/assignments/port-numbers ...
... greater than 5.0) "registers" the
IP port number that is allocated to a particular service when that
service is ...
... Transport
Independent RPC equivalent, take either a user specified port number
or RPC_ANY (-1) which effectively means "I don't care." In the "I
...
... if euid of the requesting process is 0 (i.e., root)
allocate the next available port number in the
reserved port range.
...
... allocate the next available port number in the
reserved port range.
else
allocate the next available port ...
...
Port numbers count up sequentially.
...
...
Can a port that is "assigned" can be used when the assignee's service
is not present? Say port ...
... port that is "assigned" can be used when the assignee's service
is not present? Say port 501 is assigned to the "jeans" service. On
a machine that does not have the "jeans" service ...
... service, nor has any clients
that might be expecting to use it, is port 501 available for other
uses? Any dynamic allocation process, like the portmapper, that
chooses the next unused port ...
... port 501 available for other
uses? Any dynamic allocation process, like the portmapper, that
chooses the next unused port might allocate port 501 dynamically to a
process that asked for a "I don't care" port ...
... uses? Any dynamic allocation process, like the portmapper, that
chooses the next unused port might allocate port 501 dynamically to a
process that asked for a "I don't care" port. So any dynamic
...
... port might allocate port 501 dynamically to a
process that asked for a "I don't care" port. So any dynamic
allocation scheme may pick an unused port that happened to correspond
...
... process that asked for a "I don't care" port. So any dynamic
allocation scheme may pick an unused port that happened to correspond
to a port number that had been "assigned" but was currently unused.
...
... allocation scheme may pick an unused port that happened to correspond
to a port number that had been "assigned" but was currently unused.
...
...
While it might be desirable, it is impossible to guarantee that any
unused port, even though officially assigned to a service, is not
picked by a dynamic allocator since such an assignment might occur
...
...
There is the restriction that only "superuser" on BSD derived systems
such as SunOS can bind to a port number that is less than 1024. So
programs have used this information in the past to identify whether or
not the service ...
... noted that an RPC service was using port 781, it would be just as
happy using port 891, or 951. The service ...
... service was using port 781, it would be just as
happy using port 891, or 951. The service doesn't care what port it
...
... happy using port 891, or 951. The service doesn't care what port it
gets, remote clients will query ...
... gets, remote clients will query the portmapper to ask it what port
number was assigned to the service when it was started. The key is
that the port ...
... port
number was assigned to the service when it was started. The key is
that the port was not currently in use. The only port that ONC/RPC ...
... service when it was started. The key is
that the port was not currently in use. The only port that ONC/RPC
...
... services that are ONC/RPC based just pick the next available port,
those that have pre-assigned ports bind to their pre-assigned port ...
... RPC based just pick the next available port,
those that have pre-assigned ports bind to their pre-assigned port.
Clearly the correct sequence is to have all services ...
... port,
those that have pre-assigned ports bind to their pre-assigned port.
Clearly the correct sequence is to have all services that need a
...
... Clearly the correct sequence is to have all services that need a
particular port to be started first (or if they are "latent" services
that are started by inetd, to have inetd started). Finally, the RPC ...
... that are started by inetd, to have inetd started). Finally, the RPC
services should be started as they will be assigned unused ports. (In
the BSD networking code (which we use) the algorithm for picking
...
... . (In
the BSD networking code (which we use) the algorithm for picking
ports is in the file in_pcb.c, function in_pcbbind().)
...
... a) Services that will "run" continuously and have an assigned
port. Note that this includes rpcbind (nee portmap) that has
port 111 assigned to it.
...
... port. Note that this includes rpcbind (nee portmap) that has
port 111 assigned to it.
b) inetd - which will automatically create ...
... c) RPC services - which will automatically pick unused ports and
maximize efficiency of the "IP Port ...
... * privileged processes (e.g. root).
* Ports > IPPORT_USERRESERVED are reserved
* for servers, not necessarily privileged.
*/
...
...
Portmap does not allocate ports, the kernel allocates ports. The code
that does this is part of nearly every UNIX ...
...
Portmap does not allocate ports, the kernel allocates ports. The code
that does this is part of nearly every UNIX system in the world (and
...
... RPC services
ask the kernel to allocate them a port by calling the "bind()" system
call. The parameter they pass is "INADDR_ANY" which means "allocate
me any IP ...
... call. The parameter they pass is "INADDR_ANY" which means "allocate
me any IP port you want". The kernel does that by looking at all of
the ports that are currently in use and picking one that is not
...
... IP port you want". The kernel does that by looking at all of
the ports that are currently in use and picking one that is not
currently used. The number picked is either less that 1024 if the
process is privledged, or greater than 1024 if the process is not
...
... currently used. The number picked is either less that 1024 if the
process is privledged, or greater than 1024 if the process is not
privledged. After the kernel has allocated a port, the service
registers this allocation with portmap. The portmapper is merely a
...
... registers this allocation with portmap. The portmapper is merely a
registry of previously allocated ports. Note "allocated" here is
being used in the sense that they are used by an open socket, not
...
... from or is headed to. For services like finger that have assigned
ports, they can just hard code the port they want into their
executable. (it isn't like it will change, and if they read it from
...
... like finger that have assigned
ports, they can just hard code the port they want into their
executable. (it isn't like it will change, and if they read it from
/etc/services ...
... executable. (it isn't like it will change, and if they read it from
/etc/services and someone had mistyped the port number it won't
interoperate with clients anyway!)
...
... It is not practical to read the /etc/services file into the kernel to
prevent it from giving out port numbers that are "pre-assigned", nor
is it generally desirable since with the correct ordering of startup
it is completely unneccesary.
...
... Host Unreachable
2 Protocol Unreachable
3 Port Unreachable
4 Fragmentation Needed and Don't Fragment ...
... registry, an OID value of the form
{applTCPProtoID port} or {applUDProtoID port} are used for
TCP ...
... OID value of the form
{applTCPProtoID port} or {applUDProtoID port} are used for
TCP-based and UDP ...
... TCP-based and UDP-based protocols, respectively. In either
case 'port' corresponds to the primary port number being
used by the protocol."
...
... UDP-based protocols, respectively. In either
case 'port' corresponds to the primary port number being
used by the protocol."
::= {assocEntry 3}
...
...
-- OIDs of the form {applTCPProtoID port} are intended to be used
-- for TCP-based protocols that don't have OIDs ...
... TCP-based protocols that don't have OIDs assigned by other
-- means. {applUDPProtoID port} serves the same purpose for
-- UDP-based protocols. In either case 'port ...
... port} serves the same purpose for
-- UDP-based protocols. In either case 'port' corresponds to
-- the primary port number being used by the protocol. For example,
...
... UDP-based protocols. In either case 'port' corresponds to
-- the primary port number being used by the protocol. For example,
-- assuming no other OID is assigned for SMTP ...
... registry, an OID value of the
form {applTCPProtoID port} or {applUDProtoID port} are used
for TCP ...
... OID value of the
form {applTCPProtoID port} or {applUDProtoID port} are used
for TCP-based and UDP ...
... TCP-based and UDP-based protocols, respectively. In
either case 'port' corresponds to the primary port number
being used by the group ...
... UDP-based protocols, respectively. In
either case 'port' corresponds to the primary port number
being used by the group. applTCPProtoID and applUDPProtoID
...