You got the point: in order to have multicast streams only sent where they are wanted, you use L3 and route (and use PIM-SM on the L3 routing, and IGMP in each (v)LANs). Another argument against big LANs, actually. ------------------------------ Olivier Benghozi ----------------------------- ...

thanks so much !! I noticed the version (ver. 14) caused this. ver.18 works as expected.

Hi Daniel, yes, the usage of auto-export allows to have imported routes of VRF_A appearing in the routing table of VRF_B, but then when I try to export them into BGP to make them available also for remote PEs, it doesn't work. BR ------------------------------ ERIDANO DI PIETRO --------------- ...

Hi Eridano, For importing routes from VRF to another VRF use RIB groups to ensure two-way communication. Also, are the routes from VRF-A shown in the VRF-B? ------------------------------ DANIEL TRAN ------------------------------

Hi, are the routes imported from VRF_A to VRF_B shown in the routing table of the instance? ------------------------------ DANIEL TRAN ------------------------------

Yes, that is a helpful document. It turns out that the .yml file existed, but was different. I've since attempted a new lab, and et-0/0/0 is behaving as expected. Thanks for the clarification :D ------------------------------ SIMON BROOKS ------------------------------

Hi mate, I checked the documentation and found this article: https://www.juniper.net/documentation/us/en/software/junos/routing-policy/topics/topic-map/filter-based-forwarding-policy-based-routing.html In their example, R2 has a similar configuration as yours but they include a routing-instance ...