From vommwa at yahoo.com  Mon Apr  2 14:24:27 2012
From: vommwa at yahoo.com (victor omwando)
Date: Mon, 2 Apr 2012 14:24:27 -0700 (PDT)
Subject: [Xorp-users] (no subject)
Message-ID: <1333401867.76661.YahooMailMobile@web125503.mail.ne1.yahoo.com>

<a href="http://crescendoarte.com/website.old/wp-content/plugins/extended-comment-options/02efpk.html"> http://crescendoarte.com/website.old/wp-content/plugins/extended-comment-options/02efpk.html</a>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20120402/8de9328e/attachment.html 

From vommwa at yahoo.com  Tue Apr  3 16:55:37 2012
From: vommwa at yahoo.com (victor omwando)
Date: Tue, 3 Apr 2012 16:55:37 -0700 (PDT)
Subject: [Xorp-users] (no subject)
Message-ID: <1333497337.24290.YahooMailMobile@web125515.mail.ne1.yahoo.com>

<a href="http://toptens.co.in/wp-content/plugins/extended-comment-options/jrklre.html"> http://toptens.co.in/wp-content/plugins/extended-comment-options/jrklre.html</a>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20120403/b14e7794/attachment.html 

From vommwa at yahoo.com  Wed Apr  4 17:56:11 2012
From: vommwa at yahoo.com (victor omwando)
Date: Wed, 4 Apr 2012 17:56:11 -0700 (PDT)
Subject: [Xorp-users] (no subject)
Message-ID: <1333587371.75559.YahooMailMobile@web125505.mail.ne1.yahoo.com>

<a href="http://d3phone.com/fjgvkd.html"> http://d3phone.com/fjgvkd.html</a>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20120404/7d276222/attachment.html 

From igorm at etf.rs  Tue Apr 10 05:57:24 2012
From: igorm at etf.rs (=?ISO-8859-2?Q?Igor_Maravi=E6?=)
Date: Tue, 10 Apr 2012 14:57:24 +0200
Subject: [Xorp-users] Route Redist between RIP and OSPF - working?
Message-ID: <CAFdo_mWwraYMUGNCT5Hkj4xCZak3-RSnm6T-HoAG7b6ASh4cEQ@mail.gmail.com>

Hi all,
I think that I found solution to this problem :)

I started looking where Steve stopped
(PolicyRedistTable<A>::replace_policytags function).
It was just the tip of the iceberg.

Problem was that protocol's existing EXPORT_SOURCE match policies
weren't refreshed when new export filter is created.
In this case problem was with exporting to "connected" protocol.

New protocol always has accurate policy tags for route lookup. It
always searches routes that has no tag, or
older protocol tags or it's tags. If it finds them it prepends it's tag.
Older protocols are searching routes that has no tags, or have older
tags. If it finds such a route it prepends it's tag.

EXPORT_SOURCEMATCH policies are executed in order that depends on protocol name.
If newer protocol has lower letter (for example ospf's policies are
executed before rip's, because "o" precedes "r"),
new protocol prepends new tags, that are unrecognizable to older
protocol, to routes that it has found.
Because older protocol is unaware of new tags, it concludes that
routes are deleted and it deletes them.
This is not what we are expecting.

If older protocol is executed first, it prepends it's tag to routes
that it has found. Because old tag is recognizable by
newer protocol new tags are also prepended to routes. This case works
as expected.

Solution - refresh tags for all protocol's EXPORT_SOURCEMATCH routes
when new export filter is created.

I'm sending patch to xorp-hackers list.

I tested it for simple solutions, so it does need more testing :)

It would be nice if someone would post more complicated policies to
test this issue.

BR
Igor


From igorm at etf.rs  Tue Apr 10 05:57:24 2012
From: igorm at etf.rs (=?ISO-8859-2?Q?Igor_Maravi=E6?=)
Date: Tue, 10 Apr 2012 14:57:24 +0200
Subject: [Xorp-users] Route Redist between RIP and OSPF - working?
Message-ID: <CAFdo_mWwraYMUGNCT5Hkj4xCZak3-RSnm6T-HoAG7b6ASh4cEQ@mail.gmail.com>

Hi all,
I think that I found solution to this problem :)

I started looking where Steve stopped
(PolicyRedistTable<A>::replace_policytags function).
It was just the tip of the iceberg.

Problem was that protocol's existing EXPORT_SOURCE match policies
weren't refreshed when new export filter is created.
In this case problem was with exporting to "connected" protocol.

New protocol always has accurate policy tags for route lookup. It
always searches routes that has no tag, or
older protocol tags or it's tags. If it finds them it prepends it's tag.
Older protocols are searching routes that has no tags, or have older
tags. If it finds such a route it prepends it's tag.

EXPORT_SOURCEMATCH policies are executed in order that depends on protocol name.
If newer protocol has lower letter (for example ospf's policies are
executed before rip's, because "o" precedes "r"),
new protocol prepends new tags, that are unrecognizable to older
protocol, to routes that it has found.
Because older protocol is unaware of new tags, it concludes that
routes are deleted and it deletes them.
This is not what we are expecting.

If older protocol is executed first, it prepends it's tag to routes
that it has found. Because old tag is recognizable by
newer protocol new tags are also prepended to routes. This case works
as expected.

Solution - refresh tags for all protocol's EXPORT_SOURCEMATCH routes
when new export filter is created.

I'm sending patch to xorp-hackers list.

I tested it for simple solutions, so it does need more testing :)

It would be nice if someone would post more complicated policies to
test this issue.

BR
Igor


From swdickey at rockwellcollins.com  Tue Apr 10 14:36:03 2012
From: swdickey at rockwellcollins.com (swdickey at rockwellcollins.com)
Date: Tue, 10 Apr 2012 17:36:03 -0400
Subject: [Xorp-users] Route Redist between RIP and OSPF - working?
In-Reply-To: <CAFdo_mWwraYMUGNCT5Hkj4xCZak3-RSnm6T-HoAG7b6ASh4cEQ@mail.gmail.com>
References: <CAFdo_mWwraYMUGNCT5Hkj4xCZak3-RSnm6T-HoAG7b6ASh4cEQ@mail.gmail.com>
Message-ID: <OF47F06D31.CB03C970-ON852579DC.00766FC1-852579DC.0076A851@rockwellcollins.com>

This fixes my issue.

Thanks Igor and to the others who helped with this.

Steve



Igor Maravi? <igorm at etf.rs> 
04/10/2012 08:57 AM
Please respond to
igorm at etf.rs


To
xorp-users at xorp.org, xorp-users at icir.org, xorp-hackers at icir.org
cc
swdickey at rockwellcollins.com, david at commroom.net
Subject
Route Redist between RIP and OSPF - working?






Hi all,
I think that I found solution to this problem :)

I started looking where Steve stopped
(PolicyRedistTable<A>::replace_policytags function).
It was just the tip of the iceberg.

Problem was that protocol's existing EXPORT_SOURCE match policies
weren't refreshed when new export filter is created.
In this case problem was with exporting to "connected" protocol.

New protocol always has accurate policy tags for route lookup. It
always searches routes that has no tag, or
older protocol tags or it's tags. If it finds them it prepends it's tag.
Older protocols are searching routes that has no tags, or have older
tags. If it finds such a route it prepends it's tag.

EXPORT_SOURCEMATCH policies are executed in order that depends on protocol 
name.
If newer protocol has lower letter (for example ospf's policies are
executed before rip's, because "o" precedes "r"),
new protocol prepends new tags, that are unrecognizable to older
protocol, to routes that it has found.
Because older protocol is unaware of new tags, it concludes that
routes are deleted and it deletes them.
This is not what we are expecting.

If older protocol is executed first, it prepends it's tag to routes
that it has found. Because old tag is recognizable by
newer protocol new tags are also prepended to routes. This case works
as expected.

Solution - refresh tags for all protocol's EXPORT_SOURCEMATCH routes
when new export filter is created.

I'm sending patch to xorp-hackers list.

I tested it for simple solutions, so it does need more testing :)

It would be nice if someone would post more complicated policies to
test this issue.

BR
Igor


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

From PS0083124 at techmahindra.com  Wed Apr 11 04:24:07 2012
From: PS0083124 at techmahindra.com (Peeyush.3.Sharma)
Date: Wed, 11 Apr 2012 16:54:07 +0530
Subject: [Xorp-users] Enquiry related to the Diameter Support
Message-ID: <C86CA6B754CC444FAED01331196CA25659CA807B71@SINNODMBX001.TechMahindra.com>


Hi Everyone,

I want to know that whether XORP supports Diameter Protocol, and if it do so then which 3GPP release would it support.

Thanks & Regards,
Peeyush Sharma 

 
============================================================================================================================Disclaimer:  This message and the information contained herein is proprietary and confidential and subject to the Tech Mahindra policy statement, you may review the policy at <a href="http://www.techmahindra.com/Disclaimer.html">http://www.techmahindra.com/Disclaimer.html</a> externally and <a href="http://tim.techmahindra.com/tim/disclaimer.html">http://tim.techmahindra.com/tim/disclaimer.html</a> internally within Tech Mahindra.============================================================================================================================


