From atanu at ICSI.Berkeley.EDU  Fri Mar  2 10:59:23 2007
From: atanu at ICSI.Berkeley.EDU (Atanu Ghosh)
Date: Fri, 02 Mar 2007 10:59:23 -0800
Subject: [Xorp-users] XORP and Route Server
In-Reply-To: Message from Joseph Lappa <lappa@psc.edu> of "Thu,
	08 Feb 2007 19:31:40 EST."
	<04D8ABF7-6914-4046-920C-8580C8CE0EE2@psc.edu> 
Message-ID: <24659.1172861963@tigger.icir.org>

Hi,

There seems to be a number of different definitions of route server (an
experimental RFC, a globally accessible router, a collection point for
BGP routes, ..), could you give an example of your requirement.

      Atanu.

>>>>> "Joseph" == Joseph Lappa <lappa at psc.edu> writes:

    Joseph> Sorry about that..  Can XORP be used as a Route Server?
    Joseph> Would someone mind posting a sample config?

    Joseph> Thanks!  Joe

    Joseph> On Feb 8, 2007, at 5:20 PM, Pavlin Radoslavov wrote:

    >> Joseph Lappa <lappa at psc.edu> wrote:
    >> 
    >> <EMPTY>
    >> 
    >> Please resend your email, because the body was empty.
    >> 
    >> Regards, Pavlin
    >> 
    >>>  _______________________________________________ Xorp-users
    >>> mailing list Xorp-users at xorp.org
    >>> http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users

    Joseph> _______________________________________________ Xorp-users
    Joseph> mailing list Xorp-users at xorp.org
    Joseph> http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users


From pavlin at icir.org  Fri Mar  2 15:56:47 2007
From: pavlin at icir.org (Pavlin Radoslavov)
Date: Fri, 02 Mar 2007 15:56:47 -0800
Subject: [Xorp-users] Removing unused test programs
Message-ID: <200703022356.l22Nulkx095943@possum.icir.org>

I am planning to remove the following test programs because they are
not needed anymore: fea/test_mfea, mld6igmp/test_mld6igmp and
pim/test_pim?

Does anyone use/need them?

Thanks,
Pavlin


From koippa at gmail.com  Fri Mar  2 22:20:39 2007
From: koippa at gmail.com (Kimmo Koivisto)
Date: Sat, 3 Mar 2007 08:20:39 +0200
Subject: [Xorp-users] xorp ospf endless loop problem?
In-Reply-To: <17879.1172678463@tigger.icir.org>
References: <17879.1172678463@tigger.icir.org>
Message-ID: <200703030820.39751.koippa@gmail.com>

On Wednesday 28 February 2007 18:01, Atanu Ghosh wrote:
> Hi,
>
> I was unable to reproduce the endless loop problem, however, I did find
> a problem when a router is restarted and it receives its own previously
> generated Network-LSA. Could you try the patch and see if the problem
> goes away?
>
> 	Atanu.
Hi

Thanks for the patch, I'll try to test it when I have the environment up and 
running again.

Regards
Kimmo


From agaviola at infoweapons.com  Tue Mar  6 05:56:24 2007
From: agaviola at infoweapons.com (Archimedes S. Gaviola)
Date: Tue, 6 Mar 2007 21:56:24 +0800
Subject: [Xorp-users] Some Questions on XORP
Message-ID: <010b01c75ff7$4a45fcd0$0b02030a@cebu.infoweapons.com>

To Whom It May Concerned:
 
Hi! I got some questions regarding routing module and functionalities in
XORP. 
 
1. Since XORP composed of standard routing protocols both unicast and
multicast, do you have a plan for interoperability testing with other
routing implementations?
2. I have read in the manual based on release 1.3
http://www.xorp.org/releases/1.3/docs/user_manual/user_manual.pdf that it
doesn't support for VLAN interfaces, do you have a plan to support it on the
next releases?
3. In PIM-SSM configuration, is there a way we can filter legitimate sources
to be allowed in joining a multicast group? Or filter lists of legitimate
hosts that wants to join a channel from querying IGMPv3 routers?
 
Thank you very much.
 
Sincerely Yours,
 
Archimedes S. Gaviola
Network Engineer
InfoWeapons Corporation
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20070306/0a1ac449/attachment.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 3353 bytes
Desc: not available
Url : http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20070306/0a1ac449/attachment.bin 

From a.greenhalgh at cs.ucl.ac.uk  Tue Mar  6 06:07:05 2007
From: a.greenhalgh at cs.ucl.ac.uk (Adam Greenhalgh)
Date: Tue, 6 Mar 2007 14:07:05 +0000
Subject: [Xorp-users] Some Questions on XORP
In-Reply-To: <010b01c75ff7$4a45fcd0$0b02030a@cebu.infoweapons.com>
References: <010b01c75ff7$4a45fcd0$0b02030a@cebu.infoweapons.com>
Message-ID: <4769af410703060607t2733e090lf377c395810dfdbb@mail.gmail.com>

Hi,

Some answers in line, I hope someone will correct me if I'm wrong.

Adam


On 3/6/07, Archimedes S. Gaviola <agaviola at infoweapons.com> wrote:
>
>
> To Whom It May Concerned:
>
> Hi! I got some questions regarding routing module and functionalities in
> XORP.
>
> 1. Since XORP composed of standard routing protocols both unicast and
> multicast, do you have a plan for interoperability testing with other
> routing implementations?

Yes, xorp has been through the UNH tests , paid for by vyatta, please
the test report here :

http://mailman.icsi.berkeley.edu/pipermail/xorp-users/2006-March/001137.html

> 2. I have read in the manual based on release 1.3
> http://www.xorp.org/releases/1.3/docs/user_manual/user_manual.pdf
> that it doesn't support for VLAN interfaces, do you have a plan to support
> it on the next releases?

Not in the 1.4 release, vlans are supported in the underlying os , I
think vyatta supports these, vyatta is based on the xorp suite.

> 3. In PIM-SSM configuration, is there a way we can filter legitimate sources
> to be allowed in joining a multicast group? Or filter lists of legitimate
> hosts that wants to join a channel from querying IGMPv3 routers?
>

sorry, personally I don't know. One of the others might.

Adam

> Thank you very much.
>
> Sincerely Yours,
>
> Archimedes S. Gaviola
> Network Engineer
> InfoWeapons Corporation
> _______________________________________________
> Xorp-users mailing list
> Xorp-users at xorp.org
> http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users
>
>
>


From pavlin at icir.org  Tue Mar  6 11:31:00 2007
From: pavlin at icir.org (Pavlin Radoslavov)
Date: Tue, 06 Mar 2007 11:31:00 -0800
Subject: [Xorp-users] Some Questions on XORP
In-Reply-To: Message from "Adam Greenhalgh" <a.greenhalgh@cs.ucl.ac.uk> 
	of "Tue, 06 Mar 2007 14:07:05 GMT."
	<4769af410703060607t2733e090lf377c395810dfdbb@mail.gmail.com> 
Message-ID: <200703061931.l26JV068039819@possum.icir.org>

> > 3. In PIM-SSM configuration, is there a way we can filter legitimate sources
> > to be allowed in joining a multicast group? Or filter lists of legitimate
> > hosts that wants to join a channel from querying IGMPv3 routers?
> >

No, currently it can't be done within XORP, but we should add
support for this. I just created a bugzilla entry so you can add
yourself to the CC list and get notified when it is implemented:

http://www.xorp.org/bugzilla/show_bug.cgi?id=695

Currently, the only mechanism that comes to mind is using firewall
rules (outside XORP) to allow (or block) the IGMPv3 Membership
Report messages from a specific set of hosts.

Note that such filtering can be applied only to IGMPv3/MLDv2, because
in IGMPv1,v2 and MLDv1 the hosts use Membership Report suppression.

Regards,
Pavlin


From dave at vyatta.com  Tue Mar  6 13:39:38 2007
From: dave at vyatta.com (Dave Roberts)
Date: Tue, 06 Mar 2007 13:39:38 -0800
Subject: [Xorp-users] Some Questions on XORP
In-Reply-To: <4769af410703060607t2733e090lf377c395810dfdbb@mail.gmail.com>
References: <010b01c75ff7$4a45fcd0$0b02030a@cebu.infoweapons.com>
	<4769af410703060607t2733e090lf377c395810dfdbb@mail.gmail.com>
Message-ID: <45EDDF9A.4050004@vyatta.com>

Just to follow up on what Adam wrote:

Adam Greenhalgh wrote:
>> 1. Since XORP composed of standard routing protocols both unicast and
>> multicast, do you have a plan for interoperability testing with other
>> routing implementations?
> 
> Yes, xorp has been through the UNH tests , paid for by vyatta, please
> the test report here :
> 
> http://mailman.icsi.berkeley.edu/pipermail/xorp-users/2006-March/001137.html

Just a quibble, but XORP has not be tested. Vyatta has. Vyatta 
incorporates XORP, and therefore by reference you should get a 
warm-fuzzy feeling that XORP would also pass, but according to the 
letter of our testing agreements with UNH it's improper to say that XORP 
has been tested at UNH.

>> 2. I have read in the manual based on release 1.3
>> http://www.xorp.org/releases/1.3/docs/user_manual/user_manual.pdf
>> that it doesn't support for VLAN interfaces, do you have a plan to support
>> it on the next releases?
> 
> Not in the 1.4 release, vlans are supported in the underlying os , I
> think vyatta supports these, vyatta is based on the xorp suite.

Vyatta does indeed support VLANs.

You can download the latest Vyatta Community Edition (VC2) at the Vyatta 
web site (www.vyatta.com).

Cheers,

-- Dave

-- 

Dave Roberts
Vice-President, Strategy and Marketing
Vyatta, Inc.
1 Waters Park Drive, Suite 160
San Mateo, CA 94403
Email: dave at vyatta.com
Direct: 650-350-3148

Welcome to the dawn of open-source networking...


From agaviola at infoweapons.com  Wed Mar  7 02:40:14 2007
From: agaviola at infoweapons.com (Archimedes S. Gaviola)
Date: Wed, 7 Mar 2007 18:40:14 +0800
Subject: [Xorp-users] Some Questions on XORP
In-Reply-To: <45EDDF9A.4050004@vyatta.com>
References: <010b01c75ff7$4a45fcd0$0b02030a@cebu.infoweapons.com>
	<4769af410703060607t2733e090lf377c395810dfdbb@mail.gmail.com>
	<45EDDF9A.4050004@vyatta.com>
Message-ID: <00f201c760a5$0cb11270$0b02030a@cebu.infoweapons.com>

Sirs,

Thanks for answering my concerns. Yes, I'll try using Vyatta too.

Sincerely Yours,

Archimedes S. Gaviola
Network Engineer
InfoWeapons Corporation 

-----Original Message-----
From: Dave Roberts [mailto:dave at vyatta.com] 
Sent: Wednesday, March 07, 2007 5:40 AM
To: Adam Greenhalgh
Cc: Archimedes S. Gaviola; xorp-users at xorp.org
Subject: Re: [Xorp-users] Some Questions on XORP

Just to follow up on what Adam wrote:

Adam Greenhalgh wrote:
>> 1. Since XORP composed of standard routing protocols both unicast and 
>> multicast, do you have a plan for interoperability testing with other 
>> routing implementations?
> 
> Yes, xorp has been through the UNH tests , paid for by vyatta, please 
> the test report here :
> 
> http://mailman.icsi.berkeley.edu/pipermail/xorp-users/2006-March/00113
> 7.html

Just a quibble, but XORP has not be tested. Vyatta has. Vyatta incorporates
XORP, and therefore by reference you should get a warm-fuzzy feeling that
XORP would also pass, but according to the letter of our testing agreements
with UNH it's improper to say that XORP has been tested at UNH.

>> 2. I have read in the manual based on release 1.3 
>> http://www.xorp.org/releases/1.3/docs/user_manual/user_manual.pdf
>> that it doesn't support for VLAN interfaces, do you have a plan to 
>> support it on the next releases?
> 
> Not in the 1.4 release, vlans are supported in the underlying os , I 
> think vyatta supports these, vyatta is based on the xorp suite.

Vyatta does indeed support VLANs.

You can download the latest Vyatta Community Edition (VC2) at the Vyatta web
site (www.vyatta.com).

Cheers,

-- Dave

-- 

Dave Roberts
Vice-President, Strategy and Marketing
Vyatta, Inc.
1 Waters Park Drive, Suite 160
San Mateo, CA 94403
Email: dave at vyatta.com
Direct: 650-350-3148

Welcome to the dawn of open-source networking...

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 3353 bytes
Desc: not available
Url : http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20070307/85a037ea/attachment.bin 

From agaviola at infoweapons.com  Wed Mar  7 02:48:52 2007
From: agaviola at infoweapons.com (Archimedes S. Gaviola)
Date: Wed, 7 Mar 2007 18:48:52 +0800
Subject: [Xorp-users] Some Questions on XORP
In-Reply-To: <200703061931.l26JV068039819@possum.icir.org>
References: Message from "Adam Greenhalgh" <a.greenhalgh@cs.ucl.ac.uk> of "Tue,
	06 Mar 2007 14:07:05 GMT."
	<4769af410703060607t2733e090lf377c395810dfdbb@mail.gmail.com>
	<200703061931.l26JV068039819@possum.icir.org>
Message-ID: <00fa01c760a6$439c1a90$0b02030a@cebu.infoweapons.com>

Pavlin,

Okay, thanks for your reply. I'll wait for this fucntionality to be
implemented. 

Sincerely Yours,

Archimedes S. Gaviola
Network Engineer
InfoWeapons Corporation

-----Original Message-----
From: Pavlin Radoslavov [mailto:pavlin at icir.org] 
Sent: Wednesday, March 07, 2007 3:31 AM
To: Adam Greenhalgh
Cc: Archimedes S. Gaviola; xorp-users at xorp.org
Subject: Re: [Xorp-users] Some Questions on XORP 

> > 3. In PIM-SSM configuration, is there a way we can filter legitimate 
> > sources to be allowed in joining a multicast group? Or filter lists 
> > of legitimate hosts that wants to join a channel from querying IGMPv3
routers?
> >

No, currently it can't be done within XORP, but we should add support for
this. I just created a bugzilla entry so you can add yourself to the CC list
and get notified when it is implemented:

http://www.xorp.org/bugzilla/show_bug.cgi?id=695

Currently, the only mechanism that comes to mind is using firewall rules
(outside XORP) to allow (or block) the IGMPv3 Membership Report messages
from a specific set of hosts.

Note that such filtering can be applied only to IGMPv3/MLDv2, because in
IGMPv1,v2 and MLDv1 the hosts use Membership Report suppression.

Regards,
Pavlin

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 3353 bytes
Desc: not available
Url : http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20070307/b7743742/attachment.bin 

From ashishkarpe at gmail.com  Wed Mar  7 13:34:10 2007
From: ashishkarpe at gmail.com (Ashish Karpe)
Date: Thu, 8 Mar 2007 03:04:10 +0530
Subject: [Xorp-users] doubt in Test suite !!!!
Message-ID: <f87e63a0703071334g2a8d6450s100792723673904@mail.gmail.com>

