Skip to Content.
Sympa Menu

wg-multicast - Re: strange PIM RP mapping problem

Subject: All things related to multicast

List archive

Re: strange PIM RP mapping problem


Chronological Thread 
  • From: "Greg Shepherd" <>
  • To: "Pekka Savola" <>
  • Cc: "Zenon Mousmoulas" <>, wg-multicast <>
  • Subject: Re: strange PIM RP mapping problem
  • Date: Wed, 23 Jul 2008 18:10:42 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:references; b=mO8iu4HT0gIXnNbZlg/HrD+SIRWxAlWXquQVMjjWsxHj3L4bVp3KDtlg7tMEShWrLa ZkkQpuxrSe/tM0c9koAK/0Jnf1vLsL87xzk4coiIS9ATVOOtBkeknHt8rPcczPId8WNu u7lExFtotfUbOt7zsl5Vb3y8KSyGfUynrl4W0=



On 7/23/08, Pekka Savola <> wrote:
On Wed, 23 Jul 2008, Zenon Mousmoulas wrote:
We have a client site that wants to receive multicast, but they want to limit traffic to specific groups. As is usual for most clients, they don't have their own PIM domain, but instead they rely on our national PIM domain (by use of GRNET's anycast RP).

The only easy way I've found to do this is by using a configuration that statically maps the few groups they want to the correct RP address, and everything else to a "fake" RP address, actually some interface of their own border router.

I don't know about that, but if the intent is also to limit receiving except from specific groups, maybe 'ip multicast boundary [acl]' would do it?

Pekka

Yes, the boundary statement would do it, but only after attracting the traffic. Using an RP-of-last-resort (as proposed) set to a loopback on the router then no joins propagate past the last hop router.

Greg




Archive powered by MHonArc 2.6.16.

Top of Page