From shashikumar_249 at yahoo.co.in  Tue Oct  5 02:17:28 2010
From: shashikumar_249 at yahoo.co.in (shashi kumar)
Date: Tue, 5 Oct 2010 14:47:28 +0530 (IST)
Subject: [Xorp-users] reg snmp execution with xorp
Message-ID: <450633.13358.qm@web137318.mail.in.yahoo.com>

Hi All,


When i am trying to execute snmp with the help of rtrmgr , i am facing the following problem.

i have installed net-snmp 5.5 ,


[ 2010/10/05 14:16:40? WARNING xorp_rtrmgr:13780 XrlFinderTarget +407 ../xrl/targets/finder_base.cc handle_finder_0_2_resolve_xrl ] Handling method for finder/0.2/resolve_xrl failed: XrlCmdError 102 Command failed Target "xorp_if_mib" does not exist or is not enabled.
[ 2010/10/05 14:16:41? WARNING xorp_rtrmgr:13780 XrlFinderTarget +407 ../xrl/targets/finder_base.cc handle_finder_0_2_resolve_xrl ] Handling method for finder/0.2/resolve_xrl failed: XrlCmdError 102 Command failed Target "xorp_if_mib" does not exist or is not enabled.
[ 2010/10/05 14:16:42? WARNING xorp_rtrmgr:13780 XrlFinderTarget +407 ../xrl/targets/finder_base.cc handle_finder_0_2_resolve_xrl ] Handling method for finder/0.2/resolve_xrl failed: XrlCmdError 102 Command failed Target "xorp_if_mib" does not exist or is not enabled.
[ 2010/10/05 14:16:43? WARNING xorp_rtrmgr:13780 XrlFinderTarget +407 ../xrl/targets/finder_base.cc handle_finder_0_2_resolve_xrl ] Handling method for finder/0.2/resolve_xrl failed: XrlCmdError 102 Command failed Target "xorp_if_mib" does no


can any body help me in this regard.

Thanks in Advance,
shashi



-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20101005/0fef7568/attachment.html 

From sekhar at copperheadsystems.com  Tue Oct  5 04:09:19 2010
From: sekhar at copperheadsystems.com (sekhar at copperheadsystems.com)
Date: Tue, 5 Oct 2010 16:39:19 +0530
Subject: [Xorp-users] Redistribute OSPFv2 into RIP
In-Reply-To: <mailman.5.1285786804.1475.xorp-users@xorp.org>
References: <mailman.5.1285786804.1475.xorp-users@xorp.org>
Message-ID: <4d02e784c13fa47d396507afa5c165ba.squirrel@mail.copperheadsystems.com>

  Hi Team,

         How to Redistribute OSPFv2 into RIP??? Can u Please tell me the
configuration for redistribution.

For example :-   R1 ---->  R2 ----->  R3


Thanks,
Sekhar.




From rps at maine.edu  Tue Oct  5 05:11:44 2010
From: rps at maine.edu (Ray Soucy)
Date: Tue, 5 Oct 2010 08:11:44 -0400
Subject: [Xorp-users] Redistribute OSPFv2 into RIP
In-Reply-To: <4d02e784c13fa47d396507afa5c165ba.squirrel@mail.copperheadsystems.com>
References: <mailman.5.1285786804.1475.xorp-users@xorp.org>
	<4d02e784c13fa47d396507afa5c165ba.squirrel@mail.copperheadsystems.com>
Message-ID: <AANLkTinCKYsz84ohmdsowmthD_yDpgHZnxLvtsgChecZ@mail.gmail.com>

Use a policy statement to match the routes you want to redistribute,
then redistribute them with an "export" statement in your RIP config.

Example:

----8<----
protocols {
    rip {
        export: "RIP_Export"
    }
}
policy {
    policy-statement "RIP_Export" {
        term 100 {
            from {
                protocol: "ospf4"
            }
            then {
                accept {
                }
            }
        }
        then {
            reject {
            }
        }
    }
}
----8<----



On Tue, Oct 5, 2010 at 7:09 AM,  <sekhar at copperheadsystems.com> wrote:
> ?Hi Team,
>
> ? ? ? ? How to Redistribute OSPFv2 into RIP??? Can u Please tell me the
> configuration for redistribution.
>
> For example :- ? R1 ----> ?R2 -----> ?R3
>
>
> Thanks,
> Sekhar.
>
>
>
> _______________________________________________
> Xorp-users mailing list
> Xorp-users at xorp.org
> http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users
>



-- 
Ray Soucy

Epic Communications Specialist

Phone: +1 (207) 561-3526

Networkmaine, a Unit of the University of Maine System
http://www.networkmaine.net/


From greearb at candelatech.com  Tue Oct  5 09:26:28 2010
From: greearb at candelatech.com (Ben Greear)
Date: Tue, 05 Oct 2010 09:26:28 -0700
Subject: [Xorp-users] reg snmp execution with xorp
In-Reply-To: <450633.13358.qm@web137318.mail.in.yahoo.com>
References: <450633.13358.qm@web137318.mail.in.yahoo.com>
Message-ID: <4CAB51B4.5050102@candelatech.com>

On 10/05/2010 02:17 AM, shashi kumar wrote:
> Hi All,
>
>
> When i am trying to execute snmp with the help of rtrmgr , i am facing
> the following problem.
>
> i have installed net-snmp 5.5 ,

Xorp doesn't support SNMP, at least not recent builds.  Very
old versions (maybe 1.5 from years ago), might be able to be
made to work, but I don't think even that stuff worked out
of the box.

Thanks,
Ben

>
>
> [ 2010/10/05 14:16:40 WARNING xorp_rtrmgr:13780 XrlFinderTarget +407
> ../xrl/targets/finder_base.cc handle_finder_0_2_resolve_xrl ] Handling
> method for finder/0.2/resolve_xrl failed: XrlCmdError 102 Command failed
> Target "xorp_if_mib" does not exist or is not enabled.
> [ 2010/10/05 14:16:41 WARNING xorp_rtrmgr:13780 XrlFinderTarget +407
> ../xrl/targets/finder_base.cc handle_finder_0_2_resolve_xrl ] Handling
> method for finder/0.2/resolve_xrl failed: XrlCmdError 102 Command failed
> Target "xorp_if_mib" does not exist or is not enabled.
> [ 2010/10/05 14:16:42 WARNING xorp_rtrmgr:13780 XrlFinderTarget +407
> ../xrl/targets/finder_base.cc handle_finder_0_2_resolve_xrl ] Handling
> method for finder/0.2/resolve_xrl failed: XrlCmdError 102 Command failed
> Target "xorp_if_mib" does not exist or is not enabled.
> [ 2010/10/05 14:16:43 WARNING xorp_rtrmgr:13780 XrlFinderTarget +407
> ../xrl/targets/finder_base.cc handle_finder_0_2_resolve_xrl ] Handling
> method for finder/0.2/resolve_xrl failed: XrlCmdError 102 Command failed
> Target "xorp_if_mib" does no
>
>
> can any body help me in this regard.
>
> Thanks in Advance,
> shashi
>
>
>
>
> _______________________________________________
> Xorp-users mailing list
> Xorp-users at xorp.org
> http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users


-- 
Ben Greear <greearb at candelatech.com>
Candela Technologies Inc  http://www.candelatech.com


From vik.kaul at yahoo.com  Tue Oct  5 12:43:08 2010
From: vik.kaul at yahoo.com (V K)
Date: Tue, 5 Oct 2010 12:43:08 -0700 (PDT)
Subject: [Xorp-users] (no subject)
Message-ID: <955075.63820.qm@web113316.mail.gq1.yahoo.com>

Folks

?The xorp instance I have receives an AS LSA update message (with age 1) and updates the database (see last entry below for 11.0.2.135). The database entry removal also works well. However, the routing table is not updated. 

Could it be so because the "External<A>::push_routes()" function does nothing.? I followed the trail of the push_routes and external_push_routes routines... but I am not sure that is the reason because they seem to be triggered by policy_backend_0_1_push_routes which seems to be dictated by template. 

All I want is a way to insert a route in the routing table if it appears in the database as the ASExt-2 entry.

Any help will be appreciated



>>>>>show ospf4 database
?? OSPF link state database, Area 0.0.0.0
?Type?????? ID?????????????? Adv Rtr?????????? Seq????? Age? Opt? Cksum? Len
Router? *10.2.2.254?????? 10.2.2.254?????? 0x8000000c? 1685? 0x2? 0xad63? 36
Router?? 127.1.0.2??????? 127.1.0.2??????? 0x800000cc? 1691? 0x2? 0x47ec? 48
Network? 10.2.2.2???????? 127.1.0.2??????? 0x80000002? 1691? 0x2? 0x56e0? 32
Network? 10.1.2.2???????? 127.1.0.2??????? 0x800000c6?? 205? 0x2? 0xda24? 32
Router?? 127.1.0.1??????? 127.1.0.1??????? 0x800000e1? 1732? 0x2? 0x5454? 60
Router?? 10.1.1.254?????? 10.1.1.254?????? 0x8000000e? 1728? 0x2? 0x9b7c? 36
Network? 10.1.1.1???????? 127.1.0.1??????? 0x80000002? 1732? 0x2? 0x5ae3? 32
ASExt-2? 11.0.2.135?????? 10.1.1.254?????? 0x80000001???? 7? 0x2? 0x8ea4? 36




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

From vik.kaul at yahoo.com  Tue Oct  5 12:46:20 2010
From: vik.kaul at yahoo.com (V K)
Date: Tue, 5 Oct 2010 12:46:20 -0700 (PDT)
Subject: [Xorp-users] OSPF: ASExt-2 entry in database,
	but not in routing table
In-Reply-To: <955075.63820.qm@web113316.mail.gq1.yahoo.com>
Message-ID: <552614.65023.qm@web113316.mail.gq1.yahoo.com>

Sorry. Forgot to put in the Subject line. Resending

--- On Tue, 10/5/10, V K <vik.kaul at yahoo.com> wrote:

From: V K <vik.kaul at yahoo.com>
Subject: [Xorp-users] (no subject)
To: xorp-users at xorp.org
Date: Tuesday, October 5, 2010, 3:43 PM

Folks

?The xorp instance I have receives an AS LSA update message (with age 1) and updates the database (see last entry below for 11.0.2.135). The database entry removal also works well. However, the routing table is not updated. 

Could it be so because the "External<A>::push_routes()" function does nothing.? I followed the trail of the push_routes and external_push_routes routines... but I am not sure that is the reason because they seem to be triggered by policy_backend_0_1_push_routes which seems to be dictated by template. 

All I want is a way to insert a route in the routing table if it appears in the database as the ASExt-2 entry.

Any help will be appreciated



>>>>>show ospf4 database
?? OSPF link state database, Area
 0.0.0.0
?Type?????? ID?????????????? Adv Rtr?????????? Seq????? Age? Opt? Cksum? Len
Router? *10.2.2.254?????? 10.2.2.254?????? 0x8000000c? 1685? 0x2? 0xad63? 36
Router?? 127.1.0.2??????? 127.1.0.2??????? 0x800000cc? 1691? 0x2? 0x47ec? 48
Network? 10.2.2.2???????? 127.1.0.2??????? 0x80000002? 1691? 0x2? 0x56e0? 32
Network? 10.1.2.2???????? 127.1.0.2??????? 0x800000c6?? 205?
 0x2? 0xda24? 32
Router?? 127.1.0.1??????? 127.1.0.1??????? 0x800000e1? 1732? 0x2? 0x5454? 60
Router?? 10.1.1.254?????? 10.1.1.254?????? 0x8000000e? 1728? 0x2? 0x9b7c? 36
Network? 10.1.1.1???????? 127.1.0.1??????? 0x80000002? 1732? 0x2? 0x5ae3? 32
ASExt-2? 11.0.2.135?????? 10.1.1.254?????? 0x80000001???? 7? 0x2? 0x8ea4? 36










      
-----Inline Attachment Follows-----

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



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

From vik.kaul at yahoo.com  Wed Oct  6 08:12:20 2010
From: vik.kaul at yahoo.com (V K)
Date: Wed, 6 Oct 2010 08:12:20 -0700 (PDT)
Subject: [Xorp-users] OSPF: ASExt-2 entry in database,
	but not in routing table
In-Reply-To: <552614.65023.qm@web113316.mail.gq1.yahoo.com>
Message-ID: <46360.58445.qm@web113304.mail.gq1.yahoo.com>

Folks

?Just some more information.
?When the LSA update reaches the router, it indeed does send the LSA Ack back to the advertising router (which is reachable and is a neighbor)

show ospf4 neighbor detail 
? Address???????? Interface???????????? State????? ID????????????? Pri? Dead
10.1.1.254?????? br1/br1??????????????? Full????? 10.1.1.254?????? 128??? 37
? Area 0.0.0.0, opt 0x2, DR 10.1.1.1, BDR 10.1.1.254
? Up 00:38:55, adjacent 00:38:40


?Here is what the detail of the As-External-LSA database looks like:

As-External-LSA:
LS age?? 10 Options? 0x2 DC: 0 EA: 0 N/P: 0 MC: 0 E: 1 LS type 0x5 Link State ID 11.0.1.111 Advertising Router 10.1.1.254 LS sequence number 0x80000061 LS checksum 0x439d length 36
??????? Network Mask 0xffffffff
??????? bit E true
??????? Metric 65535 0xffff
??????? Forwarding address 10.1.1.254
??????? External Route Tag 0



From: V K <vik.kaul at yahoo.com>
Subject: [Xorp-users] OSPF: ASExt-2 entry in database, but not in routing table
To: xorp-users at xorp.org
Date: Tuesday, October 5, 2010, 3:46 PM

Sorry. Forgot to put in the Subject line. Resending

--- On Tue, 10/5/10, V K <vik.kaul at yahoo.com> wrote:

From: V K <vik.kaul at yahoo.com>
Subject: [Xorp-users] (no subject)
To: xorp-users at xorp.org
Date: Tuesday, October 5, 2010, 3:43 PM

Folks

?The xorp instance I have receives an AS LSA update message (with age 1) and updates the database (see last entry below for 11.0.2.135). The database entry removal also works well. However, the routing table is not updated. 

Could it be so because the "External<A>::push_routes()" function does nothing.? I followed the trail
 of the push_routes and external_push_routes routines... but I am not sure that is the reason because they seem to be triggered by policy_backend_0_1_push_routes which seems to be dictated by template. 

All I want is a way to insert a route in the routing table if it appears in the database as the ASExt-2 entry.

Any help will be appreciated



>>>>>show ospf4 database
?? OSPF link state database, Area
 0.0.0.0
?Type?????? ID?????????????? Adv Rtr?????????? Seq????? Age? Opt? Cksum? Len
Router? *10.2.2.254?????? 10.2.2.254?????? 0x8000000c? 1685? 0x2? 0xad63? 36
Router?? 127.1.0.2??????? 127.1.0.2??????? 0x800000cc? 1691? 0x2? 0x47ec? 48
Network? 10.2.2.2???????? 127.1.0.2??????? 0x80000002? 1691? 0x2? 0x56e0? 32
Network? 10.1.2.2???????? 127.1.0.2??????? 0x800000c6?? 205?
 0x2? 0xda24? 32
