From p_latini at hotmail.com  Mon Aug  1 10:48:19 2011
From: p_latini at hotmail.com (Patricio Latini)
Date: Mon, 1 Aug 2011 14:48:19 -0300
Subject: [Xorp-users] IGMP Querier and VLAN Bug in Xorp 1.8.3?
Message-ID: <COL117-DS13B2462BC66703175CB0D8F7380@phx.gbl>

I have found a weird issue in Xorp seems not to be sending the IGMP
membership query to 224.0.0.1 when the output interface is an 802.1q vlan
interface.

>From Xorp, the packet is shown in the dump however it never arrives to the
server connected on the other side. The curious thing is that membership
report packets(224.0.0.22) arrive without problems

XORP

root at xorp:~# tshark -i vlan30 -R"(igmp)"
Running as user "root" and group "root". This could be dangerous.
Capturing on vlan30
  0.000000   172.16.4.1 -> 224.0.0.1    IGMP V3 Membership Query, general
  2.524879   172.16.4.1 -> 224.0.0.22   IGMP V3 Membership Report / Join
group 224.0.0.13 for any sources / Join group 224.0.0.22 for any sources /
Join group 224.0.0.2 for any sources / Join group 224.0.0.251 for any
sources
 10.000458   172.16.4.1 -> 224.0.0.1    IGMP V3 Membership Query, general
 19.956889   172.16.4.1 -> 224.0.0.22   IGMP V3 Membership Report / Join
group 224.0.0.13 for any sources / Join group 224.0.0.22 for any sources /
Join group 224.0.0.2 for any sources / Join group 224.0.0.251 for any
sources
 20.000371   172.16.4.1 -> 224.0.0.1    IGMP V3 Membership Query, general

Other server directly connected

root at videoserver:~# tshark -i vlan30 -R"(igmp)"
Running as user "root" and group "root". This could be dangerous.
Capturing on eth0
  4.841084   172.16.4.1 -> 224.0.0.22   IGMP V3 Membership Report / Join
group 224.0.0.13 for any sources / Join group 224.0.0.22 for any sources /
Join group 224.0.0.2 for any sources / Join group 224.0.0.251 for any
sources
 22.272951   172.16.4.1 -> 224.0.0.22   IGMP V3 Membership Report / Join
group 224.0.0.13 for any sources / Join group 224.0.0.22 for any sources /
Join group 224.0.0.2 for any sources / Join group 224.0.0.251 for any
sources

On the other side packet going to 224.0.0.1 are passing ok, as sending a
ping from Xorp to 224.0.0.1 is received fine on the server

root at videoserver:~# tshark -i eth0 -R"(ip.addr==224.0.0.1)"
Running as user "root" and group "root". This could be dangerous.
Capturing on eth0
 28.169015   172.16.4.1 -> 224.0.0.1    ICMP Echo (ping) request
 29.177341   172.16.4.1 -> 224.0.0.1    ICMP Echo (ping) request
 30.185335   172.16.4.1 -> 224.0.0.1    ICMP Echo (ping) request
 31.193331   172.16.4.1 -> 224.0.0.1    ICMP Echo (ping) request
 32.201317   172.16.4.1 -> 224.0.0.1    ICMP Echo (ping) request
 33.209310   172.16.4.1 -> 224.0.0.1    ICMP Echo (ping) request

Any idea of what might be happening.

Thanks

Patricio















From jobhunts02 at aol.com  Mon Aug  1 11:05:07 2011
From: jobhunts02 at aol.com (jobhunts02 at aol.com)
Date: Mon, 1 Aug 2011 11:05:07 -0700
Subject: [Xorp-users] Web Interface for XORP?
Message-ID: <DCBFE779-6CF6-410D-9544-F96E790F2AD4@aol.com>

Is there a web interface for XORP?

If so, where can I get it?


From greearb at candelatech.com  Mon Aug  1 11:22:56 2011
From: greearb at candelatech.com (Ben Greear)
Date: Mon, 01 Aug 2011 11:22:56 -0700
Subject: [Xorp-users] Web Interface for XORP?
In-Reply-To: <DCBFE779-6CF6-410D-9544-F96E790F2AD4@aol.com>
References: <DCBFE779-6CF6-410D-9544-F96E790F2AD4@aol.com>
Message-ID: <4E36EF00.20901@candelatech.com>

On 08/01/2011 11:05 AM, jobhunts02 at aol.com wrote:
> Is there a web interface for XORP?
>
> If so, where can I get it?

No, just the CLI.

We make a GUI tool to configure some virtual xorp routers
in conjunction with our network testing & emulation tools, but
it's not a general purpose tool to configure Xorp.

http://www.candelatech.com/ice_ex3_routedmode.php

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 jobhunts02 at aol.com  Mon Aug  1 16:00:37 2011
From: jobhunts02 at aol.com (jobhunts02 at aol.com)
Date: Mon, 1 Aug 2011 16:00:37 -0700
Subject: [Xorp-users] RIP Direction in XORP
Message-ID: <C261B013-2FE9-42F6-9B2C-546F23E33B46@aol.com>

In configuring Netgear routers, there's an option called "RIP Direction," which can be:

None - Router neither broadcasts its route table nor does it accept any RIP packets from outer routers.  Effectively disables RIP.

Both - Router broadcasts its routing table and also processes RIP information received from other routers.

Out Only - Router broadcasts its routing table periodically but does not accept RIP information from other routers.  

In Only - Router accepts RIP information from other routers, but does not broadcast its routing table.


Can XORP be configured to mimic these four choices?


From jobhunts02 at aol.com  Tue Aug  2 15:38:20 2011
From: jobhunts02 at aol.com (jobhunts02 at aol.com)
Date: Tue, 2 Aug 2011 15:38:20 -0700
Subject: [Xorp-users] XORP on an embedded system?
Message-ID: <CE68ACA1-B058-404B-B4BE-812DE0B081B2@aol.com>

I have been assigned to put XORP on a custom board, and I came across the posting below which says, "XORP's original design didn't consider the possibility of an embedded deployment."  

Being new to XORP, is it intended for use on an embedded system?
 
I have approximately 20 MB available.  Is it be possible for me to put XORP on my board?  If not, could you recommend an open source routing stack for an embedded system?

 
 From jt.conklin at xorp.net  Thu Apr  2 05:52:39 2009
From: jt.conklin at xorp.net(J.T. Conklin)
Date: Wed, 1 Apr 2009 11:52:39 -0700
Subject: Support for kernels with large (10MB+) initramfs images
Message-ID: <6c5c8a400904011152n1dadb9bdoa244004595dbd95e at mail.gmail.com>
 
I'm trying to embed the open source XORP routing stack in 85xx based
embedded system.  XORP's original design didn't consider the
possibility of an embedded deployment, so just getting it all to fit
within the 32MB flash of our target has been a challenge all by
itself.
 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20110802/0df58052/attachment.html 

From greearb at candelatech.com  Tue Aug  2 22:20:11 2011
From: greearb at candelatech.com (Ben Greear)
Date: Tue, 02 Aug 2011 22:20:11 -0700
Subject: [Xorp-users] XORP on an embedded system?
In-Reply-To: <CE68ACA1-B058-404B-B4BE-812DE0B081B2@aol.com>
References: <CE68ACA1-B058-404B-B4BE-812DE0B081B2@aol.com>
Message-ID: <4E38DA8B.7060906@candelatech.com>

On 08/02/2011 03:38 PM, jobhunts02 at aol.com wrote:
> I have been assigned to put XORP on a custom board, and I came across the posting below which says, "XORP's original design didn't consider the possibility of
> an embedded deployment."
>
>
> Being new to XORP, is it intended for use on an embedded system?
>
> I have approximately 20 MB available. Is it be possible for me to put XORP on my board? If not, could you recommend an open source routing stack for an embedded
> system?

I think that will fit.  There are scons options to compile out most of logging and various
features now to make the code smaller.

Please try the latest code from github and see if it works for you.  If not, patches
are welcome to make the code smaller...

Thanks,
Ben

>
>
>  From jt.conklin at <http://xorp.net/>xorp.net <http://xorp.net> Thu Apr 2 05:52:39 2009
>
> From: jt.conklin at <http://xorp.net/>xorp.net <http://xorp.net>(J.T. Conklin)
>
> Date: Wed, 1 Apr 2009 11:52:39 -0700
>
> Subject: Support for kernels with large (10MB+) initramfs images
>
> Message-ID: <<mailto:6c5c8a400904011152n1dadb9bdoa244004595dbd95e at mail.gmail.com>6c5c8a400904011152n1dadb9bdoa244004595dbd95e at mail.gmail.com
> <mailto:6c5c8a400904011152n1dadb9bdoa244004595dbd95e at mail.gmail.com>>
>
> I'm trying to embed the open source XORP routing stack in 85xx based
>
> embedded system. XORP's original design didn't consider the
>
> possibility of an embedded deployment, so just getting it all to fit
>
> within the 32MB flash of our target has been a challenge all by
>
> itself.
>
>
>
> _______________________________________________
> 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 jcoco at meccorp.mec.edu  Wed Aug  3 02:44:57 2011
From: jcoco at meccorp.mec.edu (Joe Coco)
Date: Wed, 3 Aug 2011 05:44:57 -0400
Subject: [Xorp-users] XORP on an embedded system?
In-Reply-To: <4E38DA8B.7060906@candelatech.com>
References: <CE68ACA1-B058-404B-B4BE-812DE0B081B2@aol.com>,
	<4E38DA8B.7060906@candelatech.com>
Message-ID: <65A6944974518C4B9C0E818727B559E994FC03A1@mecexchange2007.meccorp.mec.edu>


Everything compiled, everything enabled, it's exactly 20MB:

# dh -hs
20M     .

-- Joe

________________________________________
From: xorp-users-bounces at xorp.org [xorp-users-bounces at xorp.org] On Behalf Of Ben Greear [greearb at candelatech.com]
Sent: Wednesday, August 03, 2011 1:20 AM
To: jobhunts02 at aol.com
Cc: xorp-users at xorp.org
Subject: Re: [Xorp-users] XORP on an embedded system?

