 |
Note: If DVMRP or PIM is enabled for an interface, IGMP and MLD host-inbound traffic is enabled automatically. Because ISIS uses OSI addressing and should not generate any IP traffic, there is no host-inbound traffic option for the ISIS protocol. |
Any host-inbound traffic that corresponds to a protocol listed under this option is allowed. For example, if anywhere in the configuration, you map a protocol to a port number other than the default, you can specify the protocol in the host-inbound traffic option, and the new port number will be used.Table 31 lists the supported protocols. A value of all indicates that traffic from all of the following protocols is allowed inbound on the specified interfaces (of the zone, or a single specified interface).
Table 31: Supported Inbound System Protocols
|
Supported System Services |
|||
|---|---|---|---|
|
all |
igmp |
pgm |
sap |
|
bfd |
ldp |
pim |
vrrp |
|
bgp |
msdp |
rip |
|
|
dlsw |
nhrp |
router-discovery |
|
|
dvmrp |
ospf |
rsvp |
|
|
Note: If DVMRP or PIM is enabled for an interface, IGMP and MLD host-inbound traffic is enabled automatically. Because ISIS uses OSI addressing and should not generate any IP traffic, there is no host-inbound traffic option for the ISIS protocol. |
To use supported protocols for host-inbound traffic, use either J-Web or the CLI configuration editor.
This topic covers:
 | Copyright © 2008, Juniper Networks, Inc. All rights reserved. Trademark Notice. | |