Multicast Forwarding - Address Translation - D-Link NetDefend DFL-210 User Manual

4.6.2. Multicast Forwarding using the
SAT Multiplex Rule
The two values {outif;ip} represent a combination of output interface and, if address translation of a
group is needed, an IP address.
If, for example, multiplexing of the multicast group 239.192.100.50 is required to the output
interfaces if2 and if3, then the command to create the rule would be:
add IPRule SourceNetwork=<srcnet> SourceInterface=<if1>
DestinationInterface=core DestinationNetwork=239.192.100.50
Action=MultiplexSAT Service=<service>
MultiplexArgument={if2;},{if3;}
The destination interface is core since 239.192.100.50 is a multicast group. No address translation
of 239.192.100.50 was added but if it is required for, say, if2 then the final argument would be:
MultiplexArgument={if2;<new_ip_address>},{if3;}
4.6.2.2. Multicast Forwarding - Address Translation Scenario
Figure 4.9. Multicast Forwarding - Address Translation
This scenario is based on the previous scenario but now we are going to translate the multicast
group. When the multicast streams 239.192.10.0/24 are forwarded through the if2 interface, the
multicast groups should be translated into 237.192.10.0/24. No address translation should be made
when forwarding through interface if1. The configuration of the corresponding IGMP rules can be
found below in Section 4.6.3.2, "IGMP Rules Configuration - Address Translation".
Example 4.10. Multicast Forwarding - Address Translation
The following SAT Multiplex rule needs to be configured to match the scenario described above:
Web Interface
A. Create a custom service for multicast called multicast_service:
Caution
As previously noted, remember to add an Allow rule matching the SAT Multiplex rule.
158
Chapter 4. Routing