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 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 shows the system services that can be used for host inbound traffic.
Table 10: System Services for Host Inbound Traffic
Host Inbound System Services | |
|---|---|
all | any-service |
dns | finger |
ftp | http |
https | indent-reset |
ike | netconf |
ntp | ping |
reverse-ssh | reverse-telnet |
rlogin | rpm |
rsh | sip |
snmp | snmp-trap |
ssh | telnet |
tftp | traceroute |
xnm-clear-text | xnm-ssl |
Table 11 shows the supported protocols that can be used for host inbound traffic.
Table 11: Protocols for Host Inbound Traffic
Protocols | |
|---|---|
all | bfd |
bgp | dvmrp |
igmp | msdp |
ndp | nhrp |
ospf | ospf3 |
pgm | pim |
rip | ripng |
sap | vrrp |
![]() | Note: All services (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 OS 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
Hide Navigation Pane
Show Navigation Pane
Download
SHA1