On 08/02/2011 03:38 PM, jobhunts02 at aol.com wrote:
> I have been assigned to put XORP on a custom board, and I came across the posting below which says, "XORP's original design didn't consider the possibility of
> an embedded deployment."
>
>
> Being new to XORP, is it intended for use on an embedded system?
>
> I have approximately 20 MB available. Is it be possible for me to put XORP on my board? If not, could you recommend an open source routing stack for an embedded
> system?

I think that will fit.  There are scons options to compile out most of logging and various
features now to make the code smaller.

Please try the latest code from github and see if it works for you.  If not, patches
are welcome to make the code smaller...

Thanks,
Ben

>
>
>  From jt.conklin at <http://xorp.net/>xorp.net <http://xorp.net> Thu Apr 2 05:52:39 2009
>
> From: jt.conklin at <http://xorp.net/>xorp.net <http://xorp.net>(J.T. Conklin)
>
> Date: Wed, 1 Apr 2009 11:52:39 -0700
>
> Subject: Support for kernels with large (10MB+) initramfs images
>
> Message-ID: <<mailto:6c5c8a400904011152n1dadb9bdoa244004595dbd95e at mail.gmail.com>6c5c8a400904011152n1dadb9bdoa244004595dbd95e at mail.gmail.com
> <mailto:6c5c8a400904011152n1dadb9bdoa244004595dbd95e at mail.gmail.com>>
>
> I'm trying to embed the open source XORP routing stack in 85xx based
>
> embedded system. XORP's original design didn't consider the
>
> possibility of an embedded deployment, so just getting it all to fit
>
> within the 32MB flash of our target has been a challenge all by
>
> itself.
>
>
>
> _______________________________________________
> 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

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


From jobhunts02 at aol.com  Wed Aug  3 15:47:24 2011
From: jobhunts02 at aol.com (jobhunts02 at aol.com)
Date: Wed, 3 Aug 2011 15:47:24 -0700
Subject: [Xorp-users] Mistake in RIP example configuration?
Message-ID: <02B0E03F-63BF-4995-8AC0-074E9923BE7F@aol.com>

I am reading the user manual and on webpage 
http://xorp.run.montefiore.ulg.ac.be/latex2wiki/user_manual/rip_and_ripng 
it says that "RIP is configured on only one interface/vif 
(dc0/dc0), with address 10.10.10.10" in the example 
configuration.
 
The only interface/vif I see mentioned in the example 
configuration is fxp0/fxp0, and the only address 
I see is 69.110.224.158.  Is there a mistake in the 
example configuration?
 

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

From pierre.lepropre at student.ulg.ac.be  Wed Aug  3 15:57:16 2011
From: pierre.lepropre at student.ulg.ac.be (Pierre Lepropre)
Date: Thu, 04 Aug 2011 00:57:16 +0200
Subject: [Xorp-users] Mistake in RIP example configuration?
In-Reply-To: <02B0E03F-63BF-4995-8AC0-074E9923BE7F@aol.com>
References: <02B0E03F-63BF-4995-8AC0-074E9923BE7F@aol.com>
Message-ID: <1312412236.4864.2.camel@pierre-T500>

Hello,

I believe this might be a mistake, indeed.

Feel free to register yourself on the wiki and fix it if you'd like !
Otherwise, I'll do it tomorrow.

Cheers,

Pierre.

On Wed, 2011-08-03 at 15:47 -0700, jobhunts02 at aol.com wrote:
> 
> I am reading the user manual and on webpage 
> 
> http://xorp.run.montefiore.ulg.ac.be/latex2wiki/user_manual/rip_and_ripng 
> 
> it says that "RIP is configured on only one interface/vif 
> 
> (dc0/dc0), with address 10.10.10.10" in the example 
> 
> configuration.
> 
>  
> 
> The only interface/vif I see mentioned in the example 
> configuration is fxp0/fxp0, and the only address 
> I see is 69.110.224.158.  Is there a mistake in the 
> example configuration?
> 
>  
> 
> 
> 
> _______________________________________________
> Xorp-users mailing list
> Xorp-users at xorp.org
> http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users



From jobhunts02 at aol.com  Thu Aug  4 16:06:26 2011
From: jobhunts02 at aol.com (jobhunts02 at aol.com)
Date: Thu, 4 Aug 2011 16:06:26 -0700
Subject: [Xorp-users] Command line configuration for RIP
Message-ID: <8AD99C43-3D32-4371-A04A-492F43C4B250@aol.com>

According to the manual, the xorpsh 
command line interface can be used to 
configure a XORP router.
 
I would like to configure for RIP from the 
command line but I don't see any examples 
in the documentation.  Where are they?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20110804/c3fde4c5/attachment.html 

From jobhunts02 at aol.com  Thu Aug  4 17:46:07 2011
From: jobhunts02 at aol.com (jobhunts02 at aol.com)
Date: Thu, 4 Aug 2011 17:46:07 -0700
Subject: [Xorp-users] Command line configuration for RIP
In-Reply-To: <8AD99C43-3D32-4371-A04A-492F43C4B250@aol.com>
References: <8AD99C43-3D32-4371-A04A-492F43C4B250@aol.com>
Message-ID: <045EBFE8-DC7D-4D24-BBFE-B22A9FD91CC1@aol.com>

I am trying to use cli_send_processor_xrl or cli_generic to do the configuration, not xorpsh.
 
The following command did not give me an error:
./cli_generic -x rip/rip/0.1/set_interpacket_delay ifname sat0 vifname sat0 addr 10.0.1.220 t_msecs 29
Is that the correct syntax? 
 
I want to read it back to see if it was set but I cannot figure out how to do the interpacket_delay
command without getting errors.  What would be the syntax for the interpacket_delay command?


On Aug 4, 2011, at 4:06 PM, jobhunts02 at aol.com wrote:

> According to the manual, the xorpsh 
> command line interface can be used to 
> configure a XORP router.
>  
> I would like to configure for RIP from the 
> command line but I don't see any examples 
> in the documentation.  Where are they?
> _______________________________________________
> 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/20110804/bd0c0935/attachment.html 

From greearb at candelatech.com  Thu Aug  4 18:08:59 2011
From: greearb at candelatech.com (Ben Greear)
Date: Thu, 04 Aug 2011 18:08:59 -0700
Subject: [Xorp-users] Command line configuration for RIP
In-Reply-To: <045EBFE8-DC7D-4D24-BBFE-B22A9FD91CC1@aol.com>
References: <8AD99C43-3D32-4371-A04A-492F43C4B250@aol.com>
	<045EBFE8-DC7D-4D24-BBFE-B22A9FD91CC1@aol.com>
Message-ID: <4E3B42AB.6020600@candelatech.com>

On 08/04/2011 05:46 PM, jobhunts02 at aol.com wrote:
> I am trying to use cli_send_processor_xrl or cli_generic to do the configuration, not xorpsh.
>
> The following command did not give me an error:
>
> ./cli_generic -x rip/rip/0.1/set_interpacket_delay ifname sat0 vifname sat0 addr 10.0.1.220 t_msecs 29
>
> Is that the correct syntax?
>
> I want to read it back to see if it was set but I cannot figure out how to do the interpacket_delay
>
> command without getting errors. What would be the syntax for the interpacket_delay command?

I always use xorpsh for this sort of thing, but you might check the 'scons check' targets
for some examples that use shell scripts to do XRL things.

For xorpsh, use the -c option to pass in commands.  Basically, a command is whatever
you would be typing in xorpsh directly, and that is the same stuff that is in the
xorp config file...

Ben

>
>
>
> On Aug 4, 2011, at 4:06 PM, jobhunts02 at aol.com <mailto:jobhunts02 at aol.com> wrote:
>
>> According to the manual, the xorpsh
>>
>> command line interface can be used to
>>
>> configure a XORP router.
>>
>> I would like to configure for RIP from the
>>
>> command line but I don't see any examples
>>
>> in the documentation. Where are they?
>>
>> _______________________________________________
>> Xorp-users mailing list
>> Xorp-users at xorp.org <mailto: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 mass3mass at gmail.com  Fri Aug  5 00:13:33 2011
From: mass3mass at gmail.com (MAS .)
Date: Fri, 5 Aug 2011 12:43:33 +0530
Subject: [Xorp-users] Little Help
Message-ID: <CAKbuTVrTs=5uvx6kA17e3U=8fV_GCVLQuWnwsiiKVxgt1zcLgw@mail.gmail.com>

Hi All,

I am new user at XORP, I want to do may masters project in XORP
developement. But I dont have much experience of routing platforms, I have
coding experience in net-snmp. Can you please help me for finding out what
potential development can be done in 6 months time. How can I contribute to
open source community. Also please help me about How to start.

Thanks to all in advance.

cheers to open-source community !!!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20110805/ba225dbd/attachment.html 

From pierre.lepropre at student.ulg.ac.be  Fri Aug  5 03:16:58 2011
From: pierre.lepropre at student.ulg.ac.be (Pierre Lepropre)
Date: Fri, 05 Aug 2011 12:16:58 +0200
Subject: [Xorp-users] Command line configuration for RIP
In-Reply-To: <8AD99C43-3D32-4371-A04A-492F43C4B250@aol.com>
References: <8AD99C43-3D32-4371-A04A-492F43C4B250@aol.com>
Message-ID: <1312539418.2734.8.camel@pierre-T500>

Dear Sir or Madam,

You have to understand that the XORP project came back alive a few
months from now, almost all thanks to Ben Greear.

The manual (or documentation) project was restarted a few months ago at
the beginning of my own master thesis (which is about to end).

Its goal was *not* to put online an accurate and comprehensive
documentation. Indeed, the main objective was and still is, to make
readily the platform available to the biggest audience, with reading AND
writing permissions.

Indeed, a simple registration, which will only take a few minutes of
your time will grant you automatically both of these user rights.

We know there is a lot of stuff which is totally inaccurate and
completely outdated. Seriously, you have no idea in what shape we got
this documentation and how much work was put into it just to make it
available as it is right now.

My point is: as you're going through the "beginners steps" you're gonna
encounter a lot a discrepancies with the documentation. Registering
yourself and helping us with your personal input directly will not only
help you and us, but everybody around. And it won't take any extra time
for you just to fix these typos or anything like it.

I still believe that most of it is a good basis to lead you on the right
path but don't expect to get too many directions out of it.

Best Regards,

