D-Link DFL-260E User Manual page 202

4.6.2. Multicast Forwarding with SAT
Multiplex Rules
B. Create an IP rule:
1. Go to Rules > IP Rules > Add > IP Rule
2. Under General enter.
• Name: a name for the rule, for example Multicast_Multiplex
• Action: Multiplex SAT
• Service: multicast_service
3. Under Address Filter enter:
• Source Interface: wan
• Source Network: 192.168.10.1
• Destination Interface: core
• Destination Network: 239.192.10.0/24
4. Click the Multiplex SAT tab and add the output interfaces if1, if2 and if3 one at a time. For each interface,
leave the IPAddress field blank since no destination address translation is wanted.
5. Make sure the forwarded using IGMP checkbox is set
6. Click OK
Creating Multiplex Rules with the CLI
Creating multiplex rules through the CLI requires some additional explanation.
First, the IPRuleset, in this example main, needs to be selected as the current category:
gw-world:/> cc IPRuleset main
The CLI command to create the multiplex rule is then:
gw-world:/main> add IPRule SourceNetwork=<srcnet> SourceInterface=<srcif>
DestinationInterface=<srcif> DestinationNetwork=<destnet>
Action=MultiplexSAT Service=<service>
MultiplexArgument={outif1;ip1},{outif2;ip2},{outif3;ip3}...
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:
gw-world:/main> 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
202
Chapter 4. Routing