Router?? 127.1.0.1??????? 127.1.0.1??????? 0x800000e1? 1732? 0x2? 0x5454? 60
Router?? 10.1.1.254?????? 10.1.1.254?????? 0x8000000e? 1728? 0x2? 0x9b7c? 36
Network? 10.1.1.1???????? 127.1.0.1??????? 0x80000002? 1732? 0x2? 0x5ae3? 32
ASExt-2? 11.0.2.135?????? 10.1.1.254?????? 0x80000001???? 7? 0x2? 0x8ea4? 36










      
-----Inline Attachment Follows-----

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



      
-----Inline Attachment Follows-----

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



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

From greearb at candelatech.com  Wed Oct  6 09:23:42 2010
From: greearb at candelatech.com (Ben Greear)
Date: Wed, 06 Oct 2010 09:23:42 -0700
Subject: [Xorp-users] OSPF: ASExt-2 entry in database,
 but not in routing table
In-Reply-To: <46360.58445.qm@web113304.mail.gq1.yahoo.com>
References: <46360.58445.qm@web113304.mail.gq1.yahoo.com>
Message-ID: <4CACA28E.5020805@candelatech.com>

On 10/06/2010 08:12 AM, V K wrote:
> Folks
>
> Just some more information.
> When the LSA update reaches the router, it indeed does send the LSA Ack
> back to the advertising router (which is reachable and is a neighbor)

What version of xorp are you using?  What OS/kernel version?
If not latest xorp.ct, please
give it a try, and let us know if you still see the problem.

http://github.com/greearb/xorp.ct

The truth is, I'm buried in other work at the moment, so
I don't have much time to debug this either way.  But,
you might investigate whether you need a policy or not
for this behaviour.

Thanks,
Ben