Pierre Lepropre.
On Thu, 2011-08-04 at 16:06 -0700, jobhunts02 at aol.com wrote:
> 
> According to the manual, the xorpsh 
> 
> command line interface can be used to 
> 
> configure a XORP router.
> 
>  
> 
> I would like to configure for RIP from the 
> 
> command line but I don't see any examples 
> 
> in the documentation.  Where are they?
> 
> _______________________________________________
> Xorp-users mailing list
> Xorp-users at xorp.org
> http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users



From ahmadyudo at yahoo.com  Fri Aug  5 11:18:06 2011
From: ahmadyudo at yahoo.com (oduy ahmad)
Date: Fri, 5 Aug 2011 11:18:06 -0700 (PDT)
Subject: [Xorp-users] (no subject)
Message-ID: <1312568286.58258.androidMobile@web125415.mail.ne1.yahoo.com>

<p>I was never spoiled as a child there was no way out this was my free ride .<br><a href="http://alwa.com.pl/MatthewHarrison47.html">http://alwa.com.pl/MatthewHarrison47.html</a> now im in this for the long run imagine the possibilities<br>Dont say I never help anyone!</p>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20110805/e01047d1/attachment-0001.html 

From greearb at candelatech.com  Fri Aug  5 11:28:22 2011
From: greearb at candelatech.com (Ben Greear)
Date: Fri, 05 Aug 2011 11:28:22 -0700
Subject: [Xorp-users] RIP Direction in XORP
In-Reply-To: <C261B013-2FE9-42F6-9B2C-546F23E33B46@aol.com>
References: <C261B013-2FE9-42F6-9B2C-546F23E33B46@aol.com>
Message-ID: <4E3C3646.4030706@candelatech.com>

On 08/01/2011 04:00 PM, jobhunts02 at aol.com wrote:
> In configuring Netgear routers, there's an option called "RIP Direction," which can be:
>
> None - Router neither broadcasts its route table nor does it accept any RIP packets from outer routers.  Effectively disables RIP.
>
> Both - Router broadcasts its routing table and also processes RIP information received from other routers.
>
> Out Only - Router broadcasts its routing table periodically but does not accept RIP information from other routers.
>
> In Only - Router accepts RIP information from other routers, but does not broadcast its routing table.

You might could do this with policies if nothing else.

I assume you read through the pertinent user-guide section for RIP to see if there
was anything obvious?

Thanks,
Ben

>
>
> Can XORP be configured to mimic these four choices?
>
> _______________________________________________
> 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  Fri Aug  5 11:51:32 2011
From: greearb at candelatech.com (Ben Greear)
Date: Fri, 05 Aug 2011 11:51:32 -0700
Subject: [Xorp-users] IGMP Querier and VLAN Bug in Xorp 1.8.3?
In-Reply-To: <COL117-DS13B2462BC66703175CB0D8F7380@phx.gbl>
References: <COL117-DS13B2462BC66703175CB0D8F7380@phx.gbl>
Message-ID: <4E3C3BB4.9000100@candelatech.com>

On 08/01/2011 10:48 AM, Patricio Latini wrote:
> I have found a weird issue in Xorp seems not to be sending the IGMP
> membership query to 224.0.0.1 when the output interface is an 802.1q vlan
> interface.
>
>> From Xorp, the packet is shown in the dump however it never arrives to the
> server connected on the other side. The curious thing is that membership
> report packets(224.0.0.22) arrive without problems

Have you tried the latest xorp source from github git tree?

What OS, what kernel?

Have you tried using a different NIC or machine in case it's a bug in
the driver?

Can you sniff on a third machine to tie-break whether the sending machine is actually
sending onto the wire or not?  Could also try sniffing w/out filter on receiving machine's
physical interface to see if the pkt comes in mangled on on wrong VLAN (or no vlan at all).

Thanks,
Ben

>
> XORP
>
> root at xorp:~# tshark -i vlan30 -R"(igmp)"
> Running as user "root" and group "root". This could be dangerous.
> Capturing on vlan30
>    0.000000   172.16.4.1 ->  224.0.0.1    IGMP V3 Membership Query, general
>    2.524879   172.16.4.1 ->  224.0.0.22   IGMP V3 Membership Report / Join
> group 224.0.0.13 for any sources / Join group 224.0.0.22 for any sources /
> Join group 224.0.0.2 for any sources / Join group 224.0.0.251 for any
> sources
>   10.000458   172.16.4.1 ->  224.0.0.1    IGMP V3 Membership Query, general
>   19.956889   172.16.4.1 ->  224.0.0.22   IGMP V3 Membership Report / Join
> group 224.0.0.13 for any sources / Join group 224.0.0.22 for any sources /
> Join group 224.0.0.2 for any sources / Join group 224.0.0.251 for any
> sources
>   20.000371   172.16.4.1 ->  224.0.0.1    IGMP V3 Membership Query, general
>
> Other server directly connected
>
> root at videoserver:~# tshark -i vlan30 -R"(igmp)"
> Running as user "root" and group "root". This could be dangerous.
> Capturing on eth0
>    4.841084   172.16.4.1 ->  224.0.0.22   IGMP V3 Membership Report / Join
> group 224.0.0.13 for any sources / Join group 224.0.0.22 for any sources /
> Join group 224.0.0.2 for any sources / Join group 224.0.0.251 for any
> sources
>   22.272951   172.16.4.1 ->  224.0.0.22   IGMP V3 Membership Report / Join
> group 224.0.0.13 for any sources / Join group 224.0.0.22 for any sources /
> Join group 224.0.0.2 for any sources / Join group 224.0.0.251 for any
> sources
>
> On the other side packet going to 224.0.0.1 are passing ok, as sending a
> ping from Xorp to 224.0.0.1 is received fine on the server
>
> root at videoserver:~# tshark -i eth0 -R"(ip.addr==224.0.0.1)"
> Running as user "root" and group "root". This could be dangerous.
> Capturing on eth0
>   28.169015   172.16.4.1 ->  224.0.0.1    ICMP Echo (ping) request
>   29.177341   172.16.4.1 ->  224.0.0.1    ICMP Echo (ping) request
>   30.185335   172.16.4.1 ->  224.0.0.1    ICMP Echo (ping) request
>   31.193331   172.16.4.1 ->  224.0.0.1    ICMP Echo (ping) request
>   32.201317   172.16.4.1 ->  224.0.0.1    ICMP Echo (ping) request
>   33.209310   172.16.4.1 ->  224.0.0.1    ICMP Echo (ping) request
>
> Any idea of what might be happening.
>
> Thanks
>
> Patricio
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> _______________________________________________
> 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 mass3mass at gmail.com  Tue Aug  9 12:17:21 2011
From: mass3mass at gmail.com (MAS .)
Date: Wed, 10 Aug 2011 00:47:21 +0530
Subject: [Xorp-users] XORP for Marvell
Message-ID: <CAKbuTVqev1j_5VBwHRwtcQ7or3ka9q62rUxL+-2pHiWkMbrQeA@mail.gmail.com>

Hi All,

I am masters student. We have one router board designed in our lab which
uses Marvell switch chip, it has ARM and it runs Linux.* Is it possible to
use XORP on that board*? There will be issues regarding lower-level design.
How does FEA talks to the Marvel? Is there any material of wiki help which
elaborate it more?

I dont have much idea about this that is it doable? what kind of efforts
should I have to put into it to make it work?

Please Help me !!!

Thanks in advance !


- -
cheers to open-source community !!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20110810/5e461fba/attachment.html 

From wushuai314 at gmail.com  Tue Aug  9 18:45:50 2011
From: wushuai314 at gmail.com (=?gbk?B?oa1XYXRlcg==?=)
Date: Wed, 10 Aug 2011 09:45:50 +0800
Subject: [Xorp-users]  How to deploy a distributed router using XORP?
Message-ID: <tencent_573E12DB694FC67C7F0257C0@qq.com>

Hi all,
    
 
I am new to XORP and I am in a project that need to deploy distributed routers. I have known that XORP supports Click which is a modular router including many elements, but I wander if I can deploy distributed routers using Forz protocol on XORP, which is a interior control communication protocol based on Zebra and ForCES. I want to know if XORP support the the ForCES architecture. Has anyboby done that ? 

 


 
Thanks for any reply!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20110810/4426b2e1/attachment.html 

From wushuai314 at gmail.com  Wed Aug 10 00:23:59 2011
From: wushuai314 at gmail.com (=?ISO-8859-1?B?T3J6?=)
Date: Wed, 10 Aug 2011 15:23:59 +0800
Subject: [Xorp-users]  How to deploy a distributed router using XORP?
Message-ID: <tencent_215F5F9D6BF76DC80CF1461C@qq.com>

Hi all,
    
 
I am new to XORP and I am in a project that need to deploy distributed routers. 
 
I have known that XORP supports Click which is a modular router including many elements, but I wander if I can deploy distributed routers using Forz protocol on XORP, 
 
which is a interior control communication protocol based on Zebra and ForCES.I want to know if XORP support the the ForCES architecture. 
 
Has anyboby done that ? 

 


 
Thanks for any reply!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20110810/6feed05e/attachment.html 

From greearb at candelatech.com  Thu Aug 11 01:09:26 2011
From: greearb at candelatech.com (Ben Greear)
Date: Thu, 11 Aug 2011 01:09:26 -0700
Subject: [Xorp-users] How to deploy a distributed router using XORP?
In-Reply-To: <tencent_215F5F9D6BF76DC80CF1461C@qq.com>
References: <tencent_215F5F9D6BF76DC80CF1461C@qq.com>
Message-ID: <4E438E36.90302@candelatech.com>

On 08/10/2011 12:23 AM, Orz wrote:
> Hi all,
>
> I am new to XORP and I am in a project that need to deploy distributed routers.
>
> I have known that XORP supports Click which is a modular router including many elements, but I wander if I can deploy distributed routers using Forz protocol on
> XORP,
>
> which is a interior control communication protocol based on Zebra and ForCES.I want to know if XORP support the the ForCES architecture.
>
> Has anyboby done that ?

You would probably have to port/write support for Forz into xorp.  I have never
heard of it before, and don't have personal interest in it, but I'd be happy
to help review and merge patches if someone else wants to work on it.

For that matter, I'm not sure Click works either...patches and documentation for
making it work are welcome as well.

Thanks,
Ben

