From: slevin kremera (slevin.kremera@gmail.com)
Date: Sun Oct 28 2007 - 19:56:07 ART
---------- Forwarded message ----------
From: Joseph Brunner <joe@affirmedsystems.com>
Date: Oct 28, 2007 11:28 PM
Subject: RE: Multicast - Verify Helper Map
To: slevin kremera <slevin.kremera@gmail.com>
The helper-map catches lan broadcast traffic on a f0/0 or e0/0 port and
works with either the directed broadcast (highest ip in segment) or the
local broadcast
255.255.255.255's traffic. Any traffic from 255.255.255.255 or in this case
126.1.22.255 on the port # matching the acl, will hit the process switching
("ip forward protocol" does this) and get converted to multicast.
So you only need the "ip directed broadcast" on the last interface- facing
the lan where the traffic will once again be sent as broadcast. But you need
the destination device's helper-map where you put it, on R2's Serial 0/0.
Check out the doc cd there are some other tricks you can do with this
command, like make a TTL of 1, routable again as multicast.
-Joe
------------------------------
*From:* slevin kremera [mailto:slevin.kremera@gmail.com]
*Sent:* Sunday, October 28, 2007 9:33 AM
*To:* Joseph Brunner
*Subject:* Re: Multicast - Verify Helper Map
hey joe
i am confused about where shud i put the ip directed-broadcast...what u do
in this scenario
source-----fa0/0---------R1-serial0/0--------------------------serial 0/0
R2--------fa0/0--------------
in this scenario ip pim sparse-mode is only configured on R1 Ser0/0,R2
ser0/0 and fa0/0..so in this case i did the following pls correct me where i
went wrong
ON R1
int ser0/0:0
ip add 13.13.42.4 255.255.255.0
ip pim sparse-mode
ip multicast helper-map broadcast 224.2.2.2 105
access-list 105 permit udp host 126.1.22.199 host 126.1.22.255 eq 4000
ip forward-protocol udp 4000
ip pim rp-add 13.13.42.4
On R2
int ser0/0:0
ip pim sparse-mode
ip add 13.13.42.2 255.255.255.0
ip pim rp-add 13.13.42.4
ip multicast helper-map 224.2.2.2 13.13.26.255 105
int fa0/0
ip pim sparse-mode
ip igmp-join group 224.2.2.2
ip add 13.13.26.2 255.255.255.0
ip directed-broadcast
access-list 105 permit udp any any eq 4000
ip forward-protocol udp 4000
On 9/20/07, *Joseph Brunner* <joe@affirmedsystems.com> wrote:
I modified the doc cd example to include converting rip version 1's
broadcast to multicast and remapping the ttl to 16 hops. So my answer is
other than an SLA can you run broadcast rip on the router "before the router
converting" and on router on the other side of the router receiving the
multicast and converting back to broadcast.
If this works the rip v1 routes should make it from R1 to R4
Shall I lab this up, or would you like the honor of testing it?
(where R2 -> R3 is doing the conversion)
First Hop Router Configuration (R2)
interface ethernet 0
ip address 126.1.22.1 255.255.255.0
ip pim sparse-mode
ip multicast helper-map broadcast 239.254.2.5 105 ttl 16
access-list 105 permit udp any any eq 520
ip forward-protocol udp 520
Last Hop Router Configuration (R3)
interface ethernet 1
ip address 126.1.26.1 255.255.255.0
ip pim sparse-mode
ip multicast helper-map 239.254.2.5 126.1.28.255 105
interface ethernet 2
ip address 126.1.28.1 255.255.255.0
ip directed-broadcast
access-list 105 permit udp any any eq 520
ip forward-protocol udp 520
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
juvenn@hotmail.com
Sent: Wednesday, September 19, 2007 11:50 PM
To: ccielab@groupstudy.com
Subject: Multicast - Verify Helper Map
Hi Expert;
Verify Helper Map
how to verify / check the conversion of broadcast to multicast and multicast
to broadcast
Any Other method Beside using ip sla monitor + debug to verify the multicast
helper map ?
Thanks
This archive was generated by hypermail 2.1.4 : Fri Nov 16 2007 - 13:11:19 ART