Hello Ganesh, > 1) Is the above observation valid one ? Yes, its the intended behavior. See https://tools.ietf.org/html/rfc4605#section-4.2 Multicast Data on the Upstream is only forwarded to the Downstream if subscribers exist, but not vice versa.
> 2) How to avoid doing soo ? For this minimalist scenario you could switch Upstream and Downstream. If a simple multicast forwarder is not sufficient, you might require a multicast routing protocol such as PIM or DVMRP Regards, Sebastian On Friday, November 24, 2017 at 8:30:05 AM UTC+1, Ganesh Reddy wrote: > > Dear all, > > I am trying to analyze below case with mcproxy > > > H1 ======================== Mcproxy/Router ====================== H2 > (downstream)eth0 > eth1(upstream) > > my mcproxy.conf looks as below: > > *protocol IGMPv3;* > *pinstace myProxy: eth1 ==> eth0;* > > Description: > > When i send a UDP stream from H1, the mcproxy is forming multicat route > and blindly forwarding onto its configured upstream, irrespective of > subscriber listening @H2. > > 1)Is the above observation valid one ? > 2)Is this a known limitation ? How to avoid doing soo ? > > Please help me to analyze. > > Thanks, > Ganesh > -- You received this message because you are subscribed to the Google Groups "Multicast Proxy" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