>
>
>
> Thanks for any reply!
>
>
>
> _______________________________________________
> 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 marti at artemis.in-ulm.de  Sun Aug 14 03:46:22 2011
From: marti at artemis.in-ulm.de (Martin Keller)
Date: Sun, 14 Aug 2011 12:46:22 +0200
Subject: [Xorp-users] aggregate-prefix-len
Message-ID: <20110814104622.GC26691@artemis.in-ulm.de>

Hello.

I need a little help with the aggregate-prefix-len. I already invested several
weekends and I don't have a clue how to make it work.

At the moment I use the version 1.6 which comes with Debian GNU/Linux
(stable). I read the documentation on BGP and Policy (PDF and wiki) and also
had a look at the source code. I also tried to find an example in the mailing
list and the Internet but no luck.

I think the aggregate-prefix-len should be used in a policy for the import
of BGP but something is always wrong about my policy.

I used virtual machines with IP addresses from 10.0.0.0/8 and AS numbers above
65000.

I would really appreciate if someone could give me an example.

Martin Keller


From aservin at lacnic.net  Sun Aug 14 08:30:39 2011
From: aservin at lacnic.net (Arturo Servin)
Date: Sun, 14 Aug 2011 12:30:39 -0300
Subject: [Xorp-users] aggregate-prefix-len
In-Reply-To: <20110814104622.GC26691@artemis.in-ulm.de>
References: <20110814104622.GC26691@artemis.in-ulm.de>
Message-ID: <FD84F83B-17A3-4EC2-B24F-5B018171A73B@lacnic.net>


	Not sure about the config. But make sure that you have a static to 10.0.0.0/8, without it BGP won't announce it  (at least that happens in Cisco, Quagga and Juniper). Also you may need a command to indicate BGP that you want to advertise 10.0.0.0/8 (in cisco world is something like network 10.0.0.0 255.0.0.0.0)

/as

On 14 Aug 2011, at 07:46, Martin Keller wrote:

> Hello.
> 
> I need a little help with the aggregate-prefix-len. I already invested several
> weekends and I don't have a clue how to make it work.
> 
> At the moment I use the version 1.6 which comes with Debian GNU/Linux
> (stable). I read the documentation on BGP and Policy (PDF and wiki) and also
> had a look at the source code. I also tried to find an example in the mailing
> list and the Internet but no luck.
> 
> I think the aggregate-prefix-len should be used in a policy for the import
> of BGP but something is always wrong about my policy.
> 
> I used virtual machines with IP addresses from 10.0.0.0/8 and AS numbers above
> 65000.
> 
> I would really appreciate if someone could give me an example.
> 
> Martin Keller
> 
> _______________________________________________
> Xorp-users mailing list
> Xorp-users at xorp.org
> http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users



From JobHunts02 at aol.com  Wed Aug 17 22:12:11 2011
From: JobHunts02 at aol.com (JobHunts02 at aol.com)
Date: Thu, 18 Aug 2011 01:12:11 -0400 (EDT)
Subject: [Xorp-users] No authentication parameters displayed
Message-ID: <8e837.526c5fd8.3b7df92b@aol.com>

When I enter:
./xorpsh -c "configure" -c "show -all protocols rip interface sat0 vif sat0 
 address 10.0.1.219"
 
I get  the following output:
 
[  1970/01/03 02:14:48.245782 WARNING xorpsh RTRMGR ] [Operational Command 
File:  /home/billr/xorptest/install/xorp/share/xorp/templates/misc.cmds line 
39]:  Executable file not found: traceroute6
Invalid window width (0); window width unchanged (80)
Invalid window height (0); window height unchanged (25)
Welcome to XORP on localhost
root at localhost> configure
Entering configuration mode.
There are no other users in configuration mode.
[edit]
root at localhost# show -all protocols rip interface sat0 vif sat0 address  
10.0.1.219
    metric: 1
    horizon: "split-horizon-poison-reverse"
    disable: false
    passive: false
    accept-non-rip-requests: true
    accept-default-route: true
    advertise-default-route: true
    route-timeout: 180
    deletion-delay: 120
    triggered-delay: 3
    triggered-jitter: 66
    update-interval: 30
    update-jitter: 16
    request-interval: 30
    interpacket-delay: 50
[edit]
 
NOTE:  There is no information regarding authentication.
 
Thinking that maybe nothing was output because I had not set up any  
authentication, I entered:
 
./xorpsh -c "configure" -c "set protocols rip interface sat0 vif sat0  
address 10.0.1.219 authentication simple-password masterchef"
 
I ran  the show command again and there was still no mention of the 
authentication  parameters.
 
How do I get the  authentication parameters to be  displayed?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20110818/055e1ae4/attachment.html 

From swdickey at rockwellcollins.com  Wed Aug 17 16:34:42 2011
From: swdickey at rockwellcollins.com (swdickey at rockwellcollins.com)
Date: Wed, 17 Aug 2011 19:34:42 -0400
Subject: [Xorp-users] PIM-SM not forwarding multicast traffic
Message-ID: <OFE3A73644.D0C24000-ON852578EF.007CE1E2-852578EF.008188A8@rockwellcollins.com>

Hello all,

I am currently having an issue getting PIM-SM working with Xorp v1.8.3 on 
Fedora 14.

Setup: Three in a line

Fedora14_A    <eth0 10.10.30.1  ------------  eth1 10.10.30.2 > Fedora14_B 
running XORP   <eth0 10.10.40.2 ------------ eth1 10.10.40.3>   Fedora14_C

I am trying to send multicast traffic from A to C via multicast forwarding 
through B.  I have a test program (which I can post if needed) that will 
send UDP datagram messages from A to 224.1.1.1.  B will receive these 
messages, but will not forward them to C.  Alternately, if I try sending 
the multicast messages from B, C will then receive them- indicating that C 
is properly subscribed to the IGMP group and is correctly configured. 
Also, Unicast traffic (pings) is being forwarded by B (XORP enabling 
ip_forward) as there are static routes setup on B.

Configuration:

PIM-SM: There is only one router, so I am using static-rps.

/* $XORP$ */

interfaces {
    interface eth1 {
        vif eth1 {
            address 10.10.30.2 {
                prefix-length: 24
            }
        }
    }
    interface eth0 {
        vif eth0 {
            address 10.10.40.2 {
                prefix-length: 24
            }
        }
    }
}

fea {
    unicast-forwarding4 {
        disable: false
 
    }
}

plumbing {
    mfea4 {
        interface eth1 {
            vif eth1 {
                disable: false
            }
        }
        interface eth0 {
            vif eth0 {
                disable: false
            }
        }
        interface register_vif {
            vif register_vif {
                /* Note: this vif should be always enabled */
                disable: false
            }
        }

    }
}

protocols {
    fib2mrib {
        disable: false
    }
}

protocols {
    igmp {
        interface eth1 {
            vif eth1 {
                disable: false
            }
        }
        interface eth0 {
            vif eth0 {
                disable: false
            }
        }
        traceoptions {
            flag all {
                disable: false
            }
        }

    }
}

protocols {
    pimsm4 {
        interface eth1 {
            vif eth1 {
                disable: false
            }
        }
        interface eth0 {
            vif eth0 {
                disable: false
            }
        }
        interface register_vif {
            vif register_vif {
                /* Note: this vif should be always enabled */
                disable: false
            }
        }

        /* Note: static-rps and bootstrap should not be mixed */
        static-rps {
            rp 10.10.40.2 {
                group-prefix 224.0.0.0/4 {
                }
            }
        }
        traceoptions {
            flag all {
                disable: false
            }
        }
    }
}




Output:

[root at iptm net]# route
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use 
Iface
10.10.30.0      *               255.255.255.0   U     0      0        0 
eth1
10.10.40.0      *               255.255.255.0   U     0      0        0 
eth0
224.0.0.0       *               240.0.0.0       U     0      0        0 
eth0


