# Multicast

Den här artikeln är skriven enligt att advanced routing är aktiverat.

## Skillnader legacy routing / advanced routing

I ett långt supportärende om SSM fick vi till slut följande information av PA TAC:

*After Analyzing the Pcaps we can see the packets are coming with any source.*   
*Since we are using Dynamic IGMP, source IP must be included in the Packet for Firewall to Process further so that it's FIB can be populated*

*For Static IGMP, we are specifying Source in Firewall configuration itself so that if IGMP packets come from that particular source will be allowed*  
*While Dynamic IGMP has an option to add Filters, those are basically like access list which either allows or denies the traffic but it will not be enforced as Source*

*Why it is working on Legacy Routing but not Adv. Routing?*   
*==&gt; Legacy routing is relaxed compared to Adv. Routing which is much more strict and in compliance with RFC.*

M.a.o., IGMPv3 Membership Reports behöver en source IP och kan inte använda sig av ASM. Advanced routing generellt följer tydligen RFCerna bättre.

## IGMP

### IGMP Static Join

Konfigurerar man ett static join värde under Logical Router -&gt; LR-namn -&gt; Multicast -&gt; IGMP -&gt; Static så skickas automatiskt ett PIM Join-meddelande uppströms. I konfigurationen behövs ett namn, ett interface med en lyssnare (mot receiver), en grupp-adress och en source-adress. Source-adressen måste vara en /32.

<div class="AutoHeight" id="bkmrk-" style="transition-property: height; transition-duration: 250ms; transition-timing-function: ease; width: 100%; height: auto; overflow: visible;"><div><div class="post-message post-message--collapsed"><div class="post-message__text-container" style="max-height: 600px;"><div class="post-message__text" dir="auto" id="bkmrk--1"></div></div></div></div></div>