>
> show ospf4 neighbor detail
> Address Interface State ID Pri Dead
> 10.1.1.254 br1/br1 Full 10.1.1.254 128 37
> Area 0.0.0.0, opt 0x2, DR 10.1.1.1, BDR 10.1.1.254
> Up 00:38:55, adjacent 00:38:40
>
>
> Here is what the detail of the As-External-LSA database looks like:
>
> As-External-LSA:
> LS age 10 Options 0x2 DC: 0 EA: 0 N/P: 0 MC: 0 E: 1 LS type 0x5 Link
> State ID 11.0.1.111 Advertising Router 10.1.1.254 LS sequence number
> 0x80000061 LS checksum 0x439d length 36
> Network Mask 0xffffffff
> bit E true
> Metric 65535 0xffff
> Forwarding address 10.1.1.254
> External Route Tag 0
>
>
>
>     From: V K <vik.kaul at yahoo.com>
>     Subject: [Xorp-users] OSPF: ASExt-2 entry in database, but not in
>     routing table
>     To: xorp-users at xorp.org
>     Date: Tuesday, October 5, 2010, 3:46 PM
>
>     Sorry. Forgot to put in the Subject line. Resending
>
>     --- On *Tue, 10/5/10, V K /<vik.kaul at yahoo.com>/* wrote:
>
>
>         From: V K <vik.kaul at yahoo.com>
>         Subject: [Xorp-users] (no subject)
>         To: xorp-users at xorp.org
>         Date: Tuesday, October 5, 2010, 3:43 PM
>
>         Folks
>
>         The xorp instance I have receives an AS LSA update message (with
>         age 1) and updates the database (see last entry below for
>         11.0.2.135). The database entry removal also works well.
>         However, the routing table is not updated.
>
>         Could it be so because the "External<A>::push_routes()" function
>         does nothing. I followed the trail of the push_routes and
>         external_push_routes routines... but I am not sure that is the
>         reason because they seem to be triggered by
>         policy_backend_0_1_push_routes which seems to be dictated by
>         template.
>
>         All I want is a way to insert a route in the routing table if it
>         appears in the database as the ASExt-2 entry.
>
>         Any help will be appreciated
>
>
>
>          >>>>>show ospf4 database
>         OSPF link state database, Area 0.0.0.0
>         Type ID Adv Rtr Seq Age Opt Cksum Len
>         Router *10.2.2.254 10.2.2.254 0x8000000c 1685 0x2 0xad63 36
>         Router 127.1.0.2 127.1.0.2 0x800000cc 1691 0x2 0x47ec 48
>         Network 10.2.2.2 127.1.0.2 0x80000002 1691 0x2 0x56e0 32
>         Network 10.1.2.2 127.1.0.2 0x800000c6 205 0x2 0xda24 32
>         Router 127.1.0.1 127.1.0.1 0x800000e1 1732 0x2 0x5454 60
>         Router 10.1.1.254 10.1.1.254 0x8000000e 1728 0x2 0x9b7c 36
>         Network 10.1.1.1 127.1.0.1 0x80000002 1732 0x2 0x5ae3 32
>         ASExt-2 11.0.2.135 10.1.1.254 0x80000001 7 0x2 0x8ea4 36
>
>
>
>         -----Inline Attachment Follows-----
>
>         _______________________________________________
>         Xorp-users mailing list
>         Xorp-users at xorp.org
>         http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users
>
>
>
>     -----Inline Attachment Follows-----
>
>     _______________________________________________
>     Xorp-users mailing list
>     Xorp-users at xorp.org </mc/compose?to=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


-- 
Ben Greear <greearb at candelatech.com>
Candela Technologies Inc  http://www.candelatech.com


From vik.kaul at yahoo.com  Wed Oct  6 10:06:29 2010
From: vik.kaul at yahoo.com (V K)
Date: Wed, 6 Oct 2010 10:06:29 -0700 (PDT)
Subject: [Xorp-users] OSPF: ASExt-2 entry in database,
	but not in routing table
In-Reply-To: <4CACA28E.5020805@candelatech.com>
Message-ID: <398708.15378.qm@web113311.mail.gq1.yahoo.com>


> What version of xorp are you using?? What OS/kernel
> version?

The Linux OS is 2.6.25-14.fc9.i686 
The xorp version is from xorp.org 1.6 (1/07/2009)
This is probably quite old. I was not aware of xorp.ct

> If not latest xorp.ct, please
> give it a try, and let us know if you still see the
> problem.

I will do this next. I am downloading xorp-1.8.2-CT and will see how that responds.

> The truth is, I'm buried in other work at the moment, so
> I don't have much time to debug this either way.?
> But,
> you might investigate whether you need a policy or not
> for this behaviour.

I followed instructions in the old post here (http://mailman.icsi.berkeley.edu/pipermail/xorp-users/2006-April/001185.html), and it seems to do what it was intended to do. However, what I am trying is something different. I want to take routes from _NON_OSPF_ (and _NON_XORP_) interfaces and redistribute them using the xorp/ospf processes. I don't want to run ospf on those interfaces

Another option could be to have xorp be aware of those interfaces, but not run ospf on them and follow the patch above to see if that works. I will try that on xorp1.6 and see if it is of any help

Thanks
> 
> Thanks,
> Ben
> 
> >
> > show ospf4 neighbor detail
> > Address Interface State ID Pri Dead
> > 10.1.1.254 br1/br1 Full 10.1.1.254 128 37
> > Area 0.0.0.0, opt 0x2, DR 10.1.1.1, BDR 10.1.1.254
> > Up 00:38:55, adjacent 00:38:40
> >
> >
> > Here is what the detail of the As-External-LSA
> database looks like:
> >
> > As-External-LSA:
> > LS age 10 Options 0x2 DC: 0 EA: 0 N/P: 0 MC: 0 E: 1 LS
> type 0x5 Link
> > State ID 11.0.1.111 Advertising Router 10.1.1.254 LS
> sequence number
> > 0x80000061 LS checksum 0x439d length 36
> > Network Mask 0xffffffff
> > bit E true
> > Metric 65535 0xffff
> > Forwarding address 10.1.1.254
> > External Route Tag 0
> >
> >
> >
> >? ???From: V K <vik.kaul at yahoo.com>
> >? ???Subject: [Xorp-users] OSPF:
> ASExt-2 entry in database, but not in
> >? ???routing table
> >? ???To: xorp-users at xorp.org
> >? ???Date: Tuesday, October 5,
> 2010, 3:46 PM
> >
> >? ???Sorry. Forgot to put in the
> Subject line. Resending
> >
> >? ???--- On *Tue, 10/5/10, V K
> /<vik.kaul at yahoo.com>/*
> wrote:
> >
> >
> >? ? ? ???From: V K <vik.kaul at yahoo.com>
> >? ? ? ???Subject:
> [Xorp-users] (no subject)
> >? ? ? ???To: xorp-users at xorp.org
> >? ? ? ???Date: Tuesday,
> October 5, 2010, 3:43 PM
> >
> >? ? ? ???Folks
> >
> >? ? ? ???The xorp
> instance I have receives an AS LSA update message (with
> >? ? ? ???age 1) and
> updates the database (see last entry below for
> >? ? ? ???11.0.2.135). The
> database entry removal also works well.
> >? ? ? ???However, the
> routing table is not updated.
> >
> >? ? ? ???Could it be so
> because the "External<A>::push_routes()" function
> >? ? ? ???does nothing. I
> followed the trail of the push_routes and
> >? ? ?
> ???external_push_routes routines... but I am
> not sure that is the
> >? ? ? ???reason because
> they seem to be triggered by
> >? ? ?
> ???policy_backend_0_1_push_routes which seems
> to be dictated by
> >? ? ? ???template.
> >
> >? ? ? ???All I want is a
> way to insert a route in the routing table if it
> >? ? ? ???appears in the
> database as the ASExt-2 entry.
> >
> >? ? ? ???Any help will be
> appreciated
> >
> >
> >
> >? ? ? ? ?
> >>>>>show ospf4 database
> >? ? ? ???OSPF link state
> database, Area 0.0.0.0
> >? ? ? ???Type ID Adv Rtr
> Seq Age Opt Cksum Len
> >? ? ? ???Router
> *10.2.2.254 10.2.2.254 0x8000000c 1685 0x2 0xad63 36
> >? ? ? ???Router 127.1.0.2
> 127.1.0.2 0x800000cc 1691 0x2 0x47ec 48
> >? ? ? ???Network 10.2.2.2
> 127.1.0.2 0x80000002 1691 0x2 0x56e0 32
> >? ? ? ???Network 10.1.2.2
> 127.1.0.2 0x800000c6 205 0x2 0xda24 32
> >? ? ? ???Router 127.1.0.1
> 127.1.0.1 0x800000e1 1732 0x2 0x5454 60
> >? ? ? ???Router
> 10.1.1.254 10.1.1.254 0x8000000e 1728 0x2 0x9b7c 36
> >? ? ? ???Network 10.1.1.1
> 127.1.0.1 0x80000002 1732 0x2 0x5ae3 32
> >? ? ? ???ASExt-2
> 11.0.2.135 10.1.1.254 0x80000001 7 0x2 0x8ea4 36
> >
> >
> >
> >? ? ? ???-----Inline
> Attachment Follows-----
> >
> >? ? ?
> ???_______________________________________________
> >? ? ? ???Xorp-users
> mailing list
> >? ? ? ???Xorp-users at xorp.org
> >? ? ? ???http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users
> >
> >
> >
> >? ???-----Inline Attachment
> Follows-----
> >
> >?
> ???_______________________________________________
> >? ???Xorp-users mailing list
> >? ???Xorp-users at xorp.org
> </mc/compose?to=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
> 
> 
> -- 
> Ben Greear <greearb at candelatech.com>
> Candela Technologies Inc? http://www.candelatech.com
> 
> 


      


From greearb at candelatech.com  Wed Oct  6 11:06:59 2010
From: greearb at candelatech.com (Ben Greear)
Date: Wed, 06 Oct 2010 11:06:59 -0700
Subject: [Xorp-users] OSPF: ASExt-2 entry in database,
 but not in routing table
In-Reply-To: <398708.15378.qm@web113311.mail.gq1.yahoo.com>
References: <398708.15378.qm@web113311.mail.gq1.yahoo.com>
Message-ID: <4CACBAC3.5050406@candelatech.com>

On 10/06/2010 10:06 AM, V K wrote:
>
>> What version of xorp are you using?  What OS/kernel
>> version?
>
> The Linux OS is 2.6.25-14.fc9.i686
> The xorp version is from xorp.org 1.6 (1/07/2009)
> This is probably quite old. I was not aware of xorp.ct
>
>> If not latest xorp.ct, please
>> give it a try, and let us know if you still see the
>> problem.
>
> I will do this next. I am downloading xorp-1.8.2-CT and will see how that responds.

If you plan on doing development, you might consider checking the source
out with 'git':

git clone git://github.com/greearb/xorp.ct.git

Patches are welcome should you make any source code changes.

>> The truth is, I'm buried in other work at the moment, so
>> I don't have much time to debug this either way.
>> But,
>> you might investigate whether you need a policy or not
>> for this behaviour.
>
> I followed instructions in the old post here (http://mailman.icsi.berkeley.edu/pipermail/xorp-users/2006-April/001185.html), and it seems to do what it was intended to do. However, what I am trying is something different. I want to take routes from _NON_OSPF_ (and _NON_XORP_) interfaces and redistribute them using the xorp/ospf processes. I don't want to run ospf on those interfaces
>
> Another option could be to have xorp be aware of those interfaces, but not run ospf on them and follow the patch above to see if that works. I will try that on xorp1.6 and see if it is of any help

That patch is already in xorp.ct, by the way.

In your scenario, the routes that you want you distribute are properly added to the kernel, but just on
interfaces that OSPF is not configured to use, so OSPF will not export them?

Thanks,
Ben

-- 
Ben Greear <greearb at candelatech.com>
Candela Technologies Inc  http://www.candelatech.com


From diego360xen at gmail.com  Wed Oct  6 12:54:58 2010
From: diego360xen at gmail.com (=?ISO-8859-1?Q?Diego_Augusto_Pinzon_Carre=F1o?=)
Date: Wed, 6 Oct 2010 14:54:58 -0500
Subject: [Xorp-users] VDE and CLICK which version support xorp-ct?
Message-ID: <AANLkTimHvd+mhpjn_iGfYKmts3rarP62kzD3i=SrEyqd@mail.gmail.com>

hi list..

i just try  VDE a Virtual Distributed Ethernet network(
http://vde.sourceforge.net/) and Virtualbox with XORP.
for a practice in a class-room, my teacher ask me about the posibility of do
a practice about add some packet limit to a interface and chances that
interface when the limit up and get late sometime  the packets. my first
aproach was do with CLICK uses as part of FEA, so my question what version
of CLICK has been tested?.

VDE is not so fast as i think, and xorp-ct presented some warning while the
process rtrmgr began

p.d:.its a work of class-room our teacher asked about free  open routes
plataforms and let choose one
p.d1:i'm working for a little modulo to add some administrative tool. maybe
send log xorp message  to mail account or textmessage to user xorp about
log.

thx.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20101006/0158aae9/attachment.html 

From greearb at candelatech.com  Wed Oct  6 13:01:25 2010
From: greearb at candelatech.com (Ben Greear)
Date: Wed, 06 Oct 2010 13:01:25 -0700
Subject: [Xorp-users] VDE and CLICK which version support xorp-ct?
In-Reply-To: <AANLkTimHvd+mhpjn_iGfYKmts3rarP62kzD3i=SrEyqd@mail.gmail.com>
References: <AANLkTimHvd+mhpjn_iGfYKmts3rarP62kzD3i=SrEyqd@mail.gmail.com>
Message-ID: <4CACD595.5090508@candelatech.com>

On 10/06/2010 12:54 PM, Diego Augusto Pinzon Carre?o wrote:
> hi list..
>
> i just try  VDE a Virtual Distributed Ethernet
> network(http://vde.sourceforge.net/) and Virtualbox with XORP.
> for a practice in a class-room, my teacher ask me about the posibility
> of do a practice about add some packet limit to a interface and chances
> that interface when the limit up and get late sometime  the packets. my
> first aproach was do with CLICK uses as part of FEA, so my question what
> version of CLICK has been tested?.

If you want to do network emulation (add delay, packet-loss, etc),
then you might want to research 'netem'.

That should be done outside of xorp, I think.

I don't think CLICK is supported by xorp 1.6 or xorp.ct, but patches
to fix this are welcome!

> p.d:.its a work of class-room our teacher asked about free  open routes
> plataforms and let choose one
> p.d1:i'm working for a little modulo to add some administrative tool.
> maybe send log xorp message  to mail account or textmessage to user xorp
> about log.

Please consider developing against xorp.ct, and if you do come up with
a patch, I'll be happy to consider putting into xorp.ct.

Thanks,
Ben

-- 
Ben Greear <greearb at candelatech.com>
Candela Technologies Inc  http://www.candelatech.com


From diego360xen at gmail.com  Wed Oct  6 14:18:55 2010
From: diego360xen at gmail.com (=?ISO-8859-1?Q?Diego_Augusto_Pinzon_Carre=F1o?=)
Date: Wed, 6 Oct 2010 16:18:55 -0500
Subject: [Xorp-users] i m little confuse
Message-ID: <AANLkTikMEc4LkDmt2XDd=duGE0Nj2OCyMRCjwxfXdpmd@mail.gmail.com>

 hi Ben
I'm confused, in the / usr / local / XORP / rtrmgr / config /
I found a configuration file called click.boot
and a quick read it seems that loads the kernel modules using two files,
look for these files are not on XORP-ct.

thanks for the information of netem.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20101006/a60649c7/attachment.html 

From greearb at candelatech.com  Wed Oct  6 14:47:18 2010
From: greearb at candelatech.com (Ben Greear)
Date: Wed, 06 Oct 2010 14:47:18 -0700
Subject: [Xorp-users] i m little confuse
In-Reply-To: <AANLkTikMEc4LkDmt2XDd=duGE0Nj2OCyMRCjwxfXdpmd@mail.gmail.com>
References: <AANLkTikMEc4LkDmt2XDd=duGE0Nj2OCyMRCjwxfXdpmd@mail.gmail.com>
Message-ID: <4CACEE66.1020804@candelatech.com>

On 10/06/2010 02:18 PM, Diego Augusto Pinzon Carre?o wrote:
> hi Ben
> I'm confused, in the / usr / local / XORP / rtrmgr / config /
> I found a configuration file called click.boot
> and a quick read it seems that loads the kernel modules using two files,
> look for these files are not on XORP-ct.
>
> thanks for the information of netem.

I haven't looked into what it would take to get CLICK working,
and don't have time to work on it now (nor probably
in the future either).

You might investigate xorp 1.6 or even 1.5 to see if it
has the click files.

Thanks,
Ben

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


-- 
Ben Greear <greearb at candelatech.com>
Candela Technologies Inc  http://www.candelatech.com


From JayasriS at aaesys.com  Fri Oct  8 17:14:18 2010
From: JayasriS at aaesys.com (Jayasri Sangu)
Date: Fri, 8 Oct 2010 17:14:18 -0700
Subject: [Xorp-users] join/prune messages
Message-ID: <2DE723F44CAFD24A9B6BF606813F010C4072C0A30F@aae-exch>

Hi All,

   I have a system with routers running xorp PIM.  With the static RP configuration I can send ans receive the multicast messages.

But with the dynamic RP/ BSR,  the multicast messages are not  forwarded. And I observed that the join/prune messages are not generated.

Attached are the config files.


Thanks
Jayasri
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20101008/06c9bd61/attachment.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: multicast4_123.boot
Type: application/octet-stream
Size: 1921 bytes
Desc: multicast4_123.boot
Url : http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20101008/06c9bd61/attachment.obj 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: multicast4_223.boot
Type: application/octet-stream
Size: 1921 bytes
Desc: multicast4_223.boot
Url : http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20101008/06c9bd61/attachment-0001.obj 

From danielcamara at gmail.com  Mon Oct 11 07:31:30 2010
From: danielcamara at gmail.com (Daniel Camara)
Date: Mon, 11 Oct 2010 16:31:30 +0200
Subject: [Xorp-users] Traffic over the same interface
Message-ID: <AANLkTimcH8ibde1XUeFu6fExo=rqFfky0nPbfSVWfZBZ@mail.gmail.com>

 Hi people,

  I am with a problem here, and I would like to ask your opinion about it. I
am really sorry if this a well known problem/limitation. However, I searched
through the list and I didn't find any thing that was quite exactly the
same.

 I have a configuration that is:

        Server  <-------------------> Node2 <-----------------> Node2
<-------------> Node3 <--------------------> Client
 eth0=192.168.13.53   eth2=192.168.13.1       mesh0=10.0.1.1
eth2=192.168.14.1   eth0=192.168.14.53

mesh0=10.0.1.2                                          mesh0=10.0.1.3

 Node 1 and 3 have two interfaces configured and all the other nodes have
just one interface configured. I guess this is exactly the problem. Even
Node2, that work as a bridge for between Node1 and Node3, has just one
interface.  It makes sense because the scenario I am trying to build is in a
Wireless network, where Node1 and Node3 can not reach each other.

What happens, when I start the client  is that the join/prune reach Node1,
the data traffic starts, but stops in Node2. Is it possible that when a data
traffic cames through one interface it can not be forwarded over the same
interface?

For the regular case I even agree that it makes sense, but in this scenario
Node1 and Node3 use Node2, that has just one interface.   The traffic is
registered and the data arrives up to node2 and when the client is killed
the join/prune passes through and the data flow stops.

I am trying to debug the code to see if what is happening is this, the node
is ignoring the data traffic, but I guess gdb doesn' t like me very much, it
is saying that "No source file named pim_mre_join_prune.cc", for example if
I try to put a break point there  :)

If it can help in some way, the log output of the join, is the following:
[ 2010/10/11 15:57:05 TRACE xorp_pimsm4 PIM ] RX PIM_JOIN_PRUNE from
10.0.1.3 to 224.0.0.13 on vif nasmesh0
[ 2010/10/11 15:57:05 TRACE xorp_pimsm4 PIM ] TX PIM_JOIN_PRUNE from
10.0.1.1 to 224.0.0.13 on vif nasmesh0
[ 2010/10/11 15:57:05 TRACE xorp_igmp MLD6IGMP ] RX
IGMP_V3_MEMBERSHIP_REPORT from 10.0.1.3 to 224.0.0.22 on vif nasmesh0
[ 2010/10/11 15:57:05 TRACE xorp_igmp MLD6IGMP ] Notify routing add
membership for (192.168.13.53, 232.0.0.1) on vif nasmesh0
[ 2010/10/11 15:57:05 TRACE xorp_pimsm4 PIM ] Add membership for
(192.168.13.53, 232.0.0.1) on vif nasmesh0
[ 2010/10/11 15:57:05 TRACE xorp_fea MFEA ] RX kernel signal: message_type =
1 vif_index = 0 src = 192.168.13.53 dst = 232.0.0.1
[ 2010/10/11 15:57:05 TRACE xorp_pimsm4 PIM ] RX NOCACHE signal from MFEA_4:
vif_index = 0 src = 192.168.13.53 dst = 232.0.0.1
[ 2010/10/11 15:57:05 TRACE xorp_pimsm4 PIM ] Add MFC entry: (192.168.13.53,
232.0.0.1) iif = 0 olist = .. olist_disable_wrongvif = OO
[ 2010/10/11 15:57:05 TRACE xorp_pimsm4 PIM ] Add dataflow monitor: source =
192.168.13.53 group = 232.0.0.1 threshold_interval_sec = 210
threshold_interval_usec = 0 threshold_packets = 0 threshold_bytes = 0
is_threshold_in_packets = 1 is_threshold_in_bytes = 0 is_geq_upcall = 0
is_leq_upcall = 1
[ 2010/10/11 15:57:05 TRACE xorp_fea MFEA ] Add MFC entry: (192.168.13.53,
232.0.0.1) iif = 0 olist = ..

Thanks in advance and best regards...

                     Daniel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20101011/8497a15d/attachment.html 

From shashikumar_249 at yahoo.co.in  Wed Oct 13 03:31:36 2010
From: shashikumar_249 at yahoo.co.in (shashi kumar)
Date: Wed, 13 Oct 2010 16:01:36 +0530 (IST)
Subject: [Xorp-users] reg : module stalled problem
Message-ID: <750030.26541.qm@web137305.mail.in.yahoo.com>

Hi All,

When I am trying to run a new process with rtrmgr , i am getting the following error, can any one please help me in this regard,


[ 2010/10/13 16:00:21? INFO xorp_rtrmgr:10295 RTRMGR +334 module_manager.cc module_stopped ] Module stalled: My_Process
[ 2010/10/13 16:00:25? INFO xorp_rtrmgr:10295 RTRMGR +2236 task.cc run_task ] No more tasks to run
[ 2010/10/13 16:00:52? ERROR xorp_rtrmgr:10295 FINDER +91 finder_xrl_queue.hh dispatch_cb ] Sent xrl got response 211 Reply timed out

In which case ,new process will enter into MODULE_STALL state.

Thanks in Advance,
shashi


-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20101013/6c36a772/attachment.html 

From greearb at candelatech.com  Wed Oct 13 09:40:39 2010
From: greearb at candelatech.com (Ben Greear)
Date: Wed, 13 Oct 2010 09:40:39 -0700
Subject: [Xorp-users] reg : module stalled problem
In-Reply-To: <750030.26541.qm@web137305.mail.in.yahoo.com>
References: <750030.26541.qm@web137305.mail.in.yahoo.com>
Message-ID: <4CB5E107.50805@candelatech.com>

On 10/13/2010 03:31 AM, shashi kumar wrote:
> Hi All,
>
> When I am trying to run a new process with rtrmgr , i am getting the
> following error, can any one please help me in this regard,
>
>
> [ 2010/10/13 16:00:21 INFO xorp_rtrmgr:10295 RTRMGR +334
> module_manager.cc module_stopped ] Module stalled: My_Process
> [ 2010/10/13 16:00:25 INFO xorp_rtrmgr:10295 RTRMGR +2236 task.cc
> run_task ] No more tasks to run
> [ 2010/10/13 16:00:52 ERROR xorp_rtrmgr:10295 FINDER +91
> finder_xrl_queue.hh dispatch_cb ] Sent xrl got response 211 Reply timed out
>
> In which case ,new process will enter into MODULE_STALL state.

Maybe it's not answering keep-alive messages (or other messages)?

You could grep for MODULE_STALL in the source...

Ben

>
> Thanks in Advance,
> shashi
>
>
>
>
> _______________________________________________
> Xorp-users mailing list
> Xorp-users at xorp.org
> http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users


-- 
Ben Greear <greearb at candelatech.com>
Candela Technologies Inc  http://www.candelatech.com


From gs050486d at student.etf.rs  Wed Oct 13 10:52:36 2010
From: gs050486d at student.etf.rs (=?UTF-8?Q?Stevan_Grbi=C4=87_05/0486?=)
Date: Wed, 13 Oct 2010 20:52:36 +0300
Subject: [Xorp-users] eBGP & iBGP routes redistribution
Message-ID: <498b8a855b7997201c097667dc977b08@student.etf.rs>

Hi,

I believe and I'm sure that there are plenty of examples about this 
topic as well as questions,
but still I haven't found it work properly (without any alerts).
Following post, has explanation about the situation, but it's left 
without a response.
http://mailman.icsi.berkeley.edu/pipermail/xorp-users/2006-July/001350.html

I shall try to explain the situation as more accurate as possible.

Topology of the testing network is:

              net12
         (R1)---------(R2)------------(R5)----------(R6)
   net13   |           |               |              |
           |    AS1    | net24         |       AS2    |
         (R3)---------(R4)             (R7)----------(R8)
                net34
AS border routers R2 and R5, are expected to communicate in between by 
BGP, while rest of the routers use ospf4 as well as R2 and R5 on two 
interfaces inside AS. ASBRs (AS Border Routers ie. R2 and R5) should 
distribute iBGP routes, learned by ospf4, to other peer and vice versa,
without advertising local AS routes to iBGP peers. To be more 
precisely, R2 and R5 should "extract" routes captured from bgp peer, 
and distribute
inside it's AS. While advertising (all) ospf4 routes from its AS using 
bgp to other (bgp) peer.
(Only net25 interfaces bgp is assigned to.) The rest of its are 
configured to ospf4.
After all how should look like configuration for ASBRs and ASRs (AS 
Routers) to provide pinging peers from one AS to another (e.g. R8 to R1 
or R4 to R6 etc.)

Here is configuration for R5:

interfaces {
   interface em0 {
       disable: false
       vif em0 {
          disable: false
          address 8.8.8.3 {
             prefix-length: 24
             disable: false
			 broadcast: 8.8.8.255
          }
       }
   }
   interface em1 {
       disable: false
       vif em1 {
          disable: false
          address 1.1.1.2 {
             prefix-length: 24
             disable: false
			 broadcast: 1.1.1.255
          }
       }
   }
   interface em2 {
       disable: false
       vif em2 {
          disable: false
          address 192.168.0.2  {
             prefix-length: 24
             disable: false
			 broadcast: 19.168.0.255
          }
       }
   }
}
policy {
  policy-statement connected {
    term export {
        from {
             protocol: "connected"
        }
    }
 }
  policy-statement ospf-to-bgp {
    term ospf2bgp {
        from {
             protocol: "ospf4"
        }
		to	 {
			 neighbour: 1.1.1.3
		}
		then {
		    accept
		}
    }
 }
}
  policy-statement bgp-to-ospf {
    term bgp2ospf {
        from {
             protocol: "bgp"
        }
		then {
		     accept
		}
    }
 }
}
protocols {
  ospf4 {
     router-id: 11.0.0.0
     import: "bgp-to-ospf"
     area 0.0.0.0 {
       interface em0 {
           link-type: "broadcast"
           vif em0 {
              address 8.8.8.3 {
                 hello-interval: 10
               }
           }
        }
       interface em1 {
           link-type: "broadcast"
           vif em1 {
              address 192.168.0.2 {
                 hello-interval: 10
              }
           }
        }
     }
   }
   bgp {
      bgp-id: 1.1.1.2
      export: "ospf-to-bgp,connected"
	  import: "bgp-to-ospf"
      local-as: 65001
      peer 1.1.1.3 {
          local-ip: 1.1.1.2
          as: 65002
          next-hop: 1.1.1.2
      }
   }
}

and configuration for ASR R1:
interfaces {
   interface em0 {
       disable: false
       vif em0 {
          disable: false
          address 2.2.2.3 {
             prefix-length: 24
             disable: false
			 broadcast: 2.2.2.255
          }
       }
   }
   interface em1 {
       disable: false
       vif em1 {
          disable: false
          address 3.3.3.2 {
             prefix-length: 24
             disable: false
			 broadcast: 3.3.3.255
          }
       }
   }
}
policy {
  policy-statement ospf {
    term export {
        from {
             protocol: "connected"
        }
    }
    term ospf2bgp {
        from {
             protocol: "ospf4"
        }
	}
  }
}

protocols {
  ospf4 {
     router-id: 22.0.0.0
     export: "ospf" /* in some tests I was able to make it work 
without this tag ie. exporting routes in AS via ospf4
     area 0.0.0.0 {
       interface em0 {
           link-type: "broadcast"
           vif em0 {
              address 2.2.2.3 {
                 hello-interval: 10
               }
           }
        }
       interface em1 {
           link-type: "broadcast"
           vif em1 {
              address 3.3.3.2 {
                 hello-interval: 10
              }
           }
        }
     }
   }
}

I strongly believe that this could be helpful for other users.

Any help would be greatly appreciated.

Thanks
Stevan


From shashikumar_249 at yahoo.co.in  Tue Oct 19 00:43:19 2010
From: shashikumar_249 at yahoo.co.in (shashi kumar)
Date: Tue, 19 Oct 2010 13:13:19 +0530 (IST)
Subject: [Xorp-users] How to enable XLOG_TRACE
Message-ID: <55662.78343.qm@web137306.mail.in.yahoo.com>

Hi All,

Can any one tell , what is the procedure to enable XLOG_TRACE? ...........?

Thanks in Advance,
shashi


-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20101019/92e943a7/attachment.html 

From diego360xen at gmail.com  Tue Oct 19 12:21:14 2010
From: diego360xen at gmail.com (=?ISO-8859-1?Q?Diego_Augusto_Pinzon_Carre=F1o?=)
Date: Tue, 19 Oct 2010 14:21:14 -0500
Subject: [Xorp-users] Xorp-users Digest, Vol 55, Issue 8
In-Reply-To: <mailman.11.1287514806.10008.xorp-users@xorp.org>
References: <mailman.11.1287514806.10008.xorp-users@xorp.org>
Message-ID: <AANLkTikxYMvk_fJda5zzDzC4KetbtyC_Gi5DEjWqvpEK@mail.gmail.com>

>
>   > 1. How to enable XLOG_TRACE (shashi kumar)
>
>
> ----------------------------------------------------------------------
> two forms you can see in rtr_mgr --help
>
the option    -v ..
but the before option its not a really "trace" but give you some pointer
where you are..
and the other set up  enviroment variable XLOG_TRACE= true.

if i wrong someone correct me..
hope help.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20101019/a7b255b3/attachment.html 

From diego360xen at gmail.com  Sat Oct 23 08:33:33 2010
From: diego360xen at gmail.com (=?ISO-8859-1?Q?Diego_Augusto_Pinzon_Carre=F1o?=)
Date: Sat, 23 Oct 2010 10:33:33 -0500
Subject: [Xorp-users] how do i remove previous versions of xorp safety?
Message-ID: <AANLkTikGLU3rPOZhXoN9js=o9MdqmkUh8ALYn3=NYs+U@mail.gmail.com>

i just want to test another versions of xorp-ct,
i  wonder how remove safety xorp-ct, to install another.

thanks.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20101023/f57f667c/attachment.html 

From greearb at candelatech.com  Sat Oct 23 11:22:28 2010
From: greearb at candelatech.com (Ben Greear)
Date: Sat, 23 Oct 2010 11:22:28 -0700
Subject: [Xorp-users] how do i remove previous versions of xorp safety?
In-Reply-To: <AANLkTikGLU3rPOZhXoN9js=o9MdqmkUh8ALYn3=NYs+U@mail.gmail.com>
References: <AANLkTikGLU3rPOZhXoN9js=o9MdqmkUh8ALYn3=NYs+U@mail.gmail.com>
Message-ID: <4CC327E4.8010504@candelatech.com>

On 10/23/2010 08:33 AM, Diego Augusto Pinzon Carre?o wrote:
> i just want to test another versions of xorp-ct,
> i  wonder how remove safety xorp-ct, to install another.

Something like:

cd /usr/local
rm -fr xorp

should do the trick.

Thanks,
Ben

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


-- 
Ben Greear <greearb at candelatech.com>
Candela Technologies Inc  http://www.candelatech.com


From JayasriS at aaesys.com  Fri Oct 22 15:50:57 2010
From: JayasriS at aaesys.com (Jayasri Sangu)
Date: Fri, 22 Oct 2010 15:50:57 -0700
Subject: [Xorp-users] no RP address for this group
Message-ID: <2DE723F44CAFD24A9B6BF606813F010C4078EAF4E3@aae-exch>

Hi All,

      I have a network

                                                    PIM router                                      PIM router
               PC1      -------------       modem   1       ------ sat link -----     modem  2------------------ PC2
10.174.102.225/24            eth0               sat0                               sat0                 eth0                10.174.101.125/24

     On modem 1   eth0  address is  10.174.102.223/24
                                sat0  address is     10.0.1.223/24
                                PIM with the multicast4_223.boot

    on modem 2   eth0  address is  10.174.101.123/24
                                sat0  address is     10.0.1.123/24
                                PIM with the multicast4_123.boot


I am trying to send  multicast packets from PC1 to PC2,  If I have a static RP then the multicast packets are forwarded tp PC2.


But If I have a bootstrap mechanism enabled , the pckets are not forwarded tp PC2.
Is something I am missing ?
Why static RP works and Why not bootstrap mechanism.

./xorp_rtrmgr -b multicast4_223.boot &
Eclipse #
Eclipse # [ 2010/10/22 22:05:09  ERROR xorp_rtrmgr:391 RTRMGR +142 userdb.cc add_user ] Group "xorp"
 does not exist on this system.
[ 2010/10/22 22:05:09  ERROR xorp_rtrmgr:391 RTRMGR +142 userdb.cc add_user ] Group "xorp" does not
exist on this system.
[ 2010/10/22 22:05:09  ERROR xorp_rtrmgr:391 RTRMGR +142 userdb.cc add_user ] Group "xorp" does not
exist on this system.
[ 2010/10/22 22:05:09  ERROR xorp_rtrmgr:391 RTRMGR +142 userdb.cc add_user ] Group "xorp" does not
exist on this system.
[ 2010/10/22 22:05:09  ERROR xorp_rtrmgr:391 RTRMGR +142 userdb.cc add_user ] Group "xorp" does not
exist on this system.
[ 2010/10/22 22:05:09  ERROR xorp_rtrmgr:391 RTRMGR +142 userdb.cc add_user ] Group "xorp" does not
exist on this system.
[ 2010/10/22 22:05:09  ERROR xorp_rtrmgr:391 RTRMGR +142 userdb.cc add_user ] Group "xorp" does not
exist on this system.
[ 2010/10/22 22:05:09  ERROR xorp_rtrmgr:391 RTRMGR +142 userdb.cc add_user ] Group "xorp" does not
exist on this system.
[ 2010/10/22 22:05:09  ERROR xorp_rtrmgr:391 RTRMGR +142 userdb.cc add_user ] Group "xorp" does not
exist on this system.
[ 2010/10/22 22:05:09  ERROR xorp_rtrmgr:391 RTRMGR +142 userdb.cc add_user ] Group "xorp" does not
exist on this system.
[ 2010/10/22 22:05:09  ERROR xorp_rtrmgr:391 RTRMGR +142 userdb.cc add_user ] Group "xorp" does not
exist on this system.
[ 2010/10/22 22:05:09  INFO xorp_rtrmgr:391 RTRMGR +249 master_conf_tree.cc execute ] Changed module
s: interfaces, firewall, fea, mfea4, rib, fib2mrib, igmp, pimsm4
[ 2010/10/22 22:05:09  INFO xorp_rtrmgr:391 RTRMGR +101 module_manager.cc execute ] Executing module
: interfaces (fea/xorp_fea)
[ 2010/10/22 22:05:11  WARNING xorp_rtrmgr:391 XrlFinderTarget +407 ../xrl/targets/finder_base.cc ha
ndle_finder_0_2_resolve_xrl ] Handling method for finder/0.2/resolve_xrl failed: XrlCmdError 102 Com
mand failed Xrl target is not enabled.
[ 2010/10/22 22:05:12  WARNING xorp_rtrmgr:391 XrlFinderTarget +407 ../xrl/targets/finder_base.cc ha
ndle_finder_0_2_resolve_xrl ] Handling method for finder/0.2/resolve_xrl failed: XrlCmdError 102 Com
mand failed Xrl target is not enabled.
[ 2010/10/22 22:05:13 INFO xorp_fea MFEA ] MFEA enabled
[ 2010/10/22 22:05:13 INFO xorp_fea MFEA ] CLI enabled
[ 2010/10/22 22:05:13 INFO xorp_fea MFEA ] CLI started
[ 2010/10/22 22:05:13 INFO xorp_fea MFEA ] MFEA enabled
[ 2010/10/22 22:05:13 INFO xorp_fea MFEA ] CLI enabled
[ 2010/10/22 22:05:13 INFO xorp_fea MFEA ] CLI started
[ 2010/10/22 22:05:13  INFO xorp_rtrmgr:391 RTRMGR +101 module_manager.cc execute ] Executing module
: firewall (fea/xorp_fea)
[ 2010/10/22 22:05:17  INFO xorp_rtrmgr:391 RTRMGR +101 module_manager.cc execute ] Executing module
: fea (fea/xorp_fea)
[ 2010/10/22 22:05:23  INFO xorp_rtrmgr:391 RTRMGR +101 module_manager.cc execute ] Executing module
: mfea4 (fea/xorp_fea)
[ 2010/10/22 22:05:23 INFO xorp_fea MFEA ] Interface added: Vif[eth0] pif_index: 2 vif_index: 0 addr
: 10.174.102.223 subnet: 10.174.102.0/24 broadcast: 10.174.102.255 peer: 0.0.0.0 Flags: MULTICAST BR
OADCAST UNDERLYING_VIF_UP MTU: 1500
[ 2010/10/22 22:05:23 INFO xorp_fea MFEA ] Interface added: Vif[sat0] pif_index: 6 vif_index: 1 addr
: 10.0.1.223 subnet: 10.0.1.0/24 broadcast: 10.0.1.255 peer: 0.0.0.0 Flags: MULTICAST BROADCAST UNDE
RLYING_VIF_UP MTU: 1500
[ 2010/10/22 22:05:23 INFO xorp_fea MFEA ] MFEA started
[ 2010/10/22 22:05:23 INFO xorp_fea MFEA ] Interface enabled Vif[eth0] pif_index: 2 vif_index: 0 add
r: 10.174.102.223 subnet: 10.174.102.0/24 broadcast: 10.174.102.255 peer: 0.0.0.0 Flags: MULTICAST B
ROADCAST UNDERLYING_VIF_UP MTU: 1500 DOWN IPv4 ENABLED
[ 2010/10/22 22:05:24 INFO xorp_fea MFEA ] Interface started: Vif[eth0] pif_index: 2 vif_index: 0 ad
dr: 10.174.102.223 subnet: 10.174.102.0/24 broadcast: 10.174.102.255 peer: 0.0.0.0 Flags: MULTICAST
BROADCAST UNDERLYING_VIF_UP MTU: 1500 UP IPv4 ENABLED
[ 2010/10/22 22:05:24 INFO xorp_fea MFEA ] Interface added: Vif[register_vif] pif_index: 2 vif_index
: 2 addr: 10.174.102.223 subnet: 10.174.102.223/32 broadcast: 10.174.102.223 peer: 0.0.0.0 Flags: PI
M_REGISTER UNDERLYING_VIF_UP MTU: 1500
[ 2010/10/22 22:05:24 INFO xorp_fea MFEA ] Interface enabled Vif[sat0] pif_index: 6 vif_index: 1 add
r: 10.0.1.223 subnet: 10.0.1.0/24 broadcast: 10.0.1.255 peer: 0.0.0.0 Flags: MULTICAST BROADCAST UND
ERLYING_VIF_UP MTU: 1500 DOWN IPv4 ENABLED
[ 2010/10/22 22:05:24 INFO xorp_fea MFEA ] Interface started: Vif[sat0] pif_index: 6 vif_index: 1 ad
dr: 10.0.1.223 subnet: 10.0.1.0/24 broadcast: 10.0.1.255 peer: 0.0.0.0 Flags: MULTICAST BROADCAST UN
DERLYING_VIF_UP MTU: 1500 UP IPv4 ENABLED
[ 2010/10/22 22:05:24 INFO xorp_fea MFEA ] Interface enabled Vif[register_vif] pif_index: 2 vif_inde
x: 2 addr: 10.174.102.223 subnet: 10.174.102.223/32 broadcast: 10.174.102.223 peer: 0.0.0.0 Flags: P
IM_REGISTER UNDERLYING_VIF_UP MTU: 1500 DOWN IPv4 ENABLED
[ 2010/10/22 22:05:24 INFO xorp_fea MFEA ] Interface started: Vif[register_vif] pif_index: 2 vif_ind
ex: 2 addr: 10.174.102.223 subnet: 10.174.102.223/32 broadcast: 10.174.102.223 peer: 0.0.0.0 Flags:
PIM_REGISTER UNDERLYING_VIF_UP MTU: 1500 UP IPv4 ENABLED
[ 2010/10/22 22:05:24  INFO xorp_rtrmgr:391 RTRMGR +101 module_manager.cc execute ] Executing module
: rib (rib/xorp_rib)
[ 2010/10/22 22:05:26  INFO xorp_rtrmgr:391 RTRMGR +101 module_manager.cc execute ] Executing module
: fib2mrib (fib2mrib/xorp_fib2mrib)
[ 2010/10/22 22:05:28  INFO xorp_rtrmgr:391 RTRMGR +101 module_manager.cc execute ] Executing module
: igmp (mld6igmp/xorp_igmp)
[ 2010/10/22 22:05:28  WARNING xorp_rtrmgr:391 XrlFinderTarget +407 ../xrl/targets/finder_base.cc ha
ndle_finder_0_2_resolve_xrl ] Handling method for finder/0.2/resolve_xrl failed: XrlCmdError 102 Com
mand failed Target "IGMP" does not exist or is not enabled.
[ 2010/10/22 22:05:28 INFO xorp_igmp MLD6IGMP ] Protocol enabled
[ 2010/10/22 22:05:28 INFO xorp_igmp MLD6IGMP ] CLI enabled
[ 2010/10/22 22:05:28 INFO xorp_igmp MLD6IGMP ] CLI started
[ 2010/10/22 22:05:30 INFO xorp_igmp MLD6IGMP ] Protocol started
[ 2010/10/22 22:05:30 INFO xorp_igmp MLD6IGMP ] Interface added: Vif[eth0] pif_index: 2 vif_index: 0
 addr: 10.174.102.223 subnet: 10.174.102.0/24 broadcast: 10.174.102.255 peer: 0.0.0.0 Flags: MULTICA
ST BROADCAST UNDERLYING_VIF_UP MTU: 1500
[ 2010/10/22 22:05:30 INFO xorp_igmp MLD6IGMP ] Interface added: Vif[sat0] pif_index: 6 vif_index: 1
 addr: 10.0.1.223 subnet: 10.0.1.0/24 broadcast: 10.0.1.255 peer: 0.0.0.0 Flags: MULTICAST BROADCAST
 UNDERLYING_VIF_UP MTU: 1500
[ 2010/10/22 22:05:30 INFO xorp_igmp MLD6IGMP ] Interface enabled: Vif[eth0] pif_index: 2 vif_index:
 0 addr: 10.174.102.223 subnet: 10.174.102.0/24 broadcast: 10.174.102.255 peer: 0.0.0.0 Flags: MULTI
CAST BROADCAST UNDERLYING_VIF_UP MTU: 1500 DOWN IPv4 ENABLED
[ 2010/10/22 22:05:30 INFO xorp_igmp MLD6IGMP ] Interface started: Vif[eth0] pif_index: 2 vif_index:
 0 addr: 10.174.102.223 subnet: 10.174.102.0/24 broadcast: 10.174.102.255 peer: 0.0.0.0 Flags: MULTI
CAST BROADCAST UNDERLYING_VIF_UP MTU: 1500 UP IPv4 ENABLED
[ 2010/10/22 22:05:30 INFO xorp_igmp MLD6IGMP ] Interface enabled: Vif[sat0] pif_index: 6 vif_index:
 1 addr: 10.0.1.223 subnet: 10.0.1.0/24 broadcast: 10.0.1.255 peer: 0.0.0.0 Flags: MULTICAST BROADCA
ST UNDERLYING_VIF_UP MTU: 1500 DOWN IPv4 ENABLED
[ 2010/10/22 22:05:30 INFO xorp_igmp MLD6IGMP ] Interface started: Vif[sat0] pif_index: 6 vif_index:
 1 addr: 10.0.1.223 subnet: 10.0.1.0/24 broadcast: 10.0.1.255 peer: 0.0.0.0 Flags: MULTICAST BROADCA
ST UNDERLYING_VIF_UP MTU: 1500 UP IPv4 ENABLED
[ 2010/10/22 22:05:30 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V3_MEMBERSHIP_REPORT from 10.0.1.223 to 224
.0.0.22 on vif sat0
[ 2010/10/22 22:05:30 TRACE xorp_igmp MLD6IGMP ] RX IGMP_MEMBERSHIP_QUERY from 10.0.1.223 to 224.0.0
.1 on vif sat0
[ 2010/10/22 22:05:30 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 10.174.102.223 to
 224.0.0.22 on vif eth0
[ 2010/10/22 22:05:30  INFO xorp_rtrmgr:391 RTRMGR +101 module_manager.cc execute ] Executing module
: pimsm4 (pim/xorp_pimsm4)
[ 2010/10/22 22:05:30  WARNING xorp_rtrmgr:391 XrlFinderTarget +407 ../xrl/targets/finder_base.cc ha
ndle_finder_0_2_resolve_xrl ] Handling method for finder/0.2/resolve_xrl failed: XrlCmdError 102 Com
mand failed Target "PIMSM_4" does not exist or is not enabled.
[ 2010/10/22 22:05:31  WARNING xorp_rtrmgr:391 XrlFinderTarget +407 ../xrl/targets/finder_base.cc ha
ndle_finder_0_2_resolve_xrl ] Handling method for finder/0.2/resolve_xrl failed: XrlCmdError 102 Com
mand failed Xrl target is not enabled.
[ 2010/10/22 22:05:32  WARNING xorp_rtrmgr:391 XrlFinderTarget +407 ../xrl/targets/finder_base.cc ha
ndle_finder_0_2_resolve_xrl ] Handling method for finder/0.2/resolve_xrl failed: XrlCmdError 102 Com
mand failed Xrl target is not enabled.
[ 2010/10/22 22:05:33 INFO xorp_pimsm4 PIM ] Protocol enabled
[ 2010/10/22 22:05:33 INFO xorp_pimsm4 PIM ] CLI enabled
[ 2010/10/22 22:05:33 INFO xorp_pimsm4 PIM ] CLI started
[ 2010/10/22 22:05:34 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 10.0.1.223 to 224
.0.0.22 on vif sat0
[ 2010/10/22 22:05:34 TRACE xorp_igmp MLD6IGMP ] Notify routing add membership for (0.0.0.0, 224.0.0
.22) on vif sat0
[ 2010/10/22 22:05:34 INFO xorp_pimsm4 PIM ] Protocol started
[ 2010/10/22 22:05:34 INFO xorp_pimsm4 PIM ] Interface added: Vif[eth0] pif_index: 2 vif_index: 0 ad
dr: 10.174.102.223 subnet: 10.174.102.0/24 broadcast: 10.174.102.255 peer: 0.0.0.0 Flags: MULTICAST
BROADCAST UNDERLYING_VIF_UP MTU: 1500
[ 2010/10/22 22:05:34 INFO xorp_pimsm4 PIM ] Interface added: Vif[register_vif] pif_index: 0 vif_ind
ex: 2 addr: 10.174.102.223 subnet: 10.174.102.223/32 broadcast: 0.0.0.0 peer: 0.0.0.0 Flags: PIM_REG
ISTER UNDERLYING_VIF_UP MTU: 1500
[ 2010/10/22 22:05:34 INFO xorp_pimsm4 PIM ] Interface added: Vif[sat0] pif_index: 6 vif_index: 1 ad
dr: 10.0.1.223 subnet: 10.0.1.0/24 broadcast: 10.0.1.255 peer: 0.0.0.0 Flags: MULTICAST BROADCAST UN
DERLYING_VIF_UP MTU: 1500
[ 2010/10/22 22:05:35 INFO xorp_pimsm4 PIM ] Interface enabled: Vif[eth0] pif_index: 2 vif_index: 0
addr: 10.174.102.223 subnet: 10.174.102.0/24 broadcast: 10.174.102.255 peer: 0.0.0.0 Flags: MULTICAS
T BROADCAST UNDERLYING_VIF_UP MTU: 1500 DOWN IPv4 ENABLED
[ 2010/10/22 22:05:35 INFO xorp_pimsm4 PIM ] Interface started: Vif[eth0] pif_index: 2 vif_index: 0
addr: 10.174.102.223 subnet: 10.174.102.0/24 broadcast: 10.174.102.255 peer: 0.0.0.0 Flags: MULTICAS
T BROADCAST UNDERLYING_VIF_UP MTU: 1500 UP IPv4 ENABLED
[ 2010/10/22 22:05:35 INFO xorp_pimsm4 PIM ] Interface enabled: Vif[sat0] pif_index: 6 vif_index: 1
addr: 10.0.1.223 subnet: 10.0.1.0/24 broadcast: 10.0.1.255 peer: 0.0.0.0 Flags: MULTICAST BROADCAST
UNDERLYING_VIF_UP MTU: 1500 DOWN IPv4 ENABLED
[ 2010/10/22 22:05:35 INFO xorp_pimsm4 PIM ] Interface started: Vif[sat0] pif_index: 6 vif_index: 1
addr: 10.0.1.223 subnet: 10.0.1.0/24 broadcast: 10.0.1.255 peer: 0.0.0.0 Flags: MULTICAST BROADCAST
UNDERLYING_VIF_UP MTU: 1500 UP IPv4 ENABLED
[ 2010/10/22 22:05:35 INFO xorp_pimsm4 PIM ] Interface enabled: Vif[register_vif] pif_index: 0 vif_i
ndex: 2 addr: 10.174.102.223 subnet: 10.174.102.223/32 broadcast: 0.0.0.0 peer: 0.0.0.0 Flags: PIM_R
EGISTER UNDERLYING_VIF_UP MTU: 1500 DOWN IPv4 ENABLED
[ 2010/10/22 22:05:36 INFO xorp_pimsm4 PIM ] Interface started: Vif[register_vif] pif_index: 0 vif_i
ndex: 2 addr: 10.174.102.223 subnet: 10.174.102.223/32 broadcast: 0.0.0.0 peer: 0.0.0.0 Flags: PIM_R
EGISTER UNDERLYING_VIF_UP MTU: 1500 UP IPv4 ENABLED
[ 2010/10/22 22:05:36 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 10.174.102.223 to
 224.0.0.13 on vif eth0
[ 2010/10/22 22:05:36 TRACE xorp_igmp MLD6IGMP ] Notify routing add membership for (0.0.0.0, 224.0.0
.13) on vif eth0
[ 2010/10/22 22:05:36 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 10.0.1.223 to 224
.0.0.13 on vif sat0
[ 2010/10/22 22:05:36 TRACE xorp_igmp MLD6IGMP ] Notify routing add membership for (0.0.0.0, 224.0.0
.13) on vif sat0
[ 2010/10/22 22:05:36  INFO xorp_rtrmgr:391 RTRMGR +2233 task.cc run_task ] No more tasks to run
[ 2010/10/22 22:05:36 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 10.174.102.223 to
 224.0.0.2 on vif eth0
[ 2010/10/22 22:05:38 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 10.0.1.223 to 224
.0.0.2 on vif sat0
[ 2010/10/22 22:05:38 TRACE xorp_igmp MLD6IGMP ] Notify routing add membership for (0.0.0.0, 224.0.0
.2) on vif sat0
[ 2010/10/22 22:05:39 TRACE xorp_pimsm4 PIM ] TX PIM_HELLO from 10.174.102.223 to 224.0.0.13 on vif
eth0
[ 2010/10/22 22:05:39 TRACE xorp_pimsm4 PIM ] TX PIM_HELLO from 10.0.1.223 to 224.0.0.13 on vif sat0
[ 2010/10/22 22:05:40 TRACE xorp_igmp MLD6IGMP ] RX IGMP_MEMBERSHIP_QUERY from 10.0.1.123 to 224.0.0
.1 on vif sat0
[ 2010/10/22 22:05:41 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 10.0.1.123 to 224
.0.0.22 on vif sat0
[ 2010/10/22 22:05:41 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 10.0.1.123 to 224
.0.0.2 on vif sat0
[ 2010/10/22 22:05:42 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 10.0.1.223 to 224
.0.0.13 on vif sat0
[ 2010/10/22 22:05:43 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 10.174.102.223 to
 224.0.0.13 on vif eth0
[ 2010/10/22 22:05:44 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 10.0.1.123 to 224
.0.0.13 on vif sat0
[ 2010/10/22 22:05:45 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 10.174.102.223 to
 224.0.0.13 on vif eth0
[ 2010/10/22 22:05:48 TRACE xorp_pimsm4 PIM ] RX PIM_HELLO from 10.0.1.123 to 224.0.0.13 on vif sat0
[ 2010/10/22 22:05:48 TRACE xorp_pimsm4 PIM ] Added new neighbor 10.0.1.123 on vif sat0
[ 2010/10/22 22:05:48 TRACE xorp_pimsm4 PIM ] TX PIM_HELLO from 10.0.1.223 to 224.0.0.13 on vif sat0
[ 2010/10/22 22:05:53 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 10.0.1.123 to 224
.0.0.13 on vif sat0
[ 2010/10/22 22:05:54 TRACE xorp_pimsm4 PIM ] RX PIM_HELLO from 10.0.1.123 to 224.0.0.13 on vif sat0
[ 2010/10/22 22:05:56 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 10.0.1.123 to 224
.0.0.13 on vif sat0
[ 2010/10/22 22:06:01 TRACE xorp_igmp MLD6IGMP ] TX IGMP_MEMBERSHIP_QUERY from 10.174.102.223 to 224
.0.0.1
[ 2010/10/22 22:06:01 TRACE xorp_igmp MLD6IGMP ] RX IGMP_MEMBERSHIP_QUERY from 10.174.102.223 to 224
.0.0.1 on vif eth0
[ 2010/10/22 22:06:01 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 10.174.102.223 to
 224.0.0.22 on vif eth0
[ 2010/10/22 22:06:08 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 10.174.102.223 to
 224.0.0.13 on vif eth0
[ 2010/10/22 22:06:08 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 10.174.102.223 to
 224.0.0.2 on vif eth0
[ 2010/10/22 22:06:09 TRACE xorp_pimsm4 PIM ] TX PIM_HELLO from 10.174.102.223 to 224.0.0.13 on vif
eth0
[ 2010/10/22 22:06:09 TRACE xorp_pimsm4 PIM ] TX PIM_HELLO from 10.0.1.223 to 224.0.0.13 on vif sat0
[ 2010/10/22 22:06:09 TRACE xorp_igmp MLD6IGMP ] RX IGMP_MEMBERSHIP_QUERY from 10.0.1.123 to 224.0.0
.1 on vif sat0
[ 2010/10/22 22:06:10 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 10.0.1.223 to 224
.0.0.22 on vif sat0
[ 2010/10/22 22:06:11 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 10.0.1.123 to 224
.0.0.22 on vif sat0
[ 2010/10/22 22:06:13 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 10.0.1.123 to 224
.0.0.2 on vif sat0
[ 2010/10/22 22:06:16 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 10.0.1.123 to 224
.0.0.13 on vif sat0
[ 2010/10/22 22:06:19 TRACE xorp_pimsm4 PIM ] RX PIM_HELLO from 10.0.1.123 to 224.0.0.13 on vif sat0
[ 2010/10/22 22:06:39 TRACE xorp_pimsm4 PIM ] TX PIM_HELLO from 10.174.102.223 to 224.0.0.13 on vif
eth0
[ 2010/10/22 22:06:39 TRACE xorp_pimsm4 PIM ] TX PIM_HELLO from 10.0.1.223 to 224.0.0.13 on vif sat0
[ 2010/10/22 22:06:49 TRACE xorp_pimsm4 PIM ] RX PIM_HELLO from 10.0.1.123 to 224.0.0.13 on vif sat0
[ 2010/10/22 22:07:09 TRACE xorp_pimsm4 PIM ] TX PIM_HELLO from 10.174.102.223 to 224.0.0.13 on vif
eth0
[ 2010/10/22 22:07:09 TRACE xorp_pimsm4 PIM ] TX PIM_HELLO from 10.0.1.223 to 224.0.0.13 on vif sat0
[ 2010/10/22 22:07:19 TRACE xorp_pimsm4 PIM ] RX PIM_HELLO from 10.0.1.123 to 224.0.0.13 on vif sat0
[ 2010/10/22 22:07:39 TRACE xorp_pimsm4 PIM ] TX PIM_HELLO from 10.174.102.223 to 224.0.0.13 on vif
eth0
[ 2010/10/22 22:07:39 TRACE xorp_pimsm4 PIM ] TX PIM_HELLO from 10.0.1.223 to 224.0.0.13 on vif sat0
[ 2010/10/22 22:07:48 TRACE xorp_pimsm4 PIM ] RX PIM_HELLO from 10.0.1.123 to 224.0.0.13 on vif sat0
[ 2010/10/22 22:07:55 TRACE xorp_pimsm4 PIM ] RX PIM_BOOTSTRAP from 10.0.1.123 to 224.0.0.13 on vif
sat0

Eclipse #
Eclipse # route
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
10.0.1.0        *               255.255.255.0   U     0      0        0 sat0
10.174.102.0    *               255.255.255.0   U     0      0        0 eth0
default         10.0.1.123      0.0.0.0         UG    0      0        0 sat0
Eclipse # [ 2010/10/22 22:08:06 TRACE xorp_igmp MLD6IGMP ] TX IGMP_MEMBERSHIP_QUERY from 10.174.102.
223 to 224.0.0.1
[ 2010/10/22 22:08:06 TRACE xorp_igmp MLD6IGMP ] RX IGMP_MEMBERSHIP_QUERY from 10.174.102.223 to 224
.0.0.1 on vif eth0
[ 2010/10/22 22:08:08 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 10.174.102.223 to
 224.0.0.2 on vif eth0
[ 2010/10/22 22:08:09 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 10.174.102.223 to
 224.0.0.13 on vif eth0
[ 2010/10/22 22:08:09 TRACE xorp_pimsm4 PIM ] TX PIM_HELLO from 10.174.102.223 to 224.0.0.13 on vif
eth0
[ 2010/10/22 22:08:09 TRACE xorp_pimsm4 PIM ] TX PIM_HELLO from 10.0.1.223 to 224.0.0.13 on vif sat0
[ 2010/10/22 22:08:12 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 10.174.102.223 to
 224.0.0.22 on vif eth0
[ 2010/10/22 22:08:14 TRACE xorp_igmp MLD6IGMP ] RX IGMP_MEMBERSHIP_QUERY from 10.0.1.123 to 224.0.0
.1 on vif sat0
[ 2010/10/22 22:08:15 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 10.0.1.223 to 224
.0.0.22 on vif sat0
[ 2010/10/22 22:08:18 TRACE xorp_pimsm4 PIM ] RX PIM_HELLO from 10.0.1.123 to 224.0.0.13 on vif sat0
[ 2010/10/22 22:08:19 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 10.0.1.223 to 224
.0.0.2 on vif sat0
[ 2010/10/22 22:08:20 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 10.0.1.123 to 224
.0.0.2 on vif sat0
[ 2010/10/22 22:08:21 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 10.0.1.123 to 224
.0.0.13 on vif sat0
[ 2010/10/22 22:08:31 TRACE xorp_pimsm4 PIM ] RX NOCACHE signal from MFEA_4: vif_index = 0 src = 10.
174.102.225 dst = 224.0.1.20
[ 2010/10/22 22:08:31 TRACE xorp_pimsm4 PIM ] Add MFC entry: (10.174.102.225, 224.0.1.20) iif = 0 ol
ist = ..O olist_disable_wrongvif = OO.
[ 2010/10/22 22:08:31 TRACE xorp_pimsm4 PIM ] Add dataflow monitor: source = 10.174.102.225 group =
224.0.1.20 threshold_interval_sec = 210 threshold_interval_usec = 0 threshold_packets = 0 threshold_
bytes = 0 is_threshold_in_packets = 1 is_threshold_in_bytes = 0 is_geq_upcall = 0 is_leq_upcall = 1
[ 2010/10/22 22:08:31 TRACE xorp_pimsm4 PIM ] RX WHOLEPKT signal from MFEA_4: vif_index = 2 src = 10
.174.102.225 dst = 224.0.1.20 len = 39
[ 2010/10/22 22:08:31 WARNING xorp_pimsm4 PIM ] RX WHOLEPKT signal from MFEA_4: vif_index = 2 src =
10.174.102.225 dst = 224.0.1.20 len = 39: no RP address for this group
[ 2010/10/22 22:08:39 TRACE xorp_pimsm4 PIM ] TX PIM_HELLO from 10.174.102.223 to 224.0.0.13 on vif
eth0
[ 2010/10/22 22:08:39 TRACE xorp_pimsm4 PIM ] TX PIM_HELLO from 10.0.1.223 to 224.0.0.13 on vif sat0
[ 2010/10/22 22:08:48 TRACE xorp_pimsm4 PIM ] RX PIM_HELLO from 10.0.1.123 to 224.0.0.13 on vif sat0



-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20101022/5a2769b2/attachment-0001.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: multicast4_223.boot
Type: application/octet-stream
Size: 1921 bytes
Desc: multicast4_223.boot
Url : http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20101022/5a2769b2/attachment-0002.obj 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: multicast4_123.boot
Type: application/octet-stream
Size: 1921 bytes
Desc: multicast4_123.boot
Url : http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20101022/5a2769b2/attachment-0003.obj 

From diego360xen at gmail.com  Sat Oct 23 15:36:57 2010
From: diego360xen at gmail.com (=?ISO-8859-1?Q?Diego_Augusto_Pinzon_Carre=F1o?=)
Date: Sat, 23 Oct 2010 17:36:57 -0500
Subject: [Xorp-users] hi Jayasri Sangu, some inf
Message-ID: <AANLkTi=Rhv0ApFniSdN28z3GOeXjM9qq-FjOhKnn=khH@mail.gmail.com>

 hi Jayasri Sangu::

i just wonder wich OS do you install xorp and version.?

and did you OS come from a DVD or a CD ?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20101023/10aa8220/attachment.html 

From JayasriS at aaesys.com  Wed Oct 27 11:52:56 2010
From: JayasriS at aaesys.com (Jayasri Sangu)
Date: Wed, 27 Oct 2010 11:52:56 -0700
Subject: [Xorp-users] no RP address for this group
In-Reply-To: <2DE723F44CAFD24A9B6BF606813F010C4078EAF4E3@aae-exch>
References: <2DE723F44CAFD24A9B6BF606813F010C4078EAF4E3@aae-exch>
Message-ID: <2DE723F44CAFD24A9B6BF606813F010C4078EAF58C@aae-exch>

Hi,

       My modems are running embedded linux with  kernel 2.6.26.  And xorp version is xorp-1.6.

After debugging the xorp code, I found that rp-holdtime  is initialized to 0.  As per the XORP manual the default value for  rp-holdtime is 150.

Why  rp-holdtime  is initialized to 0 ??

And also when I start the xorp_rtrmgr, why I am getting the following warning?


[ 2010/10/22 22:05:30  WARNING xorp_rtrmgr:391 XrlFinderTarget +407 ../xrl/targets/finder_base.cc ha
ndle_finder_0_2_resolve_xrl ] Handling method for finder/0.2/resolve_xrl failed: XrlCmdError 102 Com
mand failed Target "PIMSM_4" does not exist or is not enabled.
[ 2010/10/22 22:05:31  WARNING xorp_rtrmgr:391 XrlFinderTarget +407 ../xrl/targets/finder_base.cc ha
ndle_finder_0_2_resolve_xrl ] Handling method for finder/0.2/resolve_xrl failed: XrlCmdError 102 Com
mand failed Xrl target is not enabled.
[ 2010/10/22 22:05:32  WARNING xorp_rtrmgr:391 XrlFinderTarget +407 ../xrl/targets/finder_base.cc ha
ndle_finder_0_2_resolve_xrl ] Handling method for finder/0.2/resolve_xrl failed: XrlCmdError 102 Com
mand failed Xrl target is not enabled.


Thanks,
Jayasri Sangu


From: xorp-users-bounces at xorp.org [mailto:xorp-users-bounces at xorp.org] On Behalf Of Jayasri Sangu
Sent: Friday, October 22, 2010 3:51 PM
To: xorp-users at xorp.org
Subject: [Xorp-users] no RP address for this group

Hi All,

      I have a network

                                                    PIM router                                      PIM router
               PC1      -------------       modem   1       ------ sat link -----     modem  2------------------ PC2
10.174.102.225/24            eth0               sat0                               sat0                 eth0                10.174.101.125/24

     On modem 1   eth0  address is  10.174.102.223/24
                                sat0  address is     10.0.1.223/24
                                PIM with the multicast4_223.boot

    on modem 2   eth0  address is  10.174.101.123/24
                                sat0  address is     10.0.1.123/24
                                PIM with the multicast4_123.boot


I am trying to send  multicast packets from PC1 to PC2,  If I have a static RP then the multicast packets are forwarded tp PC2.


But If I have a bootstrap mechanism enabled , the pckets are not forwarded tp PC2.
Is something I am missing ?
Why static RP works and Why not bootstrap mechanism.

./xorp_rtrmgr -b multicast4_223.boot &
Eclipse #
Eclipse # [ 2010/10/22 22:05:09  ERROR xorp_rtrmgr:391 RTRMGR +142 userdb.cc add_user ] Group "xorp"
 does not exist on this system.
[ 2010/10/22 22:05:09  ERROR xorp_rtrmgr:391 RTRMGR +142 userdb.cc add_user ] Group "xorp" does not
exist on this system.
[ 2010/10/22 22:05:09  ERROR xorp_rtrmgr:391 RTRMGR +142 userdb.cc add_user ] Group "xorp" does not
exist on this system.
[ 2010/10/22 22:05:09  ERROR xorp_rtrmgr:391 RTRMGR +142 userdb.cc add_user ] Group "xorp" does not
exist on this system.
[ 2010/10/22 22:05:09  ERROR xorp_rtrmgr:391 RTRMGR +142 userdb.cc add_user ] Group "xorp" does not
exist on this system.
[ 2010/10/22 22:05:09  ERROR xorp_rtrmgr:391 RTRMGR +142 userdb.cc add_user ] Group "xorp" does not
exist on this system.
[ 2010/10/22 22:05:09  ERROR xorp_rtrmgr:391 RTRMGR +142 userdb.cc add_user ] Group "xorp" does not
exist on this system.
[ 2010/10/22 22:05:09  ERROR xorp_rtrmgr:391 RTRMGR +142 userdb.cc add_user ] Group "xorp" does not
exist on this system.
[ 2010/10/22 22:05:09  ERROR xorp_rtrmgr:391 RTRMGR +142 userdb.cc add_user ] Group "xorp" does not
exist on this system.
[ 2010/10/22 22:05:09  ERROR xorp_rtrmgr:391 RTRMGR +142 userdb.cc add_user ] Group "xorp" does not
exist on this system.
[ 2010/10/22 22:05:09  ERROR xorp_rtrmgr:391 RTRMGR +142 userdb.cc add_user ] Group "xorp" does not
exist on this system.
[ 2010/10/22 22:05:09  INFO xorp_rtrmgr:391 RTRMGR +249 master_conf_tree.cc execute ] Changed module
s: interfaces, firewall, fea, mfea4, rib, fib2mrib, igmp, pimsm4
[ 2010/10/22 22:05:09  INFO xorp_rtrmgr:391 RTRMGR +101 module_manager.cc execute ] Executing module
: interfaces (fea/xorp_fea)
[ 2010/10/22 22:05:11  WARNING xorp_rtrmgr:391 XrlFinderTarget +407 ../xrl/targets/finder_base.cc ha
ndle_finder_0_2_resolve_xrl ] Handling method for finder/0.2/resolve_xrl failed: XrlCmdError 102 Com
mand failed Xrl target is not enabled.
[ 2010/10/22 22:05:12  WARNING xorp_rtrmgr:391 XrlFinderTarget +407 ../xrl/targets/finder_base.cc ha
ndle_finder_0_2_resolve_xrl ] Handling method for finder/0.2/resolve_xrl failed: XrlCmdError 102 Com
mand failed Xrl target is not enabled.
[ 2010/10/22 22:05:13 INFO xorp_fea MFEA ] MFEA enabled
[ 2010/10/22 22:05:13 INFO xorp_fea MFEA ] CLI enabled
[ 2010/10/22 22:05:13 INFO xorp_fea MFEA ] CLI started
[ 2010/10/22 22:05:13 INFO xorp_fea MFEA ] MFEA enabled
[ 2010/10/22 22:05:13 INFO xorp_fea MFEA ] CLI enabled
[ 2010/10/22 22:05:13 INFO xorp_fea MFEA ] CLI started
[ 2010/10/22 22:05:13  INFO xorp_rtrmgr:391 RTRMGR +101 module_manager.cc execute ] Executing module
: firewall (fea/xorp_fea)
[ 2010/10/22 22:05:17  INFO xorp_rtrmgr:391 RTRMGR +101 module_manager.cc execute ] Executing module
: fea (fea/xorp_fea)
[ 2010/10/22 22:05:23  INFO xorp_rtrmgr:391 RTRMGR +101 module_manager.cc execute ] Executing module
: mfea4 (fea/xorp_fea)
[ 2010/10/22 22:05:23 INFO xorp_fea MFEA ] Interface added: Vif[eth0] pif_index: 2 vif_index: 0 addr
: 10.174.102.223 subnet: 10.174.102.0/24 broadcast: 10.174.102.255 peer: 0.0.0.0 Flags: MULTICAST BR
OADCAST UNDERLYING_VIF_UP MTU: 1500
[ 2010/10/22 22:05:23 INFO xorp_fea MFEA ] Interface added: Vif[sat0] pif_index: 6 vif_index: 1 addr
: 10.0.1.223 subnet: 10.0.1.0/24 broadcast: 10.0.1.255 peer: 0.0.0.0 Flags: MULTICAST BROADCAST UNDE
RLYING_VIF_UP MTU: 1500
[ 2010/10/22 22:05:23 INFO xorp_fea MFEA ] MFEA started
[ 2010/10/22 22:05:23 INFO xorp_fea MFEA ] Interface enabled Vif[eth0] pif_index: 2 vif_index: 0 add
r: 10.174.102.223 subnet: 10.174.102.0/24 broadcast: 10.174.102.255 peer: 0.0.0.0 Flags: MULTICAST B
ROADCAST UNDERLYING_VIF_UP MTU: 1500 DOWN IPv4 ENABLED
[ 2010/10/22 22:05:24 INFO xorp_fea MFEA ] Interface started: Vif[eth0] pif_index: 2 vif_index: 0 ad
dr: 10.174.102.223 subnet: 10.174.102.0/24 broadcast: 10.174.102.255 peer: 0.0.0.0 Flags: MULTICAST
BROADCAST UNDERLYING_VIF_UP MTU: 1500 UP IPv4 ENABLED
[ 2010/10/22 22:05:24 INFO xorp_fea MFEA ] Interface added: Vif[register_vif] pif_index: 2 vif_index
: 2 addr: 10.174.102.223 subnet: 10.174.102.223/32 broadcast: 10.174.102.223 peer: 0.0.0.0 Flags: PI
M_REGISTER UNDERLYING_VIF_UP MTU: 1500
[ 2010/10/22 22:05:24 INFO xorp_fea MFEA ] Interface enabled Vif[sat0] pif_index: 6 vif_index: 1 add
r: 10.0.1.223 subnet: 10.0.1.0/24 broadcast: 10.0.1.255 peer: 0.0.0.0 Flags: MULTICAST BROADCAST UND
ERLYING_VIF_UP MTU: 1500 DOWN IPv4 ENABLED
[ 2010/10/22 22:05:24 INFO xorp_fea MFEA ] Interface started: Vif[sat0] pif_index: 6 vif_index: 1 ad
dr: 10.0.1.223 subnet: 10.0.1.0/24 broadcast: 10.0.1.255 peer: 0.0.0.0 Flags: MULTICAST BROADCAST UN
DERLYING_VIF_UP MTU: 1500 UP IPv4 ENABLED
[ 2010/10/22 22:05:24 INFO xorp_fea MFEA ] Interface enabled Vif[register_vif] pif_index: 2 vif_inde
x: 2 addr: 10.174.102.223 subnet: 10.174.102.223/32 broadcast: 10.174.102.223 peer: 0.0.0.0 Flags: P
IM_REGISTER UNDERLYING_VIF_UP MTU: 1500 DOWN IPv4 ENABLED
[ 2010/10/22 22:05:24 INFO xorp_fea MFEA ] Interface started: Vif[register_vif] pif_index: 2 vif_ind
ex: 2 addr: 10.174.102.223 subnet: 10.174.102.223/32 broadcast: 10.174.102.223 peer: 0.0.0.0 Flags:
PIM_REGISTER UNDERLYING_VIF_UP MTU: 1500 UP IPv4 ENABLED
[ 2010/10/22 22:05:24  INFO xorp_rtrmgr:391 RTRMGR +101 module_manager.cc execute ] Executing module
: rib (rib/xorp_rib)
[ 2010/10/22 22:05:26  INFO xorp_rtrmgr:391 RTRMGR +101 module_manager.cc execute ] Executing module
: fib2mrib (fib2mrib/xorp_fib2mrib)
[ 2010/10/22 22:05:28  INFO xorp_rtrmgr:391 RTRMGR +101 module_manager.cc execute ] Executing module
: igmp (mld6igmp/xorp_igmp)
[ 2010/10/22 22:05:28  WARNING xorp_rtrmgr:391 XrlFinderTarget +407 ../xrl/targets/finder_base.cc ha
ndle_finder_0_2_resolve_xrl ] Handling method for finder/0.2/resolve_xrl failed: XrlCmdError 102 Com
mand failed Target "IGMP" does not exist or is not enabled.
[ 2010/10/22 22:05:28 INFO xorp_igmp MLD6IGMP ] Protocol enabled
[ 2010/10/22 22:05:28 INFO xorp_igmp MLD6IGMP ] CLI enabled
[ 2010/10/22 22:05:28 INFO xorp_igmp MLD6IGMP ] CLI started
[ 2010/10/22 22:05:30 INFO xorp_igmp MLD6IGMP ] Protocol started
[ 2010/10/22 22:05:30 INFO xorp_igmp MLD6IGMP ] Interface added: Vif[eth0] pif_index: 2 vif_index: 0
 addr: 10.174.102.223 subnet: 10.174.102.0/24 broadcast: 10.174.102.255 peer: 0.0.0.0 Flags: MULTICA
ST BROADCAST UNDERLYING_VIF_UP MTU: 1500
[ 2010/10/22 22:05:30 INFO xorp_igmp MLD6IGMP ] Interface added: Vif[sat0] pif_index: 6 vif_index: 1
 addr: 10.0.1.223 subnet: 10.0.1.0/24 broadcast: 10.0.1.255 peer: 0.0.0.0 Flags: MULTICAST BROADCAST
 UNDERLYING_VIF_UP MTU: 1500
[ 2010/10/22 22:05:30 INFO xorp_igmp MLD6IGMP ] Interface enabled: Vif[eth0] pif_index: 2 vif_index:
 0 addr: 10.174.102.223 subnet: 10.174.102.0/24 broadcast: 10.174.102.255 peer: 0.0.0.0 Flags: MULTI
CAST BROADCAST UNDERLYING_VIF_UP MTU: 1500 DOWN IPv4 ENABLED
[ 2010/10/22 22:05:30 INFO xorp_igmp MLD6IGMP ] Interface started: Vif[eth0] pif_index: 2 vif_index:
 0 addr: 10.174.102.223 subnet: 10.174.102.0/24 broadcast: 10.174.102.255 peer: 0.0.0.0 Flags: MULTI
CAST BROADCAST UNDERLYING_VIF_UP MTU: 1500 UP IPv4 ENABLED
[ 2010/10/22 22:05:30 INFO xorp_igmp MLD6IGMP ] Interface enabled: Vif[sat0] pif_index: 6 vif_index:
 1 addr: 10.0.1.223 subnet: 10.0.1.0/24 broadcast: 10.0.1.255 peer: 0.0.0.0 Flags: MULTICAST BROADCA
ST UNDERLYING_VIF_UP MTU: 1500 DOWN IPv4 ENABLED
[ 2010/10/22 22:05:30 INFO xorp_igmp MLD6IGMP ] Interface started: Vif[sat0] pif_index: 6 vif_index:
 1 addr: 10.0.1.223 subnet: 10.0.1.0/24 broadcast: 10.0.1.255 peer: 0.0.0.0 Flags: MULTICAST BROADCA
ST UNDERLYING_VIF_UP MTU: 1500 UP IPv4 ENABLED
[ 2010/10/22 22:05:30 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V3_MEMBERSHIP_REPORT from 10.0.1.223 to 224
.0.0.22 on vif sat0
[ 2010/10/22 22:05:30 TRACE xorp_igmp MLD6IGMP ] RX IGMP_MEMBERSHIP_QUERY from 10.0.1.223 to 224.0.0
.1 on vif sat0
[ 2010/10/22 22:05:30 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 10.174.102.223 to
 224.0.0.22 on vif eth0
[ 2010/10/22 22:05:30  INFO xorp_rtrmgr:391 RTRMGR +101 module_manager.cc execute ] Executing module
: pimsm4 (pim/xorp_pimsm4)
[ 2010/10/22 22:05:30  WARNING xorp_rtrmgr:391 XrlFinderTarget +407 ../xrl/targets/finder_base.cc ha
ndle_finder_0_2_resolve_xrl ] Handling method for finder/0.2/resolve_xrl failed: XrlCmdError 102 Com
mand failed Target "PIMSM_4" does not exist or is not enabled.
[ 2010/10/22 22:05:31  WARNING xorp_rtrmgr:391 XrlFinderTarget +407 ../xrl/targets/finder_base.cc ha
ndle_finder_0_2_resolve_xrl ] Handling method for finder/0.2/resolve_xrl failed: XrlCmdError 102 Com
mand failed Xrl target is not enabled.
[ 2010/10/22 22:05:32  WARNING xorp_rtrmgr:391 XrlFinderTarget +407 ../xrl/targets/finder_base.cc ha
ndle_finder_0_2_resolve_xrl ] Handling method for finder/0.2/resolve_xrl failed: XrlCmdError 102 Com
mand failed Xrl target is not enabled.
[ 2010/10/22 22:05:33 INFO xorp_pimsm4 PIM ] Protocol enabled
[ 2010/10/22 22:05:33 INFO xorp_pimsm4 PIM ] CLI enabled
[ 2010/10/22 22:05:33 INFO xorp_pimsm4 PIM ] CLI started
[ 2010/10/22 22:05:34 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 10.0.1.223 to 224
.0.0.22 on vif sat0
[ 2010/10/22 22:05:34 TRACE xorp_igmp MLD6IGMP ] Notify routing add membership for (0.0.0.0, 224.0.0
.22) on vif sat0
[ 2010/10/22 22:05:34 INFO xorp_pimsm4 PIM ] Protocol started
[ 2010/10/22 22:05:34 INFO xorp_pimsm4 PIM ] Interface added: Vif[eth0] pif_index: 2 vif_index: 0 ad
dr: 10.174.102.223 subnet: 10.174.102.0/24 broadcast: 10.174.102.255 peer: 0.0.0.0 Flags: MULTICAST
BROADCAST UNDERLYING_VIF_UP MTU: 1500
[ 2010/10/22 22:05:34 INFO xorp_pimsm4 PIM ] Interface added: Vif[register_vif] pif_index: 0 vif_ind
ex: 2 addr: 10.174.102.223 subnet: 10.174.102.223/32 broadcast: 0.0.0.0 peer: 0.0.0.0 Flags: PIM_REG
ISTER UNDERLYING_VIF_UP MTU: 1500
[ 2010/10/22 22:05:34 INFO xorp_pimsm4 PIM ] Interface added: Vif[sat0] pif_index: 6 vif_index: 1 ad
dr: 10.0.1.223 subnet: 10.0.1.0/24 broadcast: 10.0.1.255 peer: 0.0.0.0 Flags: MULTICAST BROADCAST UN
DERLYING_VIF_UP MTU: 1500
[ 2010/10/22 22:05:35 INFO xorp_pimsm4 PIM ] Interface enabled: Vif[eth0] pif_index: 2 vif_index: 0
addr: 10.174.102.223 subnet: 10.174.102.0/24 broadcast: 10.174.102.255 peer: 0.0.0.0 Flags: MULTICAS
T BROADCAST UNDERLYING_VIF_UP MTU: 1500 DOWN IPv4 ENABLED
[ 2010/10/22 22:05:35 INFO xorp_pimsm4 PIM ] Interface started: Vif[eth0] pif_index: 2 vif_index: 0
addr: 10.174.102.223 subnet: 10.174.102.0/24 broadcast: 10.174.102.255 peer: 0.0.0.0 Flags: MULTICAS
T BROADCAST UNDERLYING_VIF_UP MTU: 1500 UP IPv4 ENABLED
[ 2010/10/22 22:05:35 INFO xorp_pimsm4 PIM ] Interface enabled: Vif[sat0] pif_index: 6 vif_index: 1
addr: 10.0.1.223 subnet: 10.0.1.0/24 broadcast: 10.0.1.255 peer: 0.0.0.0 Flags: MULTICAST BROADCAST
UNDERLYING_VIF_UP MTU: 1500 DOWN IPv4 ENABLED
[ 2010/10/22 22:05:35 INFO xorp_pimsm4 PIM ] Interface started: Vif[sat0] pif_index: 6 vif_index: 1
addr: 10.0.1.223 subnet: 10.0.1.0/24 broadcast: 10.0.1.255 peer: 0.0.0.0 Flags: MULTICAST BROADCAST
UNDERLYING_VIF_UP MTU: 1500 UP IPv4 ENABLED
[ 2010/10/22 22:05:35 INFO xorp_pimsm4 PIM ] Interface enabled: Vif[register_vif] pif_index: 0 vif_i
ndex: 2 addr: 10.174.102.223 subnet: 10.174.102.223/32 broadcast: 0.0.0.0 peer: 0.0.0.0 Flags: PIM_R
EGISTER UNDERLYING_VIF_UP MTU: 1500 DOWN IPv4 ENABLED
[ 2010/10/22 22:05:36 INFO xorp_pimsm4 PIM ] Interface started: Vif[register_vif] pif_index: 0 vif_i
ndex: 2 addr: 10.174.102.223 subnet: 10.174.102.223/32 broadcast: 0.0.0.0 peer: 0.0.0.0 Flags: PIM_R
EGISTER UNDERLYING_VIF_UP MTU: 1500 UP IPv4 ENABLED
[ 2010/10/22 22:05:36 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 10.174.102.223 to
 224.0.0.13 on vif eth0
[ 2010/10/22 22:05:36 TRACE xorp_igmp MLD6IGMP ] Notify routing add membership for (0.0.0.0, 224.0.0
.13) on vif eth0
[ 2010/10/22 22:05:36 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 10.0.1.223 to 224
.0.0.13 on vif sat0
[ 2010/10/22 22:05:36 TRACE xorp_igmp MLD6IGMP ] Notify routing add membership for (0.0.0.0, 224.0.0
.13) on vif sat0
[ 2010/10/22 22:05:36  INFO xorp_rtrmgr:391 RTRMGR +2233 task.cc run_task ] No more tasks to run
[ 2010/10/22 22:05:36 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 10.174.102.223 to
 224.0.0.2 on vif eth0
[ 2010/10/22 22:05:38 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 10.0.1.223 to 224
.0.0.2 on vif sat0
[ 2010/10/22 22:05:38 TRACE xorp_igmp MLD6IGMP ] Notify routing add membership for (0.0.0.0, 224.0.0
.2) on vif sat0
[ 2010/10/22 22:05:39 TRACE xorp_pimsm4 PIM ] TX PIM_HELLO from 10.174.102.223 to 224.0.0.13 on vif
eth0
[ 2010/10/22 22:05:39 TRACE xorp_pimsm4 PIM ] TX PIM_HELLO from 10.0.1.223 to 224.0.0.13 on vif sat0
[ 2010/10/22 22:05:40 TRACE xorp_igmp MLD6IGMP ] RX IGMP_MEMBERSHIP_QUERY from 10.0.1.123 to 224.0.0
.1 on vif sat0
[ 2010/10/22 22:05:41 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 10.0.1.123 to 224
.0.0.22 on vif sat0
[ 2010/10/22 22:05:41 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 10.0.1.123 to 224
.0.0.2 on vif sat0
[ 2010/10/22 22:05:42 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 10.0.1.223 to 224
.0.0.13 on vif sat0
[ 2010/10/22 22:05:43 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 10.174.102.223 to
 224.0.0.13 on vif eth0
[ 2010/10/22 22:05:44 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 10.0.1.123 to 224
.0.0.13 on vif sat0
[ 2010/10/22 22:05:45 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 10.174.102.223 to
 224.0.0.13 on vif eth0
[ 2010/10/22 22:05:48 TRACE xorp_pimsm4 PIM ] RX PIM_HELLO from 10.0.1.123 to 224.0.0.13 on vif sat0
[ 2010/10/22 22:05:48 TRACE xorp_pimsm4 PIM ] Added new neighbor 10.0.1.123 on vif sat0
[ 2010/10/22 22:05:48 TRACE xorp_pimsm4 PIM ] TX PIM_HELLO from 10.0.1.223 to 224.0.0.13 on vif sat0
[ 2010/10/22 22:05:53 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 10.0.1.123 to 224
.0.0.13 on vif sat0
[ 2010/10/22 22:05:54 TRACE xorp_pimsm4 PIM ] RX PIM_HELLO from 10.0.1.123 to 224.0.0.13 on vif sat0
[ 2010/10/22 22:05:56 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 10.0.1.123 to 224
.0.0.13 on vif sat0
[ 2010/10/22 22:06:01 TRACE xorp_igmp MLD6IGMP ] TX IGMP_MEMBERSHIP_QUERY from 10.174.102.223 to 224
.0.0.1
[ 2010/10/22 22:06:01 TRACE xorp_igmp MLD6IGMP ] RX IGMP_MEMBERSHIP_QUERY from 10.174.102.223 to 224
.0.0.1 on vif eth0
[ 2010/10/22 22:06:01 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 10.174.102.223 to
 224.0.0.22 on vif eth0
[ 2010/10/22 22:06:08 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 10.174.102.223 to
 224.0.0.13 on vif eth0
[ 2010/10/22 22:06:08 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 10.174.102.223 to
 224.0.0.2 on vif eth0
[ 2010/10/22 22:06:09 TRACE xorp_pimsm4 PIM ] TX PIM_HELLO from 10.174.102.223 to 224.0.0.13 on vif
eth0
[ 2010/10/22 22:06:09 TRACE xorp_pimsm4 PIM ] TX PIM_HELLO from 10.0.1.223 to 224.0.0.13 on vif sat0
[ 2010/10/22 22:06:09 TRACE xorp_igmp MLD6IGMP ] RX IGMP_MEMBERSHIP_QUERY from 10.0.1.123 to 224.0.0
.1 on vif sat0
[ 2010/10/22 22:06:10 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 10.0.1.223 to 224
.0.0.22 on vif sat0
[ 2010/10/22 22:06:11 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 10.0.1.123 to 224
.0.0.22 on vif sat0
[ 2010/10/22 22:06:13 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 10.0.1.123 to 224
.0.0.2 on vif sat0
[ 2010/10/22 22:06:16 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 10.0.1.123 to 224
.0.0.13 on vif sat0
[ 2010/10/22 22:06:19 TRACE xorp_pimsm4 PIM ] RX PIM_HELLO from 10.0.1.123 to 224.0.0.13 on vif sat0
[ 2010/10/22 22:06:39 TRACE xorp_pimsm4 PIM ] TX PIM_HELLO from 10.174.102.223 to 224.0.0.13 on vif
eth0
[ 2010/10/22 22:06:39 TRACE xorp_pimsm4 PIM ] TX PIM_HELLO from 10.0.1.223 to 224.0.0.13 on vif sat0
[ 2010/10/22 22:06:49 TRACE xorp_pimsm4 PIM ] RX PIM_HELLO from 10.0.1.123 to 224.0.0.13 on vif sat0
[ 2010/10/22 22:07:09 TRACE xorp_pimsm4 PIM ] TX PIM_HELLO from 10.174.102.223 to 224.0.0.13 on vif
eth0
[ 2010/10/22 22:07:09 TRACE xorp_pimsm4 PIM ] TX PIM_HELLO from 10.0.1.223 to 224.0.0.13 on vif sat0
[ 2010/10/22 22:07:19 TRACE xorp_pimsm4 PIM ] RX PIM_HELLO from 10.0.1.123 to 224.0.0.13 on vif sat0
[ 2010/10/22 22:07:39 TRACE xorp_pimsm4 PIM ] TX PIM_HELLO from 10.174.102.223 to 224.0.0.13 on vif
eth0
[ 2010/10/22 22:07:39 TRACE xorp_pimsm4 PIM ] TX PIM_HELLO from 10.0.1.223 to 224.0.0.13 on vif sat0
[ 2010/10/22 22:07:48 TRACE xorp_pimsm4 PIM ] RX PIM_HELLO from 10.0.1.123 to 224.0.0.13 on vif sat0
[ 2010/10/22 22:07:55 TRACE xorp_pimsm4 PIM ] RX PIM_BOOTSTRAP from 10.0.1.123 to 224.0.0.13 on vif
sat0

Eclipse #
Eclipse # route
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
10.0.1.0        *               255.255.255.0   U     0      0        0 sat0
10.174.102.0    *               255.255.255.0   U     0      0        0 eth0
default         10.0.1.123      0.0.0.0         UG    0      0        0 sat0
Eclipse # [ 2010/10/22 22:08:06 TRACE xorp_igmp MLD6IGMP ] TX IGMP_MEMBERSHIP_QUERY from 10.174.102.
223 to 224.0.0.1
[ 2010/10/22 22:08:06 TRACE xorp_igmp MLD6IGMP ] RX IGMP_MEMBERSHIP_QUERY from 10.174.102.223 to 224
.0.0.1 on vif eth0
[ 2010/10/22 22:08:08 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 10.174.102.223 to
 224.0.0.2 on vif eth0
[ 2010/10/22 22:08:09 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 10.174.102.223 to
 224.0.0.13 on vif eth0
[ 2010/10/22 22:08:09 TRACE xorp_pimsm4 PIM ] TX PIM_HELLO from 10.174.102.223 to 224.0.0.13 on vif
eth0
[ 2010/10/22 22:08:09 TRACE xorp_pimsm4 PIM ] TX PIM_HELLO from 10.0.1.223 to 224.0.0.13 on vif sat0
[ 2010/10/22 22:08:12 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 10.174.102.223 to
 224.0.0.22 on vif eth0
[ 2010/10/22 22:08:14 TRACE xorp_igmp MLD6IGMP ] RX IGMP_MEMBERSHIP_QUERY from 10.0.1.123 to 224.0.0
.1 on vif sat0
[ 2010/10/22 22:08:15 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 10.0.1.223 to 224
.0.0.22 on vif sat0
[ 2010/10/22 22:08:18 TRACE xorp_pimsm4 PIM ] RX PIM_HELLO from 10.0.1.123 to 224.0.0.13 on vif sat0
[ 2010/10/22 22:08:19 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 10.0.1.223 to 224
.0.0.2 on vif sat0
[ 2010/10/22 22:08:20 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 10.0.1.123 to 224
.0.0.2 on vif sat0
[ 2010/10/22 22:08:21 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 10.0.1.123 to 224
.0.0.13 on vif sat0
[ 2010/10/22 22:08:31 TRACE xorp_pimsm4 PIM ] RX NOCACHE signal from MFEA_4: vif_index = 0 src = 10.
174.102.225 dst = 224.0.1.20
[ 2010/10/22 22:08:31 TRACE xorp_pimsm4 PIM ] Add MFC entry: (10.174.102.225, 224.0.1.20) iif = 0 ol
ist = ..O olist_disable_wrongvif = OO.
[ 2010/10/22 22:08:31 TRACE xorp_pimsm4 PIM ] Add dataflow monitor: source = 10.174.102.225 group =
224.0.1.20 threshold_interval_sec = 210 threshold_interval_usec = 0 threshold_packets = 0 threshold_
bytes = 0 is_threshold_in_packets = 1 is_threshold_in_bytes = 0 is_geq_upcall = 0 is_leq_upcall = 1
[ 2010/10/22 22:08:31 TRACE xorp_pimsm4 PIM ] RX WHOLEPKT signal from MFEA_4: vif_index = 2 src = 10
.174.102.225 dst = 224.0.1.20 len = 39
[ 2010/10/22 22:08:31 WARNING xorp_pimsm4 PIM ] RX WHOLEPKT signal from MFEA_4: vif_index = 2 src =
10.174.102.225 dst = 224.0.1.20 len = 39: no RP address for this group
[ 2010/10/22 22:08:39 TRACE xorp_pimsm4 PIM ] TX PIM_HELLO from 10.174.102.223 to 224.0.0.13 on vif
eth0
[ 2010/10/22 22:08:39 TRACE xorp_pimsm4 PIM ] TX PIM_HELLO from 10.0.1.223 to 224.0.0.13 on vif sat0
[ 2010/10/22 22:08:48 TRACE xorp_pimsm4 PIM ] RX PIM_HELLO from 10.0.1.123 to 224.0.0.13 on vif sat0



-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20101027/34b562ad/attachment-0001.html 

From greearb at candelatech.com  Fri Oct 29 09:16:52 2010
From: greearb at candelatech.com (Ben Greear)
Date: Fri, 29 Oct 2010 09:16:52 -0700
Subject: [Xorp-users] no RP address for this group
In-Reply-To: <2DE723F44CAFD24A9B6BF606813F010C4078EAF58C@aae-exch>
References: <2DE723F44CAFD24A9B6BF606813F010C4078EAF4E3@aae-exch>
	<2DE723F44CAFD24A9B6BF606813F010C4078EAF58C@aae-exch>
Message-ID: <4CCAF374.8040707@candelatech.com>

On 10/27/2010 11:52 AM, Jayasri Sangu wrote:
> Hi,
>
> My modems are running embedded linux with kernel 2.6.26. And xorp
> version is xorp-1.6.
>
> After debugging the xorp code, I found that rp-holdtime is initialized
> to 0. As per the XORP manual the default value for rp-holdtime is 150.
>
> Why rp-holdtime is initialized to 0 ??
>
> And also when I start the xorp_rtrmgr, why I am getting the following
> warning?
>
> [ 2010/10/22 22:05:30 WARNING xorp_rtrmgr:391 XrlFinderTarget +407
> ../xrl/targets/finder_base.cc ha
>
> ndle_finder_0_2_resolve_xrl ] Handling method for finder/0.2/resolve_xrl
> failed: XrlCmdError 102 Com
>
> mand failed Target "PIMSM_4" does not exist or is not enabled.

These do not seem to be serious, but I haven't looked into them
in detail.

If you want to send a patch against the latest xorp.ct to fix
the hold time issue, I'll be happy to apply it.

Thanks,
Ben


-- 
Ben Greear <greearb at candelatech.com>
Candela Technologies Inc  http://www.candelatech.com


From JayasriS at aaesys.com  Fri Oct 29 09:29:59 2010
From: JayasriS at aaesys.com (Jayasri Sangu)
Date: Fri, 29 Oct 2010 09:29:59 -0700
Subject: [Xorp-users] no RP address for this group
In-Reply-To: <4CCAF374.8040707@candelatech.com>
References: <2DE723F44CAFD24A9B6BF606813F010C4078EAF4E3@aae-exch>
	<2DE723F44CAFD24A9B6BF606813F010C4078EAF58C@aae-exch>
	<4CCAF374.8040707@candelatech.com>
Message-ID: <2DE723F44CAFD24A9B6BF606813F010C4078EAF5CE@aae-exch>

Hi Ben,

       I am cross compiling the xorp for powerpc processor.

In the file xrl_pim_node.cc, calling reinterpret_cast for converting 32 bit number to 8 or 16 bit number is 
returning 0, as the powerpc is BIGENDIAN(byte order is changed). So instaed of using reinterpret_cast, I am using static_cast.

Please see the attached patch.

Thanks
Jayasri



-----Original Message-----
From: Ben Greear [mailto:greearb at candelatech.com] 
Sent: Friday, October 29, 2010 9:17 AM
To: Jayasri Sangu
Cc: xorp-users at xorp.org
Subject: Re: [Xorp-users] no RP address for this group

On 10/27/2010 11:52 AM, Jayasri Sangu wrote:
> Hi,
>
> My modems are running embedded linux with kernel 2.6.26. And xorp
> version is xorp-1.6.
>
> After debugging the xorp code, I found that rp-holdtime is initialized
> to 0. As per the XORP manual the default value for rp-holdtime is 150.
>
> Why rp-holdtime is initialized to 0 ??
>
> And also when I start the xorp_rtrmgr, why I am getting the following
> warning?
>
> [ 2010/10/22 22:05:30 WARNING xorp_rtrmgr:391 XrlFinderTarget +407
> ../xrl/targets/finder_base.cc ha
>
> ndle_finder_0_2_resolve_xrl ] Handling method for finder/0.2/resolve_xrl
> failed: XrlCmdError 102 Com
>
> mand failed Target "PIMSM_4" does not exist or is not enabled.

These do not seem to be serious, but I haven't looked into them
in detail.

If you want to send a patch against the latest xorp.ct to fix
the hold time issue, I'll be happy to apply it


Thanks,
Ben


-- 
Ben Greear <greearb at candelatech.com>
Candela Technologies Inc  http://www.candelatech.com

-------------- next part --------------
A non-text attachment was scrubbed...
Name: xrl_pim_node_patch
Type: application/octet-stream
Size: 6105 bytes
Desc: xrl_pim_node_patch
Url : http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20101029/a827d9cd/attachment.obj 

From greearb at candelatech.com  Fri Oct 29 09:36:21 2010
From: greearb at candelatech.com (Ben Greear)
Date: Fri, 29 Oct 2010 09:36:21 -0700
Subject: [Xorp-users] no RP address for this group
In-Reply-To: <2DE723F44CAFD24A9B6BF606813F010C4078EAF5CE@aae-exch>
References: <2DE723F44CAFD24A9B6BF606813F010C4078EAF4E3@aae-exch>
	<2DE723F44CAFD24A9B6BF606813F010C4078EAF58C@aae-exch>
	<4CCAF374.8040707@candelatech.com>
	<2DE723F44CAFD24A9B6BF606813F010C4078EAF5CE@aae-exch>
Message-ID: <4CCAF805.40003@candelatech.com>

On 10/29/2010 09:29 AM, Jayasri Sangu wrote:
> Hi Ben,
>
>         I am cross compiling the xorp for powerpc processor.
>
> In the file xrl_pim_node.cc, calling reinterpret_cast for converting 32 bit number to 8 or 16 bit number is
> returning 0, as the powerpc is BIGENDIAN(byte order is changed). So instaed of using reinterpret_cast, I am using static_cast.
>
> Please see the attached patch.
>
> Thanks
> Jayasri

I need to do some googling on static_cast v/s reinterpret_cast, but
probably your patch is fine.

xorp.ct should be able to cross-compile to PPC, so if you try it and
it doesn't work, please let me know.

I'll try to get the patch applied shortly..got a few more things to
get out of the way before I can start hacking on xorp again, however.

Thanks,
Ben

>
>
>
> -----Original Message-----
> From: Ben Greear [mailto:greearb at candelatech.com]
> Sent: Friday, October 29, 2010 9:17 AM
> To: Jayasri Sangu
> Cc: xorp-users at xorp.org
> Subject: Re: [Xorp-users] no RP address for this group
>
> On 10/27/2010 11:52 AM, Jayasri Sangu wrote:
>> Hi,
>>
>> My modems are running embedded linux with kernel 2.6.26. And xorp
>> version is xorp-1.6.
>>
>> After debugging the xorp code, I found that rp-holdtime is initialized
>> to 0. As per the XORP manual the default value for rp-holdtime is 150.
>>
>> Why rp-holdtime is initialized to 0 ??
>>
>> And also when I start the xorp_rtrmgr, why I am getting the following
>> warning?
>>
>> [ 2010/10/22 22:05:30 WARNING xorp_rtrmgr:391 XrlFinderTarget +407
>> ../xrl/targets/finder_base.cc ha
>>
>> ndle_finder_0_2_resolve_xrl ] Handling method for finder/0.2/resolve_xrl
>> failed: XrlCmdError 102 Com
>>
>> mand failed Target "PIMSM_4" does not exist or is not enabled.
>
> These do not seem to be serious, but I haven't looked into them
> in detail.
>
> If you want to send a patch against the latest xorp.ct to fix
> the hold time issue, I'll be happy to apply it
>
>
> Thanks,
> Ben
>
>


-- 
Ben Greear <greearb at candelatech.com>
Candela Technologies Inc  http://www.candelatech.com


From greearb at candelatech.com  Fri Oct 29 09:57:29 2010
From: greearb at candelatech.com (Ben Greear)
Date: Fri, 29 Oct 2010 09:57:29 -0700
Subject: [Xorp-users] no RP address for this group
In-Reply-To: <2DE723F44CAFD24A9B6BF606813F010C4078EAF5CE@aae-exch>
References: <2DE723F44CAFD24A9B6BF606813F010C4078EAF4E3@aae-exch>
	<2DE723F44CAFD24A9B6BF606813F010C4078EAF58C@aae-exch>
	<4CCAF374.8040707@candelatech.com>
	<2DE723F44CAFD24A9B6BF606813F010C4078EAF5CE@aae-exch>
Message-ID: <4CCAFCF9.4090007@candelatech.com>

On 10/29/2010 09:29 AM, Jayasri Sangu wrote:
> Hi Ben,
>
>         I am cross compiling the xorp for powerpc processor.
>
> In the file xrl_pim_node.cc, calling reinterpret_cast for converting 32 bit number to 8 or 16 bit number is
> returning 0, as the powerpc is BIGENDIAN(byte order is changed). So instaed of using reinterpret_cast, I am using static_cast.
>
> Please see the attached patch.

It looks like the casts have already been changed in xorp.ct.  Hopefully
the will work properly as is.

Thanks,
Ben


-- 
Ben Greear <greearb at candelatech.com>
Candela Technologies Inc  http://www.candelatech.com