[root at iptm sbin]# ./xorp_rtrmgr -b 
/home/developer/Downloads/transfer/pim_current3.boot 
Not doing pidfile...
[ 2005/08/02 09:19:49.413051  INFO xorp_rtrmgr:2375 RTRMGR 
rtrmgr/master_conf_tree.cc:257 execute ] Changed modules: interfaces, 
firewall, fea, mfea4, rib, igmp, pimsm4, policy, fib2mrib
[ 2005/08/02 09:19:49.416112  INFO xorp_rtrmgr:2375 RTRMGR 
rtrmgr/module_manager.cc:100 execute ] Executing module: interfaces 
(xorp_fea)
[ 2005/08/02 09:19:49.416935  WARNING xorp_rtrmgr:2375 XrlFinderTarget 
obj/i686-pc-linux-gnu/xrl/targets/finder_base.cc:482 
handle_finder_0_2_resolve_xrl ] Handling method for finder/0.2/resolve_xrl 
failed: XrlCmdError 102 Command failed Target "fea" does not exist or is 
not enabled.
[ 2005/08/02 09:19:49.417120  WARNING xorp_rtrmgr:2375 RTRMGR 
rtrmgr/task.cc:215 xrl_done ] Failed to receive reply, code: 201 Resolve 
failed  retries: 0  max_retries: 30
[ 2005/08/02 09:19:50.425321  INFO xorp_fea:2376 MFEA fea/mfea_node.cc:317 
enable ] MFEA enabled
[ 2005/08/02 09:19:50.425791  INFO xorp_fea:2376 MFEA 
fea/mfea_node_cli.cc:126 enable ] CLI enabled
[ 2005/08/02 09:19:50.426386  INFO xorp_fea:2376 MFEA 
fea/mfea_node_cli.cc:92 start ] CLI started
[ 2005/08/02 09:19:50.426764  INFO xorp_fea:2376 MFEA fea/mfea_node.cc:317 
enable ] MFEA enabled
[ 2005/08/02 09:19:50.426924  INFO xorp_fea:2376 MFEA 
fea/mfea_node_cli.cc:126 enable ] CLI enabled
[ 2005/08/02 09:19:50.427268  INFO xorp_fea:2376 MFEA 
fea/mfea_node_cli.cc:92 start ] CLI started
[ 2005/08/02 09:19:50.446235  WARNING xorp_fea:2376 FEA 
fea/data_plane/ifconfig/ifconfig_get_netlink_socket.cc:138 
try_read_config_one ] NOTE:  Netlink get single network device works on 
this system.
[ 2005/08/02 09:19:50.447400  INFO xorp_rtrmgr:2375 RTRMGR 
rtrmgr/module_manager.cc:100 execute ] Executing module: firewall 
(xorp_fea)
[ 2005/08/02 09:19:50.448357  INFO xorp_rtrmgr:2375 RTRMGR 
rtrmgr/module_manager.cc:100 execute ] Executing module: fea (xorp_fea)
[ 2005/08/02 09:19:50.449941  INFO xorp_rtrmgr:2375 RTRMGR 
rtrmgr/module_manager.cc:100 execute ] Executing module: mfea4 (xorp_fea)
[ 2005/08/02 09:19:50.462692  INFO xorp_fea:2376 MFEA fea/mfea_node.cc:940 
add_vif ] Interface added: Vif[eth0] pif_index: 2 vif_index: 0 addr: 
10.10.40.2 subnet: 10.10.40.0/24 broadcast: 10.10.40.255 peer: 0.0.0.0 
Flags: MULTICAST BROADCAST UNDERLYING_VIF_UP MTU: 1500
[ 2005/08/02 09:19:50.462780  INFO xorp_fea:2376 MFEA fea/mfea_node.cc:940 
add_vif ] Interface added: Vif[eth1] pif_index: 3 vif_index: 1 addr: 
10.10.30.2 subnet: 10.10.30.0/24 broadcast: 10.10.30.255 peer: 0.0.0.0 
Flags: MULTICAST BROADCAST UNDERLYING_VIF_UP MTU: 1500
[ 2005/08/02 09:19:50.462924  WARNING xorp_fea:2376 FEA 
fea/data_plane/io/io_ip_socket.cc:310 IoIpSocket ] Registering with 
iftree: pushed-config
[ 2005/08/02 09:19:50.464728  INFO xorp_fea:2376 MFEA 
fea/mfea_mrouter.cc:850 start_mrt ] NOTE: MROUTE:  setsockopt(MRT_TABLE, 
254) works!  Supports multiple mcast routing tables.
[ 2005/08/02 09:19:50.464803  INFO xorp_fea:2376 MFEA fea/mfea_node.cc:217 
final_start ] MFEA started
[ 2005/08/02 09:19:50.466040  INFO xorp_fea:2376 MFEA fea/mfea_vif.cc:217 
enable ] MfeaVif: Interface enable Vif[eth1] pif_index: 3 vif_index: 1 
addr: 10.10.30.2 subnet: 10.10.30.0/24 broadcast: 10.10.30.255 peer: 
0.0.0.0 Flags: MULTICAST BROADCAST UNDERLYING_VIF_UP MTU: 1500 DOWN IPv4 
DISABLED
[ 2005/08/02 09:19:50.467018  INFO xorp_fea:2376 MFEA fea/mfea_vif.cc:136 
start ] Interface started: Vif[eth1] pif_index: 3 vif_index: 1 addr: 
10.10.30.2 subnet: 10.10.30.0/24 broadcast: 10.10.30.255 peer: 0.0.0.0 
Flags: MULTICAST BROADCAST UNDERLYING_VIF_UP MTU: 1500 UP IPv4 ENABLED
[ 2005/08/02 09:19:50.467081  INFO xorp_fea:2376 MFEA fea/mfea_node.cc:940 
add_vif ] Interface added: Vif[register_vif] pif_index: 3 vif_index: 2 
addr: 10.10.30.2 subnet: 10.10.30.2/32 broadcast: 10.10.30.2 peer: 0.0.0.0 
Flags: PIM_REGISTER UNDERLYING_VIF_UP MTU: 1500
[ 2005/08/02 09:19:50.467452  INFO xorp_fea:2376 MFEA fea/mfea_vif.cc:217 
enable ] MfeaVif: Interface enable Vif[eth0] pif_index: 2 vif_index: 0 
addr: 10.10.40.2 subnet: 10.10.40.0/24 broadcast: 10.10.40.255 peer: 
0.0.0.0 Flags: MULTICAST BROADCAST UNDERLYING_VIF_UP MTU: 1500 DOWN IPv4 
DISABLED
[ 2005/08/02 09:19:50.468060  INFO xorp_fea:2376 MFEA fea/mfea_vif.cc:136 
start ] Interface started: Vif[eth0] pif_index: 2 vif_index: 0 addr: 
10.10.40.2 subnet: 10.10.40.0/24 broadcast: 10.10.40.255 peer: 0.0.0.0 
Flags: MULTICAST BROADCAST UNDERLYING_VIF_UP MTU: 1500 UP IPv4 ENABLED
[ 2005/08/02 09:19:50.468312  INFO xorp_fea:2376 MFEA fea/mfea_vif.cc:217 
enable ] MfeaVif: Interface enable Vif[register_vif] pif_index: 3 
vif_index: 2 addr: 10.10.30.2 subnet: 10.10.30.2/32 broadcast: 10.10.30.2 
peer: 0.0.0.0 Flags: PIM_REGISTER UNDERLYING_VIF_UP MTU: 1500 DOWN IPv4 
DISABLED
[ 2005/08/02 09:19:50.470471  INFO xorp_fea:2376 MFEA fea/mfea_vif.cc:136 
start ] Interface started: Vif[register_vif] pif_index: 3 vif_index: 2 
addr: 10.10.30.2 subnet: 10.10.30.2/32 broadcast: 10.10.30.2 peer: 0.0.0.0 
Flags: PIM_REGISTER UNDERLYING_VIF_UP MTU: 1500 UP IPv4 ENABLED
[ 2005/08/02 09:19:50.470959  INFO xorp_rtrmgr:2375 RTRMGR 
rtrmgr/module_manager.cc:100 execute ] Executing module: rib (xorp_rib)
[ 2005/08/02 09:19:50.477395  WARNING xorp_rtrmgr:2375 XrlFinderTarget 
obj/i686-pc-linux-gnu/xrl/targets/finder_base.cc:482 
handle_finder_0_2_resolve_xrl ] Handling method for finder/0.2/resolve_xrl 
failed: XrlCmdError 102 Command failed Target "rib" does not exist or is 
not enabled.
[ 2005/08/02 09:19:50.477755  WARNING xorp_rtrmgr:2375 RTRMGR 
rtrmgr/task.cc:215 xrl_done ] Failed to receive reply, code: 201 Resolve 
failed  retries: 0  max_retries: 30
[ 2005/08/02 09:19:51.483903  INFO xorp_rtrmgr:2375 RTRMGR 
rtrmgr/module_manager.cc:100 execute ] Executing module: igmp (xorp_igmp)
[ 2005/08/02 09:19:51.485595  WARNING xorp_rtrmgr:2375 XrlFinderTarget 
obj/i686-pc-linux-gnu/xrl/targets/finder_base.cc:482 
handle_finder_0_2_resolve_xrl ] Handling method for finder/0.2/resolve_xrl 
failed: XrlCmdError 102 Command failed Target "IGMP" does not exist or is 
not enabled.
[ 2005/08/02 09:19:51.486066  WARNING xorp_rtrmgr:2375 RTRMGR 
rtrmgr/task.cc:215 xrl_done ] Failed to receive reply, code: 201 Resolve 
failed  retries: 0  max_retries: 30
[ 2005/08/02 09:19:51.549666 INFO xorp_igmp MLD6IGMP ] Protocol enabled
[ 2005/08/02 09:19:51.549914 INFO xorp_igmp MLD6IGMP ] CLI enabled
[ 2005/08/02 09:19:51.550169 INFO xorp_igmp MLD6IGMP ] CLI started
[ 2005/08/02 09:19:52.557802 INFO xorp_igmp MLD6IGMP ] Protocol started
[ 2005/08/02 09:19:52.558166 INFO xorp_igmp MLD6IGMP ] mld6igmp: Interface 
added: Vif[eth0] pif_index: 2 vif_index: 0 addr: 10.10.40.2 subnet: 
10.10.40.0/24 broadcast: 10.10.40.255 peer: 0.0.0.0 Flags: MULTICAST 
BROADCAST UNDERLYING_VIF_UP MTU: 1500
[ 2005/08/02 09:19:52.558279 INFO xorp_igmp MLD6IGMP ] mld6igmp: Interface 
added: Vif[eth1] pif_index: 3 vif_index: 1 addr: 10.10.30.2 subnet: 
10.10.30.0/24 broadcast: 10.10.30.255 peer: 0.0.0.0 Flags: MULTICAST 
BROADCAST UNDERLYING_VIF_UP MTU: 1500
[ 2005/08/02 09:19:53.496629 INFO xorp_igmp MLD6IGMP ] Interface enabled: 
Vif[eth1] pif_index: 3 vif_index: 1 addr: 10.10.30.2 subnet: 10.10.30.0/24 
broadcast: 10.10.30.255 peer: 0.0.0.0 Flags: MULTICAST BROADCAST 
UNDERLYING_VIF_UP MTU: 1500 DOWN IPv4 ENABLED
[ 2005/08/02 09:19:53.501819 INFO xorp_igmp MLD6IGMP ] Interface started: 
Vif[eth1] pif_index: 3 vif_index: 1 addr: 10.10.30.2 subnet: 10.10.30.0/24 
broadcast: 10.10.30.255 peer: 0.0.0.0 Flags: MULTICAST BROADCAST 
UNDERLYING_VIF_UP MTU: 1500 UP IPv4 ENABLED
[ 2005/08/02 09:19:53.502139 INFO xorp_igmp MLD6IGMP ] Interface enabled: 
Vif[eth0] pif_index: 2 vif_index: 0 addr: 10.10.40.2 subnet: 10.10.40.0/24 
broadcast: 10.10.40.255 peer: 0.0.0.0 Flags: MULTICAST BROADCAST 
UNDERLYING_VIF_UP MTU: 1500 DOWN IPv4 ENABLED
[ 2005/08/02 09:19:53.504992  INFO xorp_fea:2376 FEA 
fea/data_plane/io/io_ip_socket.cc:878 findOrCreateInputSocket ] 
Successfully bound socket: 47 to interface: eth1  input sockets size: 1
[ 2005/08/02 09:19:53.505059  INFO xorp_fea:2376 FEA 
fea/data_plane/io/io_ip_socket.cc:607 join_multicast_group ] Joined IPv4 
group: 224.0.0.1 on interface eth1 vif eth1  socket: 47
[ 2005/08/02 09:19:53.505553  INFO xorp_fea:2376 FEA 
fea/data_plane/io/io_ip_socket.cc:607 join_multicast_group ] Joined IPv4 
group: 224.0.0.2 on interface eth1 vif eth1  socket: 47
[ 2005/08/02 09:19:53.505993  INFO xorp_fea:2376 FEA 
fea/data_plane/io/io_ip_socket.cc:607 join_multicast_group ] Joined IPv4 
group: 224.0.0.22 on interface eth1 vif eth1  socket: 47
[ 2005/08/02 09:19:53.514615  INFO xorp_fea:2376 FEA 
fea/data_plane/io/io_ip_socket.cc:878 findOrCreateInputSocket ] 
Successfully bound socket: 49 to interface: eth0  input sockets size: 2
[ 2005/08/02 09:19:53.514656  INFO xorp_fea:2376 FEA 
fea/data_plane/io/io_ip_socket.cc:607 join_multicast_group ] Joined IPv4 
group: 224.0.0.1 on interface eth0 vif eth0  socket: 49
[ 2005/08/02 09:19:53.515119  INFO xorp_fea:2376 FEA 
fea/data_plane/io/io_ip_socket.cc:607 join_multicast_group ] Joined IPv4 
group: 224.0.0.2 on interface eth0 vif eth0  socket: 49
[ 2005/08/02 09:19:53.515573  INFO xorp_fea:2376 FEA 
fea/data_plane/io/io_ip_socket.cc:607 join_multicast_group ] Joined IPv4 
group: 224.0.0.22 on interface eth0 vif eth0  socket: 49
[ 2005/08/02 09:19:53.514301 INFO xorp_igmp MLD6IGMP ] Interface started: 
Vif[eth0] pif_index: 2 vif_index: 0 addr: 10.10.40.2 subnet: 10.10.40.0/24 
broadcast: 10.10.40.255 peer: 0.0.0.0 Flags: MULTICAST BROADCAST 
UNDERLYING_VIF_UP MTU: 1500 UP IPv4 ENABLED
[ 2005/08/02 09:19:53.517741  INFO xorp_rtrmgr:2375 RTRMGR 
rtrmgr/module_manager.cc:100 execute ] Executing module: pimsm4 
(xorp_pimsm4)
[ 2005/08/02 09:19:53.518416  WARNING xorp_rtrmgr:2375 XrlFinderTarget 
obj/i686-pc-linux-gnu/xrl/targets/finder_base.cc:482 
handle_finder_0_2_resolve_xrl ] Handling method for finder/0.2/resolve_xrl 
failed: XrlCmdError 102 Command failed Target "PIMSM_4" does not exist or 
is not enabled.
[ 2005/08/02 09:19:53.518601  WARNING xorp_rtrmgr:2375 RTRMGR 
rtrmgr/task.cc:215 xrl_done ] Failed to receive reply, code: 201 Resolve 
failed  retries: 0  max_retries: 30
[ 2005/08/02 09:19:53.751173 INFO xorp_pimsm4 PIM ] Protocol enabled
[ 2005/08/02 09:19:53.751386 INFO xorp_pimsm4 PIM ] CLI enabled
[ 2005/08/02 09:19:53.751811 INFO xorp_pimsm4 PIM ] CLI started
[ 2005/08/02 09:19:54.595796 INFO xorp_pimsm4 PIM ] Protocol started
[ 2005/08/02 09:19:54.596386 INFO xorp_pimsm4 PIM ] Interface added: 
Vif[eth0] pif_index: 2 vif_index: 0 addr: 10.10.40.2 subnet: 10.10.40.0/24 
broadcast: 10.10.40.255 peer: 0.0.0.0 Flags: MULTICAST BROADCAST 
UNDERLYING_VIF_UP MTU: 1500
[ 2005/08/02 09:19:54.596681 INFO xorp_pimsm4 PIM ] Interface added: 
Vif[eth1] pif_index: 3 vif_index: 1 addr: 10.10.30.2 subnet: 10.10.30.0/24 
broadcast: 10.10.30.255 peer: 0.0.0.0 Flags: MULTICAST BROADCAST 
UNDERLYING_VIF_UP MTU: 1500
[ 2005/08/02 09:19:54.596953 INFO xorp_pimsm4 PIM ] Interface added: 
Vif[register_vif] pif_index: 0 vif_index: 2 addr: 10.10.30.2 subnet: 
10.10.30.2/32 broadcast: 0.0.0.0 peer: 0.0.0.0 Flags: PIM_REGISTER 
UNDERLYING_VIF_UP MTU: 1500
[ 2005/08/02 09:19:55.392349 TRACE xorp_igmp MLD6IGMP ] mld6igmp_process: 
RX IGMP_V2_MEMBERSHIP_REPORT from 10.10.30.2 to 224.1.1.1 on vif eth1
[ 2005/08/02 09:19:55.392504 TRACE xorp_igmp MLD6IGMP ] Notify routing add 
membership for (0.0.0.0, 224.1.1.1) on vif eth1
[ 2005/08/02 09:19:55.392677 TRACE xorp_igmp MLD6IGMP ] mld6igmp_process: 
RX IGMP_V2_MEMBERSHIP_REPORT from 10.10.30.2 to 224.1.1.1 on vif eth1
[ 2005/08/02 09:19:55.527578 INFO xorp_pimsm4 PIM ] Interface enabled: 
Vif[eth1] pif_index: 3 vif_index: 1 addr: 10.10.30.2 subnet: 10.10.30.0/24 
broadcast: 10.10.30.255 peer: 0.0.0.0 Flags: MULTICAST BROADCAST 
UNDERLYING_VIF_UP MTU: 1500 DOWN IPv4 ENABLED
[ 2005/08/02 09:19:55.530867 INFO xorp_pimsm4 PIM ] Interface started: 
Vif[eth1] pif_index: 3 vif_index: 1 addr: 10.10.30.2 subnet: 10.10.30.0/24 
broadcast: 10.10.30.255 peer: 0.0.0.0 Flags: MULTICAST BROADCAST 
UNDERLYING_VIF_UP MTU: 1500 UP IPv4 ENABLED
[ 2005/08/02 09:19:55.531283 INFO xorp_pimsm4 PIM ] Interface enabled: 
Vif[eth0] pif_index: 2 vif_index: 0 addr: 10.10.40.2 subnet: 10.10.40.0/24 
broadcast: 10.10.40.255 peer: 0.0.0.0 Flags: MULTICAST BROADCAST 
UNDERLYING_VIF_UP MTU: 1500 DOWN IPv4 ENABLED
[ 2005/08/02 09:19:55.532822  WARNING xorp_fea:2376 FEA 
fea/data_plane/io/io_ip_socket.cc:310 IoIpSocket ] Registering with 
iftree: pushed-config
[ 2005/08/02 09:19:55.536680 INFO xorp_pimsm4 PIM ] Interface started: 
Vif[eth0] pif_index: 2 vif_index: 0 addr: 10.10.40.2 subnet: 10.10.40.0/24 
broadcast: 10.10.40.255 peer: 0.0.0.0 Flags: MULTICAST BROADCAST 
UNDERLYING_VIF_UP MTU: 1500 UP IPv4 ENABLED
[ 2005/08/02 09:19:55.538419 WARNING xorp_pimsm4 PIM ] JoinDesired(*,G) = 
true: RP for group 224.1.1.1: not found
[ 2005/08/02 09:19:55.543536 INFO xorp_pimsm4 PIM ] Interface enabled: 
Vif[register_vif] pif_index: 0 vif_index: 2 addr: 10.10.30.2 subnet: 
10.10.30.2/32 broadcast: 0.0.0.0 peer: 0.0.0.0 Flags: PIM_REGISTER 
UNDERLYING_VIF_UP MTU: 1500 DOWN IPv4 ENABLED
[ 2005/08/02 09:19:55.545201  INFO xorp_fea:2376 FEA 
fea/data_plane/io/io_ip_socket.cc:878 findOrCreateInputSocket ] 
Successfully bound socket: 56 to interface: eth1  input sockets size: 1
[ 2005/08/02 09:19:55.545576  INFO xorp_fea:2376 FEA 
fea/data_plane/io/io_ip_socket.cc:607 join_multicast_group ] Joined IPv4 
group: 224.0.0.13 on interface eth1 vif eth1  socket: 56
[ 2005/08/02 09:19:55.546055  INFO xorp_fea:2376 FEA 
fea/data_plane/io/io_ip_socket.cc:878 findOrCreateInputSocket ] 
Successfully bound socket: 57 to interface: eth0  input sockets size: 2
[ 2005/08/02 09:19:55.546370  INFO xorp_fea:2376 FEA 
fea/data_plane/io/io_ip_socket.cc:607 join_multicast_group ] Joined IPv4 
group: 224.0.0.13 on interface eth0 vif eth0  socket: 57
[ 2005/08/02 09:19:55.546802 TRACE xorp_igmp MLD6IGMP ] mld6igmp_process: 
RX IGMP_V2_MEMBERSHIP_REPORT from 10.10.30.2 to 224.0.0.13 on vif eth1
[ 2005/08/02 09:19:55.546859 TRACE xorp_igmp MLD6IGMP ] Notify routing add 
membership for (0.0.0.0, 224.0.0.13) on vif eth1
[ 2005/08/02 09:19:55.546925 TRACE xorp_igmp MLD6IGMP ] mld6igmp_process: 
RX IGMP_V2_MEMBERSHIP_REPORT from 10.10.30.2 to 224.0.0.13 on vif eth1
[ 2005/08/02 09:19:55.547784 TRACE xorp_igmp MLD6IGMP ] mld6igmp_process: 
RX IGMP_V2_MEMBERSHIP_REPORT from 10.10.40.2 to 224.0.0.13 on vif eth0
[ 2005/08/02 09:19:55.547820 TRACE xorp_igmp MLD6IGMP ] Notify routing add 
membership for (0.0.0.0, 224.0.0.13) on vif eth0
[ 2005/08/02 09:19:55.547874 TRACE xorp_igmp MLD6IGMP ] mld6igmp_process: 
RX IGMP_V2_MEMBERSHIP_REPORT from 10.10.40.2 to 224.0.0.13 on vif eth0
[ 2005/08/02 09:19:55.548580 INFO xorp_pimsm4 PIM ] Interface started: 
Vif[register_vif] pif_index: 0 vif_index: 2 addr: 10.10.30.2 subnet: 
10.10.30.2/32 broadcast: 0.0.0.0 peer: 0.0.0.0 Flags: PIM_REGISTER 
UNDERLYING_VIF_UP MTU: 1500 UP IPv4 ENABLED
[ 2005/08/02 09:19:55.551172  INFO xorp_rtrmgr:2375 RTRMGR 
rtrmgr/module_manager.cc:100 execute ] Executing module: policy 
(xorp_policy)
[ 2005/08/02 09:19:55.551957  WARNING xorp_rtrmgr:2375 XrlFinderTarget 
obj/i686-pc-linux-gnu/xrl/targets/finder_base.cc:482 
handle_finder_0_2_resolve_xrl ] Handling method for finder/0.2/resolve_xrl 
failed: XrlCmdError 102 Command failed Target "policy" does not exist or 
is not enabled.
[ 2005/08/02 09:19:55.552133  WARNING xorp_rtrmgr:2375 RTRMGR 
rtrmgr/task.cc:215 xrl_done ] Failed to receive reply, code: 201 Resolve 
failed  retries: 0  max_retries: 30
[ 2005/08/02 09:19:56.148414 TRACE xorp_igmp MLD6IGMP ] mld6igmp_process: 
RX IGMP_V2_MEMBERSHIP_REPORT from 10.10.30.2 to 224.0.0.13 on vif eth1
[ 2005/08/02 09:19:56.148652 TRACE xorp_igmp MLD6IGMP ] mld6igmp_process: 
RX IGMP_V2_MEMBERSHIP_REPORT from 10.10.30.2 to 224.0.0.13 on vif eth1
[ 2005/08/02 09:19:56.558306  INFO xorp_rtrmgr:2375 RTRMGR 
rtrmgr/module_manager.cc:100 execute ] Executing module: fib2mrib 
(xorp_fib2mrib)
[ 2005/08/02 09:19:56.559083  WARNING xorp_rtrmgr:2375 XrlFinderTarget 
obj/i686-pc-linux-gnu/xrl/targets/finder_base.cc:482 
handle_finder_0_2_resolve_xrl ] Handling method for finder/0.2/resolve_xrl 
failed: XrlCmdError 102 Command failed Target "fib2mrib" does not exist or 
is not enabled.
[ 2005/08/02 09:19:56.559261  WARNING xorp_rtrmgr:2375 RTRMGR 
rtrmgr/task.cc:215 xrl_done ] Failed to receive reply, code: 201 Resolve 
failed  retries: 0  max_retries: 30
[ 2005/08/02 09:19:57.567359  INFO xorp_rtrmgr:2375 RTRMGR 
rtrmgr/task.cc:2242 run_task ] No more tasks to run
[ 2005/08/02 09:19:57.729113 TRACE xorp_igmp MLD6IGMP ] mld6igmp_process: 
RX IGMP_V2_MEMBERSHIP_REPORT from 10.10.30.2 to 224.0.0.22 on vif eth1
[ 2005/08/02 09:19:57.729336 TRACE xorp_igmp MLD6IGMP ] mld6igmp_process: 
RX IGMP_V2_MEMBERSHIP_REPORT from 10.10.30.2 to 224.0.0.22 on vif eth1
[ 2005/08/02 09:19:57.729524 TRACE xorp_igmp MLD6IGMP ] mld6igmp_process: 
RX IGMP_V2_MEMBERSHIP_REPORT from 10.10.30.2 to 224.0.0.13 on vif eth1
[ 2005/08/02 09:19:57.729673 TRACE xorp_igmp MLD6IGMP ] mld6igmp_process: 
RX IGMP_V2_MEMBERSHIP_REPORT from 10.10.30.2 to 224.0.0.13 on vif eth1
[ 2005/08/02 09:19:57.817836 TRACE xorp_pimsm4 PIM ] pim_send: TX 
PIM_HELLO from 10.10.40.2 to 224.0.0.13 on vif eth0
[ 2005/08/02 09:19:58.309620 TRACE xorp_pimsm4 PIM ] pim_send: TX 
PIM_HELLO from 10.10.30.2 to 224.0.0.13 on vif eth1
[ 2005/08/02 09:19:58.384700 TRACE xorp_igmp MLD6IGMP ] mld6igmp_process: 
RX IGMP_V2_MEMBERSHIP_REPORT from 10.10.40.2 to 224.0.0.251 on vif eth0
[ 2005/08/02 09:19:58.384849 TRACE xorp_igmp MLD6IGMP ] Notify routing add 
membership for (0.0.0.0, 224.0.0.251) on vif eth0
[ 2005/08/02 09:19:58.385023 TRACE xorp_igmp MLD6IGMP ] mld6igmp_process: 
RX IGMP_V2_MEMBERSHIP_REPORT from 10.10.40.2 to 224.0.0.251 on vif eth0
[ 2005/08/02 09:19:58.516349 TRACE xorp_igmp MLD6IGMP ] mld6igmp_process: 
RX IGMP_V2_MEMBERSHIP_REPORT from 10.10.30.1 to 224.0.0.251 on vif eth1
[ 2005/08/02 09:19:58.516456 TRACE xorp_igmp MLD6IGMP ] Notify routing add 
membership for (0.0.0.0, 224.0.0.251) on vif eth1
[ 2005/08/02 09:19:58.516548 TRACE xorp_igmp MLD6IGMP ] mld6igmp_process: 
RX IGMP_V2_MEMBERSHIP_REPORT from 10.10.30.1 to 224.0.0.251 on vif eth1
[ 2005/08/02 09:19:59.408383 TRACE xorp_igmp MLD6IGMP ] mld6igmp_process: 
RX IGMP_V2_MEMBERSHIP_REPORT from 10.10.30.2 to 224.0.0.2 on vif eth1
[ 2005/08/02 09:19:59.408616 TRACE xorp_igmp MLD6IGMP ] mld6igmp_process: 
RX IGMP_V2_MEMBERSHIP_REPORT from 10.10.30.2 to 224.0.0.2 on vif eth1
[ 2005/08/02 09:20:03.968316 TRACE xorp_igmp MLD6IGMP ] mld6igmp_process: 
RX IGMP_V2_MEMBERSHIP_REPORT from 10.10.40.2 to 224.0.0.13 on vif eth0
[ 2005/08/02 09:20:03.968537 TRACE xorp_igmp MLD6IGMP ] mld6igmp_process: 
RX IGMP_V2_MEMBERSHIP_REPORT from 10.10.40.2 to 224.0.0.13 on vif eth0
[ 2005/08/02 09:20:06.512342 TRACE xorp_igmp MLD6IGMP ] mld6igmp_process: 
RX IGMP_V2_MEMBERSHIP_REPORT from 10.10.40.2 to 224.0.0.13 on vif eth0
[ 2005/08/02 09:20:06.512568 TRACE xorp_igmp MLD6IGMP ] mld6igmp_process: 
RX IGMP_V2_MEMBERSHIP_REPORT from 10.10.40.2 to 224.0.0.13 on vif eth0
[ 2005/08/02 09:20:24.752628 TRACE xorp_igmp MLD6IGMP ] TX 
IGMP_MEMBERSHIP_QUERY from 10.10.30.2 to 224.0.0.1
[ 2005/08/02 09:20:24.753441 TRACE xorp_igmp MLD6IGMP ] mld6igmp_process: 
RX IGMP_MEMBERSHIP_QUERY from 10.10.30.2 to 224.0.0.1 on vif eth1
[ 2005/08/02 09:20:24.753519 TRACE xorp_igmp MLD6IGMP ] mld6igmp_process: 
RX IGMP_MEMBERSHIP_QUERY from 10.10.30.2 to 224.0.0.1 on vif eth1
[ 2005/08/02 09:20:24.764422 TRACE xorp_igmp MLD6IGMP ] TX 
IGMP_MEMBERSHIP_QUERY from 10.10.40.2 to 224.0.0.1
[ 2005/08/02 09:20:24.765440 TRACE xorp_igmp MLD6IGMP ] mld6igmp_process: 
RX IGMP_MEMBERSHIP_QUERY from 10.10.40.2 to 224.0.0.1 on vif eth0
[ 2005/08/02 09:20:24.765551 TRACE xorp_igmp MLD6IGMP ] mld6igmp_process: 
RX IGMP_MEMBERSHIP_QUERY from 10.10.40.2 to 224.0.0.1 on vif eth0
[ 2005/08/02 09:20:25.384325 TRACE xorp_igmp MLD6IGMP ] mld6igmp_process: 
RX IGMP_V2_MEMBERSHIP_REPORT from 10.10.40.2 to 224.0.0.2 on vif eth0
[ 2005/08/02 09:20:25.384464 TRACE xorp_igmp MLD6IGMP ] mld6igmp_process: 
RX IGMP_V2_MEMBERSHIP_REPORT from 10.10.40.2 to 224.0.0.2 on vif eth0
[ 2005/08/02 09:20:25.514033 TRACE xorp_igmp MLD6IGMP ] mld6igmp_process: 
RX IGMP_V2_MEMBERSHIP_REPORT from 10.10.40.2 to 224.0.0.13 on vif eth0
[ 2005/08/02 09:20:25.514155 TRACE xorp_igmp MLD6IGMP ] mld6igmp_process: 
RX IGMP_V2_MEMBERSHIP_REPORT from 10.10.40.2 to 224.0.0.13 on vif eth0
[ 2005/08/02 09:20:26.219976 TRACE xorp_igmp MLD6IGMP ] mld6igmp_process: 
RX IGMP_V2_MEMBERSHIP_REPORT from 10.10.40.2 to 224.0.0.251 on vif eth0
[ 2005/08/02 09:20:26.220088 TRACE xorp_igmp MLD6IGMP ] mld6igmp_process: 
RX IGMP_V2_MEMBERSHIP_REPORT from 10.10.40.2 to 224.0.0.251 on vif eth0
[ 2005/08/02 09:20:26.440235 TRACE xorp_igmp MLD6IGMP ] mld6igmp_process: 
RX IGMP_V2_MEMBERSHIP_REPORT from 10.10.30.2 to 224.0.0.22 on vif eth1
[ 2005/08/02 09:20:26.440391 TRACE xorp_igmp MLD6IGMP ] mld6igmp_process: 
RX IGMP_V2_MEMBERSHIP_REPORT from 10.10.30.2 to 224.0.0.22 on vif eth1
[ 2005/08/02 09:20:27.819634 TRACE xorp_pimsm4 PIM ] pim_send: TX 
PIM_HELLO from 10.10.40.2 to 224.0.0.13 on vif eth0
[ 2005/08/02 09:20:28.310168 TRACE xorp_pimsm4 PIM ] pim_send: TX 
PIM_HELLO from 10.10.30.2 to 224.0.0.13 on vif eth1
[ 2005/08/02 09:20:28.608305 TRACE xorp_igmp MLD6IGMP ] mld6igmp_process: 
RX IGMP_V2_MEMBERSHIP_REPORT from 10.10.30.2 to 224.0.0.13 on vif eth1
[ 2005/08/02 09:20:28.608537 TRACE xorp_igmp MLD6IGMP ] mld6igmp_process: 
RX IGMP_V2_MEMBERSHIP_REPORT from 10.10.30.2 to 224.0.0.13 on vif eth1
[ 2005/08/02 09:20:29.360370 TRACE xorp_igmp MLD6IGMP ] mld6igmp_process: 
RX IGMP_V2_MEMBERSHIP_REPORT from 10.10.30.2 to 224.0.0.2 on vif eth1
[ 2005/08/02 09:20:29.360616 TRACE xorp_igmp MLD6IGMP ] mld6igmp_process: 
RX IGMP_V2_MEMBERSHIP_REPORT from 10.10.30.2 to 224.0.0.2 on vif eth1
[ 2005/08/0
2 09:20:29.376152 TRACE xorp_igmp MLD6IGMP ] mld6igmp_process:  RX 
IGMP_V2_MEMBERSHIP_REPORT from 10.10.30.2 to 224.1.1.1 on vif eth1
[ 2005/08/02 09:20:29.376334 TRACE xorp_igmp MLD6IGMP ] mld6igmp_process: 
RX IGMP_V2_MEMBERSHIP_REPORT from 10.10.30.2 to 224.1.1.1 on vif eth1
[ 2005/08/02 09:20:30.611890 TRACE xorp_igmp MLD6IGMP ] mld6igmp_process: 
RX IGMP_V2_MEMBERSHIP_REPORT from 10.10.30.1 to 224.0.0.251 on vif eth1
[ 2005/08/02 09:20:30.612029 TRACE xorp_igmp MLD6IGMP ] mld6igmp_process: 
RX IGMP_V2_MEMBERSHIP_REPORT from 10.10.30.1 to 224.0.0.251 on vif eth1
[ 2005/08/02 09:20:33.440437 TRACE xorp_igmp MLD6IGMP ] mld6igmp_process: 
RX IGMP_V2_MEMBERSHIP_REPORT from 10.10.40.2 to 224.0.0.22 on vif eth0
[ 2005/08/02 09:20:33.440672 TRACE xorp_igmp MLD6IGMP ] mld6igmp_process: 
RX IGMP_V2_MEMBERSHIP_REPORT from 10.10.40.2 to 224.0.0.22 on vif eth0