From wrussell at incnetworks.com  Wed Apr 11 09:37:59 2012
From: wrussell at incnetworks.com (W. E. W. Russell)
Date: Wed, 11 Apr 2012 12:37:59 -0400
Subject: [Xorp-users] From RHEL5 to RHEL6: Any Issues?
Message-ID: <CAH8vcWzSGswT8rV6z9KRmTfuuQrsk6xk3f3BqeVBhXr15SZJ4w@mail.gmail.com>

All,

My name is William Russell and I'm trying to migrate from RHEL5 to RHEL6
for a particular server I have.

I was using the XORP for multicast routing and (I believe) attaching IP
addresses to bonded & bridged interfaces.

In RHEL5, I have no issues. When the server boots up, the correct addresses
are attached to the correct interfaces and everything work smoothly.
in RHEL6, I have an issue. When the server boots up, XORP starts fine, but
when I do an 'ifconfig' I don't see any of the IP addresses attached to the
interfaces (which also get created correctly).

The config.boot file is exactly the same as it was before.

Has anyone faced these issues? Any leads on where I should start looking to
solve the problem?

-- 
William E. W. Russell
Director, Systems Integration

incNETWORKS, Inc.
25 James Way
Long Branch, NJ 07724
Cell Phone # 732-744-6483
Work Phone # 732-508-2224
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20120411/cab0c04d/attachment.html 

From greearb at candelatech.com  Wed Apr 11 09:40:47 2012
From: greearb at candelatech.com (Ben Greear)
Date: Wed, 11 Apr 2012 09:40:47 -0700
Subject: [Xorp-users] From RHEL5 to RHEL6: Any Issues?
In-Reply-To: <CAH8vcWzSGswT8rV6z9KRmTfuuQrsk6xk3f3BqeVBhXr15SZJ4w@mail.gmail.com>
References: <CAH8vcWzSGswT8rV6z9KRmTfuuQrsk6xk3f3BqeVBhXr15SZJ4w@mail.gmail.com>
Message-ID: <4F85B40F.80304@candelatech.com>

On 04/11/2012 09:37 AM, W. E. W. Russell wrote:
> All,
>
> My name is William Russell and I'm trying to migrate from RHEL5 to RHEL6 for a particular server I have.
>
> I was using the XORP for multicast routing and (I believe) attaching IP addresses to bonded & bridged interfaces.
>
> In RHEL5, I have no issues. When the server boots up, the correct addresses are attached to the correct interfaces and everything work smoothly.
> in RHEL6, I have an issue. When the server boots up, XORP starts fine, but when I do an 'ifconfig' I don't see any of the IP addresses attached to the
> interfaces (which also get created correctly).
>
> The config.boot file is exactly the same as it was before.
>
> Has anyone faced these issues? Any leads on where I should start looking to solve the problem?

Tell us what version of xorp, and post xorp log files (or look through them yourself
to see if there are any obvious errors).

Post your xorp config file as well.

Thanks,
Ben

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


From wrussell at incnetworks.com  Wed Apr 11 09:48:50 2012
From: wrussell at incnetworks.com (W. E. W. Russell)
Date: Wed, 11 Apr 2012 12:48:50 -0400
Subject: [Xorp-users] From RHEL5 to RHEL6: Any Issues?
In-Reply-To: <4F85B40F.80304@candelatech.com>
References: <CAH8vcWzSGswT8rV6z9KRmTfuuQrsk6xk3f3BqeVBhXr15SZJ4w@mail.gmail.com>
	<4F85B40F.80304@candelatech.com>
Message-ID: <CAH8vcWy729fSYOGwLfDUU_WP=ojurwkuuOC591mO=6TJ2y4Evw@mail.gmail.com>

On Wed, Apr 11, 2012 at 12:40 PM, Ben Greear <greearb at candelatech.com>wrote:

> On 04/11/2012 09:37 AM, W. E. W. Russell wrote:
>
>> All,
>>
>> My name is William Russell and I'm trying to migrate from RHEL5 to RHEL6
>> for a particular server I have.
>>
>> I was using the XORP for multicast routing and (I believe) attaching IP
>> addresses to bonded & bridged interfaces.
>>
>> In RHEL5, I have no issues. When the server boots up, the correct
>> addresses are attached to the correct interfaces and everything work
>> smoothly.
>> in RHEL6, I have an issue. When the server boots up, XORP starts fine,
>> but when I do an 'ifconfig' I don't see any of the IP addresses attached to
>> the
>> interfaces (which also get created correctly).
>>
>> The config.boot file is exactly the same as it was before.
>>
>> Has anyone faced these issues? Any leads on where I should start looking
>> to solve the problem?
>>
>
> Tell us what version of xorp, and post xorp log files (or look through
> them yourself
> to see if there are any obvious errors).
>
> Post your xorp config file as well.
>
> Thanks,
> Ben
>
> --
> Ben Greear <greearb at candelatech.com>
> Candela Technologies Inc  http://www.candelatech.com
>
>
Thanks, Ben. I feel like an idiot now. I didn't think to look in the log,
because the "service xorp restart/start/stop" all sent back OKs, so I
didn't think anything of it. SMH.

I found the obvious error - the package didn't install with the PXE boot.
Thanks for the lead...albiet the OBVIOUS one. LOL.

Best regards,
William

-- 
William E. W. Russell
Director, Systems Integration

incNETWORKS, Inc.
25 James Way
Long Branch, NJ 07724
Cell Phone # 732-744-6483
Work Phone # 732-508-2224
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20120411/4fb3449a/attachment.html 

From mass3mass at gmail.com  Wed Apr 11 14:28:26 2012
From: mass3mass at gmail.com (MAS .)
Date: Wed, 11 Apr 2012 21:28:26 +0000
Subject: [Xorp-users] XORP : Embedded Platform Software requirements
Message-ID: <CAKbuTVrzLeEF-qPtGBnU6YUOC7zrfcZyGRoerEERvZLiaVROfA@mail.gmail.com>

Hi all,

I have compiled XORP and installed on x86 machine then its working fine.
But I need to put it on embedded board with ARM processor so I
cross-compiled it and put it on the board.

Now problem is that its not working fine, even its not printing any error
messages on terminal. I don't know what is wrong. Can anyone help me. Is
there any software package requirements i.e. do I need to install
any softwares on board in order to XORP to work? Basically my board only
has Linux running on it without any spacial packages.


Thanks and regards,
MAS
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20120411/7b6b4556/attachment.html 

From hozer at hozed.org  Wed Apr 11 14:52:54 2012
From: hozer at hozed.org (Troy Benjegerdes)
Date: Wed, 11 Apr 2012 16:52:54 -0500
Subject: [Xorp-users] XORP : Embedded Platform Software requirements
In-Reply-To: <CAKbuTVrzLeEF-qPtGBnU6YUOC7zrfcZyGRoerEERvZLiaVROfA@mail.gmail.com>
References: <CAKbuTVrzLeEF-qPtGBnU6YUOC7zrfcZyGRoerEERvZLiaVROfA@mail.gmail.com>
Message-ID: <20120411215254.GF19718@excalibur.hozed.org>

This would probably depend on what embedded linux distribution the
board is running and what board it is, and how you cross-compiled
the package.

If you can give us more details, we might be able to help.

I'm going to attempt to build it on my debian-arm install,
and see what happens.

If you have some constraints (or ndas) so you can't provide more
details about what board and distro, there are probably several
of us (including myself) that would be happy to do a consulting
contract to help you out as well.

On Wed, Apr 11, 2012 at 09:28:26PM +0000, MAS . wrote:
> Hi all,
> 
> I have compiled XORP and installed on x86 machine then its working fine.
> But I need to put it on embedded board with ARM processor so I
> cross-compiled it and put it on the board.
> 
> Now problem is that its not working fine, even its not printing any error
> messages on terminal. I don't know what is wrong. Can anyone help me. Is
> there any software package requirements i.e. do I need to install
> any softwares on board in order to XORP to work? Basically my board only
> has Linux running on it without any spacial packages.
> 
> 
> Thanks and regards,
> MAS


From mass3mass at gmail.com  Wed Apr 11 15:11:48 2012
From: mass3mass at gmail.com (MAS .)
Date: Wed, 11 Apr 2012 22:11:48 +0000
Subject: [Xorp-users] XORP : Embedded Platform Software requirements
In-Reply-To: <20120411215254.GF19718@excalibur.hozed.org>
References: <CAKbuTVrzLeEF-qPtGBnU6YUOC7zrfcZyGRoerEERvZLiaVROfA@mail.gmail.com>
	<20120411215254.GF19718@excalibur.hozed.org>
Message-ID: <CAKbuTVo6WvnwkLqbX5U3+V7MxiN8eEEW-DB3=C76XkgeiR_gpw@mail.gmail.com>

Hi
Thanks for the reply Troy,

I am student and we have designed ARM board with marvell switch chip
88E6065 in our lab. Actually I want to manage L2 functionality of switch
chip using XorPlus, which is another derivative  of XORP with L2
functionality.