hi all ,
         according to test Pim suite pdf (available @ xorp's website )Basic
interoperability test setup is

TN1 ---------------------------- RUT ----------------- TR1
---------------------------- TN2

please tell following ip & mask are correct :

TN1 ip 10.0.0.2 Mask 255.255.255.0

RUP eth0 10.0.0.1  Mask  <http://255.255.255.0/>255.255.255.0   eth1
30.0.0.1 mask 255.0.0.0

TR1  eth0 30.0.0.2 mask 255.0.0.0 eth1 192.168.0.1 mask 255.255.255.0

TN2 192.168.0.2 mask 255.255.255.0


We have problem to decide  ip address of link between RUT & TR1 !! so please
tell us that ip address & masks mentioned above are right or not ?? Will
those ip address work for all tests mentioned in Test suite ?? if not please
suggest changes or new ips & masks to be used !!

Thank you,
Ashish
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20070308/96be55ce/attachment.html 

From pavlin at icir.org  Wed Mar  7 14:50:50 2007
From: pavlin at icir.org (Pavlin Radoslavov)
Date: Wed, 07 Mar 2007 14:50:50 -0800
Subject: [Xorp-users] doubt in Test suite !!!!
In-Reply-To: Message from "Ashish Karpe" <ashishkarpe@gmail.com> of "Thu,
	08 Mar 2007 03:04:10 +0530."
	<f87e63a0703071334g2a8d6450s100792723673904@mail.gmail.com> 
Message-ID: <200703072250.l27MooJo051033@possum.icir.org>

>          according to test Pim suite pdf (available @ xorp's website )Basic
> interoperability test setup is
> 
> TN1 ---------------------------- RUT ----------------- TR1
> ---------------------------- TN2
> 
> please tell following ip & mask are correct :
> 
> TN1 ip 10.0.0.2 Mask 255.255.255.0
> 
> RUP eth0 10.0.0.1  Mask  <http://255.255.255.0/>255.255.255.0   eth1
> 30.0.0.1 mask 255.0.0.0
> 
> TR1  eth0 30.0.0.2 mask 255.0.0.0 eth1 192.168.0.1 mask 255.255.255.0
> 
> TN2 192.168.0.2 mask 255.255.255.0
> 
> 
> We have problem to decide  ip address of link between RUT & TR1 !! so please
> tell us that ip address & masks mentioned above are right or not ?? Will
> those ip address work for all tests mentioned in Test suite ?? if not please
> suggest changes or new ips & masks to be used !!

Yes, those values should work.

In general, you can use any addressing on each of the subnets as
long as they are valid (e.g., each interface has unique IP address,
the subnet addresses are not overlapping, etc).

Regards,
Pavlin

> Thank you,
> Ashish
> _______________________________________________
> Xorp-users mailing list
> Xorp-users at xorp.org
> http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users


From moreauf at enseirb.fr  Thu Mar  8 08:47:02 2007
From: moreauf at enseirb.fr (moreauf)
Date: Thu, 8 Mar 2007 17:47:02 +0100
Subject: [Xorp-users] How configure a multicast static route with xorp_sh ?
Message-ID: <F8C24C81-D446-48F7-B067-377D76770401@enseirb.fr>

Hello, after reading the docs, I haven't find a solution.


my configuration :
----                                                       -----
|    |             ___                ___           |  V |
|    | ---------|      |-----------|      |--------|  L |
|    |             |__ |               |__ |           |  C |
----                 2                    3              ----
   1

1. A video streamer in multicast (172.17.0.1)
2. a xorp_router  (172.17.0.10 and 192.168.18.1)
3. a another xorp_router (192.168.18.2 and 192.168.17.1)
VLC is a client to read video streaming (192.168.18.1)

I search the xorp_sh command to configure router 2 and 3 with static  
multicast routing  .


Thanks,
Fabien


From pavlin at icir.org  Thu Mar  8 10:50:49 2007
From: pavlin at icir.org (Pavlin Radoslavov)
Date: Thu, 08 Mar 2007 10:50:49 -0800
Subject: [Xorp-users] How configure a multicast static route with
	xorp_sh ?
In-Reply-To: Message from moreauf <moreauf@enseirb.fr> of "Thu,
	08 Mar 2007 17:47:02 +0100."
	<F8C24C81-D446-48F7-B067-377D76770401@enseirb.fr> 
Message-ID: <200703081850.l28IonmK064242@possum.icir.org>

Note: in my examples below I assume all subnet mask lengths are /24.

> Hello, after reading the docs, I haven't find a solution.
> 
> 
> my configuration :
> ----                                                       -----
> |    |             ___                ___           |  V |
> |    | ---------|      |-----------|      |--------|  L |
> |    |             |__ |               |__ |           |  C |
> ----                 2                    3              ----
>    1
> 
> 1. A video streamer in multicast (172.17.0.1)
> 2. a xorp_router  (172.17.0.10 and 192.168.18.1)
> 3. a another xorp_router (192.168.18.2 and 192.168.17.1)
> VLC is a client to read video streaming (192.168.18.1)
                                           ~~~~~~~~~~~~
This address doesn't seem right. It should belong to the same subnet
as 192.168.17.1/24 (e.g., 192.168.17.2).

> I search the xorp_sh command to configure router 2 and 3 with static  
> multicast routing  .

The routes you need to add are:
(a) A route inside XORP2 how to reach the VLC subnet
   (192.168.17.0/24).
(b) A route inside XIRP3 how to reach the streamer's subnet
   (172.17.0.0/24).

Then the static configuration inside XORP2 will look like:

protocols {
    static {
        route 192.168.17.0/24 {
            next-hop: 192.168.18.2
        }
    }
}

Similarly, the static configuration inside XORP3 will look like:

protocols {
    static {
        route 172.17.0.0/24 {
            next-hop: 192.168.18.1
        }
    }
}

The above setup will add unicast static routes to the system. If you
have fib2mrib configured, then they will be used for multicast
purpose as well.
If you want to install static routes that will be used for multicast
purpose only, then replace "route" with "mrib-route".

Regards,
Pavlin


From agaviola at infoweapons.com  Fri Mar  9 04:47:28 2007
From: agaviola at infoweapons.com (Archimedes S. Gaviola)
Date: Fri, 9 Mar 2007 20:47:28 +0800
Subject: [Xorp-users] Some Questions on XORP
In-Reply-To: <200703061931.l26JV068039819@possum.icir.org>
References: Message from "Adam Greenhalgh" <a.greenhalgh@cs.ucl.ac.uk> of "Tue,
	06 Mar 2007 14:07:05 GMT."
	<4769af410703060607t2733e090lf377c395810dfdbb@mail.gmail.com>
	<200703061931.l26JV068039819@possum.icir.org>
Message-ID: <011a01c76249$2825d090$0b02030a@cebu.infoweapons.com>

Pavlin,

I have encountered some documents that are useful for multicast source
filtering http://www.ietf.org/rfc/rfc4604.txt?number=4604 and
http://www.ietf.org/rfc/rfc3678.txt?number=3678. I do hope this could help.

Thanks.

Sincerely Yours,

Archimedes S. Gaviola
Network Engineer
InfoWeapons Corporation 

-----Original Message-----
From: Pavlin Radoslavov [mailto:pavlin at icir.org] 
Sent: Wednesday, March 07, 2007 3:31 AM
To: Adam Greenhalgh
Cc: Archimedes S. Gaviola; xorp-users at xorp.org
Subject: Re: [Xorp-users] Some Questions on XORP 

> > 3. In PIM-SSM configuration, is there a way we can filter legitimate 
> > sources to be allowed in joining a multicast group? Or filter lists 
> > of legitimate hosts that wants to join a channel from querying IGMPv3
routers?
> >

No, currently it can't be done within XORP, but we should add support for
this. I just created a bugzilla entry so you can add yourself to the CC list
and get notified when it is implemented:

http://www.xorp.org/bugzilla/show_bug.cgi?id=695

Currently, the only mechanism that comes to mind is using firewall rules
(outside XORP) to allow (or block) the IGMPv3 Membership Report messages
from a specific set of hosts.

Note that such filtering can be applied only to IGMPv3/MLDv2, because in
IGMPv1,v2 and MLDv1 the hosts use Membership Report suppression.

Regards,
Pavlin

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 3353 bytes
Desc: not available
Url : http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20070309/108e0208/attachment.bin 

From pavlin at icir.org  Fri Mar  9 12:26:54 2007
From: pavlin at icir.org (Pavlin Radoslavov)
Date: Fri, 09 Mar 2007 12:26:54 -0800
Subject: [Xorp-users] Some Questions on XORP
In-Reply-To: Message from "Archimedes S. Gaviola" <agaviola@infoweapons.com> 
	of "Fri, 09 Mar 2007 20:47:28 +0800."
	<011a01c76249$2825d090$0b02030a@cebu.infoweapons.com> 
Message-ID: <200703092026.l29KQsl6075160@possum.icir.org>

> I have encountered some documents that are useful for multicast source
> filtering http://www.ietf.org/rfc/rfc4604.txt?number=4604 and
> http://www.ietf.org/rfc/rfc3678.txt?number=3678. I do hope this could help.

Thank you for the info. I added it to the Bugzilla entry.

Regards,
Pavlin


From ashishkarpe at gmail.com  Sun Mar 11 15:55:34 2007
From: ashishkarpe at gmail.com (Ashish Karpe)
Date: Mon, 12 Mar 2007 04:25:34 +0530
Subject: [Xorp-users] Want test result of PIM-BIDIR protocol !!!
Message-ID: <f87e63a0703111555u2932b404yd7c9bd903bded94@mail.gmail.com>

hi all,

do anybody have comparative test results of PIM-SM & PIM-BIDIR ?? can u
share it ?? or else from where can i get those ??

Thanking in Anticipation
-Ashish Karpe
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20070312/54794fc2/attachment.html 

From pavlin at icir.org  Mon Mar 12 11:22:29 2007
From: pavlin at icir.org (Pavlin Radoslavov)
Date: Mon, 12 Mar 2007 11:22:29 -0700
Subject: [Xorp-users] Want test result of PIM-BIDIR protocol !!!
In-Reply-To: Message from "Ashish Karpe" <ashishkarpe@gmail.com> of "Mon,
	12 Mar 2007 04:25:34 +0530."
	<f87e63a0703111555u2932b404yd7c9bd903bded94@mail.gmail.com> 
Message-ID: <200703121822.l2CIMT6X002467@possum.icir.org>

> do anybody have comparative test results of PIM-SM & PIM-BIDIR ?? can u
> share it ?? or else from where can i get those ??

Can you be more specific what you mean by "comparative test
results".

I haven't heard about a detailed study targeting both PIM-SM and
Bidir-PIM (at least I don't remember anyting beint sent to the
relevant mailing lists).
So there is a window of opportunity for you for such study after you
complete your Bidir-PIM implementation :)

Regards,
Pavlin


From moreauf at enseirb.fr  Tue Mar 13 09:21:47 2007
From: moreauf at enseirb.fr (moreauf)
Date: Tue, 13 Mar 2007 17:21:47 +0100
Subject: [Xorp-users] How configure a multicast static route with
	xorp_sh ?
In-Reply-To: <200703081850.l28IonmK064242@possum.icir.org>
References: <200703081850.l28IonmK064242@possum.icir.org>
Message-ID: <39DF2403-10BB-425C-89E5-F81E74100135@enseirb.fr>

After many try of the proposed solution and some variation, routing  
doesn't work if I don't activate PIM-SM too.
But I search to route multicast stream with only, a static routing  
beetween router 2 and 3,  IGMP beetween router 1 and 2 and IGMP  
beetween 3 and 4.

Thanks ,
Fabien

Le 8 mars 07 ? 19:50, Pavlin Radoslavov a ?crit :

> Note: in my examples below I assume all subnet mask lengths are /24.
>
>> Hello, after reading the docs, I haven't find a solution.
>>
>>
>> my configuration :
>> ----                                                       -----
>> |    |             ___                ___           |  V |
>> |    | ---------|      |-----------|      |--------|  L |
>> |    |             |__ |               |__ |           |  C |
>> ----                 2                    3              ----
>>    1
>>
>> 1. A video streamer in multicast (172.17.0.1)
>> 2. a xorp_router  (172.17.0.10 and 192.168.18.1)
>> 3. a another xorp_router (192.168.18.2 and 192.168.17.1)
>> VLC is a client to read video streaming (192.168.18.1)
>                                            ~~~~~~~~~~~~
> This address doesn't seem right. It should belong to the same subnet
> as 192.168.17.1/24 (e.g., 192.168.17.2).
effectively , I write my case with this syntax error.
>
>> I search the xorp_sh command to configure router 2 and 3 with static
>> multicast routing  .
>
> The routes you need to add are:
> (a) A route inside XORP2 how to reach the VLC subnet
>    (192.168.17.0/24).
> (b) A route inside XIRP3 how to reach the streamer's subnet
>    (172.17.0.0/24).
>
> Then the static configuration inside XORP2 will look like:
>
> protocols {
>     static {
>         route 192.168.17.0/24 {
>             next-hop: 192.168.18.2
>         }
>     }
> }
>
> Similarly, the static configuration inside XORP3 will look like:
>
> protocols {
>     static {
>         route 172.17.0.0/24 {
>             next-hop: 192.168.18.1
>         }
>     }
> }
>
> The above setup will add unicast static routes to the system. If you
> have fib2mrib configured, then they will be used for multicast
> purpose as well.
> If you want to install static routes that will be used for multicast
> purpose only, then replace "route" with "mrib-route".
>
> Regards,
> Pavlin



From pavlin at icir.org  Tue Mar 13 09:37:12 2007
From: pavlin at icir.org (Pavlin Radoslavov)
Date: Tue, 13 Mar 2007 09:37:12 -0700
Subject: [Xorp-users] How configure a multicast static route with
	xorp_sh ?
In-Reply-To: Message from moreauf <moreauf@enseirb.fr> of "Tue,
	13 Mar 2007 17:21:47 BST."
	<39DF2403-10BB-425C-89E5-F81E74100135@enseirb.fr> 
Message-ID: <200703131637.l2DGbCg8011928@possum.icir.org>

> After many try of the proposed solution and some variation, routing  
> doesn't work if I don't activate PIM-SM too.
> But I search to route multicast stream with only, a static routing  
> beetween router 2 and 3,  IGMP beetween router 1 and 2 and IGMP  
> beetween 3 and 4.

You MUST activate PIM-SM (or any other multicast routing protocol)
if you want multicast routing to work. The purpose of IGMP is to
inform PIM-SM about multicast members.
Unlike unicast, there is no such thing as static multicast routing
for a variety of reasons.
The "mrib-route" XORP configuration is about configuring
Reverse-Path Forwarding information that is used by PIM-SM.

Regards,
Pavlin


> Thanks ,
> Fabien
> 
> Le 8 mars 07 ? 19:50, Pavlin Radoslavov a ?crit :
> 
> > Note: in my examples below I assume all subnet mask lengths are /24.
> >
> >> Hello, after reading the docs, I haven't find a solution.
> >>
> >>
> >> my configuration :
> >> ----                                                       -----
> >> |    |             ___                ___           |  V |
> >> |    | ---------|      |-----------|      |--------|  L |
> >> |    |             |__ |               |__ |           |  C |
> >> ----                 2                    3              ----
> >>    1
> >>
> >> 1. A video streamer in multicast (172.17.0.1)
> >> 2. a xorp_router  (172.17.0.10 and 192.168.18.1)
> >> 3. a another xorp_router (192.168.18.2 and 192.168.17.1)
> >> VLC is a client to read video streaming (192.168.18.1)
> >                                            ~~~~~~~~~~~~
> > This address doesn't seem right. It should belong to the same subnet
> > as 192.168.17.1/24 (e.g., 192.168.17.2).
> effectively , I write my case with this syntax error.
> >
> >> I search the xorp_sh command to configure router 2 and 3 with static
> >> multicast routing  .
> >
> > The routes you need to add are:
> > (a) A route inside XORP2 how to reach the VLC subnet
> >    (192.168.17.0/24).
> > (b) A route inside XIRP3 how to reach the streamer's subnet
> >    (172.17.0.0/24).
> >
> > Then the static configuration inside XORP2 will look like:
> >
> > protocols {
> >     static {
> >         route 192.168.17.0/24 {
> >             next-hop: 192.168.18.2
> >         }
> >     }
> > }
> >
> > Similarly, the static configuration inside XORP3 will look like:
> >
> > protocols {
> >     static {
> >         route 172.17.0.0/24 {
> >             next-hop: 192.168.18.1
> >         }
> >     }
> > }
> >
> > The above setup will add unicast static routes to the system. If you
> > have fib2mrib configured, then they will be used for multicast
> > purpose as well.
> > If you want to install static routes that will be used for multicast
> > purpose only, then replace "route" with "mrib-route".
> >
> > Regards,
> > Pavlin
> 
> 
> _______________________________________________
> Xorp-users mailing list
> Xorp-users at xorp.org
> http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users


From ez201 at mail2.selye.sk  Wed Mar 14 06:59:21 2007
From: ez201 at mail2.selye.sk (Elzer Zoltan)
Date: Wed, 14 Mar 2007 14:59:21 +0100
Subject: [Xorp-users] Cannot start vif
Message-ID: <20070314135921.21015.qmail@selye.sk>

Hello
I am new in xorp. I would like to try th multicast forwarding, but a problem 
occured.
 - I use live cd version 1.4
 - The network layout:  Host1 --- Xorp router --- Host2
 - I succeeded in setting up unicast forwarding between the two host, but 
when I tried to set multicast plumbing, or adding new protocol (IGMP, PIM), 
after commit I  got the following error: 102 Command failed Cannot start vif 
rl0: underlying vif is not UP
I tried it on all interfaces an on different machines.
Please help me, how can I resolve this problem. Thanks. 

                                                   Turbo


From lleandro at gmail.com  Wed Mar 14 07:40:48 2007
From: lleandro at gmail.com (Leandro Castanheira)
Date: Wed, 14 Mar 2007 11:40:48 -0300
Subject: [Xorp-users] Problems with multicast routes
Message-ID: <eddbd9c00703140740u5827e571se5a2995e96720bc8@mail.gmail.com>

Hi,

My network is like this:


0000         0000         0000            0000
0 1 0 ------- 0 2 0 ------- 0 3 0 --------- 0 4 0
0000         0000         0000            0000
                                   |                  |
                                   |                  |
                                0000            0000
                                0 5 0            0 6 0
                                0000            0000


1) 200.17.77.5 -> server/client VLC
2) 200.17.77.2 - 192.168.0.1 -> XORP router
3) 192.168.0.125 - 192.168.1.1 -> XORP router and server/client VLC
4) 192.168.1.3 - 192.168.2.1 -> XORP router and server/client VLC
5) 192.168.1.2 -> server/client VLC
6) 192.168.2.2 -> server/client VLC

Well,
If I try to stream from 5 and receieve in 6 - ok
If I try to stream from 6 and receive in 5 - ok
If I try to stream from 3 and receive in 1 - ok
But if I try to stream from 5 and receive in 1 - it doesn't work
and if I try to stream from 1 and receive in 3, 5 or 6 - it doesn't work
But if I close xorp in 3 I can stram from 1 and receive in 3

What can I do to fix it?

Thanks,
Leandro

My config.boot for 2, 3 and 4 are:

2)
/*XORP Configuration File*/
interfaces {
    interface eth0 {
        description: "Ethernet"
        disable: false
        vif eth0 {
                disable: false
                address 200.17.77.2 {
                        prefix-length: 24
                        broadcast: 200.17.77.255
                        disable: false
                }
        }
    }
    interface eth1 {
        description: "Ethernet"
        disable: false
        vif eth1 {
                disable: false
                address 192.168.0.1 {
                        prefix-length: 24
                        broadcast: 192.168.0.255
                        disable: false
                }
         }
    }
    interface lo {
        description: "Loopback interface"
        vif lo {
        }
    }
}
fea{
   unicast-forwarding4 {
        disable: false
    }

 }
protocols {
   static {
   route 192.168.1.0/24 {
        next-hop: 192.168.0.125
        metric: 1
   }
/*   mrib-route 192.168.2.0/16 {
        next-hop: 192.168.2.1
        metric: 1
   }*/
}
}

plumbing {
    mfea4 {
        disable: false
        interface eth0 {
            vif eth0 {
                disable: false
            }
        }

        interface eth1 {
            vif eth1 {
                disable: false
            }
        }
        interface register_vif {
            vif register_vif {
                /* Note: this vif should be always enabled */
                disable: false
            }
        }
        traceoptions {
            flag all {
                disable: false
            }
        }
    }
 }
protocols {
    igmp {
        disable: false
        interface eth0 {
            vif eth0 {
                disable: false
                /* version: 2 */
                /* enable-ip-router-alert-option-check: false */
                /* query-interval: 125 */
                /* query-last-member-interval: 1 */
                /* query-response-interval: 10 */
                /* robust-count: 2 */
            }
        }
        interface eth1 {
            vif eth1 {
                disable: false
                /* version: 2 */
                /* enable-ip-router-alert-option-check: false */
                /* query-interval: 125 */
                /* query-last-member-interval: 1 */
                /* query-response-interval: 10 */
                /* robust-count: 2 */
            }
        }
        traceoptions {
            flag all {
                disable: false
            }
        }
    }
}
protocols {
    pimsm4 {
        disable: false
        interface eth0 {
            vif eth0 {
                disable: false
                /* enable-ip-router-alert-option-check: false */
                /* dr-priority: 1 */
                /* hello-period: 30 */
                /* hello-triggered-delay: 5 */
                /* alternative-subnet 10.40.0.0/16 */
            }
        }
        interface eth1 {
            vif eth1 {
                disable: false
                /* enable-ip-router-alert-option-check: false */
                /* dr-priority: 1 */
                /* hello-period: 30 */
                /* hello-triggered-delay: 5 */
                /* alternative-subnet 10.40.0.0/16 */
            }
        }
        interface register_vif {
            vif register_vif {
                /* Note: this vif should be always enabled */
                disable: false
            }
        }

        bootstrap {
            disable: false
            cand-bsr {
                scope-zone 224.0.0.0/4 {
                    /* is-scope-zone: false */
                    cand-bsr-by-vif-name: "eth1"
                    /* cand-bsr-by-vif-addr: 10.10.10.10 */
                    /* bsr-priority: 1 */
                    /* hash-mask-len: 30 */
              }
            }

            cand-rp {
                group-prefix 224.0.0.0/4 {
                    /* is-scope-zone: false */
                    cand-rp-by-vif-name: "eth1"
                    /* cand-rp-by-vif-addr: 10.10.10.10 */
                    /* rp-priority: 192 */
                    /* rp-holdtime: 150 */
              }
            }
        }

        switch-to-spt-threshold {
            /* approx. 1K bytes/s (10Kbps) threshold */
            disable: false
            interval: 100
            bytes: 102400
        }

        traceoptions {
            flag all {
                disable: false
            }
        }
    }
}
-----------------------------------------------
3)
/*XORP Configuration File*/
interfaces {
    interface eth0 {
        description: "Ethernet"
        disable: false
        vif eth0 {
                disable: false
                address 192.168.1.1 {
                        prefix-length: 24
                        broadcast: 192.168.1.255
                        disable: false
                }
        }
    }
    interface eth1 {
        description: "Ethernet"
        disable: false
        vif eth1 {
                disable: false
                address 192.168.0.125 {
                        prefix-length: 24
                        broadcast: 192.168.0.255
                        disable: false
                }
         }
    }
    interface lo {
        description: "Loopback interface"
        vif lo {
        }
    }
}
fea{
   unicast-forwarding4 {
        disable: false
    }

 }
