Revision 1 as of 2005-03-31 18:31:00
fix RPC link
|Deletions are marked like this.||Additions are marked like this.|
|Line 4:||Line 4:|
|The Portmap protocol is part of the ["RPC"] protocol family.||The Portmap protocol is part of the ["ONC-RPC"] protocol family.|
|Line 14:||Line 14:|
|* ["RPC"]: Typically, Portmap uses ["RPC"] as its transport protocol.||* ["ONC-RPC"]: Typically, Portmap uses ["ONC-RPC"] as its transport protocol.|
The Portmap protocol is part of the ["ONC-RPC"] protocol family.
XXX - add a brief PROTO description here
XXX - add a brief description of Portmap history
- ["ONC-RPC"]: Typically, Portmap uses ["ONC-RPC"] as its transport protocol.
XXX - Add example traffic here (as plain text or Ethereal screenshot).
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.
(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.
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:
You cannot directly filter Portmap protocols while capturing.
- add link to Portmap specification and where to find additional info on the web about Portmap