From: gladston@br.ibm.com
Date: Fri Mar 11 2005 - 11:38:23 GMT-3
If multicast can not be configured on R3, my point of view is that 'ip multicast helper-map..." is not the way to go.
Recalling, multicast helper-map will convert broadcast on the local LAN into multicast on the local router; this router will sent the multicast to the remote router, and the remote router will convert the multicast back to broadcast.
The DOC CD was update and are much more comprehensive on this topic now:
What about "Stub Multicast"?
Even though R3 still have 'ip pim dense-mode' in this case, it does not participate in flood-and-prune behavior.
If it is not allowed at all, I would go with MVR (considering there is a layer 2 between both routers).
==================
quoted
Multicast server is connected to e0 on R1 and sending multicast stream
for group 230.30.30.30. There are users connected to e0 on R3 who need
to receive this traffic. Will the below config forward the traffic to
e0 on R3.
I can only enable multicasting on R1. I am using sparse-mode on e0 of
R1 because there was a previous requirement where I had to configure
pim sparse-mode.
Topology:
e0 R1 s0 -- s0 R2 s1 -- s0 R3 e0
R1:
ip multicast-routing
int e0
ip pim sparse-mode
ip igmp join-group 230.30.30.30
ip directed-broadcast
ip multicast helper-map 230.30.30.30 192.168.3.255 120
access-list 120 permit udp any any
int s0
ip directed-broadcast
R2:
int s0
ip directed-broadcast
int s1
ip directed-broadcast
R3:
int s0
ip diected-broadcast
int e0
ip add 192.168.3.1 255.255.255.0
ip directed-broadcast
TIA,
Sundar Palaniappan
=====================
This archive was generated by hypermail 2.1.4 : Sun Apr 03 2005 - 17:56:44 GMT-3