Create an IPv4 MRoute
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
Create an IPv4 MRoute
Create an mroute for IPv4 multicast on a logical router.
The Advanced Routing Engine allows you to Configure IPv4 Multicast routing for
a logical router. Recall that PIM checks whether the firewall received
the packets on the same interface that the firewall uses to send
unicast packets back to the source, by checking the unicast RIB.
In
a topology where you want unicast packets to take a different route
from multicast packets, you can configure an mroute. An mroute is
static unicast route that points to a multicast source; the mroute
is stored in the multicast RIB (MRIB). PIM uses the mroute for the
RPF checks, rather than using the unicast RIB for RPF checks. Whether
PIM uses the MRIB or URIB for RPF checking depends on the RPF lookup
mode configured for PIM. During RPF checks, the mroute used is the
one with the longest prefix match.
An mroute is useful, for
example, when some devices along the path do not support multicast
routing, so a tunnel is used to connect multicast routers.
- Selectand select a logical router.NetworkRoutingLogical Routers
- SelectMulticastandenable multicast protocol.
- Create an mroute.
- SelectStaticandAddan mroute byName. The name must start with an alphanumeric character, underscore (_), or hyphen (-), and contain zero or more alphanumeric characters, underscore, or hyphen. No dot (.) or space is allowed.
- Enter theDestination(IPv4 Address/Mask or address object) of the mroute, which is the multicast source or subnet to which the firewall performs an RPF check.
- Select the egressInterfacefor the unicast route to the multicast source.
- Enter the IPv4 address (or address object) of theNext Hoprouter toward the source.
- Enter aPreferencefor the route; range is 1 to 255.
- ClickOK.
- ClickOK.
- Commityour changes.