Board has Linux-2.6.30 kernel version running on it and Uboot-1.3.4.. we
also have gcc, gdb nothing more. I cross-compiled Xorplus and put it on the
board but its literally doing nothing, no logs, no error messages. Same
XorPlus is running fine on x86 machine.

For trial purpose I executed xorp_rtrmgr on x86 and board without any
configuration. On x86 machine atleast its printing error messages but on
board its doing nothing? I thought may be xorp needed some packages other
than xorp libreary.

thanks and regards,
MAS.

On 11 April 2012 21:52, Troy Benjegerdes <hozer at hozed.org> wrote:

> This would probably depend on what embedded linux distribution the
> board is running and what board it is, and how you cross-compiled
> the package.
>
> If you can give us more details, we might be able to help.
>
> I'm going to attempt to build it on my debian-arm install,
> and see what happens.
>
> If you have some constraints (or ndas) so you can't provide more
> details about what board and distro, there are probably several
> of us (including myself) that would be happy to do a consulting
> contract to help you out as well.
>
> On Wed, Apr 11, 2012 at 09:28:26PM +0000, MAS . wrote:
> > Hi all,
> >
> > I have compiled XORP and installed on x86 machine then its working fine.
> > But I need to put it on embedded board with ARM processor so I
> > cross-compiled it and put it on the board.
> >
> > Now problem is that its not working fine, even its not printing any error
> > messages on terminal. I don't know what is wrong. Can anyone help me. Is
> > there any software package requirements i.e. do I need to install
> > any softwares on board in order to XORP to work? Basically my board only
> > has Linux running on it without any spacial packages.
> >
> >
> > Thanks and regards,
> > MAS
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20120411/5b983957/attachment.html 

From hozer at hozed.org  Wed Apr 11 15:18:51 2012
From: hozer at hozed.org (Troy Benjegerdes)
Date: Wed, 11 Apr 2012 17:18:51 -0500
Subject: [Xorp-users] XORP : Embedded Platform Software requirements
In-Reply-To: <CAKbuTVo6WvnwkLqbX5U3+V7MxiN8eEEW-DB3=C76XkgeiR_gpw@mail.gmail.com>
References: <CAKbuTVrzLeEF-qPtGBnU6YUOC7zrfcZyGRoerEERvZLiaVROfA@mail.gmail.com>
	<20120411215254.GF19718@excalibur.hozed.org>
	<CAKbuTVo6WvnwkLqbX5U3+V7MxiN8eEEW-DB3=C76XkgeiR_gpw@mail.gmail.com>
Message-ID: <20120411221851.GJ19718@excalibur.hozed.org>

What cpu are you using to talk to the marvell chip? I assume
you have an SMI (serial managment interface) port and driver
on your embedded ARM cpu..

Would you have a way to install and boot a debian-arm image?

On Wed, Apr 11, 2012 at 10:11:48PM +0000, MAS . wrote:
> Hi
> Thanks for the reply Troy,
> 
> I am student and we have designed ARM board with marvell switch chip
> 88E6065 in our lab. Actually I want to manage L2 functionality of switch
> chip using XorPlus, which is another derivative  of XORP with L2
> functionality.
> 
> Board has Linux-2.6.30 kernel version running on it and Uboot-1.3.4.. we
> also have gcc, gdb nothing more. I cross-compiled Xorplus and put it on the
> board but its literally doing nothing, no logs, no error messages. Same
> XorPlus is running fine on x86 machine.
> 
> For trial purpose I executed xorp_rtrmgr on x86 and board without any
> configuration. On x86 machine atleast its printing error messages but on
> board its doing nothing? I thought may be xorp needed some packages other
> than xorp libreary.
> 
> thanks and regards,
> MAS.
> 
> On 11 April 2012 21:52, Troy Benjegerdes <hozer at hozed.org> wrote:
> 
> > This would probably depend on what embedded linux distribution the
> > board is running and what board it is, and how you cross-compiled
> > the package.
> >
> > If you can give us more details, we might be able to help.
> >
> > I'm going to attempt to build it on my debian-arm install,
> > and see what happens.
> >
> > If you have some constraints (or ndas) so you can't provide more
> > details about what board and distro, there are probably several
> > of us (including myself) that would be happy to do a consulting
> > contract to help you out as well.
> >
> > On Wed, Apr 11, 2012 at 09:28:26PM +0000, MAS . wrote:
> > > Hi all,
> > >
> > > I have compiled XORP and installed on x86 machine then its working fine.
> > > But I need to put it on embedded board with ARM processor so I
> > > cross-compiled it and put it on the board.
> > >
> > > Now problem is that its not working fine, even its not printing any error
> > > messages on terminal. I don't know what is wrong. Can anyone help me. Is
> > > there any software package requirements i.e. do I need to install
> > > any softwares on board in order to XORP to work? Basically my board only
> > > has Linux running on it without any spacial packages.
> > >
> > >
> > > Thanks and regards,
> > > MAS
> >
> >

-- 
----------------------------------------------------------------------------
Troy Benjegerdes                 'da hozer'                hozer at hozed.org  
7 elements Farm						TerraCarbo biofuels

An Engineer is a man who can do for a dime what any fool can do for a dollar.
-anonymous

If you're going through hell, keep going. ~ Winston Churchill

The challenge in changing the world is not in having great ideas, it's in
having stupid simple ideas, as those are the ones that cause change.


From mass3mass at gmail.com  Wed Apr 11 15:28:07 2012
From: mass3mass at gmail.com (MAS .)
Date: Wed, 11 Apr 2012 22:28:07 +0000
Subject: [Xorp-users] XORP : Embedded Platform Software requirements
In-Reply-To: <20120411221851.GJ19718@excalibur.hozed.org>
References: <CAKbuTVrzLeEF-qPtGBnU6YUOC7zrfcZyGRoerEERvZLiaVROfA@mail.gmail.com>
	<20120411215254.GF19718@excalibur.hozed.org>
	<CAKbuTVo6WvnwkLqbX5U3+V7MxiN8eEEW-DB3=C76XkgeiR_gpw@mail.gmail.com>
	<20120411221851.GJ19718@excalibur.hozed.org>
Message-ID: <CAKbuTVp8uJ7iOs52YX6u_K6sT+AyYdoSYih_MOjPPwLYzgeg7Q@mail.gmail.com>

We have AT91SAM9G20EK ( Maxim ARM9). SMI Driver is working fine. Also I
have marvell SDK for switch and its too working fine.
I think there is NO way to install debian-arm, I'll look into it.

On 11 April 2012 22:18, Troy Benjegerdes <hozer at hozed.org> wrote:

> What cpu are you using to talk to the marvell chip? I assume
> you have an SMI (serial managment interface) port and driver
> on your embedded ARM cpu..
>
> Would you have a way to install and boot a debian-arm image?
>
> On Wed, Apr 11, 2012 at 10:11:48PM +0000, MAS . wrote:
> > Hi
> > Thanks for the reply Troy,
> >
> > I am student and we have designed ARM board with marvell switch chip
> > 88E6065 in our lab. Actually I want to manage L2 functionality of switch
> > chip using XorPlus, which is another derivative  of XORP with L2
> > functionality.
> >
> > Board has Linux-2.6.30 kernel version running on it and Uboot-1.3.4.. we
> > also have gcc, gdb nothing more. I cross-compiled Xorplus and put it on
> the
> > board but its literally doing nothing, no logs, no error messages. Same
> > XorPlus is running fine on x86 machine.
> >
> > For trial purpose I executed xorp_rtrmgr on x86 and board without any
> > configuration. On x86 machine atleast its printing error messages but on
> > board its doing nothing? I thought may be xorp needed some packages other
> > than xorp libreary.
> >
> > thanks and regards,
> > MAS.
> >
> > On 11 April 2012 21:52, Troy Benjegerdes <hozer at hozed.org> wrote:
> >
> > > This would probably depend on what embedded linux distribution the
> > > board is running and what board it is, and how you cross-compiled
> > > the package.
> > >
> > > If you can give us more details, we might be able to help.
> > >
> > > I'm going to attempt to build it on my debian-arm install,
> > > and see what happens.
> > >
> > > If you have some constraints (or ndas) so you can't provide more
> > > details about what board and distro, there are probably several
> > > of us (including myself) that would be happy to do a consulting
> > > contract to help you out as well.
> > >
> > > On Wed, Apr 11, 2012 at 09:28:26PM +0000, MAS . wrote:
> > > > Hi all,
> > > >
> > > > I have compiled XORP and installed on x86 machine then its working
> fine.
> > > > But I need to put it on embedded board with ARM processor so I
> > > > cross-compiled it and put it on the board.
> > > >
> > > > Now problem is that its not working fine, even its not printing any
> error
> > > > messages on terminal. I don't know what is wrong. Can anyone help
> me. Is
> > > > there any software package requirements i.e. do I need to install
> > > > any softwares on board in order to XORP to work? Basically my board
> only
> > > > has Linux running on it without any spacial packages.
> > > >
> > > >
> > > > Thanks and regards,
> > > > MAS
> > >
> > >
>
> --
>
> ----------------------------------------------------------------------------
> Troy Benjegerdes                 'da hozer'                hozer at hozed.org
> 7 elements Farm                                         TerraCarbo biofuels
>
> An Engineer is a man who can do for a dime what any fool can do for a
> dollar.
> -anonymous
>
> If you're going through hell, keep going. ~ Winston Churchill
>
> The challenge in changing the world is not in having great ideas, it's in
> having stupid simple ideas, as those are the ones that cause change.
>
>