[root at iptm sbin]# ./xorpsh
Welcome to XORP on iptm.development
root at iptm.development> show route table ipv4 multicast final
10.10.30.0/24   [connected(0)/0]
                > via eth1/eth1
10.10.40.0/24   [connected(0)/0]
                > via eth0/eth0
root at iptm.development> show mfea interface 
Interface    State    Vif/PifIndex Addr            Flags
eth0         UP                0/2 10.10.40.2      MULTICAST BROADCAST 
KERN_UP
eth1         UP                1/3 10.10.30.2      MULTICAST BROADCAST 
KERN_UP
register_vif UP                2/3 10.10.30.2      PIM_REGISTER KERN_UP
root at iptm.development> show pim mrib 
DestPrefix         NextHopRouter   VifName VifIndex MetricPref Metric
10.10.30.0/24      10.10.30.2      eth1    1                 0      0
10.10.40.0/24      10.10.40.2      eth0    0                 0      0



Any help or suggestions would be much appreciated.

S. Dickey
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20110817/0e5f4583/attachment-0001.html 

From greearb at candelatech.com  Thu Aug 18 11:25:23 2011
From: greearb at candelatech.com (Ben Greear)
Date: Thu, 18 Aug 2011 11:25:23 -0700
Subject: [Xorp-users] PIM-SM not forwarding multicast traffic
In-Reply-To: <OFE3A73644.D0C24000-ON852578EF.007CE1E2-852578EF.008188A8@rockwellcollins.com>
References: <OFE3A73644.D0C24000-ON852578EF.007CE1E2-852578EF.008188A8@rockwellcollins.com>
Message-ID: <4E4D5913.6070503@candelatech.com>