protocols {
   static {
    route 200.17.77.0/24 {
        next-hop: 192.168.0.1
        metric: 1
    }
    route 191.168.2.0/24 {
        next-hop: 192.168.1.3
                metric: 1
        }

    /*mrib-route 10.20.0.0/16 {
        next-hop: 10.10.10.30
            metric: 1
    }*/
}
}

plumbing {
    mfea4 {
        disable: false
        interface eth0 {
            vif eth0 {
                disable: false
            }
        }

        interface eth1 {
            vif eth1 {
                disable: false
            }
        }
        interface register_vif {
            vif register_vif {
                /* Note: this vif should be always enabled */
                disable: false
            }
        }
        traceoptions {
            flag all {
                disable: false
            }
        }
    }
 }
protocols {
    igmp {
        disable: false
        interface eth0 {
            vif eth0 {
                disable: false
                /* version: 2 */
                /* enable-ip-router-alert-option-check: false */
                /* query-interval: 125 */
                /* query-last-member-interval: 1 */
                /* query-response-interval: 10 */
                /* robust-count: 2 */
            }
        }
        interface eth1 {
            vif eth1 {
                disable: false
                /* version: 2 */
                /* enable-ip-router-alert-option-check: false */
                /* query-interval: 125 */
                /* query-last-member-interval: 1 */
                /* query-response-interval: 10 */
                /* robust-count: 2 */
            }
        }
        traceoptions {
            flag all {
                disable: false
            }
        }
    }
}
protocols {
    pimsm4 {
        disable: false
        interface eth0 {
            vif eth0 {
                disable: false
                /* enable-ip-router-alert-option-check: false */
                /* dr-priority: 1 */
                /* hello-period: 30 */
                /* hello-triggered-delay: 5 */
                /* alternative-subnet 10.40.0.0/16 */
            }
        }
        interface eth1 {
            vif eth1 {
                disable: false
                /* enable-ip-router-alert-option-check: false */
                /* dr-priority: 1 */
                /* hello-period: 30 */
                /* hello-triggered-delay: 5 */
                /* alternative-subnet 10.40.0.0/16 */
            }
        }
        interface register_vif {
            vif register_vif {
                /* Note: this vif should be always enabled */
                disable: false
            }
        }

        /*static-rps {
            rp 10.60.0.1 {
                group-prefix 224.0.0.0/4 {
                    /* rp-priority: 192 */
                    /* hash-mask-len: 30 */
        /*      }
            }
        }
*/
        bootstrap {
            disable: false
            cand-bsr {
                scope-zone 224.0.0.0/4 {
                    /* is-scope-zone: false */
                 cand-bsr-by-vif-name: "eth1"
                    /* cand-bsr-by-vif-addr: 10.10.10.10 */
                    /* bsr-priority: 1 */
                    /* hash-mask-len: 30 */
              }
            }
            cand-rp {
                group-prefix 224.0.0.0/4 {
                    /* is-scope-zone: false */
                    cand-rp-by-vif-name: "eth1"
                    /* cand-rp-by-vif-addr: 10.10.10.10 */
                    /* rp-priority: 192 */
                    /* rp-holdtime: 150 */
              }
            }
        }

        switch-to-spt-threshold {
            /* approx. 1K bytes/s (10Kbps) threshold */
            disable: false
            interval: 100
            bytes: 102400
        }

        traceoptions {
            flag all {
                disable: false
            }
        }
    }
}
-------------------------------------------
4)


/*XORP Configuration File*/
interfaces {
    interface eth0 {
        description: "Ethernet"
        disable: false
        vif eth0 {
                disable: false
                address 192.168.2.1 {
                        prefix-length: 24
                        broadcast: 192.168.2.255
                        disable: false
                }
        }
    }
    interface eth1 {
        description: "Ethernet"
        disable: false
        vif eth1 {
                disable: false
                address 192.168.1.3 {
                        prefix-length: 24
                        broadcast: 192.168.1.255
                        disable: false
                }
         }
    }
    interface lo {
        description: "Loopback interface"
        vif lo {
        }
    }
}
fea{
   unicast-forwarding4 {
        disable: false
    }

 }
protocols {
   static {
    route 192.168.1.0/24 {
        next-hop: 192.168.1.1
        metric: 1
    }
    /*mrib-route 10.20.0.0/16 {
        next-hop: 10.10.10.30
            metric: 1
    }*/
}
}

plumbing {
    mfea4 {
        disable: false
        interface eth0 {
            vif eth0 {
                disable: false
            }
        }

        interface eth1 {
            vif eth1 {
                disable: false
            }
        }
        interface register_vif {
            vif register_vif {
                /* Note: this vif should be always enabled */
                disable: false
            }
        }
        traceoptions {
            flag all {
                disable: false
            }
        }
    }
 }
protocols {
    igmp {
        disable: false
        interface eth0 {
            vif eth0 {
                disable: false
                /* version: 2 */
                /* enable-ip-router-alert-option-check: false */
                /* query-interval: 125 */
                /* query-last-member-interval: 1 */
                /* query-response-interval: 10 */
                /* robust-count: 2 */
            }
        }
        interface eth1 {
            vif eth1 {
                disable: false
                /* version: 2 */
                /* enable-ip-router-alert-option-check: false */
                /* query-interval: 125 */
                /* query-last-member-interval: 1 */
                /* query-response-interval: 10 */
                /* robust-count: 2 */
            }
        }
        traceoptions {
            flag all {
                disable: false
            }
        }
    }
}
protocols {
    pimsm4 {
        disable: false
        interface eth0 {
            vif eth0 {
                disable: false
                /* enable-ip-router-alert-option-check: false */
                /* dr-priority: 1 */
                /* hello-period: 30 */
                /* hello-triggered-delay: 5 */
                /* alternative-subnet 10.40.0.0/16 */
            }
        }
        interface eth1 {
            vif eth1 {
                disable: false
                /* enable-ip-router-alert-option-check: false */
                /* dr-priority: 1 */
                /* hello-period: 30 */
                /* hello-triggered-delay: 5 */
                /* alternative-subnet 10.40.0.0/16 */
            }
        }
        interface register_vif {
            vif register_vif {
                /* Note: this vif should be always enabled */
                disable: false
            }
        }

        /*static-rps {
            rp 10.60.0.1 {
                group-prefix 224.0.0.0/4 {
                    /* rp-priority: 192 */
                    /* hash-mask-len: 30 */
        /*      }
            }
        }
*/
        bootstrap {
            disable: false
            cand-bsr {
                scope-zone 224.0.0.0/4 {
                    /* is-scope-zone: false */
                 cand-bsr-by-vif-name: "eth1"
                    /* cand-bsr-by-vif-addr: 10.10.10.10 */
                    /* bsr-priority: 1 */
                    /* hash-mask-len: 30 */
              }
            }
            cand-rp {
                group-prefix 224.0.0.0/4 {
                    /* is-scope-zone: false */
                    cand-rp-by-vif-name: "eth1"
                    /* cand-rp-by-vif-addr: 10.10.10.10 */
                    /* rp-priority: 192 */
                    /* rp-holdtime: 150 */
              }
            }
        }

        switch-to-spt-threshold {
            /* approx. 1K bytes/s (10Kbps) threshold */
            disable: false
            interval: 100
            bytes: 102400
        }

        traceoptions {
            flag all {
                disable: false
            }
        }
    }
}
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20070314/9ebcfa3a/attachment-0001.html 

From pavlin at icir.org  Wed Mar 14 11:17:42 2007
From: pavlin at icir.org (Pavlin Radoslavov)
Date: Wed, 14 Mar 2007 11:17:42 -0700
Subject: [Xorp-users] Cannot start vif
In-Reply-To: Message from "Elzer Zoltan" <ez201@mail2.selye.sk> of "Wed,
	14 Mar 2007 14:59:21 BST." <20070314135921.21015.qmail@selye.sk> 
Message-ID: <200703141817.l2EIHgBN051637@possum.icir.org>

> I am new in xorp. I would like to try th multicast forwarding, but a problem 
> occured.
>  - I use live cd version 1.4
           ~~~~~~~~~~~~~~~~~~~
This has to be 1.4-RC (Release Candidate), because the final 1.4
version is not released yet.

>  - The network layout:  Host1 --- Xorp router --- Host2
>  - I succeeded in setting up unicast forwarding between the two host, but 
> when I tried to set multicast plumbing, or adding new protocol (IGMP, PIM), 
> after commit I  got the following error: 102 Command failed Cannot start vif 
> rl0: underlying vif is not UP
> I tried it on all interfaces an on different machines.
> Please help me, how can I resolve this problem. Thanks. 

Can you send your configuration file.
Also, did you configure/enable rl0 in the "mfea4" section as well.
Finally, is "rl0" connected to the network.

Regards,
Pavlin


From pavlin at icir.org  Wed Mar 14 11:41:03 2007
From: pavlin at icir.org (Pavlin Radoslavov)
Date: Wed, 14 Mar 2007 11:41:03 -0700
Subject: [Xorp-users] Problems with multicast routes
In-Reply-To: Message from "Leandro Castanheira" <lleandro@gmail.com> of "Wed,
	14 Mar 2007 11:40:48 -0300."
	<eddbd9c00703140740u5827e571se5a2995e96720bc8@mail.gmail.com> 
Message-ID: <200703141841.l2EIf3h2051891@possum.icir.org>

> My network is like this:
> 
> 
> 0000         0000         0000            0000
> 0 1 0 ------- 0 2 0 ------- 0 3 0 --------- 0 4 0
> 0000         0000         0000            0000
>                                    |                  |
>                                    |                  |
>                                 0000            0000
>                                 0 5 0            0 6 0
>                                 0000            0000
> 
> 
> 1) 200.17.77.5 -> server/client VLC
> 2) 200.17.77.2 - 192.168.0.1 -> XORP router
> 3) 192.168.0.125 - 192.168.1.1 -> XORP router and server/client VLC
> 4) 192.168.1.3 - 192.168.2.1 -> XORP router and server/client VLC
> 5) 192.168.1.2 -> server/client VLC
> 6) 192.168.2.2 -> server/client VLC
> 
> Well,
> If I try to stream from 5 and receieve in 6 - ok
> If I try to stream from 6 and receive in 5 - ok
> If I try to stream from 3 and receive in 1 - ok
> But if I try to stream from 5 and receive in 1 - it doesn't work
> and if I try to stream from 1 and receive in 3, 5 or 6 - it doesn't work
> But if I close xorp in 3 I can stram from 1 and receive in 3
> 
> What can I do to fix it?

Leandro,

You need to apply the following fixes to your configuration:

* Add a static route in (2) to 192.168.2.0/24

* Add a static route in (4) to 192.168.0.0/24 and 200.17.77.0/24

* Remove a static route in (4) to directly connected subnet
  192.168.1.0/24

* Configure the fib2mrib module:

protocols {
    fib2mrib {
        disable: false
    }
}

Also, it seems to be using the Bootstrap mechanism to propagate the
Cand-RP set. You should be aware that on startup it might take up to
1-3 minutes or so until the Cand-RP set is propagated and converged
across your domain, and in the mean time the multicast forwarding
might not work. For testing purpose I'd recommend to use a single
static RP, because it is easier to debug.
E.g., remove all "bootstrap" configuration sections and replace them
with the following static RP configuration (instead of 192.168.1.1
you can choose any of the IP addresses of your XORP routers):

        static-rps {
            rp 192.168.1.1 {
                group-prefix 224.0.0.0/4 {
                    /* rp-priority: 192 */
                    /* hash-mask-len: 30 */
                }
            }
        }

After you get it working with static RP you can switch back to the
Bootstrap mechanism.

Regards,
Pavlin

> 
> Thanks,
> Leandro
> 
> My config.boot for 2, 3 and 4 are:
> 
> 2)
> /*XORP Configuration File*/
> interfaces {
>     interface eth0 {
>         description: "Ethernet"
>         disable: false
>         vif eth0 {
>                 disable: false
>                 address 200.17.77.2 {
>                         prefix-length: 24
>                         broadcast: 200.17.77.255
>                         disable: false
>                 }
>         }
>     }
>     interface eth1 {
>         description: "Ethernet"
>         disable: false
>         vif eth1 {
>                 disable: false
>                 address 192.168.0.1 {
>                         prefix-length: 24
>                         broadcast: 192.168.0.255
>                         disable: false
>                 }
>          }
>     }
>     interface lo {
>         description: "Loopback interface"
>         vif lo {
>         }
>     }
> }
> fea{
>    unicast-forwarding4 {
>         disable: false
>     }
> 
>  }
> protocols {
>    static {
>    route 192.168.1.0/24 {
>         next-hop: 192.168.0.125
>         metric: 1
>    }
> /*   mrib-route 192.168.2.0/16 {
>         next-hop: 192.168.2.1
>         metric: 1
>    }*/
> }
> }
> 
> plumbing {
>     mfea4 {
>         disable: false
>         interface eth0 {
>             vif eth0 {
>                 disable: false
>             }
>         }
> 
>         interface eth1 {
>             vif eth1 {
>                 disable: false
>             }
>         }
>         interface register_vif {
>             vif register_vif {
>                 /* Note: this vif should be always enabled */
>                 disable: false
>             }
>         }
>         traceoptions {
>             flag all {
>                 disable: false
>             }
>         }
>     }
>  }
> protocols {
>     igmp {
>         disable: false
>         interface eth0 {
>             vif eth0 {
>                 disable: false
>                 /* version: 2 */
>                 /* enable-ip-router-alert-option-check: false */
>                 /* query-interval: 125 */
>                 /* query-last-member-interval: 1 */
>                 /* query-response-interval: 10 */
>                 /* robust-count: 2 */
>             }
>         }
>         interface eth1 {
>             vif eth1 {
>                 disable: false
>                 /* version: 2 */
>                 /* enable-ip-router-alert-option-check: false */
>                 /* query-interval: 125 */
>                 /* query-last-member-interval: 1 */
>                 /* query-response-interval: 10 */
>                 /* robust-count: 2 */
>             }
>         }
>         traceoptions {
>             flag all {
>                 disable: false
>             }
>         }
>     }
> }
> protocols {
>     pimsm4 {
>         disable: false
>         interface eth0 {
>             vif eth0 {
>                 disable: false
>                 /* enable-ip-router-alert-option-check: false */
>                 /* dr-priority: 1 */
>                 /* hello-period: 30 */
>                 /* hello-triggered-delay: 5 */
>                 /* alternative-subnet 10.40.0.0/16 */
>             }
>         }
>         interface eth1 {
>             vif eth1 {
>                 disable: false
>                 /* enable-ip-router-alert-option-check: false */
>                 /* dr-priority: 1 */
>                 /* hello-period: 30 */
>                 /* hello-triggered-delay: 5 */
>                 /* alternative-subnet 10.40.0.0/16 */
>             }
>         }
>         interface register_vif {
>             vif register_vif {
>                 /* Note: this vif should be always enabled */
>                 disable: false
>             }
>         }
> 
>         bootstrap {
>             disable: false
>             cand-bsr {
>                 scope-zone 224.0.0.0/4 {
>                     /* is-scope-zone: false */
>                     cand-bsr-by-vif-name: "eth1"
>                     /* cand-bsr-by-vif-addr: 10.10.10.10 */
>                     /* bsr-priority: 1 */
>                     /* hash-mask-len: 30 */
>               }
>             }
> 
>             cand-rp {
>                 group-prefix 224.0.0.0/4 {
>                     /* is-scope-zone: false */
>                     cand-rp-by-vif-name: "eth1"
>                     /* cand-rp-by-vif-addr: 10.10.10.10 */
>                     /* rp-priority: 192 */
>                     /* rp-holdtime: 150 */
>               }
>             }
>         }
> 
>         switch-to-spt-threshold {
>             /* approx. 1K bytes/s (10Kbps) threshold */
>             disable: false
>             interval: 100
>             bytes: 102400
>         }
> 
>         traceoptions {
>             flag all {
>                 disable: false
>             }
>         }
>     }
> }
> -----------------------------------------------
> 3)
> /*XORP Configuration File*/
> interfaces {
>     interface eth0 {
>         description: "Ethernet"
>         disable: false
>         vif eth0 {
>                 disable: false
>                 address 192.168.1.1 {
>                         prefix-length: 24
>                         broadcast: 192.168.1.255
>                         disable: false
>                 }
>         }
>     }
>     interface eth1 {
>         description: "Ethernet"
>         disable: false
>         vif eth1 {
>                 disable: false
>                 address 192.168.0.125 {
>                         prefix-length: 24
>                         broadcast: 192.168.0.255
>                         disable: false
>                 }
>          }
>     }
>     interface lo {
>         description: "Loopback interface"
>         vif lo {
>         }
>     }
> }
> fea{
>    unicast-forwarding4 {
>         disable: false
>     }
> 
>  }
> protocols {
>    static {
>     route 200.17.77.0/24 {
>         next-hop: 192.168.0.1
>         metric: 1
>     }
>     route 191.168.2.0/24 {
>         next-hop: 192.168.1.3
>                 metric: 1
>         }
> 
>     /*mrib-route 10.20.0.0/16 {
>         next-hop: 10.10.10.30
>             metric: 1
>     }*/
> }
> }
> 
> plumbing {
>     mfea4 {
>         disable: false
>         interface eth0 {
>             vif eth0 {
>                 disable: false
>             }
>         }
> 
>         interface eth1 {
>             vif eth1 {
>                 disable: false
>             }
>         }
>         interface register_vif {
>             vif register_vif {
>                 /* Note: this vif should be always enabled */
>                 disable: false
>             }
>         }
>         traceoptions {
>             flag all {
>                 disable: false
>             }
>         }
>     }
>  }
> protocols {
>     igmp {
>         disable: false
>         interface eth0 {
>             vif eth0 {
>                 disable: false
>                 /* version: 2 */
>                 /* enable-ip-router-alert-option-check: false */
>                 /* query-interval: 125 */
>                 /* query-last-member-interval: 1 */
>                 /* query-response-interval: 10 */
>                 /* robust-count: 2 */
>             }
>         }
>         interface eth1 {
>             vif eth1 {
>                 disable: false
>                 /* version: 2 */
>                 /* enable-ip-router-alert-option-check: false */
>                 /* query-interval: 125 */
>                 /* query-last-member-interval: 1 */
>                 /* query-response-interval: 10 */
>                 /* robust-count: 2 */
>             }
>         }
>         traceoptions {
>             flag all {
>                 disable: false
>             }
>         }
>     }
> }
> protocols {
>     pimsm4 {
>         disable: false
>         interface eth0 {
>             vif eth0 {
>                 disable: false
>                 /* enable-ip-router-alert-option-check: false */
>                 /* dr-priority: 1 */
>                 /* hello-period: 30 */
>                 /* hello-triggered-delay: 5 */
>                 /* alternative-subnet 10.40.0.0/16 */
>             }
>         }
>         interface eth1 {
>             vif eth1 {
>                 disable: false
>                 /* enable-ip-router-alert-option-check: false */
>                 /* dr-priority: 1 */
>                 /* hello-period: 30 */
>                 /* hello-triggered-delay: 5 */
>                 /* alternative-subnet 10.40.0.0/16 */
>             }
>         }
>         interface register_vif {
>             vif register_vif {
>                 /* Note: this vif should be always enabled */
>                 disable: false
>             }
>         }
> 
>         /*static-rps {
>             rp 10.60.0.1 {
>                 group-prefix 224.0.0.0/4 {
>                     /* rp-priority: 192 */
>                     /* hash-mask-len: 30 */
>         /*      }
>             }
>         }
> */
>         bootstrap {
>             disable: false
>             cand-bsr {
>                 scope-zone 224.0.0.0/4 {
>                     /* is-scope-zone: false */
>                  cand-bsr-by-vif-name: "eth1"
>                     /* cand-bsr-by-vif-addr: 10.10.10.10 */
>                     /* bsr-priority: 1 */
>                     /* hash-mask-len: 30 */
>               }
>             }
>             cand-rp {
>                 group-prefix 224.0.0.0/4 {
>                     /* is-scope-zone: false */
>                     cand-rp-by-vif-name: "eth1"
>                     /* cand-rp-by-vif-addr: 10.10.10.10 */
>                     /* rp-priority: 192 */
>                     /* rp-holdtime: 150 */
>               }
>             }
>         }
> 
>         switch-to-spt-threshold {
>             /* approx. 1K bytes/s (10Kbps) threshold */
>             disable: false
>             interval: 100
>             bytes: 102400
>         }
> 
>         traceoptions {
>             flag all {
>                 disable: false
>             }
>         }
>     }
> }
> -------------------------------------------
> 4)
> 
> 
> /*XORP Configuration File*/
> interfaces {
>     interface eth0 {
>         description: "Ethernet"
>         disable: false
>         vif eth0 {
>                 disable: false
>                 address 192.168.2.1 {
>                         prefix-length: 24
>                         broadcast: 192.168.2.255
>                         disable: false
>                 }
>         }
>     }
>     interface eth1 {
>         description: "Ethernet"
>         disable: false
>         vif eth1 {
>                 disable: false
>                 address 192.168.1.3 {
>                         prefix-length: 24
>                         broadcast: 192.168.1.255
>                         disable: false
>                 }
>          }
>     }
>     interface lo {
>         description: "Loopback interface"
>         vif lo {
>         }
>     }
> }
> fea{
>    unicast-forwarding4 {
>         disable: false
>     }
> 
>  }
> protocols {
>    static {
>     route 192.168.1.0/24 {
>         next-hop: 192.168.1.1
>         metric: 1
>     }
>     /*mrib-route 10.20.0.0/16 {
>         next-hop: 10.10.10.30
>             metric: 1
>     }*/
> }
> }
> 
> plumbing {
>     mfea4 {
>         disable: false
>         interface eth0 {
>             vif eth0 {
>                 disable: false
>             }
>         }
> 
>         interface eth1 {
>             vif eth1 {
>                 disable: false
>             }
>         }
>         interface register_vif {
>             vif register_vif {
>                 /* Note: this vif should be always enabled */
>                 disable: false
>             }
>         }
>         traceoptions {
>             flag all {
>                 disable: false
>             }
>         }
>     }
>  }
> protocols {
>     igmp {
>         disable: false
>         interface eth0 {
>             vif eth0 {
>                 disable: false
>                 /* version: 2 */
>                 /* enable-ip-router-alert-option-check: false */
>                 /* query-interval: 125 */
>                 /* query-last-member-interval: 1 */
>                 /* query-response-interval: 10 */
>                 /* robust-count: 2 */
>             }
>         }
>         interface eth1 {
>             vif eth1 {
>                 disable: false
>                 /* version: 2 */
>                 /* enable-ip-router-alert-option-check: false */
>                 /* query-interval: 125 */
>                 /* query-last-member-interval: 1 */
>                 /* query-response-interval: 10 */
>                 /* robust-count: 2 */
>             }
>         }
>         traceoptions {
>             flag all {
>                 disable: false
>             }
>         }
>     }
> }
> protocols {
>     pimsm4 {
>         disable: false
>         interface eth0 {
>             vif eth0 {
>                 disable: false
>                 /* enable-ip-router-alert-option-check: false */
>                 /* dr-priority: 1 */
>                 /* hello-period: 30 */
>                 /* hello-triggered-delay: 5 */
>                 /* alternative-subnet 10.40.0.0/16 */
>             }
>         }
>         interface eth1 {
>             vif eth1 {
>                 disable: false
>                 /* enable-ip-router-alert-option-check: false */
>                 /* dr-priority: 1 */
>                 /* hello-period: 30 */
>                 /* hello-triggered-delay: 5 */
>                 /* alternative-subnet 10.40.0.0/16 */
>             }
>         }
>         interface register_vif {
>             vif register_vif {
>                 /* Note: this vif should be always enabled */
>                 disable: false
>             }
>         }
> 
>         /*static-rps {
>             rp 10.60.0.1 {
>                 group-prefix 224.0.0.0/4 {
>                     /* rp-priority: 192 */
>                     /* hash-mask-len: 30 */
>         /*      }
>             }
>         }
> */
>         bootstrap {
>             disable: false
>             cand-bsr {
>                 scope-zone 224.0.0.0/4 {
>                     /* is-scope-zone: false */
>                  cand-bsr-by-vif-name: "eth1"
>                     /* cand-bsr-by-vif-addr: 10.10.10.10 */
>                     /* bsr-priority: 1 */
>                     /* hash-mask-len: 30 */
>               }
>             }
>             cand-rp {
>                 group-prefix 224.0.0.0/4 {
>                     /* is-scope-zone: false */
>                     cand-rp-by-vif-name: "eth1"
>                     /* cand-rp-by-vif-addr: 10.10.10.10 */
>                     /* rp-priority: 192 */
>                     /* rp-holdtime: 150 */
>               }
>             }
>         }
> 
>         switch-to-spt-threshold {
>             /* approx. 1K bytes/s (10Kbps) threshold */
>             disable: false
>             interval: 100
>             bytes: 102400
>         }
> 
>         traceoptions {
>             flag all {
>                 disable: false
>             }
>         }
>     }
> }
> _______________________________________________
> Xorp-users mailing list
> Xorp-users at xorp.org
> http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users