-- 
Thanks and Regards,
MAS.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20120411/e82d3b3d/attachment-0001.html 

From hozer at hozed.org  Wed Apr 11 17:19:18 2012
From: hozer at hozed.org (Troy Benjegerdes)
Date: Wed, 11 Apr 2012 19:19:18 -0500
Subject: [Xorp-users] XORP : Embedded Platform Software requirements
In-Reply-To: <CAKbuTVp8uJ7iOs52YX6u_K6sT+AyYdoSYih_MOjPPwLYzgeg7Q@mail.gmail.com>
References: <CAKbuTVrzLeEF-qPtGBnU6YUOC7zrfcZyGRoerEERvZLiaVROfA@mail.gmail.com>
	<20120411215254.GF19718@excalibur.hozed.org>
	<CAKbuTVo6WvnwkLqbX5U3+V7MxiN8eEEW-DB3=C76XkgeiR_gpw@mail.gmail.com>
	<20120411221851.GJ19718@excalibur.hozed.org>
	<CAKbuTVp8uJ7iOs52YX6u_K6sT+AyYdoSYih_MOjPPwLYzgeg7Q@mail.gmail.com>
Message-ID: <20120412001918.GK19718@excalibur.hozed.org>

Is this the board you have, or did you do a custom board?

http://www.atmel.com/tools/SAM9G20-EK.aspx

If you've got USB-host, (or SDcard) you should be able to put
a debian-arm chroot on a usb driver/sdcard. This is how I'm 
running debian (and self-hosted compiling xorp) on a Asus
transformer android tablet.

On Wed, Apr 11, 2012 at 10:28:07PM +0000, MAS . wrote:
> We have AT91SAM9G20EK ( Maxim ARM9). SMI Driver is working fine. Also I
> have marvell SDK for switch and its too working fine.
> I think there is NO way to install debian-arm, I'll look into it.
> 
> On 11 April 2012 22:18, Troy Benjegerdes <hozer at hozed.org> wrote:
> 
> > What cpu are you using to talk to the marvell chip? I assume
> > you have an SMI (serial managment interface) port and driver
> > on your embedded ARM cpu..
> >
> > Would you have a way to install and boot a debian-arm image?
> >
> > On Wed, Apr 11, 2012 at 10:11:48PM +0000, MAS . wrote:
> > > Hi
> > > Thanks for the reply Troy,
> > >
> > > I am student and we have designed ARM board with marvell switch chip
> > > 88E6065 in our lab. Actually I want to manage L2 functionality of switch
> > > chip using XorPlus, which is another derivative  of XORP with L2
> > > functionality.
> > >
> > > Board has Linux-2.6.30 kernel version running on it and Uboot-1.3.4.. we
> > > also have gcc, gdb nothing more. I cross-compiled Xorplus and put it on
> > the
> > > board but its literally doing nothing, no logs, no error messages. Same
> > > XorPlus is running fine on x86 machine.
> > >
> > > For trial purpose I executed xorp_rtrmgr on x86 and board without any
> > > configuration. On x86 machine atleast its printing error messages but on
> > > board its doing nothing? I thought may be xorp needed some packages other
> > > than xorp libreary.
> > >
> > > thanks and regards,
> > > MAS.
> > >
> > > On 11 April 2012 21:52, Troy Benjegerdes <hozer at hozed.org> wrote:
> > >
> > > > This would probably depend on what embedded linux distribution the
> > > > board is running and what board it is, and how you cross-compiled
> > > > the package.
> > > >
> > > > If you can give us more details, we might be able to help.
> > > >
> > > > I'm going to attempt to build it on my debian-arm install,
> > > > and see what happens.
> > > >
> > > > If you have some constraints (or ndas) so you can't provide more
> > > > details about what board and distro, there are probably several
> > > > of us (including myself) that would be happy to do a consulting
> > > > contract to help you out as well.
> > > >
> > > > On Wed, Apr 11, 2012 at 09:28:26PM +0000, MAS . wrote:
> > > > > Hi all,
> > > > >
> > > > > I have compiled XORP and installed on x86 machine then its working
> > fine.
> > > > > But I need to put it on embedded board with ARM processor so I
> > > > > cross-compiled it and put it on the board.
> > > > >
> > > > > Now problem is that its not working fine, even its not printing any
> > error
> > > > > messages on terminal. I don't know what is wrong. Can anyone help
> > me. Is
> > > > > there any software package requirements i.e. do I need to install
> > > > > any softwares on board in order to XORP to work? Basically my board
> > only
> > > > > has Linux running on it without any spacial packages.
> > > > >
> > > > >
> > > > > Thanks and regards,
> > > > > MAS
> > > >
> > > >
> >
> > --
> >
> > ----------------------------------------------------------------------------
> > Troy Benjegerdes                 'da hozer'                hozer at hozed.org
> > 7 elements Farm                                         TerraCarbo biofuels
> >
> > An Engineer is a man who can do for a dime what any fool can do for a
> > dollar.
> > -anonymous
> >
> > If you're going through hell, keep going. ~ Winston Churchill
> >
> > The challenge in changing the world is not in having great ideas, it's in
> > having stupid simple ideas, as those are the ones that cause change.
> >
> >
> 
> 
> -- 
> Thanks and Regards,
> MAS.

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


-- 
----------------------------------------------------------------------------
Troy Benjegerdes                 'da hozer'                hozer at hozed.org  
7 elements Farm						TerraCarbo biofuels

An Engineer is a man who can do for a dime what any fool can do for a dollar.
-anonymous

If you're going through hell, keep going. ~ Winston Churchill

The challenge in changing the world is not in having great ideas, it's in
having stupid simple ideas, as those are the ones that cause change.


From david at commroom.net  Thu Apr 12 21:49:29 2012
From: david at commroom.net (David Davidson)
Date: Thu, 12 Apr 2012 21:49:29 -0700
Subject: [Xorp-users] Route Redist between RIP and OSPF - working?
In-Reply-To: <OF47F06D31.CB03C970-ON852579DC.00766FC1-852579DC.0076A851@rockwellcollins.com>
References: <CAFdo_mWwraYMUGNCT5Hkj4xCZak3-RSnm6T-HoAG7b6ASh4cEQ@mail.gmail.com>
	<OF47F06D31.CB03C970-ON852579DC.00766FC1-852579DC.0076A851@rockwellcollins.com>
Message-ID: <4F87B059.8010609@commroom.net>

Hey Folks,

Yes, same here. Thank you Steve for identifying this and helping to find 
a solution.

Thank you folks for all your hard work and troubleshooting this. And 
thanks to Igor for the patches and thanks to Ben also.

The attachment works as shown. I removed the OSPF interface (notice the 
commented lines) and it still works the way I would expect, after 
applying the patches. Thank you again!

David


On 04/10/2012 02:36 PM, swdickey at rockwellcollins.com wrote:
> This fixes my issue.
>
> Thanks Igor and to the others who helped with this.
>
> Steve
>
>
> *Igor Maravic' <igorm at etf.rs>*
>
> 04/10/2012 08:57 AM
> Please respond to
> igorm at etf.rs
>
>
> 	
> To
> 	xorp-users at xorp.org, xorp-users at icir.org, xorp-hackers at icir.org
> cc
> 	swdickey at rockwellcollins.com, david at commroom.net
> Subject
> 	Route Redist between RIP and OSPF - working?
>
>
>
> 	
>
>
>
>
>
> Hi all,
> I think that I found solution to this problem :)
>
> I started looking where Steve stopped
> (PolicyRedistTable<A>::replace_policytags function).
> It was just the tip of the iceberg.
>
> Problem was that protocol's existing EXPORT_SOURCE match policies
> weren't refreshed when new export filter is created.
> In this case problem was with exporting to "connected" protocol.
>
> New protocol always has accurate policy tags for route lookup. It
> always searches routes that has no tag, or
> older protocol tags or it's tags. If it finds them it prepends it's tag.
> Older protocols are searching routes that has no tags, or have older
> tags. If it finds such a route it prepends it's tag.
>
> EXPORT_SOURCEMATCH policies are executed in order that depends on 
> protocol name.
> If newer protocol has lower letter (for example ospf's policies are
> executed before rip's, because "o" precedes "r"),
> new protocol prepends new tags, that are unrecognizable to older
> protocol, to routes that it has found.
> Because older protocol is unaware of new tags, it concludes that
> routes are deleted and it deletes them.
> This is not what we are expecting.
>
> If older protocol is executed first, it prepends it's tag to routes
> that it has found. Because old tag is recognizable by
> newer protocol new tags are also prepended to routes. This case works
> as expected.
>
> Solution - refresh tags for all protocol's EXPORT_SOURCEMATCH routes
> when new export filter is created.
>
> I'm sending patch to xorp-hackers list.
>
> I tested it for simple solutions, so it does need more testing :)
>
> It would be nice if someone would post more complicated policies to
> test this issue.
>
> BR
> Igor
>
>
>
>
> _______________________________________________
> 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/20120412/bf756033/attachment.html 
-------------- next part --------------
##########################
#xorp1
##########################
configure exclusive
set rtrmgr config-directory /etc/xorp
set protocols ospf4 router-id 192.168.30.1
set protocols ospf4 area 0.0.0.0 interface eth0 vif eth0 address 192.168.30.1 disable false
set protocols ospf4 area 0.0.0.0 interface eth1 vif eth1 address 172.16.1.1 disable false
set interfaces interface eth0 vif eth0 address 192.168.30.1 prefix-length 24
set interfaces interface eth1 vif eth1 address 172.16.1.1 prefix-length 24
set fea unicast-forwarding4 disable false
commit
exit configuration-mode



