IP Multicast
Table of Contents
Expand all | Collapse all
-
- Tap Interfaces
-
- Layer 2 and Layer 3 Packets over a Virtual Wire
- Port Speeds of Virtual Wire Interfaces
- LLDP over a Virtual Wire
- Aggregated Interfaces for a Virtual Wire
- Virtual Wire Support of High Availability
- Zone Protection for a Virtual Wire Interface
- VLAN-Tagged Traffic
- Virtual Wire Subinterfaces
- Configure Virtual Wires
- Configure an Aggregate Interface Group
- Configure Bonjour Reflector for Network Segmentation
- Use Interface Management Profiles to Restrict Access
-
- DNS Overview
- DNS Proxy Object
- DNS Server Profile
- Multi-Tenant DNS Deployments
- Configure a DNS Proxy Object
- Configure a DNS Server Profile
- Use Case 1: Firewall Requires DNS Resolution
- Use Case 2: ISP Tenant Uses DNS Proxy to Handle DNS Resolution for Security Policies, Reporting, and Services within its Virtual System
- Use Case 3: Firewall Acts as DNS Proxy Between Client and Server
- DNS Proxy Rule and FQDN Matching
-
- NAT Rule Capacities
- Dynamic IP and Port NAT Oversubscription
- Dataplane NAT Memory Statistics
-
- Translate Internal Client IP Addresses to Your Public IP Address (Source DIPP NAT)
- Enable Clients on the Internal Network to Access your Public Servers (Destination U-Turn NAT)
- Enable Bi-Directional Address Translation for Your Public-Facing Servers (Static Source NAT)
- Configure Destination NAT with DNS Rewrite
- Configure Destination NAT Using Dynamic IP Addresses
- Modify the Oversubscription Rate for DIPP NAT
- Reserve Dynamic IP NAT Addresses
- Disable NAT for a Specific Host or Interface
-
- Network Packet Broker Overview
- How Network Packet Broker Works
- Prepare to Deploy Network Packet Broker
- Configure Transparent Bridge Security Chains
- Configure Routed Layer 3 Security Chains
- Network Packet Broker HA Support
- User Interface Changes for Network Packet Broker
- Limitations of Network Packet Broker
- Troubleshoot Network Packet Broker
-
- Enable Advanced Routing
- Logical Router Overview
- Configure a Logical Router
- Create a Static Route
- Configure BGP on an Advanced Routing Engine
- Create BGP Routing Profiles
- Create Filters for the Advanced Routing Engine
- Configure OSPFv2 on an Advanced Routing Engine
- Create OSPF Routing Profiles
- Configure OSPFv3 on an Advanced Routing Engine
- Create OSPFv3 Routing Profiles
- Configure RIPv2 on an Advanced Routing Engine
- Create RIPv2 Routing Profiles
- Create BFD Profiles
- Configure IPv4 Multicast
- Create Multicast Routing Profiles
- Create an IPv4 MRoute
IP Multicast
A virtual router supports IP multicast so that it can
participate in multicast protocols (IGMP and PIM) and forward multicast
traffic from a source to multiple receivers.
IP multicast is a set of protocols that network appliances
use to send multicast IP datagrams to a group of interested receivers
using one transmission rather than unicasting the traffic to multiple
receivers, thereby saving bandwidth. IP multicast is suitable for
communication from one source (or many sources) to many receivers,
such as audio or video streaming, IPTV, video conferencing, and
distribution of other communication, such as news and financial
data.
A multicast address identifies a group of receivers that want
to receive the traffic going to that address. You should not use
the multicast addresses reserved for special uses, such as the range
224.0.0.0 through 224.0.0.255 or 239.0.0.0 through 239.255.255.255.
Multicast traffic uses UDP, which does not resend missed packets.
Palo Alto Networks® firewalls support IP multicast and Protocol
Independent Multicast (PIM) on a Layer 3 interface that you configure
for a virtual router on
the firewall.
For multicast routing, the Layer 3 interface type can be Ethernet,
Aggregate Ethernet (AE), VLAN, loopback, or tunnel. Interface groups
allow you to configure more than one firewall interface at a time
with the same Internet Group Management Protocol (IGMP) and PIM
parameters, and with the same group permissions (multicast groups
allowed to accept traffic from any source or from only a specific
source). An interface can belong to only one interface group.
The firewall supports IPv4 multicast—it does not support IPv6
multicast. The firewall also does not support PIM Dense Mode (PIM-DM),
IGMP proxy, IGMP static joins, Anycast RP, GRE, or multicast configurations
on a Layer 2 or virtual wire interface type. However, a virtual
wire interface can pass multicast packets. Also, a Layer 2 interface
can switch Layer 3 IPv4 multicast packets between different VLANs
and the firewall will retag the VLAN ID using the VLAN ID of the
egress interface.
You must enable multicast for a virtual router and enable PIM
for an ingress and an egress interface in order for the interfaces
to receive or forward multicast packets. In addition to PIM, you
must also enable IGMP on egress interfaces that face receivers.
You must configure a Security policy rule to allow IP multicast
traffic to a predefined Layer 3 destination zone named
multicast
or
to any
destination zone.