D-Link DFL-260E User Manual for DFL-260E - Page 220
Multicast Routing, 4.6.1. Overview, Note: Interface multicast handling must be On or Auto
View all D-Link DFL-260E manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 220 highlights
4.6. Multicast Routing Chapter 4. Routing 4.6. Multicast Routing 4.6.1. Overview The Multicast Problem Certain types of Internet interactions, such as conferencing and video broadcasts, require a single client or host to send the same packet to multiple receivers. This could be achieved through the sender duplicating the packet with different receiving IP addresses or by a broadcast of the packet across the Internet. These solutions waste large amounts of sender resources or network bandwidth and are therefore not satisfactory. An appropriate solution should also be able to scale to large numbers of receivers. The Multicast Routing Solution Multicast Routing solves the problem by the network routers themselves, replicating and forwarding packets via the optimum route to all members of a group. The IETF standards that allow multicast routing are the following: • Class D of the IPv4 address space which is reserved for multicast traffic. Each multicast IP address represent an arbitrary group of recipients. • The Internet Group Membership Protocol (IGMP) allows a receiver to tell the network that it is a member of a particular multicast group. • Protocol Independent Multicast (PIM) is a group of routing protocols for deciding the optimal path for multicast packets. Underlying Principles Multicast routing functions on the principle that an interested receiver joins a group for a multicast by using the IGMP protocol. PIM routers can then duplicate and forward packets to all members of such a multicast group, thus creating a distribution tree for packet flow. Rather than acquiring new network information, PIM uses the routing information from existing protocols, such as OSPF, to decide the optimal path. Reverse Path Forwarding A key mechanism in the multicast routing process is Reverse Path Forwarding. For unicast traffic, a router is concerned only with a packet's destination. With multicast, the router is also concerned with a packets source since it forwards the packet on paths which are known to be downstream, away from the packet's source. This approach is adopted to avoid loops in the distribution tree. Routing to the Correct Interface By default, multicast packets are routed by NetDefendOS to the core interface (in other words, to NetDefendOS itself). SAT Multiplex rules are set up in the IP rule set in order to perform forwarding to the correct interfaces. This is demonstrated in the examples described later. Note: Interface multicast handling must be On or Auto For multicast to function with an Ethernet interface on any NetDefend Firewall, that interface must have multicast handling set to On or Auto. For further details on this 220