##########################
#xorp2
##########################
configure exclusive
set rtrmgr config-directory /etc/xorp
set protocols ospf4 router-id 192.168.30.2
set protocols ospf4 area 0.0.0.0 interface eth0 vif eth0 address 192.168.30.2 disable false

#set protocols ospf4 area 0.0.0.0 interface eth1 vif eth1 address 192.168.40.1 disable false
#set protocols ospf4 area 0.0.0.0 interface eth1 vif eth1 address 192.168.40.1 passive

set protocols rip interface eth1 vif eth1 address 192.168.40.1 disable false
set interfaces interface eth0 vif eth0 address 192.168.30.2 prefix-length 24
set interfaces interface eth1 vif eth1 address 192.168.40.1 prefix-length 24
set policy policy-statement OSPF-to-RIP term 10 from protocol ospf4
set policy policy-statement OSPF-to-RIP term 20 from protocol connected
set policy policy-statement OSPF-to-RIP then accept
set policy policy-statement RIP-to-OSPF term 10 from protocol rip
set policy policy-statement RIP-to-OSPF term 20 from protocol connected
set policy policy-statement RIP-to-OSPF then accept
set protocols ospf4 export RIP-to-OSPF
set protocols rip export OSPF-to-RIP
set fea unicast-forwarding4 disable false
commit
exit configuration-mode



##########################
#xorp3
##########################
configure exclusive
set rtrmgr config-directory /etc/xorp
set protocols rip interface eth1 vif eth1 address 192.168.40.2 disable false
set protocols rip interface eth0 vif eth0 address 10.0.0.1 disable false
set interfaces interface eth1 vif eth1 address 192.168.40.2 prefix-length 24
set interfaces interface eth0 vif eth0 address 10.0.0.1 prefix-length 24
set fea unicast-forwarding4 disable false
set policy policy-statement CON-to-RIP term 10 from protocol connected
set policy policy-statement CON-to-RIP term 10 then accept
set protocols rip export CON-to-RIP
commit
exit configuration-mode


##########################
#xorp4
##########################
configure exclusive
set rtrmgr config-directory /etc/xorp
set protocols rip interface eth0 vif eth0 address 10.0.0.2 disable false
set interfaces interface eth0 vif eth0 address 10.0.0.2 prefix-length 24
set fea unicast-forwarding4 disable false
commit
exit configuration-mode


##########################
#xorp5
##########################
configure exclusive
set rtrmgr config-directory /etc/xorp
set protocols ospf4 router-id 172.16.1.2
set protocols ospf4 area 0.0.0.0 interface eth0 vif eth0 address 172.16.1.2 disable false
set interfaces interface eth0 vif eth0 address 172.16.1.2 prefix-length 24
set fea unicast-forwarding4 disable false
commit
exit configuration-mode






From mass3mass at gmail.com  Mon Apr 16 04:57:43 2012
From: mass3mass at gmail.com (MAS .)
Date: Mon, 16 Apr 2012 11:57:43 +0000
Subject: [Xorp-users] XORP : Embedded Platform Software requirements
In-Reply-To: <20120412001918.GK19718@excalibur.hozed.org>
References: <CAKbuTVrzLeEF-qPtGBnU6YUOC7zrfcZyGRoerEERvZLiaVROfA@mail.gmail.com>
	<20120411215254.GF19718@excalibur.hozed.org>
	<CAKbuTVo6WvnwkLqbX5U3+V7MxiN8eEEW-DB3=C76XkgeiR_gpw@mail.gmail.com>
	<20120411221851.GJ19718@excalibur.hozed.org>
	<CAKbuTVp8uJ7iOs52YX6u_K6sT+AyYdoSYih_MOjPPwLYzgeg7Q@mail.gmail.com>
	<20120412001918.GK19718@excalibur.hozed.org>
Message-ID: <CAKbuTVrYhu8brk5tZmmS6juLgDrjrX4usT4SVfK=t_CWAX3wBQ@mail.gmail.com>

We have designed our own custom board. We are using nand flash for storing
kernel image.

I figured out previous problem, actually error logs are going to
/dev/stderr but was not getting displayed on stdout.

Now I have another problem XORP is giving following error message, here is
the log:
===============================================================================================
[ 1970/01/01 05:22:44  WARNING xorp_rtrmgr:720 LIBXORP +461 timer.cc
expire_one ] Timer Expiry *much* later than scheduled: behind by 25.827435
seconds
[ 1970/01/01 05:22:46  INFO xorp_rtrmgr:720 RTRMGR +101 module_manager.cc
execute ] Executing module: login (system/pica_login)
[ 1970/01/01 05:22:47  INFO xorp_rtrmgr:720 RTRMGR +101 module_manager.cc
execute ] Executing module: cardmgr (cardmgr/pica_cardmgr)
[ 1970/01/01 05:22:50  INFO xorp_rtrmgr:720 RTRMGR +101 module_manager.cc
execute ] Executing module: fea (fea/xorp_fea)
[ 1970/01/01 05:22:54  INFO xorp_rtrmgr:720 RTRMGR +101 module_manager.cc
execute ] Executing module: interfaces (sif/pica_sif)
[ 1970/01/01 05:22:54  ERROR xorp_fea:729 LIBCOMM +101 comm_sock.c
comm_sock_open ] Error opening socket (domain = 10, type = 2, protocol =
0): Address family not supported by protocol
[ 1970/01/01 05:22:54 INFO xorp_fea MFEA ] MFEA enabled
[ 1970/01/01 05:22:54 INFO xorp_fea MFEA ] CLI enabled
[ 1970/01/01 05:22:54 INFO xorp_fea MFEA ] CLI started
[ 1970/01/01 05:22:54 INFO xorp_fea MFEA ] MFEA enabled
[ 1970/01/01 05:22:55 INFO xorp_fea MFEA ] CLI enabled
[ 1970/01/01 05:22:55 INFO xorp_fea MFEA ] CLI started
[ 1970/01/01 05:22:56  WARNING xorp_rtrmgr:720 XrlFinderTarget +437
../xrl/targets/finder_base.cc handle_finder_0_2_resolve_xrl ] Handling
method for finder/0.2/resolve_xrl failed: XrlCmdError 102 Command failed
Xrl target is not enabled.
[ 1970/01/01 05:22:57 INFO pica_cardmgr XifFinderEventNotifier ] Registered
{state,client} = {CARD_REMOVED_STATE,
sif-d1fe8452916e5bc4c817cd317a516074 at 10.107.48.61}
[ 1970/01/01 05:22:57 INFO pica_cardmgr XifFinderEventNotifier ] Registered
{state,client} = {CARD_MISCONFIGURED_STATE,
sif-d1fe8452916e5bc4c817cd317a516074 at 10.107.48.61}
[ 1970/01/01 05:22:57 INFO pica_cardmgr XifFinderEventNotifier ] Registered
{state,client} = {CARD_INITIALIZED_STATE,
sif-d1fe8452916e5bc4c817cd317a516074 at 10.107.48.61}
[ 1970/01/01 05:22:57 INFO pica_cardmgr XifFinderEventNotifier ] Registered
{state,client} = {CARD_PHASE_1_DONE_STATE,
sif-d1fe8452916e5bc4c817cd317a516074 at 10.107.48.61}
[ 1970/01/01 05:22:57 INFO pica_cardmgr XifFinderEventNotifier ] Registered
{state,client} = {CARD_PHASE_2_DONE_STATE,
sif-d1fe8452916e5bc4c817cd317a516074 at 10.107.48.61}
[ 1970/01/01 05:22:57 INFO pica_cardmgr XifFinderEventNotifier ] Registered
{state,client} = {CARD_PHASE_3_DONE_STATE,
sif-d1fe8452916e5bc4c817cd317a516074 at 10.107.48.61}
[ 1970/01/01 05:22:57 INFO pica_cardmgr XifFinderEventNotifier ] Registered
{state,client} = {CARD_RUNNING_STATE,
sif-d1fe8452916e5bc4c817cd317a516074 at 10.107.48.61}
[ 1970/01/01 05:22:57 INFO pica_cardmgr XifFinderEventNotifier ] Registered
{state,client} = {CARD_DEAD_STATE,
sif-d1fe8452916e5bc4c817cd317a516074 at 10.107.48.61}
[ 1970/01/01 05:22:57 INFO pica_cardmgr XifFinderEventNotifier ] Succeeding
in dispatching card state(CARD_REMOVED_STATE) to
sif-d1fe8452916e5bc4c817cd317a516074 at 10.107.48.61
[ 1970/01/01 05:22:58  ERROR xorp_rtrmgr:720 RTRMGR +925
master_conf_tree.cc commit_pass2_done ] Commit failed: 102 Command failed
invalid ifname:ge-1/1/25
[ 1970/01/01 05:22:58  ERROR xorp_rtrmgr:720 RTRMGR +389
master_conf_tree.cc config_done ] Configuration failed: 102 Command failed
invalid ifname:ge-1/1/25
[ 1970/01/01 05:22:58  INFO xorp_rtrmgr:720 RTRMGR +2239 task.cc run_task ]
No more tasks to run
========================================================================================================

