411
• Determine the join/prune interval (global value/interface level value).
• Determine the join/prune timeout (global value/interface value).
• Determine the IPv6 multicast source lifetime.
• Determine the maximum size of join/prune messages.
• Determine the maximum number of (S, G) entries in a join/prune message.
• Determine the DSCP value for IPv6 PIM messages.
Configuring an IPv6 multicast data filter
In either an IPv6 PIM-DM domain or an IPv6 PIM-SM domain, routers can check passing-by IPv6 multicast
data based on the configured filtering rules and determine whether to continue forwarding the IPv6
multicast data. In other words, IPv6 PIM routers can act as IPv6 multicast data filters. These filters can help
implement traffic control on one hand, and control the information available to downstream receivers to
enhance data security on the other hand.
Configuration guidelines
• Generally, a smaller distance from the filter to the IPv6 multicast source results in a more remarkable
filtering effect.
• This filter works not only on independent IPv6 multicast data but also on IPv6 multicast data
encapsulated in register messages.
Configuration procedure
To configure an IPv6 multicast data filter:
Ste
Command Remarks
1. Enter system view.
system-view N/A
2. Enter IPv6 PIM view.
pim ipv6 N/A
3. Configure an IPv6 multicast
group filter.
source-policy acl6-number No IPv6 multicast data filter by default
Configuring a hello message filter
Along with the wide applications of IPv6 PIM, the security requirement for the protocol is becoming
increasingly demanding. The establishment of correct IPv6 PIM neighboring relationships is a
prerequisite for secure application of IPv6 PIM. To guide against IPv6 PIM message attacks, you can
configure a legal source address range for hello messages on interfaces of routers to ensure the correct
IPv6 PIM neighboring relationships.
To configure a hello message filter:
Ste
Command
Remarks
1. Enter system view.
system-view N/A
To Next Page
Loading...
