<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<style>
<!--
/* Font Definitions */
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman";}
a:link, span.MsoHyperlink
{color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{color:blue;
text-decoration:underline;}
pre
{margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:Arial;
color:navy;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=EN-US link=blue vlink=blue>
<div class=Section1>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>You could use static RPs or the bootstrap mechanism.
If you go with static, you need to ensure that the RP set is consistent among
all routers in the PIM domain. In your scenario, I would configure the Cisco as
the BSR, and configure it as an RP-candidate for the ghost multicast group
range 224.77.0.0/16, since the Cisco will be the DR for that group. <o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>One problem that I see in your setup is
the Xorp box does not have a route to the other side of the Cisco router, where
your multicast sender is. This will cause problems when the Xorp system wants
to send the source-specific join message back up the multicast tree. I’m
not sure if you can use kernel routes, or if you will have to use a routing
protocol within Xorp. <o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>-Mark Williams<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<div>
<div class=MsoNormal align=center style='text-align:center'><font size=3
face="Times New Roman"><span style='font-size:12.0pt'>
<hr size=2 width="100%" align=center tabindex=-1>
</span></font></div>
<p class=MsoNormal><b><font size=2 face=Tahoma><span style='font-size:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font size=2
face=Tahoma><span style='font-size:10.0pt;font-family:Tahoma'>
xorp-users-bounces@xorp.org [mailto:xorp-users-bounces@xorp.org] <b><span
style='font-weight:bold'>On Behalf Of </span></b>Lucky Stud<br>
<b><span style='font-weight:bold'>Sent:</span></b> Friday, May 22, 2009 22:14<br>
<b><span style='font-weight:bold'>To:</span></b> xorp-users@xorp.org<br>
<b><span style='font-weight:bold'>Subject:</span></b> [Xorp-users] XORP - Linux
- Multicast setup help</span></font><o:p></o:p></p>
</div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'>Hi,<br>
<br>
I am trying to setup the xorp on a linux (RHEL4) machine with 3 interfaces
which routes the traffic for two subnets (setup below). eth0 is directly
connected to the a cisco router. I need to enable multicast routing in order to
be able to use norton ghost and multicast to image the machines in the 192.0/26
and 192.64/26 subnets and also to receive a multicast video feed transmission
from internet. cisco router is setup properly as I can use multicast on all
other subnets that are directly connected to the cisco router. The two subnets
behind the linux router are live ip and not natted. <br>
<br>
I am not sure how to setup the static-rps and/or the bootstrap for the pimsm4
directive to get it to work properly. which interface needs to be the BSR or RP
or just use the static rps.<br>
<br>
Any advise is greatly appreciated.<br>
<br>
I downloaded the latest version of xorp from official site, compiled and
installed it.<br>
<br>
Thanks.<br>
<br>
<br>
<br>
<br>
[muulticast receivers] 192.0/26 ---------- [192.1 (eth1) \<br>
| XORP-linux router- 67.141 (eth0) ]-----------------------[
67.129 Cisco Router ]-----------> out / multicast sender<br>
[muulticast receivers] 192.64/26---------- [192.65 (eth2) /<br>
<br>
<br>
route -n<br>
<br>
192.0 0.0.0.0 255.255.255.192
U 0
0 0 eth1<br>
192.64 0.0.0.0
255.255.255.192 U 0
0 0 eth2<br>
67.128 0.0.0.0
255.255.255.192 U 0
0 0 eth0<br>
0.0.0.0 142.204.67.129
0.0.0.0 UG
0 0 0 eth0<br>
<br>
config.boot<br>
<br>
interfaces {<br>
restore-original-config-on-shutdown: true; <br>
interface eth0 {<br>
default-system-config<br>
}<br>
<br>
interface eth1 {<br>
default-system-config<br>
}<br>
interface eth2 {<br>
default-system-config<br>
}<br>
<br>
}<br>
<br>
fea {<br>
unicast-forwarding4 {<br>
disable: false<br>
}<br>
unicast-forwarding6 {<br>
disable: true<br>
}<br>
}<br>
<br>
plumbing {<br>
mfea4 {<br>
disable: false<br>
interface eth0 {<br>
vif eth0 {<br>
}<br>
}<br>
interface eth1{<br>
vif eth1 {<br>
}<br>
}<br>
interface eth2{<br>
vif eth2 {<br>
}<br>
}<br>
interface register_vif {<br>
vif
register_vif {<br>
}<br>
}<br>
traceoptions {<br>
flag all {<br>
disable: false<br>
}<br>
}<br>
}<br>
}<br>
<br>
<br>
protocols {<br>
igmp {<br>
interface eth0 {<br>
vif eth0 {<br>
}<br>
}<br>
interface eth1 {<br>
vif eth1 {<br>
}<br>
}<br>
interface eth2 {<br>
vif eth2 {<br>
}<br>
}<br>
traceoptions {<br>
flag all {<br>
disable: false<br>
}<br>
}<br>
}<br>
}<br>
<br>
protocols {<br>
pimsm4 {<br>
disable: false<br>
interface eth0 {<br>
vif eth0 {<br>
}<br>
}<br>
interface eth1 {<br>
vif eth1 {<br>
}<br>
}<br>
interface eth2 {<br>
vif eth2 {<br>
}<br>
}<br>
<br>
interface register_vif {<br>
vif
register_vif {<br>
}<br>
}<br>
/*<br>
static-rps {<br>
rp
142.204.67.129 {<br>
group-prefix <a href="http://224.0.0.0/4">224.0.0.0/4</a> {<br>
}<br>
}<br>
}<br>
*/<br>
<br>
bootstrap {<br>
disable:
false<br>
cand-bsr {<br>
scope-zone <a href="http://224.0.0.0/4">224.0.0.0/4</a> {<br>
/* is-scope-zone: false */<br>
cand-bsr-by-vif-name: "eth0"<br>
/* cand-bsr-by-vif-addr: 10.10.10.10 */<br>
/* bsr-priority: 1 */<br>
/* hash-mask-len: 30 */<br>
}<br>
}<br>
<br>
cand-rp {<br>
group-prefix <a href="http://224.0.0.0/4">224.0.0.0/4</a> {<br>
/* is-scope-zone: false */<br>
cand-rp-by-vif-name: "eth0"<br>
/* cand-rp-by-vif-addr: 10.10.10.10 */<br>
/* rp-priority: 192 */<br>
/* rp-holdtime: 150 */<br>
}<br>
}<br>
}<br>
<br>
traceoptions {<br>
flag all {<br>
disable: false<br>
}<br>
}<br>
}<br>
}<br>
<br>
protocols {<br>
fib2mrib {<br>
}<br>
}<br>
<br>
<br>
<br>
<br>
<br>
<o:p></o:p></span></font></p>
<pre><font size=2 face="Courier New"><span style='font-size:10.0pt'><o:p> </o:p></span></font></pre></div>
</body>
</html>