Can anyone help to figure this out?
Your help will be greatly appreciated, thanks.



On 12 April 2012 00:19, Troy Benjegerdes <hozer at hozed.org> wrote:

> Is this the board you have, or did you do a custom board?
>
> http://www.atmel.com/tools/SAM9G20-EK.aspx
>
> If you've got USB-host, (or SDcard) you should be able to put
> a debian-arm chroot on a usb driver/sdcard. This is how I'm
> running debian (and self-hosted compiling xorp) on a Asus
> transformer android tablet.
>
> On Wed, Apr 11, 2012 at 10:28:07PM +0000, MAS . wrote:
> > We have AT91SAM9G20EK ( Maxim ARM9). SMI Driver is working fine. Also I
> > have marvell SDK for switch and its too working fine.
> > I think there is NO way to install debian-arm, I'll look into it.
> >
> > On 11 April 2012 22:18, Troy Benjegerdes <hozer at hozed.org> wrote:
> >
> > > What cpu are you using to talk to the marvell chip? I assume
> > > you have an SMI (serial managment interface) port and driver
> > > on your embedded ARM cpu..
> > >
> > > Would you have a way to install and boot a debian-arm image?
> > >
> > > On Wed, Apr 11, 2012 at 10:11:48PM +0000, MAS . wrote:
> > > > Hi
> > > > Thanks for the reply Troy,
> > > >
> > > > I am student and we have designed ARM board with marvell switch chip
> > > > 88E6065 in our lab. Actually I want to manage L2 functionality of
> switch
> > > > chip using XorPlus, which is another derivative  of XORP with L2
> > > > functionality.
> > > >
> > > > Board has Linux-2.6.30 kernel version running on it and
> Uboot-1.3.4.. we
> > > > also have gcc, gdb nothing more. I cross-compiled Xorplus and put it
> on
> > > the
> > > > board but its literally doing nothing, no logs, no error messages.
> Same
> > > > XorPlus is running fine on x86 machine.
> > > >
> > > > For trial purpose I executed xorp_rtrmgr on x86 and board without any
> > > > configuration. On x86 machine atleast its printing error messages
> but on
> > > > board its doing nothing? I thought may be xorp needed some packages
> other
> > > > than xorp libreary.
> > > >
> > > > thanks and regards,
> > > > MAS.
> > > >
> > > > On 11 April 2012 21:52, Troy Benjegerdes <hozer at hozed.org> wrote:
> > > >
> > > > > This would probably depend on what embedded linux distribution the
> > > > > board is running and what board it is, and how you cross-compiled
> > > > > the package.
> > > > >
> > > > > If you can give us more details, we might be able to help.
> > > > >
> > > > > I'm going to attempt to build it on my debian-arm install,
> > > > > and see what happens.
> > > > >
> > > > > If you have some constraints (or ndas) so you can't provide more
> > > > > details about what board and distro, there are probably several
> > > > > of us (including myself) that would be happy to do a consulting
> > > > > contract to help you out as well.
> > > > >
> > > > > On Wed, Apr 11, 2012 at 09:28:26PM +0000, MAS . wrote:
> > > > > > Hi all,
> > > > > >
> > > > > > I have compiled XORP and installed on x86 machine then its
> working
> > > fine.
> > > > > > But I need to put it on embedded board with ARM processor so I
> > > > > > cross-compiled it and put it on the board.
> > > > > >
> > > > > > Now problem is that its not working fine, even its not printing
> any
> > > error
> > > > > > messages on terminal. I don't know what is wrong. Can anyone help
> > > me. Is
> > > > > > there any software package requirements i.e. do I need to install
> > > > > > any softwares on board in order to XORP to work? Basically my
> board
> > > only
> > > > > > has Linux running on it without any spacial packages.
> > > > > >
> > > > > >
> > > > > > Thanks and regards,
> > > > > > MAS
> > > > >
> > > > >
> > >
> > > --
> > >
> > >
> ----------------------------------------------------------------------------
> > > Troy Benjegerdes                 'da hozer'
> hozer at hozed.org
> > > 7 elements Farm                                         TerraCarbo
> biofuels
> > >
> > > An Engineer is a man who can do for a dime what any fool can do for a
> > > dollar.
> > > -anonymous
> > >
> > > If you're going through hell, keep going. ~ Winston Churchill
> > >
> > > The challenge in changing the world is not in having great ideas, it's
> in
> > > having stupid simple ideas, as those are the ones that cause change.
> > >
> > >
> >
> >
> > --
> > Thanks and Regards,
> > MAS.
>
> > _______________________________________________
> > Xorp-users mailing list
> > Xorp-users at xorp.org
> > http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users
>
>
> --
>
> ----------------------------------------------------------------------------
> Troy Benjegerdes                 'da hozer'                hozer at hozed.org
> 7 elements Farm                                         TerraCarbo biofuels
>
> An Engineer is a man who can do for a dime what any fool can do for a
> dollar.
> -anonymous
>
> If you're going through hell, keep going. ~ Winston Churchill
>
> The challenge in changing the world is not in having great ideas, it's in
> having stupid simple ideas, as those are the ones that cause change.
>
>


-- 
Thanks and Regards,
MAS.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20120416/0e3bc0fa/attachment.html 

From mass3mass at gmail.com  Tue Apr 17 03:08:08 2012
From: mass3mass at gmail.com (MAS .)
Date: Tue, 17 Apr 2012 10:08:08 +0000
Subject: [Xorp-users] XORP : Embedded Platform Software requirements
In-Reply-To: <CAKbuTVrYhu8brk5tZmmS6juLgDrjrX4usT4SVfK=t_CWAX3wBQ@mail.gmail.com>
References: <CAKbuTVrzLeEF-qPtGBnU6YUOC7zrfcZyGRoerEERvZLiaVROfA@mail.gmail.com>
	<20120411215254.GF19718@excalibur.hozed.org>
	<CAKbuTVo6WvnwkLqbX5U3+V7MxiN8eEEW-DB3=C76XkgeiR_gpw@mail.gmail.com>
	<20120411221851.GJ19718@excalibur.hozed.org>
	<CAKbuTVp8uJ7iOs52YX6u_K6sT+AyYdoSYih_MOjPPwLYzgeg7Q@mail.gmail.com>
	<20120412001918.GK19718@excalibur.hozed.org>
	<CAKbuTVrYhu8brk5tZmmS6juLgDrjrX4usT4SVfK=t_CWAX3wBQ@mail.gmail.com>
Message-ID: <CAKbuTVqMDgQ+ByAPHSoGkVoVsqCLm8vkin4NYEJKxk-wW=uyuw@mail.gmail.com>

I figured that out. It seems that my kernel is not supporting ipv6. so
either you need to enable it or recompile XORP with ipv6 disabled.

i.e.
    ./configure --disable-ipv6


On 16 April 2012 11:57, MAS . <mass3mass at gmail.com> wrote:

