Open Network Computing (ONC) Remote Procedure Call (RPC)

This is the ONC variant of RPC. See the RPC page for other variants and a basic description.

ONC-RPC clients will first use the Portmap service to map a well known program number (e.g. 100020 for KLM) into the current port address information at the server (e.g. servers KLM service is available at TCP port 1234) and then contact the actual required service at that port.

XXX - add a brief ONC RPC description here


XXX - add a brief description of ONC RPC history

Protocol dependencies

Most ONC RPC services have no fixed port numbers assigned to them. The only exceptions are Portmap and NFS.

Example traffic

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


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

Preference Settings

(XXX add links to preference settings affecting how RPC 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 Wireshark can open gzipped files automatically.

Display Filter

A complete list of ONC RPC display filter fields can be found in the display filter reference

Show only the ONC RPC based traffic:


Capture Filter

You cannot directly filter ONC RPC protocols while capturing. However, if you know the UDP or TCP port used for a particular protocol on a particular server, you can filter on that one for traffic to and from that server.

External links


Imported from https://wiki.wireshark.org/ONC-RPC on 2020-08-11 23:17:39 UTC