From: Petr Lapukhov (petrsoft@gmail.com)
Date: Wed Mar 22 2006 - 05:29:57 GMT-3
Hello Alexei,
AFAIR cisco only forwards broadcasts if they are udp, i.e.
if they are permitted by ip forward-protocol and we have
some sort of helper-address / spanning-tree flooding.
While it is true that 99% of multicast applications are UDP
based, in the lab we usually use pings to test mcast connectivity.
(Althought one can use IP SLA monitor/traceroute to simulate
UDP traffic). So limiting ourselves just to UDP is a little bit
overthinking.
Anyway,the idea of mcast->bcast conversion sounds cool,
But at least, we need to setup R4 to perform some part of the job,
and we are only allowed to configure R2..
And at last, if the bcast->mcast conversion was the case, the task
should have noted some words about broadcasting/udp.
HTH
Petr
22.03.06, Alexei Monastyrnyi <alexeim@orcsoftware.com> NAPISAL(A):
>
> Hi.
> IMO you don't have to know a UDP details of multicast traffic for
> particular group, you will translate all multicast for this group to an
> arbitrary UDP port of your choice for directed broadcast and than back.
> Just reverse an example below from
> broadcast <-> multicast <-> broadcast
> to
> multicast <-> broadcast <-> multicast
>
> Using tunnels is a tricky Q cause they usually say in preamble that you
> cannot create any new interface unless it is necessary to accomplish a
> task. So this is usually a Q to proctor.
>
> A.
>
> on 22/03/2006 00:21 david robin wrote:
> > I think tunnel interface will not solve the problem as you must enable
> > multicast on the tunnel interface,
> > with multicast helper, it may work but you must know the udp port which
> the
> > multicast is use in order to make that work
> >
> >
> > On 3/22/06, Alexei Monastyrnyi <alexeim@orcsoftware.com> wrote:
> >
> >> Hi.
> >> you can do that either via tunnel interface or via multicast to
> >> broadcast convention.
> >>
> >> multicast helper example may help
> >>
> >>
> >>
> >
> http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122cgcr/fipr_
> > c/ipcpt3/1cfmulti.htm#wp1003511
> >
> >> A.
> >>
> >> on 21/03/2006 22:54 Schulz, Dave wrote:
> >>
> >>> Group -
> >>>
> >>> If I have a multicast group that is running in sparse-mode with 3
> >>> routers and a static RP.....R1, R2 and R3. I have a loopback on R3
> that
> >>> has a igmp join to 225.5.5.5. And, everything is working good and can
> >>> ping the group from all routers, and everyone is happy. However, the
> >>> next requirement is to have a router R4 attached to R2 that does not
> >>> have multicast enabled, but allowing users on VLAN70 to reach this
> >>> multicast group. And, you have to configure this on R2, not R4. Any
> >>> thoughts?
> >>>
> >>> R1---------------R2(RP)------------------R3
> >>> | s0
> >>> \
> >>> R4........VLAN70
> >>>
> >>>
> >>>
> >>> Dave Schulz,
> >>> Email: dschulz@dpsciences.com <mailto:dschulz@dpsciences.com >
> >>>
> >>>
> _______________________________________________________________________
> >>> Subscription information may be found at:
> >>> http://www.groupstudy.com/list/CCIELab.html
> >>>
> >> _______________________________________________________________________
> >> Subscription information may be found at:
> >> http://www.groupstudy.com/list/CCIELab.html
> >>
> >
> > _______________________________________________________________________
> > Subscription information may be found at:
> > http://www.groupstudy.com/list/CCIELab.html
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
This archive was generated by hypermail 2.1.4 : Sat Apr 01 2006 - 10:07:39 GMT-3