15-19
Cisco ASA Series Firewall CLI Configuration Guide
Chapter 15 Inspection of Database, Directory, and Management Protocols
Sun RPC Inspection
SQL*Net Version 1 is assumed for all other cases. TNSFrame types (Connect, Accept, Refuse, Resend,
Marker, Redirect, and Data) and all packets
will be scanned for ports and addresses. Addresses will be
translated and port connections will be opened.
For information on enabling SQL*Net inspection, see
Configure Application Layer Protocol Inspection,
.
Sun RPC Inspection
This section describes Sun RPC application inspection.
•
Sun RPC Inspection Overview, page 15-19
•
Managing Sun RPC Services, page 15-19
•
Verifying and Monitoring Sun RPC Inspection, page 15-20
Sun RPC Inspection Overview
The Sun RPC inspection engine enables or disables application inspection for the Sun RPC protocol. Sun
RPC is used by NFS and NIS. Sun RPC services can run on any port. When a client attempts to access
a Sun RPC service on a server, it must learn the port that service is running on. It does this by querying
the port mapper process, usually rpcbind, on the well-known port of 111.
The client sends the Sun RPC program number of the service and the port mapper process responds with
the port number of the service. The client sends its Sun RPC queries to the server, specifying the port
identified by the port mapper process. When the server replies, the ASA intercepts this packet and opens
both embryonic TCP and UDP connections on that port.
Tip
Sun RPC inspection is enabled by default. You simply need to manage the Sun RPC server table to
identify which services are allowed to traverse the firewall. For information on enabling Sun RPC
inspection, see
Configure Application Layer Protocol Inspection, page 12-9
The following limitations apply to Sun RPC inspection:
•
NAT or PAT of Sun RPC payload information is not supported.
•
Sun RPC inspection supports inbound ACLs only. Sun RPC inspection does not support outbound
ACLs because the inspection engine uses dynamic ACLs instead of secondary connections.
Dynamic ACLs are always added on the ingress direction and not on egress; therefore, this
inspection engine does not support outbound ACLs. To view the dynamic ACLs configured for the
ASA, use the
show asp table classify domain permit
command.
Managing Sun RPC Services
Use the Sun RPC services table to control Sun RPC traffic through the ASA based on established Sun
RPC sessions. To create entries in the Sun RPC services table, use the
sunrpc-server
command in global
configuration mode:
hostname(config)#
sunrpc-server
interface_name
ip_address mask
service
service_type
protocol
{
tcp
|
udp
}
port
[
-
port
]
timeout
hh
:
mm
:
ss
Summary of Contents for ASA 5508-X
Page 11: ...P A R T 1 Access Control ...
Page 12: ......
Page 157: ...P A R T 2 Network Address Translation ...
Page 158: ......
Page 233: ...P A R T 3 Service Policies and Application Inspection ...
Page 234: ......
Page 379: ...P A R T 4 Connection Management and Threat Detection ...
Page 380: ......