From ez201 at mail2.selye.sk  Thu Mar 15 03:01:46 2007
From: ez201 at mail2.selye.sk (Elzer Zoltan)
Date: Thu, 15 Mar 2007 11:01:46 +0100
Subject: [Xorp-users] Cannot start vif
In-Reply-To: <200703141817.l2EIHgBN051637@possum.icir.org>
References: <200703141817.l2EIHgBN051637@possum.icir.org>
Message-ID: <20070315100146.25006.qmail@selye.sk>

Hello Pavlin 

I still have the same problem. I dont have config file, because I use live 
cd version and I dont have floppy drive. I  setup everything manally. Here 
is the config: 


interfaces {
   interface xl0 {
      vif xl0 {
	address 192.168.2.1 {
		prefix-length: 24
}
}
}
} 

interfaces {
   interface rl0 {
      vif rl0 {
	address 192.168.3.1 {
		prefix-length: 24
}
}
}
} 


fea {
   unicast-forwarding4 {
 }
} 

protocols {
   fib2mrib {
      }
} 

 ----- Here I ran commit and it succeeded. 


plumbing {
   mfea4 { 

      interface xl0 {
         vif xl0 {

         }
      } 

      interface register_vif {
         vif register_vif {

         }
      } 

 --- After this when I ran commit the same error occurred:
102 Command failed Cannot start vif xl0: underlying vif is not UP 

All interfaces are enabled (disable: false) and unicast forwarding worked 
fine. 

Regards, Turbo 

 

 


Pavlin Radoslavov writes: 

>> I am new in xorp. I would like to try th multicast forwarding, but a problem 
>> occured.
>>  - I use live cd version 1.4
>            ~~~~~~~~~~~~~~~~~~~
> This has to be 1.4-RC (Release Candidate), because the final 1.4
> version is not released yet. 
> 
>>  - The network layout:  Host1 --- Xorp router --- Host2
>>  - I succeeded in setting up unicast forwarding between the two host, but 
>> when I tried to set multicast plumbing, or adding new protocol (IGMP, PIM), 
>> after commit I  got the following error: 102 Command failed Cannot start vif 
>> rl0: underlying vif is not UP
>> I tried it on all interfaces an on different machines.
>> Please help me, how can I resolve this problem. Thanks. 
> 
> Can you send your configuration file.
> Also, did you configure/enable rl0 in the "mfea4" section as well.
> Finally, is "rl0" connected to the network. 
> 
> Regards,
> Pavlin 
> 
> _______________________________________________
> Xorp-users mailing list
> Xorp-users at xorp.org
> http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users
 


From hilalchouman at gmail.com  Thu Mar 15 07:47:21 2007
From: hilalchouman at gmail.com (hilal chouman)
Date: Thu, 15 Mar 2007 16:47:21 +0200
Subject: [Xorp-users] Dynamic RP and other issues
Message-ID: <9579816a0703150747g78bad4ubc65bbc0fee47ad7@mail.gmail.com>

Hi Pavlin,



Rec?R3---R1---R2--- rec



More specifically this:



Rec---(eth0 of  R3 | eth1 of R3)---(eth0 of  R1 | eth1 of R1)---


  |

                                           Send---(eth0 of  R2 | eth1 of R2)
---
addresses:


(Rec: 10.0.80.12)---(R3: 10.0.80.10 | R3: 10.1.50.1)---(R1: 10.1.50.10 | R1:
10.1.200.1)---


  |

                                              ( Send: 10.1.100.10)---(R2:
10.1.100.1 | R2: 10.1.200.10) ---

Rec=Receiver

Send=Sender



I have the above network and multicast worked well with static RP
configuration. I have been setting VLC steaming video on sender and received
it successfully on the receiver.



I am now trying to set up the bootsrap cand BSR/ cand RP but it can't find
the RP. My config.boot files are at the end of the email.

I have a couple of questions about the dynamic RP configuration:

1- how do you select the cand-bsr-by-vif-name and the cand-rp-by-vif-name? I
've selected them in a way that they point towards the sender. Is that right
or it has nothing to do with it?

2- what is the minimum configuration for dynamic RP ?



On other topics:

1-     what is the significance of the group-prefix 224.0.0.0? I know that
after this address, the range of multicast addresses are found. Does it
relate by anyway to the multicast group addresses used in the network?

2-     Do you have any information on SSM with XORP or SSM with VLC (other
than enabling version 3 of IGMP?

3-     A stream is sent by multicast to a certain a multicast group address.
It was received. What will happen if another stream was sent to the same
multicast group address?

Sorry for making it long. And thanks in advance.



*My Config.boot files:*



*Router 2 (R2)*

*------------------*

/* $XORP: xorp/rtrmgr/config.boot.sample,v 1.41 2006/06/30 00:43:05 pavlin
Exp $ */





interfaces {

    restore-original-config-on-shutdown: false

    interface eth1 {

      description: "Ethernet"

      disable: false

      discard: false

      /* default-system-config */

      vif eth1 {

          disable: false

          address 10.1.200.10 {

            prefix-length: 25

                multicast-capable: true

            disable: false

          }

      }

    }

   /* interface eth2 {

        description: "Ethernet"

        disable: false

        discard: false

        vif eth2 {

           disable: false

           address 10.1.150.1 {

                prefix-length: 25

                multicast-capable: true

                disable: false

           }

        }

    } */

    interface eth0 {

      description: "Ethernet"

      disable: false

        discard: false

      /* default-system-config */

      vif eth0 {

          disable: false

          address 10.1.100.1 {

            prefix-length: 25

            multicast-capable: true

            disable: false

          }

      }

    }

/*      interface lo {

        description: "Loopback interface"

        disable: false

        discard: false

        vif lo {

            disable: false

       }

     }

*/

}



fea {

    unicast-forwarding4 {

      disable: false

        }

    }





plumbing {

     mfea4 {

      disable: false

      interface eth0 {

          vif eth0 {

            disable: false

          }

      }



       /* interface eth2 {

            vif eth2 {

                disable: false

            }

        } */



      interface eth1 {

            vif eth1 {

                  disable: false

         }

      }

      interface "register_vif" {

          vif "register_vif" {

            /* Note: this vif should be always enabled */

            disable: false

          }

      }

      traceoptions {

          flag {

              all {

            disable: false

              }

          }

      }

    }

}



protocols {

    igmp {

      disable: false

      interface eth0 {

          vif eth0 {

            disable: false

            version: 3

            enable-ip-router-alert-option-check: false

            query-interval: 125

            query-last-member-interval: 1

            query-response-interval: 10

            robust-count: 2

          }

      }



/* interface eth2 {

            vif eth2 {

                disable: false

                version: 3

                enable-ip-router-alert-option-check: false

                query-interval: 125

                query-last-member-interval: 1

                query-response-interval: 10

                robust-count: 2

            }

        }



*/

        interface eth1 {

            vif eth1 {

                disable: false

                version: 3

                enable-ip-router-alert-option-check: false

                query-interval: 125

                query-last-member-interval: 1

                query-response-interval: 10

                robust-count: 2

           }

        }

      traceoptions {

          flag {

               all {

            disable: false

               }

          }

      }

    }

    pimsm4 {

      disable: false

      interface eth0 {

          vif eth0 {

            disable: false

            enable-ip-router-alert-option-check: false

            dr-priority: 1

            hello-period: 30

            hello-triggered-delay: 5

          }

      }



      /* interface eth2 {

            vif eth2 {

                disable: false

                enable-ip-router-alert-option-check: false

                dr-priority: 1

                hello-period: 30

                hello-triggered-delay: 5

            }

        } */



        interface eth1 {

            vif eth1 {

                disable: false

                enable-ip-router-alert-option-check: false

                dr-priority: 1

                hello-period: 30

                hello-triggered-delay: 5

            }

        }

      interface register_vif {

          vif register_vif {

            /* Note: this vif should be always enabled */

            disable: false

          }

      }



/*    static-rps {

          rp 10.1.200.1 {

            group-prefix 224.0.0.0/4 {

                rp-priority: 192

                hash-mask-len: 30

            }

          }

      }

*/



      bootstrap {

            disable: false

            cand-bsr {

                  scope-zone 224.0.0.0/4 {

                  cand-bsr-by-vif-name: "eth0"

                  }

            }



            cand-rp {

                  group-prefix 224.0.0.0/4 {

                  cand-rp-by-vif-name: "eth0"

                  }

            }

      }

      switch-to-spt-threshold {

          /* approx. 1K bytes/s (10Kbps) threshold */

          disable: true

          interval: 100

          bytes: 102400

      }



      traceoptions {

          flag {

                all {

                disable: false

                }

          }

      }

    }



    fib2mrib {

      disable: false

    }

}





*Router 1 (R1)*

*------------------*

/* $XORP: xorp/rtrmgr/config.boot.sample,v 1.41 2006/06/30 00:43:05 pavlin
Exp $ */





interfaces {

    restore-original-config-on-shutdown: false

    interface eth1 {

      description: "Ethernet"

      disable: false

      discard: false

      /* default-system-config */

      vif eth1 {

          disable: false

          address 10.1.200.1 {

            prefix-length: 25

                multicast-capable: true

            disable: false

          }

      }

    }

    interface eth0 {

      description: "Ethernet"

      disable: false

        discard: false

      /* default-system-config */

      vif eth0 {

          disable: false

          address 10.1.50.10 {

            prefix-length: 25

            multicast-capable: true

            disable: false

          }

      }

    }

      interface lo {

        description: "Loopback interface"

        disable: false

        discard: false

        vif lo {

            disable: false

       }

     }

}



fea {

    unicast-forwarding4 {

      disable: false

        }

    }





plumbing {

     mfea4 {

      disable: false

      interface eth0 {

          vif eth0 {

            disable: false

          }

      }

        interface eth1 {

          vif eth1 {

              disable: false

            }

        }

      interface "register_vif" {

          vif "register_vif" {

            /* Note: this vif should be always enabled */

            disable: false

          }

      }

      traceoptions {

          flag {

              all {

            disable: false

              }

          }

      }

    }

}



protocols {

    igmp {

      disable: false

      interface eth0 {

          vif eth0 {

            disable: false

            version: 3

            enable-ip-router-alert-option-check: false

            query-interval: 125

            query-last-member-interval: 1

            query-response-interval: 10

            robust-count: 2

          }

      }

        interface eth1 {

            vif eth1 {

                disable: false

                version: 3

                enable-ip-router-alert-option-check: false

                query-interval: 125

                query-last-member-interval: 1

                query-response-interval: 10

                robust-count: 2

           }

        }

      traceoptions {

          flag {

               all {

            disable: false

               }

          }

      }

    }

    pimsm4 {

      disable: false

      interface eth0 {

          vif eth0 {

            disable: false

            enable-ip-router-alert-option-check: false

            dr-priority: 1

            hello-period: 30

            hello-triggered-delay: 5

          }

      }

        interface eth1 {

            vif eth1 {

                disable: false

                enable-ip-router-alert-option-check: false

                dr-priority: 1

                hello-period: 30

                hello-triggered-delay: 5

            }

        }

      interface register_vif {

          vif register_vif {

            /* Note: this vif should be always enabled */

            disable: false

          }

      }



      static-rps {

          rp 10.1.200.1 {

            group-prefix 224.0.0.0/4 {

                rp-priority: 192

                hash-mask-len: 30

            }

          }

      }



      switch-to-spt-threshold {

          /* approx. 1K bytes/s (10Kbps) threshold */

          disable: true

          interval: 100

          bytes: 102400

      }



      traceoptions {

          flag {

                all {

                disable: false

                }

          }

      }

    }



    fib2mrib {

      disable: false

    }

}





*Router 3 (R3)*

*------------------*

/* $XORP: xorp/rtrmgr/config.boot.sample,v 1.41 2006/06/30 00:43:05 pavlin
Exp $ */





interfaces {

    restore-original-config-on-shutdown: false

    interface eth1 {

      description: "Ethernet"

      disable: false

      discard: false

      /* default-system-config */

      vif eth1 {

          disable: false

          address 10.1.50.1 {

            prefix-length: 25

                multicast-capable: true

            disable: false

          }

      }

    }

    interface eth0 {

      description: "Ethernet"

      disable: false

        discard: false

      /* default-system-config */

      vif eth0 {

          disable: false

          address 10.0.80.10 {

            prefix-length: 25

            multicast-capable: true

            disable: false

          }

      }

    }

      interface lo {

        description: "Loopback interface"

        disable: false

        discard: false

        vif lo {

            disable: false

       }

     }

}



fea {

    unicast-forwarding4 {

      disable: false

        }

    }





plumbing {

     mfea4 {

      disable: false

      interface eth0 {

          vif eth0 {

            disable: false

          }

      }

        interface eth1 {

          vif eth1 {

              disable: false

            }

        }

      interface "register_vif" {

          vif "register_vif" {

            /* Note: this vif should be always enabled */

            disable: false

          }

      }

      traceoptions {

          flag {

              all {

            disable: false

              }

          }

      }

    }

}



protocols {

    igmp {

      disable: false

      interface eth0 {

          vif eth0 {

            disable: false

            version: 3

            enable-ip-router-alert-option-check: false

            query-interval: 125

            query-last-member-interval: 1

            query-response-interval: 10

            robust-count: 2

          }

      }

        interface eth1 {

            vif eth1 {

                disable: false

                version: 3

                enable-ip-router-alert-option-check: false

                query-interval: 125

                query-last-member-interval: 1

                query-response-interval: 10

                robust-count: 2

           }

        }

      traceoptions {

          flag {

               all {

            disable: false

               }

          }

      }

    }

    pimsm4 {

      disable: false

      interface eth0 {

          vif eth0 {

            disable: false

            enable-ip-router-alert-option-check: false

            dr-priority: 1

            hello-period: 30

            hello-triggered-delay: 5

          }

      }

        interface eth1 {

            vif eth1 {

                disable: false

                enable-ip-router-alert-option-check: false

                dr-priority: 1

                hello-period: 30

                hello-triggered-delay: 5

            }

        }

      interface register_vif {

          vif register_vif {

            /* Note: this vif should be always enabled */

            disable: false

          }

      }



      /* static-rps {

          rp 10.1.200.1 {

            group-prefix 224.0.0.0/4 {

                rp-priority: 192

                hash-mask-len: 30

            }

          }

      } */



      bootstrap {

            disable: false

            cand-bsr {

                  scope-zone 224.0.0.0/4 {

                        cand-bsr-by-vif-name: "eth1"

                        }

                  }

            cand-rp {

                  group-prefix 224.0.0.0/4 {

                        cand-rp-by-vif-name: "eth1"

                        }

                  }

      }



      switch-to-spt-threshold {

          /* approx. 1K bytes/s (10Kbps) threshold */

          disable: true

          interval: 100

          bytes: 102400

      }



      traceoptions {

          flag {

                all {

                disable: false

                }

          }

      }

    }



    fib2mrib {

      disable: false

    }

}

-- 
Hilal Chouman
???? ?????
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20070315/0130733a/attachment-0001.html 

From ez201 at mail2.selye.sk  Thu Mar 15 11:43:47 2007
From: ez201 at mail2.selye.sk (Elzer Zoltan)
Date: Thu, 15 Mar 2007 19:43:47 +0100
Subject: [Xorp-users] Cannot start vif
In-Reply-To: <20070315100146.25006.qmail@selye.sk>
References: <200703141817.l2EIHgBN051637@possum.icir.org>
	<20070315100146.25006.qmail@selye.sk>
Message-ID: <20070315184347.606.qmail@selye.sk>

Hello Pavlin 

I managed to configure the router. I installed the xorp to the machine 
instead of live cd and I used one of the config file from mailing list. 
Thanks! 

                       Turbo 

Elzer Zoltan writes: 

> Hello Pavlin  
> 
> I still have the same problem. I dont have config file, because I use live 
> cd version and I dont have floppy drive. I  setup everything manally. Here 
> is the config:  
> 
> 
> interfaces {
>    interface xl0 {
>       vif xl0 {
> 	address 192.168.2.1 {
> 		prefix-length: 24
> }
> }
> }
> }  
> 
> interfaces {
>    interface rl0 {
>       vif rl0 {
> 	address 192.168.3.1 {
> 		prefix-length: 24
> }
> }
> }
> }  
> 
> 
> fea {
>    unicast-forwarding4 {
>  }
> }  
> 
> protocols {
>    fib2mrib {
>       }
> }  
> 
>  ----- Here I ran commit and it succeeded.  
> 
> 
> plumbing {
>    mfea4 {  
> 
>       interface xl0 {
>          vif xl0 { 
> 
>          }
>       }  
> 
>       interface register_vif {
>          vif register_vif { 
> 
>          }
>       }  
> 
>  --- After this when I ran commit the same error occurred:
> 102 Command failed Cannot start vif xl0: underlying vif is not UP  
> 
> All interfaces are enabled (disable: false) and unicast forwarding worked 
> fine.  
> 
> Regards, Turbo  
> 
>   
> 
>   
> 
> 
> Pavlin Radoslavov writes:  
> 
>>> I am new in xorp. I would like to try th multicast forwarding, but a problem 
>>> occured.
>>>  - I use live cd version 1.4
>>            ~~~~~~~~~~~~~~~~~~~
>> This has to be 1.4-RC (Release Candidate), because the final 1.4
>> version is not released yet.  
>> 
>>>  - The network layout:  Host1 --- Xorp router --- Host2
>>>  - I succeeded in setting up unicast forwarding between the two host, but 
>>> when I tried to set multicast plumbing, or adding new protocol (IGMP, PIM), 
>>> after commit I  got the following error: 102 Command failed Cannot start vif 
>>> rl0: underlying vif is not UP
>>> I tried it on all interfaces an on different machines.
>>> Please help me, how can I resolve this problem. Thanks. 
>> 
>> Can you send your configuration file.
>> Also, did you configure/enable rl0 in the "mfea4" section as well.
>> Finally, is "rl0" connected to the network.  
>> 
>> Regards,
>> Pavlin  
>> 
>> _______________________________________________
>> Xorp-users mailing list
>> Xorp-users at xorp.org
>> http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users
>   
> 
> _______________________________________________
> Xorp-users mailing list
> Xorp-users at xorp.org
> http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users
 


From ashishkarpe at gmail.com  Thu Mar 15 13:07:55 2007
From: ashishkarpe at gmail.com (Ashish Karpe)
Date: Fri, 16 Mar 2007 01:37:55 +0530
Subject: [Xorp-users] cannot add multicast vif to kernel !!!!
Message-ID: <f87e63a0703151307q5a07db4ax6c7076f4b78b7c60@mail.gmail.com>

Hi all,
         i am getting following error on Knoppix 3.3 kernel ver 2.4.22 (I
have installed knoppix its not from live CD )

error : cannot add multicast vif to kernel !!!!

how do i add it ???
-- 
-Ashish
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20070316/1469b750/attachment.html 

From pavlin at icir.org  Thu Mar 15 13:45:19 2007
From: pavlin at icir.org (Pavlin Radoslavov)
Date: Thu, 15 Mar 2007 13:45:19 -0700
Subject: [Xorp-users] Cannot start vif
In-Reply-To: Message from "Elzer Zoltan" <ez201@mail2.selye.sk> 
	of "Thu, 15 Mar 2007 19:43:47 BST." <20070315184347.606.qmail@selye.sk> 
Message-ID: <200703152045.l2FKjJ2n079498@possum.icir.org>

> Hello Pavlin 
> 
> I managed to configure the router. I installed the xorp to the machine 
> instead of live cd and I used one of the config file from mailing list. 
> Thanks! 
> 
>                        Turbo 

That's odd. I don't see the reason why it didn't work from LiveCD if
it worked when installed on the disk.

If you still care about the LiveCD issue, could you run the
"show interfaces" after you configure the interfaces, but before
configuring mfea4. Then please run it again after you try to
configure and commit the mfea4 configuration.
It will be great if you find a way of sending me both outputs :)
I care only about the interface that failed to be configured/started
by the MFEA.

Thanks,
Pavlin

> Elzer Zoltan writes: 
> 
> > Hello Pavlin  
> > 
> > I still have the same problem. I dont have config file, because I use live 
> > cd version and I dont have floppy drive. I  setup everything manally. Here 
> > is the config:  
> > 
> > 
> > interfaces {
> >    interface xl0 {
> >       vif xl0 {
> > 	address 192.168.2.1 {
> > 		prefix-length: 24
> > }
> > }
> > }
> > }  
> > 
> > interfaces {
> >    interface rl0 {
> >       vif rl0 {
> > 	address 192.168.3.1 {
> > 		prefix-length: 24
> > }
> > }
> > }
> > }  
> > 
> > 
> > fea {
> >    unicast-forwarding4 {
> >  }
> > }  
> > 
> > protocols {
> >    fib2mrib {
> >       }
> > }  
> > 
> >  ----- Here I ran commit and it succeeded.  
> > 
> > 
> > plumbing {
> >    mfea4 {  
> > 
> >       interface xl0 {
> >          vif xl0 { 
> > 
> >          }
> >       }  
> > 
> >       interface register_vif {
> >          vif register_vif { 
> > 
> >          }
> >       }  
> > 
> >  --- After this when I ran commit the same error occurred:
> > 102 Command failed Cannot start vif xl0: underlying vif is not UP  
> > 
> > All interfaces are enabled (disable: false) and unicast forwarding worked 
> > fine.  
> > 
> > Regards, Turbo  
> > 
> >   
> > 
> >   
> > 
> > 
> > Pavlin Radoslavov writes:  
> > 
> >>> I am new in xorp. I would like to try th multicast forwarding, but a problem 
> >>> occured.
> >>>  - I use live cd version 1.4
> >>            ~~~~~~~~~~~~~~~~~~~
> >> This has to be 1.4-RC (Release Candidate), because the final 1.4
> >> version is not released yet.  
> >> 
> >>>  - The network layout:  Host1 --- Xorp router --- Host2
> >>>  - I succeeded in setting up unicast forwarding between the two host, but 
> >>> when I tried to set multicast plumbing, or adding new protocol (IGMP, PIM), 
> >>> after commit I  got the following error: 102 Command failed Cannot start vif 
> >>> rl0: underlying vif is not UP
> >>> I tried it on all interfaces an on different machines.
> >>> Please help me, how can I resolve this problem. Thanks. 
> >> 
> >> Can you send your configuration file.
> >> Also, did you configure/enable rl0 in the "mfea4" section as well.
> >> Finally, is "rl0" connected to the network.  
> >> 
> >> Regards,
> >> Pavlin  
> >> 
> >> _______________________________________________
> >> Xorp-users mailing list
> >> Xorp-users at xorp.org
> >> http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users
> >   
> > 
> > _______________________________________________
> > Xorp-users mailing list
> > Xorp-users at xorp.org
> > http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users
>  
> 
> _______________________________________________
> Xorp-users mailing list
> Xorp-users at xorp.org
> http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users


From pavlin at icir.org  Thu Mar 15 14:15:51 2007
From: pavlin at icir.org (Pavlin Radoslavov)
Date: Thu, 15 Mar 2007 14:15:51 -0700
Subject: [Xorp-users] Dynamic RP and other issues
In-Reply-To: Message from "hilal chouman" <hilalchouman@gmail.com> of "Thu,
	15 Mar 2007 16:47:21 +0200."
	<9579816a0703150747g78bad4ubc65bbc0fee47ad7@mail.gmail.com> 
Message-ID: <200703152115.l2FLFpAW080079@possum.icir.org>

> Rec?R3---R1---R2--- rec
> 
> 
> 
> More specifically this:
> 
> 
> 
> Rec---(eth0 of  R3 | eth1 of R3)---(eth0 of  R1 | eth1 of R1)---
> 
> 
>   |
> 
>                                            Send---(eth0 of  R2 | eth1 of R2)
> ---
> addresses:
> 
> 
> (Rec: 10.0.80.12)---(R3: 10.0.80.10 | R3: 10.1.50.1)---(R1: 10.1.50.10 | R1:
> 10.1.200.1)---
> 
> 
>   |
> 
>                                               ( Send: 10.1.100.10)---(R2:
> 10.1.100.1 | R2: 10.1.200.10) ---
> 
> Rec=Receiver
> 
> Send=Sender
> 
> 
> 
> I have the above network and multicast worked well with static RP
> configuration. I have been setting VLC steaming video on sender and received
> it successfully on the receiver.
> 
> 
> 
> I am now trying to set up the bootsrap cand BSR/ cand RP but it can't find
> the RP. My config.boot files are at the end of the email.
> 
> I have a couple of questions about the dynamic RP configuration:
> 
> 1- how do you select the cand-bsr-by-vif-name and the cand-rp-by-vif-name? I
> 've selected them in a way that they point towards the sender. Is that right
> or it has nothing to do with it?

You can select any of the interfaces of a XORP router, as long as
this interface is enabled for multicast routing. In addition, all
other XORP routers must have Reverse-Path Forwarding information
toward the IP address of that interface. Typically that means that
you need to run an unicast routing protocol (or at least install the
appropriate static routes).

In your configuration I didn't see any static routes so you might
want to add them.

I see that inisde the Router 1 configuration you have the
"static-rps" section enabled.
If you want to use the Bootstrap mechanism you should delete all
static RPs (that overlap with the prefix(es) advertised by
Bootstrap), otherwise the result is unpredictable.

Note that if you want to use the Bootstrap mechanism, you don't have
to configure Bootstrap information in each XORP router. You need to
include the "bootstrap" section only if you want to configure a
router as a Cand-BSR and/or Cand-RP.

> 2- what is the minimum configuration for dynamic RP ?

You must have a Cand-BSR and a Cand-RP in at least one router, which
actually can be two different routers.
Then, again, you should not have any static RPs (in any multicast
router).

> On other topics:
> 
> 1-     what is the significance of the group-prefix 224.0.0.0? I know that
> after this address, the range of multicast addresses are found. Does it
> relate by anyway to the multicast group addresses used in the network?

The significance of group-prefix 224.0.0.0/4 is that with a single
configuration block you configure the Cand-RP or Cand-BSR for all
multicast groups. You can use any subprefix of the multicast address
space instead (except the link-local 224.0.0.0/8 which are not
routable).

> 2-     Do you have any information on SSM with XORP or SSM with VLC (other
> than enabling version 3 of IGMP?

Enabling IGMPv3 should be sufficient.
If you will be using ONLY SSM, then you don't need any RP-related
configuration (but it is better to keep the register_vif
interfaces).


> 3-     A stream is sent by multicast to a certain a multicast group address.
> It was received. What will happen if another stream was sent to the same
> multicast group address?

I presume the second stream is from a different source address.

Did the receiver use IGMPv1 or IGMPv2 to join the multicast group
(i.e., a group-specific (*,G) join).
If yes, then it should receive the second stream as well.

If the receiver used IGMPv3 to join the group address and a specific
source address (the address of the first sender) with a join like
(S1,G), then it will receive only the first stream. If it wants to
receive the second stream as well, then it needs to use another
IGMPv3 (S2,G) join.

Regards,
Pavlin



From pavlin at icir.org  Thu Mar 15 14:20:28 2007
From: pavlin at icir.org (Pavlin Radoslavov)
Date: Thu, 15 Mar 2007 14:20:28 -0700
Subject: [Xorp-users] cannot add multicast vif to kernel !!!!
In-Reply-To: Message from "Ashish Karpe" <ashishkarpe@gmail.com> of "Fri,
	16 Mar 2007 01:37:55 +0530."
	<f87e63a0703151307q5a07db4ax6c7076f4b78b7c60@mail.gmail.com> 
Message-ID: <200703152120.l2FLKSOf080381@possum.icir.org>

>          i am getting following error on Knoppix 3.3 kernel ver 2.4.22 (I
> have installed knoppix its not from live CD )
> 
> error : cannot add multicast vif to kernel !!!!

My guess is that multicast forwarding and PIM-SM support are not
enabled in your kernel.

See Section 13.3.1 "Configuring Multicast Routing on UNIX Systems"
in the XORP User Manual for information about the options you need
to enable.

Regards,
Pavlin


From ashishkarpe at gmail.com  Thu Mar 15 15:23:37 2007
From: ashishkarpe at gmail.com (Ashish Karpe)
Date: Fri, 16 Mar 2007 03:53:37 +0530
Subject: [Xorp-users] Want test result of PIM-BIDIR protocol !!!
In-Reply-To: <200703121822.l2CIMT6X002467@possum.icir.org>
References: <ashishkarpe@gmail.com>
	<f87e63a0703111555u2932b404yd7c9bd903bded94@mail.gmail.com>
	<200703121822.l2CIMT6X002467@possum.icir.org>
Message-ID: <f87e63a0703151523h290c60b3t5e1fa6e515a03ad@mail.gmail.com>

On 3/12/07, Pavlin Radoslavov <pavlin at icir.org> wrote:
>
> > do anybody have comparative test results of PIM-SM & PIM-BIDIR ?? can u
> > share it ?? or else from where can i get those ??
>
> Can you be more specific what you mean by "comparative test
> results".


means we want to see test result proving that PIM-Bidir in beneficial over
PIm-SM  for many-to-many applications !!!


I haven't heard about a detailed study targeting both PIM-SM and
> Bidir-PIM (at least I don't remember anyting beint sent to the
> relevant mailing lists).
> So there is a window of opportunity for you for such study after you
> complete your Bidir-PIM implementation :)




             Problems for us is that we don't  have large setup to see/test
this comparative (PIM-SM Vs Bidir ) result !!! Currently we are using Vmware
on single machine so we can only test basic interoperability between bidir
routers for our implementation !! But we are unable to compare between these
to protocols !! bty what do you prefer to compare between this two protocols
??


  ps: large setup is required because Bidir PIM enables many-to-many
applications by allowing them to easily scale to a very large number of
groups and sources by eliminating the maintenance of source state.

Regards,
> Pavlin
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20070316/49a25dac/attachment.html 

From pavlin at icir.org  Thu Mar 15 15:47:21 2007
From: pavlin at icir.org (Pavlin Radoslavov)
Date: Thu, 15 Mar 2007 15:47:21 -0700
Subject: [Xorp-users] Want test result of PIM-BIDIR protocol !!!
In-Reply-To: Message from "Ashish Karpe" <ashishkarpe@gmail.com> of "Fri,
	16 Mar 2007 03:53:37 +0530."
	<f87e63a0703151523h290c60b3t5e1fa6e515a03ad@mail.gmail.com> 
Message-ID: <200703152247.l2FMlLmJ084057@possum.icir.org>

> > > do anybody have comparative test results of PIM-SM & PIM-BIDIR ?? can u
> > > share it ?? or else from where can i get those ??
> >
> > Can you be more specific what you mean by "comparative test
> > results".
> 
> 
> means we want to see test result proving that PIM-Bidir in beneficial over
> PIm-SM  for many-to-many applications !!!

You don't have to run a large-scale experiment to show that.
For example, Bidir-PIM doesn't have the PIM Register
encapsulation/decapsulation mechanism and the PIM Assert mechanism.
You can do some analyses to show why/when this is beneficial.

Regards,
Pavlin

> I haven't heard about a detailed study targeting both PIM-SM and
> > Bidir-PIM (at least I don't remember anyting beint sent to the
> > relevant mailing lists).
> > So there is a window of opportunity for you for such study after you
> > complete your Bidir-PIM implementation :)
> 
> 
> 
> 
>              Problems for us is that we don't  have large setup to see/test
> this comparative (PIM-SM Vs Bidir ) result !!! Currently we are using Vmware
> on single machine so we can only test basic interoperability between bidir
> routers for our implementation !! But we are unable to compare between these
> to protocols !! bty what do you prefer to compare between this two protocols
> ??
> 
> 
>   ps: large setup is required because Bidir PIM enables many-to-many
> applications by allowing them to easily scale to a very large number of
> groups and sources by eliminating the maintenance of source state.
> 
> Regards,
> > Pavlin
> >
> _______________________________________________
> Xorp-users mailing list
> Xorp-users at xorp.org
> http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users


From ez201 at mail2.selye.sk  Sat Mar 17 11:41:36 2007
From: ez201 at mail2.selye.sk (Elzer Zoltan)
Date: Sat, 17 Mar 2007 19:41:36 +0100
Subject: [Xorp-users] Cannot start vif + IPv6 multicast question
In-Reply-To: <200703152045.l2FKjJ2n079498@possum.icir.org>
References: <200703152045.l2FKjJ2n079498@possum.icir.org>
Message-ID: <20070317184149.8355.qmail@selye.sk>

Hello Pavlin, 

As I wrote in my last letter, I managed to start the xorp. unfortunately I
don't have the live CD's config file but I have the working config so I
attached it to my mail.
I would like to ask another question. We would like to run the IPv6
multicast forwarding. I browsed the net and found the IPv6 multicast patch
for linux. I have the 2.6.7 kernel version and I patched it. but
unfortunately the xorp's answer was an Error:
add_multicast_vif() failed: IPv6 multicast routing not supported
I got this error because I added the mfea6 to the config file. I set the
variables in the kernel config as the xorp manual said. But nothing. 

To add more I found your answer to a mail:
http//mailman.icsi.berkeley.edu/pipermail/xorp-users/2007-January/001638.htm
l
and you said that there is no confirmation whether the patched Linux kernel
really works with XORP. Have you tried it, is it working now properly or I
didn't check something ? Thanks for your answer! 



                                               Best regards
                                                       Turbo 


Pavlin Radoslavov writes: 

>> Hello Pavlin  
>> 
>> I managed to configure the router. I installed the xorp to the machine 
>> instead of live cd and I used one of the config file from mailing list. 
>> Thanks!  
>> 
>>                        Turbo 
> 
> That's odd. I don't see the reason why it didn't work from LiveCD if
> it worked when installed on the disk. 
> 
> If you still care about the LiveCD issue, could you run the
> "show interfaces" after you configure the interfaces, but before
> configuring mfea4. Then please run it again after you try to
> configure and commit the mfea4 configuration.
> It will be great if you find a way of sending me both outputs :)
> I care only about the interface that failed to be configured/started
> by the MFEA. 
> 
> Thanks,
> Pavlin 
> 
>> Elzer Zoltan writes:  
>> 
>> > Hello Pavlin  
>> > 
>> > I still have the same problem. I dont have config file, because I use live 
>> > cd version and I dont have floppy drive. I  setup everything manally. Here 
>> > is the config:  
>> > 
>> > 
>> > interfaces {
>> >    interface xl0 {
>> >       vif xl0 {
>> > 	address 192.168.2.1 {
>> > 		prefix-length: 24
>> > }
>> > }
>> > }
>> > }  
>> > 
>> > interfaces {
>> >    interface rl0 {
>> >       vif rl0 {
>> > 	address 192.168.3.1 {
>> > 		prefix-length: 24
>> > }
>> > }
>> > }
>> > }  
>> > 
>> > 
>> > fea {
>> >    unicast-forwarding4 {
>> >  }
>> > }  
>> > 
>> > protocols {
>> >    fib2mrib {
>> >       }
>> > }  
>> > 
>> >  ----- Here I ran commit and it succeeded.  
>> > 
>> > 
>> > plumbing {
>> >    mfea4 {  
>> > 
>> >       interface xl0 {
>> >          vif xl0 { 
>> > 
>> >          }
>> >       }  
>> > 
>> >       interface register_vif {
>> >          vif register_vif { 
>> > 
>> >          }
>> >       }  
>> > 
>> >  --- After this when I ran commit the same error occurred:
>> > 102 Command failed Cannot start vif xl0: underlying vif is not UP  
>> > 
>> > All interfaces are enabled (disable: false) and unicast forwarding worked 
>> > fine.  
>> > 
>> > Regards, Turbo  
>> > 
>> >   
>> > 
>> >   
>> > 
>> > 
>> > Pavlin Radoslavov writes:  
>> > 
>> >>> I am new in xorp. I would like to try th multicast forwarding, but a problem 
>> >>> occured.
>> >>>  - I use live cd version 1.4
>> >>            ~~~~~~~~~~~~~~~~~~~
>> >> This has to be 1.4-RC (Release Candidate), because the final 1.4
>> >> version is not released yet.  
>> >> 
>> >>>  - The network layout:  Host1 --- Xorp router --- Host2
>> >>>  - I succeeded in setting up unicast forwarding between the two host, but 
>> >>> when I tried to set multicast plumbing, or adding new protocol (IGMP, PIM), 
>> >>> after commit I  got the following error: 102 Command failed Cannot start vif 
>> >>> rl0: underlying vif is not UP
>> >>> I tried it on all interfaces an on different machines.
>> >>> Please help me, how can I resolve this problem. Thanks. 
>> >> 
>> >> Can you send your configuration file.
>> >> Also, did you configure/enable rl0 in the "mfea4" section as well.
>> >> Finally, is "rl0" connected to the network.  
>> >> 
>> >> Regards,
>> >> Pavlin  
>> >> 
>> >> _______________________________________________
>> >> Xorp-users mailing list
>> >> Xorp-users at xorp.org
>> >> http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users
>> >   
>> > 
>> > _______________________________________________
>> > Xorp-users mailing list
>> > Xorp-users at xorp.org
>> > http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users
>>   
>> 
>> _______________________________________________
>> Xorp-users mailing list
>> Xorp-users at xorp.org
>> http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users
 


?dv?zlettel: Elzer Zolt?n 

-------------- next part --------------
interfaces {

restore-original-config-on-shutdown: false

interface eth1 {

   description: "Ethernet"

   disable: false

   discard: false

   /* default-system-config */

   vif eth1 {

       disable: false

       address 192.168.3.1 {

         prefix-length: 24

             multicast-capable: true

         disable: false

       }

   }

}

interface eth0 {

   description: "Ethernet"

   disable: false

     discard: false

   /* default-system-config */

   vif eth0 {

       disable: false

       address 192.168.1.2 {

         prefix-length: 24

         multicast-capable: true

         disable: false

       }

   }

}



}

fea {

unicast-forwarding4 {

   disable: false

     }

}

plumbing {

  mfea4 {

   disable: false

   interface eth0 {

       vif eth0 {

         disable: false

       }

   }

 
   interface eth1 {

         vif eth1 {

               disable: false

      }

   }

   interface "register_vif" {

       vif "register_vif" {

         /* Note: this vif should be always enabled */

         disable: false

       }

   }

   traceoptions {

       flag {

           all {

         disable: false

           }

       }

   }

}

}

protocols {

igmp {

   disable: false

   interface eth0 {

       vif eth0 {

         disable: false

         version: 3

         enable-ip-router-alert-option-check: false

         query-interval: 125

         query-last-member-interval: 1

         query-response-interval: 10

         robust-count: 2

       }

   }

     
     interface eth1 {

         vif eth1 {

             disable: false

             version: 3

             enable-ip-router-alert-option-check: false

             query-interval: 125

             query-last-member-interval: 1

             query-response-interval: 10

             robust-count: 2

        }

     }

   traceoptions {

       flag {

            all {

         disable: false

            }

       }

   }

}

pimsm4 {

   disable: false

   interface eth0 {

       vif eth0 {

         disable: false

         enable-ip-router-alert-option-check: false

         dr-priority: 1

         hello-period: 30

         hello-triggered-delay: 5

       }

   }


     interface eth1 {

         vif eth1 {

             disable: false

             enable-ip-router-alert-option-check: false

             dr-priority: 1

             hello-period: 30

             hello-triggered-delay: 5

         }

     }

   interface register_vif {

       vif register_vif {

         /* Note: this vif should be always enabled */

         disable: false

       }

   }

/*
   bootstrap {

         disable: false

         cand-bsr {

               scope-zone 224.0.0.0/4 {

               cand-bsr-by-vif-name: "eth0"

               }

         }

         cand-rp {

               group-prefix 224.0.0.0/4 {

               cand-rp-by-vif-name: "eth0"

               }

         }

   }
*/
   switch-to-spt-threshold {

       /* approx. 1K bytes/s (10Kbps) threshold */

       disable: true

       interval: 100

       bytes: 102400

   }

   traceoptions {

       flag {

             all {

             disable: false

             }

       }

   }

}

fib2mrib {

   disable: false

}

}

From pavlin at icir.org  Sun Mar 18 00:47:04 2007
From: pavlin at icir.org (Pavlin Radoslavov)
Date: Sun, 18 Mar 2007 00:47:04 -0700
Subject: [Xorp-users] Cannot start vif + IPv6 multicast question
In-Reply-To: Message from "Elzer Zoltan" <ez201@mail2.selye.sk> of "Sat,
	17 Mar 2007 19:41:36 BST." <20070317184149.8355.qmail@selye.sk> 
Message-ID: <200703180747.l2I7l4qG007868@possum.icir.org>

> Hello Pavlin, As I wrote in my last letter, I managed to start the
> xorp. unfortunately I
> don't have the live CD's config file but I have the working config so I
> attached it to my mail.

Thank you for the info. The config file seems fine, so the problem
is somewhere else.
If you can send the "show interfaces" output that will be great,
because the information I have so far is not sufficient to track the
problem.

> I would like to ask another question. We would like to run the IPv6
> multicast forwarding. I browsed the net and found the IPv6 multicast patch
> for linux. I have the 2.6.7 kernel version and I patched it. but
> unfortunately the xorp's answer was an Error:
> add_multicast_vif() failed: IPv6 multicast routing not supported

The reason you see the above error is probably because
HAVE_IPV6_MULTICAST_ROUTING is not defined inside your config.h (in
the top-level XORP directory). This is conditionally defined based
on various checks when ./configure is executed. To track the
problem, could you send me the output from ./configure and the
content of config.log file. The config.log file will appear in the
top-level XORP directory after running ./configure.

Regards,
Pavlin

> I got this error because I added the mfea6 to the config file. I set the
> variables in the kernel config as the xorp manual said. But nothing. To add
> more I found your answer to a mail:
> http//mailman.icsi.berkeley.edu/pipermail/xorp-users/2007-January/001638.htm
> l
> and you said that there is no confirmation whether the patched Linux kernel
> really works with XORP. Have you tried it, is it working now properly or I
> didn't check something ? Thanks for your answer!

> Best regards
>                                                        Turbo Pavlin Radoslavov
> writes:
> >> Hello Pavlin  I managed to configure the router. I installed the xorp to
> >> the machine instead of live cd and I used one of the config file from
> >> mailing list. Thanks!                         Turbo
> > That's odd. I don't see the reason why it didn't work from LiveCD if
> > it worked when installed on the disk. If you still care about the LiveCD
> > issue, could you run the
> > "show interfaces" after you configure the interfaces, but before
> > configuring mfea4. Then please run it again after you try to
> > configure and commit the mfea4 configuration.
> > It will be great if you find a way of sending me both outputs :)
> > I care only about the interface that failed to be configured/started
> > by the MFEA. Thanks,
> > Pavlin
> >> Elzer Zoltan writes:  > Hello Pavlin  > > I still have the same problem. I
> >> dont have config file, because I use live > cd version and I dont have
> >> floppy drive. I  setup everything manally. Here > is the config:  > > >
> >> interfaces {
> >> >    interface xl0 {
> >> >       vif xl0 {
> >> > 	address 192.168.2.1 {
> >> > 		prefix-length: 24
> >> > }
> >> > }
> >> > }
> >> > }  > > interfaces {
> >> >    interface rl0 {
> >> >       vif rl0 {
> >> > 	address 192.168.3.1 {
> >> > 		prefix-length: 24
> >> > }
> >> > }
> >> > }
> >> > }  > > > fea {
> >> >    unicast-forwarding4 {
> >> >  }
> >> > }  > > protocols {
> >> >    fib2mrib {
> >> >       }
> >> > }  > >  ----- Here I ran commit and it succeeded.  > > > plumbing {
> >> >    mfea4 {  > >       interface xl0 {
> >> >          vif xl0 { > >          }
> >> >       }  > >       interface register_vif {
> >> >          vif register_vif { > >          }
> >> >       }  > >  --- After this when I ran commit the same error occurred:
> >> > 102 Command failed Cannot start vif xl0: underlying vif is not UP  > >
> >> All interfaces are enabled (disable: false) and unicast forwarding worked >
> >> fine.  > > Regards, Turbo  > >   > >   > > > Pavlin Radoslavov writes:  >
> >> >>> I am new in xorp. I would like to try th multicast forwarding, but a
> >> problem >>> occured.
> >> >>>  - I use live cd version 1.4
> >> >>            ~~~~~~~~~~~~~~~~~~~
> >> >> This has to be 1.4-RC (Release Candidate), because the final 1.4
> >> >> version is not released yet.  >> >>>  - The network layout:  Host1 ---
> >> Xorp router --- Host2
> >> >>>  - I succeeded in setting up unicast forwarding between the two host,
> >> but >>> when I tried to set multicast plumbing, or adding new protocol
> >> (IGMP, PIM), >>> after commit I  got the following error: 102 Command
> >> failed Cannot start vif >>> rl0: underlying vif is not UP
> >> >>> I tried it on all interfaces an on different machines.
> >> >>> Please help me, how can I resolve this problem. Thanks. >> >> Can you
> >> send your configuration file.
> >> >> Also, did you configure/enable rl0 in the "mfea4" section as well.
> >> >> Finally, is "rl0" connected to the network.  >> >> Regards,
> >> >> Pavlin  >> >> _______________________________________________
> >> >> Xorp-users mailing list
> >> >> Xorp-users at xorp.org
> >> >> http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users
> >> >   > > _______________________________________________
> >> > Xorp-users mailing list
> >> > Xorp-users at xorp.org
> >> > http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users
> >>   _______________________________________________
> >> Xorp-users mailing list
> >> Xorp-users at xorp.org
> >> http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users
>  ?dv?zlettel: Elzer Zolt?n
> _______________________________________________
> Xorp-users mailing list
> Xorp-users at xorp.org
> http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users


From guptalavi at gmail.com  Mon Mar 19 16:44:31 2007
From: guptalavi at gmail.com (Pallavi Gupta)
Date: Mon, 19 Mar 2007 15:44:31 -0800
Subject: [Xorp-users] Help! RIP Conf on xorp router wont work.
Message-ID: <22e357c80703191644l6431326dsa1da08f27bb51e26@mail.gmail.com>

Hi,

I am trying to set up a simple test network with two xorp routers
(Live CD, v1.3) connected using a crossover cable. The problem I am
encountering is that the routers are not exchanging information about
the loopbacks. So, I am unable to ping the other router's loopback. I
am pretty sure that I have configured everything correctly, but if
someone could point something that maybe I have missed........

when i use the show command for connected routes, it shows both
ethernet and loopbak, but when i use the show command as follows, it
doesnt show me any RIP routes. It should have 1 rip route to the other
router's loopback, right ?
> show route table ipv4 unicast rip

Router A :    Lo0  -   192.168.9.1  subnet /24
                   fxp0 -   192.168.10.1  subnet  /24
Router B :
                   fxp0 - 192.168.10.2    subnet / 24
                   Lo0 - 192.168.11.1    subnet /24

I am configuring the routers as below :

Router B :
# Set fea unicast-forwarding4 disable : false
# Set interfaces restore-original-config-on-shutdown : false
# Set interfaces interface lo0 vif lo0 address 192.168.11.1 prefix-length 24
# Set interfaces interface fxp0 vif fxp0 address 192.168.10.2 prefix-length 24
# set protocols rip interface fxp0 vif fxp0 address 192.168.10.2
# Set protocols rip interface lo0 vif lo0 address 192.168.11.1
# set protocols rip export connected
# set policy policy-statement connected term export from protocol : "connected"
# commit

configuration for router A is identical except for the ip address , of course.

Thanks sooo much.
Regards ,
Pallavi Gupta,
-- 
"Little things make big differences in life"


From atanu at ICSI.Berkeley.EDU  Wed Mar 21 11:58:27 2007
From: atanu at ICSI.Berkeley.EDU (Atanu Ghosh)
Date: Wed, 21 Mar 2007 11:58:27 -0700
Subject: [Xorp-users] Announcing XORP Release 1.4
Message-ID: <66492.1174503507@tigger.icir.org>

On behalf of the entire XORP team, I'm delighted to announce the XORP
1.4 Release, which is now available from <http://www.xorp.org>.

The major new feature with this release is:

* OSPFv3 (draft-ietf-ospf-ospfv3-update-14.txt)

In addition, this release contains numerous bug fixes.

There are still a number of non-critical bugs that we know about which
will not be addressed until the 1.5 release; these are documented in
the XORP Bugzilla database <http://www.xorp.org/bugzilla/index.cgi>.

In general, to test XORP, we run automated regression tests on a daily
basis with various operating systems and compilers. We also run a
number of PCs as XORP routers. We have enabled as many protocols as
feasible on those routers to test protocol interactions (for example a
BGP IPv6 multicast feed being used by PIM-SM). In addition, automated
scripts are run to externally toggle BGP peerings. Finally, we have
automated scripts that interact directly with the xorpsh to change the
configuration settings.

We have put significant effort into testing but obviously we have not
found all the problems. This is where you can help us to make XORP
more stable, by downloading and using it!

As always we'd welcome your comments - xorp-users at xorp.org is the
right place for general discussion, and private feedback to the XORP
core team can be sent to feedback at xorp.org.

 - The XORP Team

P.S.
Release notes are included below.

------------------------------------------------------------------
		XORP RELEASE NOTES

Release 1.4 (2007/03/20)
=========================
  ALL:
    - XORP now builds on DragonFlyBSD-1.8, FreeBSD-6.2, Linux Fedora
      Core6, Linux Debian-3.1 (sarge), NetBSD-3.1 and OpenBSD-4.0.

    - XORP now can be compiled with the Intel C/C++ compiler 9.* on
      Linux.

    - XORP now can be cross-compiled for IA-64, MIPS (Broadcom for
      Linksys WRT54G), PowerPC-603, Sparc64, and XScale processors.

    - Implementation of OSPFv3 (draft-ietf-ospf-ospfv3-update-14.txt).

    - Implementation of floating static routes (i.e., static routes
      for the same prefix with different next hop and metrics).

  CONFIGURATION:
    - Allow static routes to have "nexthop4" and "nexthop6" policy
      matching conditions in the "from" block.

    - Addition of new FEA configuration statements to retain XORP
      unicast forwarding entries on startup or shutdown:

      fea {
          unicast-forwarding4 {
              forwarding-entries {
                  retain-on-startup: false
                  retain-on-shutdown: false
              }
          }
          unicast-forwarding6 {
              forwarding-entries {
                  retain-on-startup: false
                  retain-on-shutdown: false
              }
          }
      }

      The default value for each statement is false.
      Note that those statements prevent the FEA itself from deleting
      the forwarding entries and does not prevent the RIB or any of the
      unicast routing protocols from deleting the entries on shutdown.

    - The "elements" policy statements for configuring sets of network
      routes have been deprecated:

      policy {
          network4-list foo {
              elements: "1.2.0.0/16,3.4.0.0/16"
          }
          network6-list bar {
              elements: "2222::/64,3333::/64"
          }
      }

      The new replacement statement is "network" and can be used to
      specify one element per line:

      policy {
          network4-list foo {
              network 1.2.0.0/16
              network 3.4.0.0/16
          }
          network6-list bar {
              network 2222::/64
              network 3333::/64
          }
      }

    - The following keywords are supported inside the policy
      configuration when comparing IPv4 or IPv6 network prefixes:
      exact, longer, orlonger, shorter, orshorter, not. For example:

      "network4 exact 10.0.0.0/8"     SAME AS "network4 == 10.0.0.0/8"
      "network4 longer 10.0.0.0/8"    SAME AS "network4 < 10.0.0.0/8"
      "network4 orlonger 10.0.0.0/8"  SAME AS "network4 <= 10.0.0.0/8"
      "network4 shorter 10.0.0.0/8"   SAME AS "network4 > 10.0.0.0/8"
      "network4 orshorter 10.0.0.0/8" SAME AS "network4 >= 10.0.0.0/8"
      "network4 not 10.0.0.0/8"       SAME AS "network4 != 10.0.0.0/8"

      The original operators are supported as well.

    - A floating static route (also called "qualified" by some router
      vendors) can be added with a configuration like:

      protocols {
          static {
              route 10.10.0.0/16 {
                  next-hop: 172.16.0.1
                  metric: 1
                  qualified-next-hop 172.17.0.2 {
                      metric: 10
                  }
              }
              interface-route 10.30.30.0/24 {
                  next-hop-interface: "rl0"
                  next-hop-vif: "rl0"
                  next-hop-router: 172.16.0.1
                  metric: 1
                  qualified-next-hop-interface rl1 {
                      qualified-next-hop-vif rl1 {
                          next-hop-router: 172.17.0.2
                          metric: 10
                      }
                  }
              }
          }
      }

  LIBXORP:
    - The XORP scheduler now has support for priority-based tasks.

  LIBXIPC:
    - No significant changes.

  LIBFEACLIENT:
    - No significant changes.

  XRL:
    - No significant changes.

  RTRMGR:
    - Bug fix in the semantics of the rtrmgr template %activate keyword.

  XORPSH:
    - No significant changes.

  POLICY:
    - Bug fix related to creating export policies that match protocol's
      its own routes (e.g., a policy that modifies the BGP routes
      exported to its peers).

    - Various other bug fixes.

  FEA/MFEA:
    - Fix the routing socket based mechanism (used by BSD-derived
      systems) for obtaining the interface name (toward the destination)
      for a routing entry.

    - Apply a performance improvement when configuring a large number of
      interfaces/VIFs, each of them with the "default-system-config"
      configuration statement.

    - Bug fix related to atomically modifying the IP address of an interface.

  RIB:
    - Bug fix related to (not) installing redundant host-specific
      entries for the other side of a point-to-point interface if the
      netmask for the interface covers the host-specific entry.

  RIP:
    - No significant changes.

  OSPF:
    - OSPFv3 is now available.

    - The OSPFv3 protocol requires that link-local addresses are used,
      therefore it is necessary to configure a link-local address for
      each interface, this restriction will be removed in the future.

    - The OSPFv3 configuration allows multiple instances to be configured
      however only one instance will be created. Configuring multiple
      OSPFv3 instances is guaranteed to cause problems.

    - Bug fix related to the processing of previously generated LSAs
      on startup has been fixed. Restarting a router that was the
      designated router could exhibit this problem.
      
    - Bug fix on a broadcast interface if the router was not the
      designated router then the nexthop was incorrectly
      unconditionally set to the designated router; introducing an
      unnecessary extra hop.

  BGP:
    - BGP has taken advantage of the priority-based tasks in the XORP
      scheduler and background tasks are run at a low priority;
      leading to improved performance.

  STATIC_ROUTES:
    - Bug fix related to declaring some of the policy matching
      conditions in the "from" block.

  MLD/IGMP:
    - Bug fix related to atomically modifying the IP address of an
      interface.

    - Bug fix related to ignoring protocol messages that are not
      recognized by the configured protocol version on an interface.

    - Ignore control messages if the source address is not directly
      connected.

    - Don't send the periodic Group-Specific or Group-and-Source-Specific
      Queries for entries that are in IGMPv1 mode.

  PIM-SM:
    - Bug fix related to atomically modifying the IP address of an
      interface.

    - The PIM-SM control messages do not include the IP Router Alert
      option anymore, because it has been included from the newer
      revisions of the PIM-SM protocol specification (RFC 4601 and
      draft-ietf-pim-sm-bsr-09.txt,.ps).

    - Don't send PIM Hello message with DR Priority of 0 when shutting
      down an interface, because this is not part of the protocol
      specification.

  FIB2MRIB:
    - Bug fix related to updating the interface and vif name of a
      forwarding entry received from the FEA.

  CLI:
    - Performance improvement if the CLI is processing a large amount
      of data. E.g., if xorpsh is used in a pipe like:

      cat commands.txt | xorpsh

  SNMP:
    - Bug fix with the snmpd arguments when sampling whether snmpd
      can start and its version is >= 5.2.


From malazarte.maritess at gmail.com  Thu Mar 22 01:48:12 2007
From: malazarte.maritess at gmail.com (Maritess Malazarte)
Date: Thu, 22 Mar 2007 16:48:12 +0800
Subject: [Xorp-users] SNMP Compilation Error
Message-ID: <5bef59280703220148o2f0a14a5v232324ba80f399ef@mail.gmail.com>

Hi,

I've downloaded the latest version Xorp 1.4 and I'm trying to compile is
using FreeBSD 6.1 as my operating system.  I modified my bootstrap's
following entries:
ACLOCAL=${ACLOCAL:-"aclocal15"}
AUTOCONF=${AUTOCONF:-"autoconf259"}
AUTOHEADER=${AUTOHEADER:-"autoheader259"}
AUTOMAKE=${AUTOMAKE:-"automake15"}
then I ran configure --with-snmp
When I ran gmake, an error occurred.  Here is what was outputted.

/bin/sh ./libtool --mode=link g++  -DNETSNMP_NO_INLINE -g -W -Wall
-Wwrite-strings -Wcast-qual -Werror -Wpointer-arith -Wcast-align
-Woverloaded-virtual -ftemplate-depth-22   -o libnetsnmpxorp.la -rpath
/usr/local/xorp/mibs/. -avoid-version -fPIC
xorpevents.lo../libxipc/libxipc.la ../libxorp/libxorp.la
../libcomm/libcomm.la -lcrypto
rm -fr .libs/libnetsnmpxorp.la .libs/libnetsnmpxorp.* .libs/libnetsnmpxorp.*
g++ -shared  xorpevents.lo -Wl,--whole-archive ../libxipc/.libs/libxipc.a
../libxorp/.libs/libxorp.a ../libcomm/.libs/libcomm.a
-Wl,--no-whole-archive  ../libxipc/.libs/libxipc.a
../libxorp/.libs/libxorp.a ../libcomm/.libs/libcomm.a -lcrypto    -lc
-Wl,-soname -Wl,libnetsnmpxorp -o .libs/libnetsnmpxorp
/usr/bin/ld: ../libxipc/.libs/libxipc.a(hmac_md5.o): relocation R_X86_64_32S
can not be used when making a shared object; recompile with -fPIC
../libxipc/.libs/libxipc.a(hmac_md5.o): could not read symbols: Bad value

Can you tell me what I'm doing wrong here?

Thanks.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20070322/c03f5652/attachment.html 

From agaviola at infoweapons.com  Thu Mar 22 06:39:25 2007
From: agaviola at infoweapons.com (Archimedes S. Gaviola)
Date: Thu, 22 Mar 2007 21:39:25 +0800
Subject: [Xorp-users] XORP IGMP/MLD Proxy
Message-ID: <008201c76c87$9145bd40$0b02030a@cebu.infoweapons.com>

To Who It May Concerned:
 
I have read from the TODO file of MLD6IGMP directory on XORP RC 1.4 about
IGMP/MLD proxy
 
* Implement an MLD/IGMP "proxy" where the Join/Leave messages from one
interface are forwarded on another interface. This may be useful with
satellite routers which do support IGMP, but do NOT support PIM-SM for
example.
 
Is this pertaining to RFC 4605 http://tools.ietf.org/rfc/rfc4605.txt? When
is this feature be implemented?
 
Thank you very much.
 
Sincerely Yours,
 
Archimedes S. Gaviola
Network Engineer
InfoWeapons Corporation
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20070322/b018249f/attachment.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 3353 bytes
Desc: not available
Url : http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20070322/b018249f/attachment.bin 

From pavlin at icir.org  Thu Mar 22 13:19:56 2007
From: pavlin at icir.org (Pavlin Radoslavov)
Date: Thu, 22 Mar 2007 13:19:56 -0700
Subject: [Xorp-users] Help! RIP Conf on xorp router wont work.
In-Reply-To: Message from "Pallavi Gupta" <guptalavi@gmail.com> of "Mon,
	19 Mar 2007 15:44:31 -0800."
	<22e357c80703191644l6431326dsa1da08f27bb51e26@mail.gmail.com> 
Message-ID: <200703222019.l2MKJuGk099593@possum.icir.org>

[Apology for the late reply; we were occupied with the 1.4 release]

> I am trying to set up a simple test network with two xorp routers
> (Live CD, v1.3) connected using a crossover cable. The problem I am
> encountering is that the routers are not exchanging information about
> the loopbacks. So, I am unable to ping the other router's loopback. I
> am pretty sure that I have configured everything correctly, but if
> someone could point something that maybe I have missed........
> 
> when i use the show command for connected routes, it shows both
> ethernet and loopbak, but when i use the show command as follows, it
> doesnt show me any RIP routes. It should have 1 rip route to the other
> router's loopback, right ?
> > show route table ipv4 unicast rip
> 
> Router A :    Lo0  -   192.168.9.1  subnet /24
>                    fxp0 -   192.168.10.1  subnet  /24
> Router B :
>                    fxp0 - 192.168.10.2    subnet / 24
>                    Lo0 - 192.168.11.1    subnet /24
> 
> I am configuring the routers as below :
> 
> Router B :
> # Set fea unicast-forwarding4 disable : false
> # Set interfaces restore-original-config-on-shutdown : false
> # Set interfaces interface lo0 vif lo0 address 192.168.11.1 prefix-length 24
> # Set interfaces interface fxp0 vif fxp0 address 192.168.10.2 prefix-length 24
> # set protocols rip interface fxp0 vif fxp0 address 192.168.10.2
> # Set protocols rip interface lo0 vif lo0 address 192.168.11.1
> # set protocols rip export connected
> # set policy policy-statement connected term export from protocol : "connected"
> # commit
> 
> configuration for router A is identical except for the ip address , of course.

I tried to replicate the problem, but I couldn't (i.e., I was able
to ping the loopback of the other router).
Note that in my tests I was using the latest XORP code (1.4
release), but not from LiveCD. Below I am including the
configuration from one of the routers.

Could you download the 1.4 LiveCD and test whether you still have
the problem.

If yes, one way to start debugging the problem is to run tcpdump on
the link connecting the two routers. If the exporting of connected
routes is fine you should see RIPv2-resp packets with both connected
subnets included. E.g.:

tcpdump -i fxp0 -n -vvv -s 0 -x proto \\udp and port 520

Regards,
Pavlin


/************************************/
interfaces {
    interface lo0 {
	vif lo0 {
	    address 192.168.11.1 {
		prefix-length 24
	    }
	}
    }
    interface rl0 {
	vif rl0 {
	    address 10.10.10.10 {
		prefix-length 24
	    }
	}
    }
}

fea {
    unicast-forwarding4 {
	disable: false
    }
}

policy {
    policy-statement connected {
	term export {
	    from {
		protocol: "connected"
	    }
	}
    }
}

protocols {
    rip {
	export: "connected"
	interface lo0 {
	    vif lo0 {
		address 192.168.11.1 {
		    disable: false
		}
	    }
	}
	interface rl0 {
	    vif rl0 {
		address 10.10.10.10 {
		    disable: false
		}
	    }
	}
    }
}
/************************************/


From pavlin at icir.org  Thu Mar 22 15:43:56 2007
From: pavlin at icir.org (Pavlin Radoslavov)
Date: Thu, 22 Mar 2007 15:43:56 -0700
Subject: [Xorp-users] XORP IGMP/MLD Proxy
In-Reply-To: Message from "Archimedes S. Gaviola" <agaviola@infoweapons.com> 
	of "Thu, 22 Mar 2007 21:39:25 +0800."
	<008201c76c87$9145bd40$0b02030a@cebu.infoweapons.com> 
Message-ID: <200703222243.l2MMhu4I016321@possum.icir.org>

> I have read from the TODO file of MLD6IGMP directory on XORP RC 1.4 about
> IGMP/MLD proxy
>  
> * Implement an MLD/IGMP "proxy" where the Join/Leave messages from one
> interface are forwarded on another interface. This may be useful with
> satellite routers which do support IGMP, but do NOT support PIM-SM for
> example.
>  
> Is this pertaining to RFC 4605 http://tools.ietf.org/rfc/rfc4605.txt? When
> is this feature be implemented?

Yes, RFC 4605 is what we have in mind.
Unfortunately we cannot give any estimate when it will be
implemented due to our (very) limited resources.

FYI, I just replaced the TODO entry with a Bugzilla entry:
http://www.xorp.org/bugzilla/show_bug.cgi?id=700

You can add yourself to the CC list for that entry so you will get
automated email notifications whenever there is any change in the
status.

Regards,
Pavlin


From pavlin at icir.org  Thu Mar 22 16:34:36 2007
From: pavlin at icir.org (Pavlin Radoslavov)
Date: Thu, 22 Mar 2007 16:34:36 -0700
Subject: [Xorp-users] SNMP Compilation Error
In-Reply-To: Message from "Maritess Malazarte" <malazarte.maritess@gmail.com> 
	of "Thu, 22 Mar 2007 16:48:12 +0800."
	<5bef59280703220148o2f0a14a5v232324ba80f399ef@mail.gmail.com> 
Message-ID: <200703222334.l2MNYaHS016818@possum.icir.org>

Maritess Malazarte <malazarte.maritess at gmail.com> wrote:

> Hi,
> 
> I've downloaded the latest version Xorp 1.4 and I'm trying to compile is
> using FreeBSD 6.1 as my operating system.  I modified my bootstrap's
> following entries:
> ACLOCAL=${ACLOCAL:-"aclocal15"}
> AUTOCONF=${AUTOCONF:-"autoconf259"}
> AUTOHEADER=${AUTOHEADER:-"autoheader259"}
> AUTOMAKE=${AUTOMAKE:-"automake15"}

If you only need to compile XORP, then you don't need to modify or
execute the "bootstrap" script. This script is used only if you do XORP
development.

> then I ran configure --with-snmp
> When I ran gmake, an error occurred.  Here is what was outputted.
> 
> /bin/sh ./libtool --mode=link g++  -DNETSNMP_NO_INLINE -g -W -Wall
> -Wwrite-strings -Wcast-qual -Werror -Wpointer-arith -Wcast-align
> -Woverloaded-virtual -ftemplate-depth-22   -o libnetsnmpxorp.la -rpath
> /usr/local/xorp/mibs/. -avoid-version -fPIC
> xorpevents.lo../libxipc/libxipc.la ../libxorp/libxorp.la
> ../libcomm/libcomm.la -lcrypto
> rm -fr .libs/libnetsnmpxorp.la .libs/libnetsnmpxorp.* .libs/libnetsnmpxorp.*
> g++ -shared  xorpevents.lo -Wl,--whole-archive ../libxipc/.libs/libxipc.a
> ../libxorp/.libs/libxorp.a ../libcomm/.libs/libcomm.a
> -Wl,--no-whole-archive  ../libxipc/.libs/libxipc.a
> ../libxorp/.libs/libxorp.a ../libcomm/.libs/libcomm.a -lcrypto    -lc
> -Wl,-soname -Wl,libnetsnmpxorp -o .libs/libnetsnmpxorp
> /usr/bin/ld: ../libxipc/.libs/libxipc.a(hmac_md5.o): relocation R_X86_64_32S
> can not be used when making a shared object; recompile with -fPIC
> ../libxipc/.libs/libxipc.a(hmac_md5.o): could not read symbols: Bad value
> 
> Can you tell me what I'm doing wrong here?

Please use the --enable-shared flag as well and see whether you
still have the problem:

./configure --with-snmp --enable-shared

Though, first you need to "gmake clean" the previous compilation.

BTW, what hardware/CPU are you running?
I was able to replicate the problem on AMD-64 with FreeBSD-6.2, but
I'd like to find whether the problem is specific to 64-bits
hardware.

Thanks,
Pavlin


From agaviola at infoweapons.com  Thu Mar 22 19:14:48 2007
From: agaviola at infoweapons.com (Archimedes S. Gaviola)
Date: Fri, 23 Mar 2007 10:14:48 +0800
Subject: [Xorp-users] XORP IGMP/MLD Proxy
In-Reply-To: <200703222243.l2MMhu4I016321@possum.icir.org>
References: Message from "Archimedes S. Gaviola" <agaviola@infoweapons.com> of
	"Thu, 22 Mar 2007 21:39:25 +0800."
	<008201c76c87$9145bd40$0b02030a@cebu.infoweapons.com>
	<200703222243.l2MMhu4I016321@possum.icir.org>
Message-ID: <000b01c76cf1$17d212f0$0b02030a@cebu.infoweapons.com>

Pavlin,

Thanks for your response. I was concerned on this functionality because I am
planning for our remote site's XORP multicast router to act as an IGMPv3
proxy without PIM-SSM running. Thank you for CC'ing me in the Bugzilla
mailing list to keep me notified and there's no hurry on this functionality.
For now, I can still use PIM-SSM fucntionality for our remote's site
multicast router.

Sincerely Yours,

Archimedes S. Gaviola
Network Engineer
InfoWeapons Corporation

-----Original Message-----
From: Pavlin Radoslavov [mailto:pavlin at icir.org] 
Sent: Friday, March 23, 2007 6:44 AM
To: Archimedes S. Gaviola
Cc: xorp-users at xorp.org
Subject: Re: [Xorp-users] XORP IGMP/MLD Proxy 

> I have read from the TODO file of MLD6IGMP directory on XORP RC 1.4 
> about IGMP/MLD proxy
>  
> * Implement an MLD/IGMP "proxy" where the Join/Leave messages from one 
> interface are forwarded on another interface. This may be useful with 
> satellite routers which do support IGMP, but do NOT support PIM-SM for 
> example.
>  
> Is this pertaining to RFC 4605 http://tools.ietf.org/rfc/rfc4605.txt? 
> When is this feature be implemented?

Yes, RFC 4605 is what we have in mind.
Unfortunately we cannot give any estimate when it will be implemented due to
our (very) limited resources.

FYI, I just replaced the TODO entry with a Bugzilla entry:
http://www.xorp.org/bugzilla/show_bug.cgi?id=700

You can add yourself to the CC list for that entry so you will get automated
email notifications whenever there is any change in the status.

Regards,
Pavlin

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 3353 bytes
Desc: not available
Url : http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20070323/4f635b08/attachment.bin 

From shameemarshad at gmail.com  Mon Mar 26 10:51:56 2007
From: shameemarshad at gmail.com (shameem arshad)
Date: Mon, 26 Mar 2007 23:21:56 +0530
Subject: [Xorp-users] Problems in running XORP
Message-ID: <f4606860703261051o5df2ee2ft222ed647fa87f050@mail.gmail.com>

Hello, I am a new user.
I have compiled XORP but unable to run it.
I have problems with executable files (XORPSH and RTR_MGR).
I am using LINUX platform. How should I run these executable files?
                          As far as the Live CD is concerned, I have
burn files but it is not booting on my PC. What should I do in this
case?

Thank You?..


From shameemarshad at gmail.com  Mon Mar 26 10:30:38 2007
From: shameemarshad at gmail.com (shameem arshad)
Date: Mon, 26 Mar 2007 23:00:38 +0530
Subject: [Xorp-users] Problems in running XORP
Message-ID: <f4606860703261030tcffbbe7s6f62b6a42bc7af0d@mail.gmail.com>

Hello, I am a new user.
I have compiled XORP but unable to run it.
I have problems with executable files (XORPSH and RTR_MGR).
I am using LINUX platform. How should I run these executable files?
                           As far as the Live CD is concerned, I have
burn files but it is not booting on my PC. What should I do in this
case?

Thank You?..


From pavlin at icir.org  Mon Mar 26 13:54:44 2007
From: pavlin at icir.org (Pavlin Radoslavov)
Date: Mon, 26 Mar 2007 13:54:44 -0700
Subject: [Xorp-users] Problems in running XORP
In-Reply-To: Message from "shameem arshad" <shameemarshad@gmail.com> of "Mon,
	26 Mar 2007 23:00:38 +0530."
	<f4606860703261030tcffbbe7s6f62b6a42bc7af0d@mail.gmail.com> 
Message-ID: <200703262054.l2QKsiTf088100@possum.icir.org>

> Hello, I am a new user.
> I have compiled XORP but unable to run it.
> I have problems with executable files (XORPSH and RTR_MGR).
> I am using LINUX platform. How should I run these executable files?

Please have a look at the following document. It should have enough
information to get you started:

http://www.xorp.org/getting_started.html

If you are still having problems running XORP, please send more
details about the issue: the command that you use to run XORP and
the exact error messages you are seeing.

>                            As far as the Live CD is concerned, I have
> burn files but it is not booting on my PC. What should I do in this
> case?

What OS did you use and what software/command did you use to burn
the LiveCD?
Note that the LiveCD.iso.gz download file is compressed so first you
need to uncompress it before burning the CD:

gunzip LiveCD.iso.gz

Regards,
Pavlin


From njh at ecs.soton.ac.uk  Tue Mar 27 10:21:32 2007
From: njh at ecs.soton.ac.uk (Nicholas J Humfrey)
Date: Tue, 27 Mar 2007 18:21:32 +0100
Subject: [Xorp-users] IPv6 Router Advertisements?
Message-ID: <2CE52DD9-BC30-4136-BA78-014059D9EE9D@ecs.soton.ac.uk>

Hi,

I am running XORP version 1.4 on Debian Linux/unstable.I am trying to  
configure XORP to be an IPv4 multicast router on the end of a tunnel  
to a Cisco and an IPv6 Unicast & Multicast router on the end of  
another tunnel to a Cisco.

To complicate matters, my IPv4 hosts are part of a large (/22)  
subnet. So I have my box setup as an Ethernet Bridge and using  
ebtables to prevent the multicast and IPv6 traffic leaking into the  
rest of the subnet. I wish it didn't have to be this way but my  
University's network staff won't give me my own subnet.

https://www.surgeradio.co.uk/wiki/index.php/Image:Surge-network- 
topology.png


Has anyone else had any success with such a setup?


Does XORP support IPv6 Router Advertisements? I can't see any mention  
of it in the manual, but I thought it would be something that would  
be built-in. Do I have to use radvd instead?


nick.


From pavlin at icir.org  Tue Mar 27 11:55:44 2007
From: pavlin at icir.org (Pavlin Radoslavov)
Date: Tue, 27 Mar 2007 11:55:44 -0700
Subject: [Xorp-users] IPv6 Router Advertisements?
In-Reply-To: Message from Nicholas J Humfrey <njh@ecs.soton.ac.uk> of "Tue,
	27 Mar 2007 18:21:32 BST."
	<2CE52DD9-BC30-4136-BA78-014059D9EE9D@ecs.soton.ac.uk> 
Message-ID: <200703271855.l2RItiU8010937@possum.icir.org>

> I am running XORP version 1.4 on Debian Linux/unstable.I am trying to  
> configure XORP to be an IPv4 multicast router on the end of a tunnel  
> to a Cisco and an IPv6 Unicast & Multicast router on the end of  
> another tunnel to a Cisco.

If you want to use Linux as IPv6 multicast router, you should know
that the default Linux kernel doesn't have IPv6 multicast forwarding
support. You need to use the USAGI kernel instead which has
Mickael Hoerdt's patch included. See the following email for
additional info:
http://mailman.icsi.berkeley.edu/pipermail/xorp-users/2005-November/000901.html

> To complicate matters, my IPv4 hosts are part of a large (/22)  
> subnet. So I have my box setup as an Ethernet Bridge and using  
> ebtables to prevent the multicast and IPv6 traffic leaking into the  
> rest of the subnet. I wish it didn't have to be this way but my  
> University's network staff won't give me my own subnet.
> 
> https://www.surgeradio.co.uk/wiki/index.php/Image:Surge-network- 
> topology.png
> 
> 
> Has anyone else had any success with such a setup?

Unfortunately I don't know whether such setup will work.

> 
> Does XORP support IPv6 Router Advertisements? I can't see any mention  
> of it in the manual, but I thought it would be something that would  
> be built-in. Do I have to use radvd instead?

No, it doesn't send IPv6 Router Advertisements, but yes it
should. In the mean time you need to use radvd instead.
FYI, I just created a Bugzilla entry for that new feature:
http://www.xorp.org/bugzilla/show_bug.cgi?id=702

Regards,
Pavlin


From ez201 at mail2.selye.sk  Tue Mar 27 12:55:17 2007
From: ez201 at mail2.selye.sk (Elzer Zoltan)
Date: Tue, 27 Mar 2007 21:55:17 +0200
Subject: [Xorp-users] Xorp HIP support
Message-ID: <20070327195517.29352.qmail@selye.sk>

Hello Pavlin! 

I have a difficult(for me) question. I want to modify xorp mld6igmp part, to 
accept and use HIT identifiers (Host Identity Tag in Host Identity Protocol) 
besides IP addresses. These identifiers are like IPv6 addresses, 128 bit 
long. I have already written a small client which can send HIT identifiers 
in ICMP6 packets. 

My aim is that xorp accepts the ICMP6 package which contain HIT identifiers 
and forward them toward PIM module. Its a difficult task to modify xorp like 
this, or its possible at all? 

I have already looked into the source codes. There is something which I 
don&#8217;t understand.
 - how does mld module call pim module?
 - how does xorp send query message to the interfaces? (I followed the query 
sending, but I lost in mfea_xif.cc)
 - where(in which function) does xorp receive the raw message from socket? 

I hope I was clear:) 

                                            Regards, Turbo 


From pavlin at icir.org  Tue Mar 27 15:12:26 2007
From: pavlin at icir.org (Pavlin Radoslavov)
Date: Tue, 27 Mar 2007 15:12:26 -0700
Subject: [Xorp-users] Xorp HIP support
In-Reply-To: Message from "Elzer Zoltan" <ez201@mail2.selye.sk> of "Tue,
	27 Mar 2007 21:55:17 +0200." <20070327195517.29352.qmail@selye.sk> 
Message-ID: <200703272212.l2RMCQOW012566@possum.icir.org>

> I have a difficult(for me) question. I want to modify xorp mld6igmp part, to 
> accept and use HIT identifiers (Host Identity Tag in Host Identity Protocol) 
> besides IP addresses. These identifiers are like IPv6 addresses, 128 bit 
> long. I have already written a small client which can send HIT identifiers 
> in ICMP6 packets. 
> 
> My aim is that xorp accepts the ICMP6 package which contain HIT identifiers 
> and forward them toward PIM module. Its a difficult task to modify xorp like 
> this, or its possible at all? 

Yes, it should be possible. How difficult? Well, it won't be few
lines of code, but it won't be a major refactoring either.

> I have already looked into the source codes. There is something which I 
> don&#8217;t understand.

First, I presume that your ICMP6 packets will have a new type.
In that case the first thing to do is to modify the MFEA so it won't
block them. Inside fea/mfea_proto_comm.cc method
ProtoComm::open_proto_sockets() there is code like:

#ifdef HAVE_IPV6_MULTICAST_ROUTING
            if (module_id() == XORP_MODULE_MLD6IGMP) {
                // Filter all non-MLD ICMPv6 messages
                ICMP6_FILTER_SETBLOCKALL(&filter);
                ICMP6_FILTER_SETPASS(MLD_LISTENER_QUERY, &filter);
                ICMP6_FILTER_SETPASS(MLD_LISTENER_REPORT, &filter);
                ICMP6_FILTER_SETPASS(MLD_LISTENER_DONE, &filter);
                ICMP6_FILTER_SETPASS(MLD_MTRACE_RESP, &filter);
                ICMP6_FILTER_SETPASS(MLD_MTRACE, &filter);
#ifdef MLDV2_LISTENER_REPORT
                ICMP6_FILTER_SETPASS(MLDV2_LISTENER_REPORT, &filter);
#endif
            }
#endif // HAVE_IPV6_MULTICAST_ROUTING

You need to add another ICMP6_FILTER_SETPASS(YOUR_ICMP6_TYPE, &filter);
for your ICMPv6 messages type.

>  - how does mld module call pim module?

The PIM module registeres interest in the MLD/IGMP module using the
mld6igmp/0.1/add_protocol{4,6} XRLs.

Then, whenever the MLD/IGMP module detects multicast membership
change, it uses the mld6igmp_client/0.1/add_membership{4,6} and 
mld6igmp_client/0.1/delete_membership{4,6} XRLs to inform the PIM
module about the change.

Hence, as you see there is no XRL interface to forward control
packets from MLD/IGMP to PIM. You need to add such interface, and
the easiest way is to modify the xrl/interfaces/mld6igmp_client.xif
XRL interface. Then, inside the mld6igmp.xif interface you need to
add another set of add/delete XRLs that will allow PIM to register
interest with MLD/IGMP in receiving specific control packets.

>  - how does xorp send query message to the interfaces? (I followed the query 
> sending, but I lost in mfea_xif.cc)

It uses the mfea/0.1/send_protocol_message{4,6} XRLs. The payload
goes via XRL to the MFEA, and then the MFEA transmits the message on
the wire using the kernel API.

>  - where(in which function) does xorp receive the raw message from socket? 

The multicast specific protocols use the MFEA for sending and
receiving raw IP packets. The rest of the protocols that need to
send/receive raw IP packets (currently only OSPF) use the FEA raw IP
socket interface (FYI, the reason there are two mechanisms for
sending/receiving raw IP packets is historic; in the future there
should be one single mechanism).

The particular function inside the MFEA that reads the packets is
ProtoComm::proto_socket_read() inside fea/mfea_proto_comm.cc
The corresponding function inside the FEA is
RawSocket::proto_socket_read() inside fea/rawsock.cc.

Then the paylod from the received packet is sent by using XRLs to
the interested parties.
For the MFEA clients, the XRL is
mfea_client/0.1/recv_protocol_message{4,6}, while for the FEA
clients the XRL is raw_packet{4,6}_client/0.1/recv.

BTW, currently there is no mechanism to send/receive raw link-level
packets, but it is on our TODO list.

Regards,
Pavlin


From malazarte.maritess at gmail.com  Thu Mar 29 20:39:26 2007
From: malazarte.maritess at gmail.com (Maritess Malazarte)
Date: Fri, 30 Mar 2007 11:39:26 +0800
Subject: [Xorp-users] Testing snmp
Message-ID: <5bef59280703292039na6aabc7rd737d37af47c68b@mail.gmail.com>

Hi,

I'm new to using net-snmp but I would like to test using the snmp in Xorp.
I've already managed to compile Xorp 1.4 with the --with-snmp option.  But I
cannot find where the bgp4_mib_1657.so goes.  I haven't changed any of the
code.  I was expecting it to be in /usr/local/xorp/mibs or if not in the
source directory xorp-1.4/mibs.

The following were the steps I did:
1. ./configure --with-snmp --enable-shared
2. gmake
3. gmake install

Could you give me guidance on what I'm doing wrong or what I'm supposed to
expect?

Thanks,
Maritess
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20070330/c48b34a4/attachment.html 

From malazarte.maritess at gmail.com  Fri Mar 30 01:27:05 2007
From: malazarte.maritess at gmail.com (Maritess Malazarte)
Date: Fri, 30 Mar 2007 16:27:05 +0800
Subject: [Xorp-users] Testing snmp (cont'd)
Message-ID: <5bef59280703300127g6e165391sc0d2a988febe753e@mail.gmail.com>

Just an update on this.  I first tested this on FreeBSD 6.1 AMD64.  I tried
the same process this time on FreeBSD 6.1 i386.
The files xorp_if_mib_module.so, bgp4_mib_1657.so were generated.  Has
anyone tested Xorp's snmp modules on AMD64 already?  I would really
appreciate any tips, clues, help I can get regarding this matter.

---------- Forwarded message ----------
From: Maritess Malazarte <malazarte.maritess at gmail.com>
Date: Mar 30, 2007 11:39 AM
Subject: Testing snmp
To: xorp-users at xorp.org

Hi,

I'm new to using net-snmp but I would like to test using the snmp in Xorp.
I've already managed to compile Xorp 1.4 with the --with-snmp option.  But I
cannot find where the bgp4_mib_1657.so goes.  I haven't changed any of the
code.  I was expecting it to be in /usr/local/xorp/mibs or if not in the
source directory xorp-1.4/mibs.

The following were the steps I did:
1. ./configure --with-snmp --enable-shared
2. gmake
3. gmake install

Could you give me guidance on what I'm doing wrong or what I'm supposed to
expect?

Thanks,
Maritess
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20070330/02d87412/attachment.html 

From pavlin at icir.org  Fri Mar 30 20:09:20 2007
From: pavlin at icir.org (Pavlin Radoslavov)
Date: Fri, 30 Mar 2007 20:09:20 -0700
Subject: [Xorp-users] Testing snmp
In-Reply-To: Message from "Maritess Malazarte" <malazarte.maritess@gmail.com> 
	of "Fri, 30 Mar 2007 11:39:26 +0800."
	<5bef59280703292039na6aabc7rd737d37af47c68b@mail.gmail.com> 
Message-ID: <200703310309.l2V39KPq077165@possum.icir.org>

> I'm new to using net-snmp but I would like to test using the snmp in Xorp.
> I've already managed to compile Xorp 1.4 with the --with-snmp option.  But I
> cannot find where the bgp4_mib_1657.so goes.  I haven't changed any of the
> code.  I was expecting it to be in /usr/local/xorp/mibs or if not in the
> source directory xorp-1.4/mibs.
> 
> The following were the steps I did:
> 1. ./configure --with-snmp --enable-shared
> 2. gmake
> 3. gmake install
> 
> Could you give me guidance on what I'm doing wrong or what I'm supposed to
> expect?

The bgp4_mib_1657.so file is suppose to be installed under
/usr/local/xorp/mibs .
I just tried it on FreeBSD-6.2 amd64 and the file was installed as
expected in that directory.
Make sure that you start with a clean directory just in case there
is no some leftover state.

For reference, below are some of the log messages when I run
"gmake install":


g++ -shared   bgp4_mib_1657.lo bgp4_mib_1657_bgpversion.lo bgp4_mib_1657_bgplocalas.lo bgp4_mib_1657_bgpidentifier.lo bgp4_mib_1657_bgppeertable.lo bgp4_mib_1657_bgp4pathattrtable.lo bgp4_mib_xrl_target.lo -Wl,--whole-archive ../xrl/targets/.libs/libbgp4mibbase.al ../xrl/interfaces/.libs/libbgpxif.al -Wl,--no-whole-archive  -L/usr/local/xorp/mibs/. -lnetsnmpxorp ../xrl/targets/.libs/libbgp4mibbase.al ../xrl/interfaces/.libs/libbgpxif.al -lcrypto  -Wl,-soname -Wl,bgp4_mib_1657.so -o .libs/bgp4_mib_1657.so
/usr/bin/install -c .libs/bgp4_mib_1657.soT /usr/local/xorp/mibs/./bgp4_mib_1657.so
/usr/bin/install -c .libs/bgp4_mib_1657.lai /usr/local/xorp/mibs/./bgp4_mib_1657.la

Note that the bgp4_mib_1657.so file is compiled inside the
local mibs/.libs directory but is installed inside the
/usr/local/xorp/mibs directory.

Regards,
Pavlin


From pavlin at icir.org  Fri Mar 30 20:36:50 2007
From: pavlin at icir.org (Pavlin Radoslavov)
Date: Fri, 30 Mar 2007 20:36:50 -0700
Subject: [Xorp-users] Testing snmp (cont'd)
In-Reply-To: Message from "Maritess Malazarte" <malazarte.maritess@gmail.com> 
	of "Fri, 30 Mar 2007 16:27:05 +0800."
	<5bef59280703300127g6e165391sc0d2a988febe753e@mail.gmail.com> 
Message-ID: <200703310336.l2V3ao9u077452@possum.icir.org>

Maritess Malazarte <malazarte.maritess at gmail.com> wrote:

> Just an update on this.  I first tested this on FreeBSD 6.1 AMD64.  I tried
> the same process this time on FreeBSD 6.1 i386.
> The files xorp_if_mib_module.so, bgp4_mib_1657.so were generated.  Has
> anyone tested Xorp's snmp modules on AMD64 already?  I would really
> appreciate any tips, clues, help I can get regarding this matter.

See my reply to your previous email on the subject.
Yes, I was using AMD64 (on FreeBSD 6.2) and I didn't have problems
generating  the above two modules.

Regards,
Pavlin

> ---------- Forwarded message ----------
> From: Maritess Malazarte <malazarte.maritess at gmail.com>
> Date: Mar 30, 2007 11:39 AM
> Subject: Testing snmp
> To: xorp-users at xorp.org
> 
> Hi,
> 
> I'm new to using net-snmp but I would like to test using the snmp in Xorp.
> I've already managed to compile Xorp 1.4 with the --with-snmp option.  But I
> cannot find where the bgp4_mib_1657.so goes.  I haven't changed any of the
> code.  I was expecting it to be in /usr/local/xorp/mibs or if not in the
> source directory xorp-1.4/mibs.
> 
> The following were the steps I did:
> 1. ./configure --with-snmp --enable-shared
> 2. gmake
> 3. gmake install
> 
> Could you give me guidance on what I'm doing wrong or what I'm supposed to
> expect?
> 
> Thanks,
> Maritess
> _______________________________________________
> Xorp-users mailing list
> Xorp-users at xorp.org
> http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users