Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?




Hierarchy Level


You can configure an incoming interface to accept multicast traffic from a remote source. A remote source is a source that is not on the same subnet as the incoming interface. Figure 1 shows just such a topology – R2 connects to the R1 source on one subnet, and to the incoming interface on R3 on another subnet (ge-1/3/0.0 in the figure).

Figure 1: Accepting Multicast Traffic from a Remote SourceAccepting Multicast Traffic from a Remote Source

In this topology R2 is a pass-through device not running PIM, so R3 is the first hop router for multicast packets sent from R1. Because R1 and R3 are in different subnets, the default behavior of R3 is to disregard R1 as a remote source. You can have R3 accept multicast traffic from R1, however, by enabling accept-remote-source on the target interface.


If the interface you identified is not the only path from the remote source, be sure it is the best path. For example you can configure a static route on the receiver side PE router to the source, or you can prepend the AS path on the other possible routes. That said, do not use accept-remote-source to receive multicast traffic over multiple upstream interfaces, as this use case for the command is not supported.

Commit the configuration changes, and then to confirm that the interface you configured is accepting traffic from the remote source, run the following command:

Required Privilege Level

routing—To view this statement in the configuration.

routing-control—To add this statement to the configuration.

Release Information

Statement introduced in Junos OS Release 9.6.