Any host-inbound traffic that corresponds to a service listed under this option is allowed. For example, suppose a user whose system was directly connected to interface 1.3.1.4 in zone ABC wanted to telnet into interface 2.1.2.4 in zone ABC. For this action to be allowed, the telnet application must be configured as an allowed inbound service on both interfaces and a policy must permit the traffic transmission.
Table 19 lists the supported services. A value of all indicates that traffic from all of the following services is allowed inbound on the specified interfaces (of the zone, or a single specified interface)
Table 19: Supported System Services
|
Supported System Services |
|||
|---|---|---|---|
|
all |
http |
rpm |
traceroute |
|
bootp |
https |
rsh |
xnm-clear-text |
|
dhcp |
ike |
snmp |
xnm-ssl |
|
finger |
netconf |
snmp-trap |
|
|
ftp |
ping |
ssh |
|
|
ident-reset |
rlogin |
telnet |
|
 |
Note: All services listed Table 19 (except DHCP and BOOTP) can be configured either per zone or per interface. A DHCP server is configured only per interface because the incoming interface must be known by the server to be able to send out DHCP replies. |
To configure zones to allow use of supported application services as inbound services, use either J-Web or the CLI configuration editor.