> We have designed our own custom board. We are using nand flash for storing
> kernel image.
>
> I figured out previous problem, actually error logs are going to
> /dev/stderr but was not getting displayed on stdout.
>
> Now I have another problem XORP is giving following error message, here is
> the log:
>
> ===============================================================================================
>  [ 1970/01/01 05:22:44  WARNING xorp_rtrmgr:720 LIBXORP +461 timer.cc
> expire_one ] Timer Expiry *much* later than scheduled: behind by 25.827435
> seconds
> [ 1970/01/01 05:22:46  INFO xorp_rtrmgr:720 RTRMGR +101 module_manager.cc
> execute ] Executing module: login (system/pica_login)
> [ 1970/01/01 05:22:47  INFO xorp_rtrmgr:720 RTRMGR +101 module_manager.cc
> execute ] Executing module: cardmgr (cardmgr/pica_cardmgr)
> [ 1970/01/01 05:22:50  INFO xorp_rtrmgr:720 RTRMGR +101 module_manager.cc
> execute ] Executing module: fea (fea/xorp_fea)
> [ 1970/01/01 05:22:54  INFO xorp_rtrmgr:720 RTRMGR +101 module_manager.cc
> execute ] Executing module: interfaces (sif/pica_sif)
> [ 1970/01/01 05:22:54  ERROR xorp_fea:729 LIBCOMM +101 comm_sock.c
> comm_sock_open ] Error opening socket (domain = 10, type = 2, protocol =
> 0): Address family not supported by protocol
> [ 1970/01/01 05:22:54 INFO xorp_fea MFEA ] MFEA enabled
> [ 1970/01/01 05:22:54 INFO xorp_fea MFEA ] CLI enabled
> [ 1970/01/01 05:22:54 INFO xorp_fea MFEA ] CLI started
> [ 1970/01/01 05:22:54 INFO xorp_fea MFEA ] MFEA enabled
> [ 1970/01/01 05:22:55 INFO xorp_fea MFEA ] CLI enabled
> [ 1970/01/01 05:22:55 INFO xorp_fea MFEA ] CLI started
> [ 1970/01/01 05:22:56  WARNING xorp_rtrmgr:720 XrlFinderTarget +437
> ../xrl/targets/finder_base.cc handle_finder_0_2_resolve_xrl ] Handling
> method for finder/0.2/resolve_xrl failed: XrlCmdError 102 Command failed
> Xrl target is not enabled.
> [ 1970/01/01 05:22:57 INFO pica_cardmgr XifFinderEventNotifier ]
> Registered {state,client} = {CARD_REMOVED_STATE,
> sif-d1fe8452916e5bc4c817cd317a516074 at 10.107.48.61}
> [ 1970/01/01 05:22:57 INFO pica_cardmgr XifFinderEventNotifier ]
> Registered {state,client} = {CARD_MISCONFIGURED_STATE,
> sif-d1fe8452916e5bc4c817cd317a516074 at 10.107.48.61}
> [ 1970/01/01 05:22:57 INFO pica_cardmgr XifFinderEventNotifier ]
> Registered {state,client} = {CARD_INITIALIZED_STATE,
> sif-d1fe8452916e5bc4c817cd317a516074 at 10.107.48.61}
> [ 1970/01/01 05:22:57 INFO pica_cardmgr XifFinderEventNotifier ]
> Registered {state,client} = {CARD_PHASE_1_DONE_STATE,
> sif-d1fe8452916e5bc4c817cd317a516074 at 10.107.48.61}
> [ 1970/01/01 05:22:57 INFO pica_cardmgr XifFinderEventNotifier ]
> Registered {state,client} = {CARD_PHASE_2_DONE_STATE,
> sif-d1fe8452916e5bc4c817cd317a516074 at 10.107.48.61}
> [ 1970/01/01 05:22:57 INFO pica_cardmgr XifFinderEventNotifier ]
> Registered {state,client} = {CARD_PHASE_3_DONE_STATE,
> sif-d1fe8452916e5bc4c817cd317a516074 at 10.107.48.61}
> [ 1970/01/01 05:22:57 INFO pica_cardmgr XifFinderEventNotifier ]
> Registered {state,client} = {CARD_RUNNING_STATE,
> sif-d1fe8452916e5bc4c817cd317a516074 at 10.107.48.61}
> [ 1970/01/01 05:22:57 INFO pica_cardmgr XifFinderEventNotifier ]
> Registered {state,client} = {CARD_DEAD_STATE,
> sif-d1fe8452916e5bc4c817cd317a516074 at 10.107.48.61}
> [ 1970/01/01 05:22:57 INFO pica_cardmgr XifFinderEventNotifier ]
> Succeeding in dispatching card state(CARD_REMOVED_STATE) to
> sif-d1fe8452916e5bc4c817cd317a516074 at 10.107.48.61
> [ 1970/01/01 05:22:58  ERROR xorp_rtrmgr:720 RTRMGR +925
> master_conf_tree.cc commit_pass2_done ] Commit failed: 102 Command failed
> invalid ifname:ge-1/1/25
> [ 1970/01/01 05:22:58  ERROR xorp_rtrmgr:720 RTRMGR +389
> master_conf_tree.cc config_done ] Configuration failed: 102 Command failed
> invalid ifname:ge-1/1/25
> [ 1970/01/01 05:22:58  INFO xorp_rtrmgr:720 RTRMGR +2239 task.cc run_task
> ] No more tasks to run
>
> ========================================================================================================
>
> Can anyone help to figure this out?
> Your help will be greatly appreciated, thanks.
>
>
>
> On 12 April 2012 00:19, Troy Benjegerdes <hozer at hozed.org> wrote:
>
>> Is this the board you have, or did you do a custom board?
>>
>> http://www.atmel.com/tools/SAM9G20-EK.aspx
>>
>> If you've got USB-host, (or SDcard) you should be able to put
>> a debian-arm chroot on a usb driver/sdcard. This is how I'm
>> running debian (and self-hosted compiling xorp) on a Asus
>> transformer android tablet.
>>
>> On Wed, Apr 11, 2012 at 10:28:07PM +0000, MAS . wrote:
>> > We have AT91SAM9G20EK ( Maxim ARM9). SMI Driver is working fine. Also I
>> > have marvell SDK for switch and its too working fine.
>> > I think there is NO way to install debian-arm, I'll look into it.
>> >
>> > On 11 April 2012 22:18, Troy Benjegerdes <hozer at hozed.org> wrote:
>> >
>> > > What cpu are you using to talk to the marvell chip? I assume
>> > > you have an SMI (serial managment interface) port and driver
>> > > on your embedded ARM cpu..
>> > >
>> > > Would you have a way to install and boot a debian-arm image?
>> > >
>> > > On Wed, Apr 11, 2012 at 10:11:48PM +0000, MAS . wrote:
>> > > > Hi
>> > > > Thanks for the reply Troy,
>> > > >
>> > > > I am student and we have designed ARM board with marvell switch chip
>> > > > 88E6065 in our lab. Actually I want to manage L2 functionality of
>> switch
>> > > > chip using XorPlus, which is another derivative  of XORP with L2
>> > > > functionality.
>> > > >
>> > > > Board has Linux-2.6.30 kernel version running on it and
>> Uboot-1.3.4.. we
>> > > > also have gcc, gdb nothing more. I cross-compiled Xorplus and put
>> it on
>> > > the
>> > > > board but its literally doing nothing, no logs, no error messages.
>> Same
>> > > > XorPlus is running fine on x86 machine.
>> > > >
>> > > > For trial purpose I executed xorp_rtrmgr on x86 and board without
>> any
>> > > > configuration. On x86 machine atleast its printing error messages
>> but on
>> > > > board its doing nothing? I thought may be xorp needed some packages
>> other
>> > > > than xorp libreary.
>> > > >
>> > > > thanks and regards,
>> > > > MAS.
>> > > >
>> > > > On 11 April 2012 21:52, Troy Benjegerdes <hozer at hozed.org> wrote:
>> > > >
>> > > > > This would probably depend on what embedded linux distribution the
>> > > > > board is running and what board it is, and how you cross-compiled
>> > > > > the package.
>> > > > >
>> > > > > If you can give us more details, we might be able to help.
>> > > > >
>> > > > > I'm going to attempt to build it on my debian-arm install,
>> > > > > and see what happens.
>> > > > >
>> > > > > If you have some constraints (or ndas) so you can't provide more
>> > > > > details about what board and distro, there are probably several
>> > > > > of us (including myself) that would be happy to do a consulting
>> > > > > contract to help you out as well.
>> > > > >
>> > > > > On Wed, Apr 11, 2012 at 09:28:26PM +0000, MAS . wrote:
>> > > > > > Hi all,
>> > > > > >
>> > > > > > I have compiled XORP and installed on x86 machine then its
>> working
>> > > fine.
>> > > > > > But I need to put it on embedded board with ARM processor so I
>> > > > > > cross-compiled it and put it on the board.
>> > > > > >
>> > > > > > Now problem is that its not working fine, even its not printing
>> any
>> > > error
>> > > > > > messages on terminal. I don't know what is wrong. Can anyone
>> help
>> > > me. Is
>> > > > > > there any software package requirements i.e. do I need to
>> install
>> > > > > > any softwares on board in order to XORP to work? Basically my
>> board
>> > > only
>> > > > > > has Linux running on it without any spacial packages.
>> > > > > >
>> > > > > >
>> > > > > > Thanks and regards,
>> > > > > > MAS
>> > > > >
>> > > > >
>> > >
>> > > --
>> > >
>> > >
>> ----------------------------------------------------------------------------
>> > > Troy Benjegerdes                 'da hozer'
>> hozer at hozed.org
>> > > 7 elements Farm                                         TerraCarbo
>> biofuels
>> > >
>> > > An Engineer is a man who can do for a dime what any fool can do for a
>> > > dollar.
>> > > -anonymous
>> > >
>> > > If you're going through hell, keep going. ~ Winston Churchill
>> > >
>> > > The challenge in changing the world is not in having great ideas,
>> it's in
>> > > having stupid simple ideas, as those are the ones that cause change.
>> > >
>> > >
>> >
>> >
>> > --
>> > Thanks and Regards,
>> > MAS.
>>
>> > _______________________________________________
>> > Xorp-users mailing list
>> > Xorp-users at xorp.org
>> > http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users
>>
>>
>> --
>>
>> ----------------------------------------------------------------------------
>> Troy Benjegerdes                 'da hozer'
>> hozer at hozed.org
>> 7 elements Farm                                         TerraCarbo
>> biofuels
>>
>> An Engineer is a man who can do for a dime what any fool can do for a
>> dollar.
>> -anonymous
>>
>> If you're going through hell, keep going. ~ Winston Churchill
>>
>> The challenge in changing the world is not in having great ideas, it's in
>> having stupid simple ideas, as those are the ones that cause change.
>>
>>
>
>
> --
> Thanks and Regards,
> MAS.
>
>