On 08/17/2011 04:34 PM, swdickey at rockwellcollins.com wrote:
>
> Hello all,
>
> I am currently having an issue getting PIM-SM working with Xorp v1.8.3 on Fedora 14.
>
> *Setup:* Three in a line
>
> Fedora14_A <eth0 10.10.30.1 ------------ eth1 10.10.30.2 > Fedora14_B running XORP <eth0 10.10.40.2 ------------ eth1 10.10.40.3> Fedora14_C
>
> I am trying to send multicast traffic from A to C via multicast forwarding through B. I have a test program (which I can post if needed) that will send UDP
> datagram messages from A to 224.1.1.1. B will receive these messages, but will not forward them to C. Alternately, if I try sending the multicast messages from
> B, C will then receive them- indicating that C is properly subscribed to the IGMP group and is correctly configured. Also, Unicast traffic (pings) is being
> forwarded by B (XORP enabling ip_forward) as there are static routes setup on B.

Can you sniff to make doubly sure that you have TTl > 3 or so?

If unsure, post a small pcap capture file on the sending machine.

Thanks,
Ben

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


From swdickey at rockwellcollins.com  Fri Aug 19 06:52:58 2011
From: swdickey at rockwellcollins.com (swdickey at rockwellcollins.com)
Date: Fri, 19 Aug 2011 09:52:58 -0400
Subject: [Xorp-users] PIM-SM not forwarding multicast traffic
In-Reply-To: <4E4D5913.6070503@candelatech.com>
Message-ID: <OF70ED5171.65FFDB61-ON852578F1.004BECA1-852578F1.004C4393@rockwellcollins.com>

