Hi, since PIM needs to be enabled on all interfaces towards senders/receivers (besides on the interfaces between the multicast routers), it'd possible for an attacker/malicious user to form a …

Loopback interfaces may be used as an RP address, if you enable PIM on them as you would your other interfaces. The advantage of a loopback interface, is that it may still be reachable, …

The ip pim accept-register command prevents a source from registering with the RP who in turn responds with a register stop. This does not prevent the downstream device from sending join …

I assume that you've got the command ip pim sparse on all the right interfaces from the outputs you gave above, but because you didn't post the interface config I can't say for certain. A good …

option. It makes me think that it's platform or version or interface type (or all of the above) specific. It's definitely relevant to a particular scenario. I tried it in VIRL using switches with VLAN …

The “ ip pim auto-rp listener ” will cause the auto-rp group 224.0.1.39 and 224.0.1.40 to be flooded at dense. Because this command was not allowed and having configured the interfaces in …

When I deleted "ip pim autorp listener" command on R1 and made it DR on the R1-R2 segment (and issued "clear ip pim rp" on all the routers), the 224.0.1.40 group traffic from R1 still …

Important is the Note: To use PIM snooping, you must enable IGMP snooping on the switch. IGMP snooping restricts multicast traffic that exits through the LAN ports to which hosts are …

ip pim rp-address 1.1.1.1 bidir Netmask on Primary RP is configured for the longest match (1.1.1.1 255.255.255.255) and secondary is configured with (1.1.1.0 255.255.255.254). The …

Poison3000, Your configuration is missing the “ip pim auto-rp listener” command. When you configure Auto-RP the candidate RPs send multicast messages to 224.0.1.39 towards the …