Supported System Services for Host Inbound Traffic
This topic describes the supported system services for host inbound traffic on the specified zone or interface.
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 10 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 10: Supported System Services
Supported System Services | |||
|---|---|---|---|
all | ident-reset | rlogin | telnet |
bootp | http | rpm | traceroute |
dhcp | https | rsh | xnm-clear-text |
dhcpv6 | ike | snmp | xnm-ssl |
finger | netconf | snmp-trap |
|
ftp | ping | ssh |
|
 | Note: All services listed in Table 10 (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. |
Related Topics
- JUNOS Software Feature Support Reference for SRX Series and J Series Devices
- Understanding How to Control Inbound Traffic Based on Traffic Types
- Example: Controlling Inbound Traffic Based on Traffic Types