-- 
Thanks and Regards,
MAS.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20120417/153a7043/attachment.html 

From danro at kth.se  Mon Apr 23 04:50:40 2012
From: danro at kth.se (Dan Rosenqvist)
Date: Mon, 23 Apr 2012 11:50:40 +0000
Subject: [Xorp-users] XORP IPv4 multicast routing with PIM-SM
Message-ID: <54DD4F682C240845BF5F7D0EECBDB6F208393673@EXDB3.ug.kth.se>

Hi,

I'm having problems configuring multicast routing for a small test network. The
network consist of four virtual Ubuntu (10.04) machines in the following setup:

Host1 <--> Router1 <--> Router2 <--> Host2

Router1 and Router2 is running XORP with the configurations displayed at the end
of this message. Host1 has an interface eth1 configured with the ipaddr
10.10.12.1 and Host2 has an interface eth3 configured with the ipaddr
10.10.45.5. Their default routes are 10.10.12.2 and 10.10.45.4 respectively. No
other interfaces are configured on the hosts.

The problem occurs when I try to use ssmping to test the multicast routing.
If I set up ssmpingd on Host2 and use "ssmping -4 -I eth1 10.10.45.5" from Host1
I get the correct response, but if I set up the ssmpingd on Host1 and run
"ssmping -4 -I eth3 10.10.12.1" from Host2, interesting things start happening.

I get massive amounts of multicast packet duplicates. My guess is that this has
something to do with the RP configuration, but I'm not sure. In this case the RP
is selected as Router1s interface towards Router2. If the RP is set to the
ipaddr of Router2s interface towards Router1, I get the opposite response
compared to the description above.

Can anyone please tell me what I'm doing wrong?

Regards,
Dan

--- R1 configuration start ---

interfaces {
    interface "eth2" {
        vif "eth2" {
            address 10.10.12.2 {
                prefix-length: 24
            }
        }
    }
    interface "eth3" {
        vif "eth3" {
            address 10.10.23.2 {
                prefix-length: 24
            }
        }
    }
}

fea {
    unicast-forwarding4 {
        disable: false
    }
}

plumbing {
    mfea4 {
        disable: false
        interface "eth2" {
            vif "eth2" {
                disable: false
            }
        }
        interface "eth3" {
            vif "eth3" {
                disable: false
            }
        }
        interface register_vif {
            vif register_vif {
                disable: false
            }
        }
    }
}

protocols {
    ospf4 {
        router-id: 2.2.2.2
        area 0.0.0.0 {
            interface "eth2" {
                vif "eth2" {
                    address 10.10.12.2 {
                        interface-cost: 1
                    }
                }
            }
            interface "eth3" {
                vif "eth3" {
                    address 10.10.23.2 {
                        interface-cost: 1
                    }
                }
            }
        }
    }

    fib2mrib {
        disable: false
    }

    igmp {
        disable: false
        interface "eth2" {
            vif "eth2" {
                disable: false
            }
        }
        interface "eth3" {
            vif "eth3" {
                disable: false
            }
        }
    }

    pimsm4 {
        disable: false
        interface "eth2" {
            vif "eth2" {
                disable: false
            }
        }
        interface "eth3" {
            vif "eth3" {
                disable: false
            }
        }
        interface register_vif {
            vif register_vif {
                disable: false
            }
        }
        static-rps {
            rp 10.10.23.2 {
                group-prefix 224.0.0.0/4 {
                }
            }
        }
    }
}

--- R1 configuration end ---

--- R2 configuration start ---
interfaces {
    interface "eth2" {
        vif "eth2" {
            address 10.10.23.3 {
                prefix-length: 24
            }
        }
    }
    interface "eth3" {
        vif "eth3" {
            address 10.10.45.4 {
                prefix-length: 24
            }
        }
    }
}

fea {
    unicast-forwarding4 {
        disable: false
    }
}

plumbing {
    mfea4 {
        disable: false
        interface "eth2" {
            vif "eth2" {
                disable: false
            }
        }
        interface "eth3" {
            vif "eth3" {
                disable: false
            }
        }
        interface register_vif {
            vif register_vif {
                disable: false
            }
        }
    }
}

protocols {
    ospf4 {
        router-id: 4.4.4.4
        area 0.0.0.0 {
            interface "eth2" {
                vif "eth2" {
                    address 10.10.23.3 {
                        interface-cost: 1
                    }
                }
            }
            interface "eth3" {
                vif "eth3" {
                    address 10.10.45.4 {
                        interface-cost: 1
                    }
                }
            }
        }
    }

    fib2mrib {
        disable: false
    }

    igmp {
        disable: false
        interface "eth2" {
            vif "eth2" {
                disable: false
            }
        }
        interface "eth3" {
            vif "eth3" {
                disable: false
            }
        }
    }

    pimsm4 {
        disable: false
        interface "eth2" {
            vif "eth2" {
                disable: false
            }
        }
        interface "eth3" {
            vif "eth3" {
                disable: false
            }
        }
        interface register_vif {
            vif register_vif {
                disable: false
            }
        }
        static-rps {
            rp 10.10.23.2 {
                group-prefix 224.0.0.0/4 {
                }
            }
        }
    }
}

--- R2 configuration end ---
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20120423/ac60d0e1/attachment.html 

From jobhunts02 at aol.com  Tue Apr 24 23:57:43 2012
From: jobhunts02 at aol.com (jobhunts02 at aol.com)
Date: Wed, 25 Apr 2012 02:57:43 -0400 (EDT)
Subject: [Xorp-users] (no subject)
Message-ID: <8CEF0C7D909C916-4F8-2A0EF@webmail-d146.sysops.aol.com>

http://www.krshna.me/wp-content/themes/TheStyle/mooney10000.html


From esj at cs.fiu.edu  Fri Apr 27 15:42:12 2012
From: esj at cs.fiu.edu (Eric S. Johnson)
Date: Fri, 27 Apr 2012 18:42:12 -0400
Subject: [Xorp-users] ospfv3 for IPv6 ospf - oddity
Message-ID: <20120427224212.6432F3680006@cheetah.cs.fiu.edu>


I started playing vith ospf for v6 recently. I have noticed
an oddity. I am curious if I have something miss-configured 
or I have found a bug.

OSPFv3 for ipv6 has a couple new link-state adv types. 
The one I am running into interoperability issues with is 
the Intra-area prefix type. 

It appears that xorp is sending these out with a cost of zero.
No matter what the config file cost setting is. 

This causes all the other ospf3 impelmentations it talks to
(well, ok, cisco IOS and quagga are the only ones I have tested)
to count the cost to that network as zero. 

xorp sends the ole fashioned router lsa's with the appropriate costs. 
But not the new fangled intra-area prefix costs.

xorp also seems to send a /128 IA prefix LSA with the address of 
the interface also with metric of 0. This doesn't impact things
as much as the network prefixs being 0, but seems odd too.

I have verified with wireshark that it is sending the IA prefix lsa's
with cost 0.

Below are relavant snips of my configs.

Xorp showing this behavior is 1.8.5 and git pulled on 2012-04-19
Running on centos 5.6 (RHEL 5). 
Linux test-router 2.6.18-164.6.1.el5 #1 SMP Tue Nov 3 16:18:27 EST 2009 i686 i686 i386 GNU/Linux

Am I missing something? Or is this a bug?

E

--
    ospf6 0 {
        ip-router-alert: false
        area 0.0.0.1 {
            area-type: "normal" 
            interface "eth0.16" {
                link-type: "broadcast"
                vif "eth0.16" {
                    priority: 128
                    hello-interval: 10
                    router-dead-interval: 40
                    interface-cost: 70
                    retransmit-interval: 5
                    transit-delay: 1
                    passive: false
                    disable: false
                }
            }
            interface "eth0.2128" {
                link-type: "broadcast"
                vif "eth0.2128" {
                    priority: 128
                    hello-interval: 10
                    router-dead-interval: 40
                    interface-cost: 70
                    retransmit-interval: 5
                    transit-delay: 1
                    passive: false
                    disable: false
                }
            }
        }
    }


    interface "eth0.16" {
        description: ""
        disable: false
        discard: false
        unreachable: false
        management: false
        vif "eth0.16" {
            disable: false
            address fe80::206:5bff:fe88:84c6 {
                prefix-length: 64
                disable: false
            }
            address 2001:468:701:4000::5 {
                prefix-length: 64
                disable: false
            }
        }
    }

    interface "eth0.2128" {
        description: ""
        disable: false
        discard: false
        unreachable: false
        management: false
        vif "eth0.2128" {
            disable: false
            address fe80::206:5bff:fe88:84c6 {
                prefix-length: 64
                disable: false
            }
            address 2001:468:701:4001:206:5bff:fe88:84c6 {
                prefix-length: 64
                disable: false
            }
        }
    }