S R A / S F X 2 1 0 0 S E R I E S S A T E L L I T E R E C E I V E R
67
that listens to 224.1.1.1:1234 is started on the receiver (e.g. XD). A static route for
this application is entered, to bind to the receiving socket:
Interface: eth0
Gateway: 0.0.0.0
Destination: 224.1.1.1
Netmask: 255.255.255.255
From the previous Local Application Rule #2, we know that output of 224.1.1.1 on
eth0 will stop. Output of 224.1.1.1 on eth1 will, however, continue.
Only
i
f the
incoming multicast IP packets are fragmented
, the application may see
occasional packet loss. The loss will not be constant or periodic and no packets
will be lost on the eth1 output. The rule in this case is to bind the static route to an
interface that is not being used to output the multicast traffic (via a multicast route).
So in the above example, you must change the static route to:
Interface: sat0
Gateway: 0.0.0.0
Destination: 224.1.1.1
Netmask: 255.255.255.255
When the Multicast Routing submenu item is selected under Data Delivery, the Multicast
Routing page is displayed for all network interfaces. A sample Multicast Routing page is
shown in Figure 4-20.
Figure 4-20 Multicast Routing Page
The columns in the Multicast Routing page are described under the Edit Default Route
page (Figure 4-21) and Edit Multicast Routing Table page (Figure 4-22).
