Expand description
Portmapper v2 (RFC 1057 appendix A) and rpcbind v3/v4 (RFC 1833) clients for ONC RPC service discovery.
The portmapper (program 100000, port 111) maps a (program, version,
protocol) triple onto the TCP or UDP port serving it. DUMP returns the
entire mapping table to any caller, which makes it the fastest way to
enumerate what RPC services a host runs and on which ports.
rpcbind extends the portmapper with versioned protocol bindings. Version 3
adds GETTIME (server clock); version 4 adds GETSTAT (per-version
operational statistics).
This crate depends on onc_rpc_client for the generic RPC client and
transport layer – the portmapper is program 100000 (a specific RPC
service), not part of the RPC machinery itself.
Re-exports§
pub use programs::known_programs;pub use programs::program_name;pub use programs::security_note;pub use rpcbind::Netbuf;pub use rpcbind::RpcbAddrEntry;pub use rpcbind::RpcbAddrList;pub use rpcbind::RpcbEntry;pub use rpcbind::RpcbList;pub use rpcbind::RpcbRmtCallArgs;pub use rpcbind::RpcbRmtCallRes;pub use rpcbind::RpcbStatByvers;pub use rpcbind::RpcbindClient;pub use rpcbind::RpcbindStatEntry;pub use types::IPPROTO_TCP;pub use types::IPPROTO_UDP;pub use types::PMAP_PORT;pub use types::PMAP_PROG;pub use types::PROGRAM;pub use types::VERSION;pub use types::call_args;pub use types::call_result;pub use types::mapping;pub use types::pmaplist;
Modules§
- programs
- Well-known RPC program number table. Well-known RPC program number table.
- rpcbind
- rpcbind v3/v4 types and client (RFC 1833).
- types
- Portmapper v2 XDR types (RFC 1057 appendix A).
Structs§
- Portmapper
Client - Client for the portmapper service
Enums§
- Portmap
Error - Error from portmapper operations.