Differences between revisions 4 and 5
Revision 4 as of 2005-04-01 03:17:45
Size: 2431
Editor: GuyHarris
Comment: Portmap *always* uses ONC RPC.
Revision 5 as of 2005-04-01 23:41:19
Size: 2435
Editor: GuyHarris
Comment: Italicize RFC titles, as is done on other pages.
Deletions are marked like this. Additions are marked like this.
Line 47: Line 47:
 * [http://www.ietf.org/rfc/rfc1057.txt RFC 1057] "Remote Procedure Call, Version 2" - an older version of the ONC RPC specification, which describes, in appendix A, version 2 of the protocol.
 * [http://www.ietf.org/rfc/rfc1833.txt RFC 1833] "Binding Protocols for ONC RPC Version 2" - describes version 3 and 4 of the protocol. Those versions are also called "RPCBIND", as they support binding transport endpoint addresses, not just port numbers, to an ONC RPC program number, for use with protocols other than ["TCP"] or ["UDP"], such as the OSI ["COTP"] and ["CLTP"] protocols.
 * [http://www.ietf.org/rfc/rfc1057.txt RFC 1057] ''Remote Procedure Call, Version 2'' - an older version of the ONC RPC specification, which describes, in appendix A, version 2 of the protocol.
 * [http://www.ietf.org/rfc/rfc1833.txt RFC 1833] ''Binding Protocols for ONC RPC Version 2'' - describes version 3 and 4 of the protocol. Those versions are also called "RPCBIND", as they support binding transport endpoint addresses, not just port numbers, to an ONC RPC program number, for use with protocols other than ["TCP"] or ["UDP"], such as the OSI ["COTP"] and ["CLTP"] protocols.

Portmap

The Portmap protocol is part of the ["ONC-RPC"] protocol family.

XXX - add a brief PROTO description here

History

XXX - add a brief description of Portmap history

Protocol dependencies

  • ["ONC-RPC"]: Portmap uses ["ONC-RPC"] as its transport protocol. It is one of the two ["ONC-RPC"] protocols that have a port number assigned to it; it is used to find out the port number or transport endpoint address assigned to a particular ["ONC-RPC"] program, so it needs to have its port number be a well known port number. The well known port number for Portmap is 111.

Example traffic

XXX - Add example traffic here (as plain text or Ethereal screenshot).

Ethereal

The Portmap dissector is (fully functional, partially functional, not existing, ... whatever the current state is). Also add info of additional Ethereal features where appropriate, like special statistics of this protocol.

Preference Settings

(XXX add links to preference settings affecting how Portmap is dissected).

Example capture file

XXX - Add a simple example capture file to the SampleCaptures page and link from here. Keep it short, it's also a good idea to gzip it to make it even smaller, as Ethereal can open gzipped files automatically.

Display Filter

A complete list of Portmap display filter fields can be found in the [http://www.ethereal.com/docs/dfref/p/portmap.html display filter reference]

  • Show only the Portmap based traffic:

     portmap 

Capture Filter

You cannot directly filter the Portmap protocol while capturing. However, as the port number used over ["TCP"] and ["UDP"] is well known (see above), you can filter on that one.

  • Capture Portmap traffic:

     port 111 

  • [http://www.ietf.org/rfc/rfc1057.txt RFC 1057] Remote Procedure Call, Version 2 - an older version of the ONC RPC specification, which describes, in appendix A, version 2 of the protocol.

  • [http://www.ietf.org/rfc/rfc1833.txt RFC 1833] Binding Protocols for ONC RPC Version 2 - describes version 3 and 4 of the protocol. Those versions are also called "RPCBIND", as they support binding transport endpoint addresses, not just port numbers, to an ONC RPC program number, for use with protocols other than ["TCP"] or ["UDP"], such as the OSI ["COTP"] and ["CLTP"] protocols.

Discussion

Portmap (last edited 2008-04-12 17:51:29 by localhost)