Thanks Ben.  Wireshark showed a TTL of 1 which is the default multicast 
datagram TTL.  My test program I needed the lines:

u_char ttl 64;
setsockopt(sd, IPPROTO_IP, IP_MULTICAST_TTL, &ttl, sizeof(ttl) < 0);

S. Dickey




Ben Greear <greearb at candelatech.com> 
18/08/2011 02:25 PM

To
swdickey at rockwellcollins.com
cc
xorp-users at xorp.org
Subject
Re: [Xorp-users] PIM-SM not forwarding multicast traffic






On 08/17/2011 04:34 PM, swdickey at rockwellcollins.com wrote:
>
> Hello all,
>
> I am currently having an issue getting PIM-SM working with Xorp v1.8.3 
on Fedora 14.
>
> *Setup:* Three in a line
>
> Fedora14_A <eth0 10.10.30.1 ------------ eth1 10.10.30.2 > Fedora14_B 
running XORP <eth0 10.10.40.2 ------------ eth1 10.10.40.3> Fedora14_C
>
> I am trying to send multicast traffic from A to C via multicast 
forwarding through B. I have a test program (which I can post if needed) 
that will send UDP
> datagram messages from A to 224.1.1.1. B will receive these messages, 
but will not forward them to C. Alternately, if I try sending the 
multicast messages from
> B, C will then receive them- indicating that C is properly subscribed to 
the IGMP group and is correctly configured. Also, Unicast traffic (pings) 
is being
> forwarded by B (XORP enabling ip_forward) as there are static routes 
setup on B.

Can you sniff to make doubly sure that you have TTl > 3 or so?

If unsure, post a small pcap capture file on the sending machine.

Thanks,
Ben

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

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

From jobhunts02 at aol.com  Tue Aug 23 16:02:15 2011
From: jobhunts02 at aol.com (jobhunts02 at aol.com)
Date: Tue, 23 Aug 2011 16:02:15 -0700
Subject: [Xorp-users] No authentication parameters displayed
In-Reply-To: <8e837.526c5fd8.3b7df92b@aol.com>
References: <8e837.526c5fd8.3b7df92b@aol.com>
Message-ID: <2418322E-BA4D-44A8-9725-9096F80764F5@aol.com>

The authentication parameters were not displayed because I had not committed the command setting simple-password.

Thank you.



On Aug 17, 2011, at 10:12 PM, JobHunts02 at aol.com wrote:

> When I enter:
> ./xorpsh -c "configure" -c "show -all protocols rip interface sat0 vif sat0 address 10.0.1.219"
>  
> I get the following output:
>  
> [ 1970/01/03 02:14:48.245782 WARNING xorpsh RTRMGR ] [Operational Command File: /home/billr/xorptest/install/xorp/share/xorp/templates/misc.cmds line 39]: Executable file not found: traceroute6
> Invalid window width (0); window width unchanged (80)
> Invalid window height (0); window height unchanged (25)
> Welcome to XORP on localhost
> root at localhost> configure
> Entering configuration mode.
> There are no other users in configuration mode.
> [edit]
> root at localhost# show -all protocols rip interface sat0 vif sat0 address 10.0.1.219
>     metric: 1
>     horizon: "split-horizon-poison-reverse"
>     disable: false
>     passive: false
>     accept-non-rip-requests: true
>     accept-default-route: true
>     advertise-default-route: true
>     route-timeout: 180
>     deletion-delay: 120
>     triggered-delay: 3
>     triggered-jitter: 66
>     update-interval: 30
>     update-jitter: 16
>     request-interval: 30
>     interpacket-delay: 50
> [edit]
>  
> NOTE:  There is no information regarding authentication.
>  
> Thinking that maybe nothing was output because I had not set up any authentication, I entered:
>  
> ./xorpsh -c "configure" -c "set protocols rip interface sat0 vif sat0 address 10.0.1.219 authentication simple-password masterchef"
>  
> I ran the show command again and there was still no mention of the authentication parameters.
>  
> How do I get the authentication parameters to be displayed?
> _______________________________________________
> 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/20110823/02a09b60/attachment.html