From jcoco at meccorp.mec.edu  Tue Mar  1 06:31:42 2011
From: jcoco at meccorp.mec.edu (Joe Coco)
Date: Tue, 1 Mar 2011 09:31:42 -0500
Subject: [Xorp-users] RFC:  New VLAN api for xorp.ct
In-Reply-To: <4D6C8D74.9090602@candelatech.com>
References: <4D6C8D74.9090602@candelatech.com>
Message-ID: <65A6944974518C4B9C0E818727B559E9397F8DF4@mecexchange2007.meccorp.mec.edu>

Hi Ben,


Should have a good test case by the end of the day. Thank you for taking the time to do this.

-- Joe

-----Original Message-----
From: xorp-users-bounces at xorp.org [mailto:xorp-users-bounces at xorp.org] On Behalf Of Ben Greear
Sent: Tuesday, March 01, 2011 1:09 AM
To: xorp-users at xorp.org; xorp
Subject: [Xorp-users] RFC: New VLAN api for xorp.ct

Here is a patch I cooked up to deal with automatically
creating/deleting VLANs, while treating them as real
interfaces.

This is totally un-tested (it does compile on Linux, at least).

Comments welcome.  I hope to test it in the next few days.

http://www.candelatech.com/~greearb/0001-vlans-Treat-vlans-as-primary-interfaces.patch

Thanks,
Ben

-- 
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 B32946 at freescale.com  Tue Mar  1 08:53:16 2011
From: B32946 at freescale.com (Vunnava Kesava Srinivas-B32946)
Date: Tue, 1 Mar 2011 16:53:16 +0000
Subject: [Xorp-users] Help Needed in PIM-Join Messages !!
In-Reply-To: <C025046A77B3034399C773D87A765D2E1B13BDCC@LRCCD-MBX01.LRCCD.ad.losrios.edu>
References: <9D8289DE2B23FA4EBC165B4CFB3718660B3586@039-SN1MPN1-004.039d.mgd.msft.net>,
	<C025046A77B3034399C773D87A765D2E1B13BDCC@LRCCD-MBX01.LRCCD.ad.losrios.edu>
Message-ID: <9D8289DE2B23FA4EBC165B4CFB3718660B367C@039-SN1MPN1-004.039d.mgd.msft.net>

Thanks Mark for throwing some light on the dark path.I have uncommented the fib2mrib Configuration part  &  also I have used Bootstrap Mechanism to learn the RP. I can see that DSR is learning RP through Bootstrap [<show pim rps>]. Even MRIB [<show pim mrib>] is also populated with the Path to the RP. But still ; I am unable to see PIM-JOIN Messages getting generated .

Some other Observations are ; I can see that Multicast Listener-group was registered in the DSR [<show igmp group>]when the listener sends the IGMPv2 Message. So; there is NO PROBLEM between the Listener & DSR. As per the protocol specification ; once DSR learns the Group it needs to create (*,G) state and should send the (*,G) JOIN to RP.But that's Not Happening.Is there any provision in DSR to see whether it is creating (*,G) state??  Also I have enabled only PIM-SM Communication between the RP & DSR. I  have totally disabled the IGMP between RP & DSR. When I look at the mfea dataflow [<show mfea dataflow>]., it is empty. I am suspecting if every thing went fine; this data-flow should have got some entries!!!

Any way ; would request you to suggest me Next step to move on this further.

-Thanks in advance,
VKS.

________________________________
From: Williams, Mark [william at losrios.edu]
Sent: 28 February 2011 21:53:21
To: Vunnava Kesava Srinivas-B32946; xorp-users at xorp.org
Subject: RE: Help Needed in PIM-Join Messages !!

You need to uncomment the section on fib2mrib in the configuration on your DSR. PIM routers need to use the unicast forwarding table to be able to find the reverse path back to the RP.

If you configure the RP router as a BSR and candidate RP, then let the DSR learn the RP information using bootstrap; don?t configure it statically.

-Mark Williams

From: xorp-users-bounces at xorp.org [mailto:xorp-users-bounces at xorp.org] On Behalf Of Vunnava Kesava Srinivas-B32946
Sent: Monday, February 28, 2011 08:10
To: xorp-users at xorp.org
Subject: [Xorp-users] Help Needed in PIM-Join Messages !!

Hi Guys,
I have a requirement to bring up Multicast Routing [IPv4 Network] with pimsm4. The Topology that I am trying to configure is ;
"Multicast Sender <--------->RP<------------->DSR<-------------->Multicast Listener". I have connected everything Point- Point. So., No need to worry about routes.

I am seeing that Listener is sending IGMPv3 Join reports to the DSR. But even though pim-sm is running on DSR; it is NOT sending PIM-Join Messages to the RP. I have configured staticrp in the DSR & and the connectivity between the RP & DSP is Fine. I have attached the configuration file of both the RP & DSR. Please let me know what configuration am I missing !!!

Few Doubts:
1] Also another question is., If I am enabling IGMP on both the interfaces of DSR & RP will that matter & effect PIM Routing ??
2] How Plumbing effects Multicast Routing.


-Thanks in Advance,
VKS.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20110301/d32ab844/attachment.html 

From william at losrios.edu  Tue Mar  1 08:59:20 2011
From: william at losrios.edu (Williams, Mark)
Date: Tue, 1 Mar 2011 16:59:20 +0000
Subject: [Xorp-users] Help Needed in PIM-Join Messages !!
In-Reply-To: <9D8289DE2B23FA4EBC165B4CFB3718660B367C@039-SN1MPN1-004.039d.mgd.msft.net>
References: <9D8289DE2B23FA4EBC165B4CFB3718660B3586@039-SN1MPN1-004.039d.mgd.msft.net>,
	<C025046A77B3034399C773D87A765D2E1B13BDCC@LRCCD-MBX01.LRCCD.ad.losrios.edu>
	<9D8289DE2B23FA4EBC165B4CFB3718660B367C@039-SN1MPN1-004.039d.mgd.msft.net>
Message-ID: <C025046A77B3034399C773D87A765D2E1B13C086@LRCCD-MBX01.LRCCD.ad.losrios.edu>

When a PIM router receives an IGMP join request on and interface that is a DR, the next step is for it to send the PIM join to the RP. Make sure your DSR router knows how to get to the RP. I noticed that each of the routers has two interfaces. If the RP IP address is not on the interface on the shared link between the DSR and the RP, the DSR won't know how to get there because you are not running a unicast routing protocol.

Next step: add static routes, or configure OSPF, so that both routers know how to reach all 3 subnets.

-Mark Williams

From: Vunnava Kesava Srinivas-B32946 [mailto:B32946 at freescale.com]
Sent: Tuesday, March 01, 2011 08:53
To: Williams, Mark; xorp-users at xorp.org
Subject: RE: Help Needed in PIM-Join Messages !!

Thanks Mark for throwing some light on the dark path.I have uncommented the fib2mrib Configuration part  &  also I have used Bootstrap Mechanism to learn the RP. I can see that DSR is learning RP through Bootstrap [<show pim rps>]. Even MRIB [<show pim mrib>] is also populated with the Path to the RP. But still ; I am unable to see PIM-JOIN Messages getting generated .

Some other Observations are ; I can see that Multicast Listener-group was registered in the DSR [<show igmp group>]when the listener sends the IGMPv2 Message. So; there is NO PROBLEM between the Listener & DSR. As per the protocol specification ; once DSR learns the Group it needs to create (*,G) state and should send the (*,G) JOIN to RP.But that's Not Happening.Is there any provision in DSR to see whether it is creating (*,G) state??  Also I have enabled only PIM-SM Communication between the RP & DSR. I  have totally disabled the IGMP between RP & DSR. When I look at the mfea dataflow [<show mfea dataflow>]., it is empty. I am suspecting if every thing went fine; this data-flow should have got some entries!!!

Any way ; would request you to suggest me Next step to move on this further.

-Thanks in advance,
VKS.
________________________________
From: Williams, Mark [william at losrios.edu]
Sent: 28 February 2011 21:53:21
To: Vunnava Kesava Srinivas-B32946; xorp-users at xorp.org
Subject: RE: Help Needed in PIM-Join Messages !!
You need to uncomment the section on fib2mrib in the configuration on your DSR. PIM routers need to use the unicast forwarding table to be able to find the reverse path back to the RP.

If you configure the RP router as a BSR and candidate RP, then let the DSR learn the RP information using bootstrap; don't configure it statically.

-Mark Williams

From: xorp-users-bounces at xorp.org [mailto:xorp-users-bounces at xorp.org] On Behalf Of Vunnava Kesava Srinivas-B32946
Sent: Monday, February 28, 2011 08:10
To: xorp-users at xorp.org
Subject: [Xorp-users] Help Needed in PIM-Join Messages !!

Hi Guys,
I have a requirement to bring up Multicast Routing [IPv4 Network] with pimsm4. The Topology that I am trying to configure is ;
"Multicast Sender <--------->RP<------------->DSR<-------------->Multicast Listener". I have connected everything Point- Point. So., No need to worry about routes.

I am seeing that Listener is sending IGMPv3 Join reports to the DSR. But even though pim-sm is running on DSR; it is NOT sending PIM-Join Messages to the RP. I have configured staticrp in the DSR & and the connectivity between the RP & DSP is Fine. I have attached the configuration file of both the RP & DSR. Please let me know what configuration am I missing !!!

Few Doubts:
1] Also another question is., If I am enabling IGMP on both the interfaces of DSR & RP will that matter & effect PIM Routing ??
2] How Plumbing effects Multicast Routing.


-Thanks in Advance,
VKS.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20110301/af63f23d/attachment-0001.html 

From B32946 at freescale.com  Tue Mar  1 09:22:16 2011
From: B32946 at freescale.com (Vunnava Kesava Srinivas-B32946)
Date: Tue, 1 Mar 2011 17:22:16 +0000
Subject: [Xorp-users] Help Needed in PIM-Join Messages !!
In-Reply-To: <C025046A77B3034399C773D87A765D2E1B13C086@LRCCD-MBX01.LRCCD.ad.losrios.edu>
References: <9D8289DE2B23FA4EBC165B4CFB3718660B3586@039-SN1MPN1-004.039d.mgd.msft.net>,
	<C025046A77B3034399C773D87A765D2E1B13BDCC@LRCCD-MBX01.LRCCD.ad.losrios.edu>
	<9D8289DE2B23FA4EBC165B4CFB3718660B367C@039-SN1MPN1-004.039d.mgd.msft.net>,
	<C025046A77B3034399C773D87A765D2E1B13C086@LRCCD-MBX01.LRCCD.ad.losrios.edu>
Message-ID: <9D8289DE2B23FA4EBC165B4CFB3718660B36BA@039-SN1MPN1-004.039d.mgd.msft.net>

Ok. As I mentioned before ., RP is DIRECTLY CONNECTED to DSR (RP[10.10.10.2/24]<------------->DSR[10.10.10.1/24]). They are Back-Back connected & both are able to ping each other happily.In this scenario ; I believe there is NO Need of any unicast routing Protocol.More over if mrib is already populated with the route to RP;I guess we crossed Routing part.Becoz as per my knowledge ; unicast routing protocols are JUST Needed to populate mrib & in our case it is already done.But one thing to mention is., mfc [Multicast Forwarding cache] is empty. Is that also needed to be populated for "PIM-SM Join Messages" Generation ??

But let us say ; even if there is NO Route to RP ., will that effect generating PIM-SM Join packets ?? I think at-least should see PIM-SM JOIN packets on interface of DSR..rt ? Will some other stuff like Plumbing play some role here ??? Just a suspection........

Please bear with my questions ... ;-)

-VKS.
________________________________
From: Williams, Mark [william at losrios.edu]
Sent: 01 March 2011 22:29:20
To: Vunnava Kesava Srinivas-B32946; xorp-users at xorp.org
Subject: RE: Help Needed in PIM-Join Messages !!

When a PIM router receives an IGMP join request on and interface that is a DR, the next step is for it to send the PIM join to the RP. Make sure your DSR router knows how to get to the RP. I noticed that each of the routers has two interfaces. If the RP IP address is not on the interface on the shared link between the DSR and the RP, the DSR won?t know how to get there because you are not running a unicast routing protocol.

Next step: add static routes, or configure OSPF, so that both routers know how to reach all 3 subnets.

-Mark Williams

From: Vunnava Kesava Srinivas-B32946 [mailto:B32946 at freescale.com]
Sent: Tuesday, March 01, 2011 08:53
To: Williams, Mark; xorp-users at xorp.org
Subject: RE: Help Needed in PIM-Join Messages !!

Thanks Mark for throwing some light on the dark path.I have uncommented the fib2mrib Configuration part  &  also I have used Bootstrap Mechanism to learn the RP. I can see that DSR is learning RP through Bootstrap [<show pim rps>]. Even MRIB [<show pim mrib>] is also populated with the Path to the RP. But still ; I am unable to see PIM-JOIN Messages getting generated .

Some other Observations are ; I can see that Multicast Listener-group was registered in the DSR [<show igmp group>]when the listener sends the IGMPv2 Message. So; there is NO PROBLEM between the Listener & DSR. As per the protocol specification ; once DSR learns the Group it needs to create (*,G) state and should send the (*,G) JOIN to RP.But that's Not Happening.Is there any provision in DSR to see whether it is creating (*,G) state??  Also I have enabled only PIM-SM Communication between the RP & DSR. I  have totally disabled the IGMP between RP & DSR. When I look at the mfea dataflow [<show mfea dataflow>]., it is empty. I am suspecting if every thing went fine; this data-flow should have got some entries!!!

Any way ; would request you to suggest me Next step to move on this further.

-Thanks in advance,
VKS.
________________________________
From: Williams, Mark [william at losrios.edu]
Sent: 28 February 2011 21:53:21
To: Vunnava Kesava Srinivas-B32946; xorp-users at xorp.org
Subject: RE: Help Needed in PIM-Join Messages !!
You need to uncomment the section on fib2mrib in the configuration on your DSR. PIM routers need to use the unicast forwarding table to be able to find the reverse path back to the RP.

If you configure the RP router as a BSR and candidate RP, then let the DSR learn the RP information using bootstrap; don?t configure it statically.

-Mark Williams

From: xorp-users-bounces at xorp.org [mailto:xorp-users-bounces at xorp.org] On Behalf Of Vunnava Kesava Srinivas-B32946
Sent: Monday, February 28, 2011 08:10
To: xorp-users at xorp.org
Subject: [Xorp-users] Help Needed in PIM-Join Messages !!

Hi Guys,
I have a requirement to bring up Multicast Routing [IPv4 Network] with pimsm4. The Topology that I am trying to configure is ;
"Multicast Sender <--------->RP<------------->DSR<-------------->Multicast Listener". I have connected everything Point- Point. So., No need to worry about routes.

I am seeing that Listener is sending IGMPv3 Join reports to the DSR. But even though pim-sm is running on DSR; it is NOT sending PIM-Join Messages to the RP. I have configured staticrp in the DSR & and the connectivity between the RP & DSP is Fine. I have attached the configuration file of both the RP & DSR. Please let me know what configuration am I missing !!!

Few Doubts:
1] Also another question is., If I am enabling IGMP on both the interfaces of DSR & RP will that matter & effect PIM Routing ??
2] How Plumbing effects Multicast Routing.


-Thanks in Advance,
VKS.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20110301/9fcee618/attachment.html 

From william at losrios.edu  Tue Mar  1 11:01:58 2011
From: william at losrios.edu (Williams, Mark)
Date: Tue, 1 Mar 2011 19:01:58 +0000
Subject: [Xorp-users] Help Needed in PIM-Join Messages !!
In-Reply-To: <9D8289DE2B23FA4EBC165B4CFB3718660B36BA@039-SN1MPN1-004.039d.mgd.msft.net>
References: <9D8289DE2B23FA4EBC165B4CFB3718660B3586@039-SN1MPN1-004.039d.mgd.msft.net>,
	<C025046A77B3034399C773D87A765D2E1B13BDCC@LRCCD-MBX01.LRCCD.ad.losrios.edu>
	<9D8289DE2B23FA4EBC165B4CFB3718660B367C@039-SN1MPN1-004.039d.mgd.msft.net>,
	<C025046A77B3034399C773D87A765D2E1B13C086@LRCCD-MBX01.LRCCD.ad.losrios.edu>
	<9D8289DE2B23FA4EBC165B4CFB3718660B36BA@039-SN1MPN1-004.039d.mgd.msft.net>
Message-ID: <C025046A77B3034399C773D87A765D2E1B13C12D@LRCCD-MBX01.LRCCD.ad.losrios.edu>

How about running xorp_rtrmgr interactively (without -d option), then watch the output after the client sends an IGMP join? You should see something there about why it can't send a PIM join upstream.

-Mark Williams

From: Vunnava Kesava Srinivas-B32946 [mailto:B32946 at freescale.com]
Sent: Tuesday, March 01, 2011 09:22
To: Williams, Mark; xorp-users at xorp.org
Subject: RE: Help Needed in PIM-Join Messages !!

Ok. As I mentioned before ., RP is DIRECTLY CONNECTED to DSR (RP[10.10.10.2/24]<------------->DSR[10.10.10.1/24]). They are Back-Back connected & both are able to ping each other happily.In this scenario ; I believe there is NO Need of any unicast routing Protocol.More over if mrib is already populated with the route to RP;I guess we crossed Routing part.Becoz as per my knowledge ; unicast routing protocols are JUST Needed to populate mrib & in our case it is already done.But one thing to mention is., mfc [Multicast Forwarding cache] is empty. Is that also needed to be populated for "PIM-SM Join Messages" Generation ??

But let us say ; even if there is NO Route to RP ., will that effect generating PIM-SM Join packets ?? I think at-least should see PIM-SM JOIN packets on interface of DSR..rt ? Will some other stuff like Plumbing play some role here ??? Just a suspection........

Please bear with my questions ... ;-)

-VKS.
________________________________
From: Williams, Mark [william at losrios.edu]
Sent: 01 March 2011 22:29:20
To: Vunnava Kesava Srinivas-B32946; xorp-users at xorp.org
Subject: RE: Help Needed in PIM-Join Messages !!
When a PIM router receives an IGMP join request on and interface that is a DR, the next step is for it to send the PIM join to the RP. Make sure your DSR router knows how to get to the RP. I noticed that each of the routers has two interfaces. If the RP IP address is not on the interface on the shared link between the DSR and the RP, the DSR won't know how to get there because you are not running a unicast routing protocol.

Next step: add static routes, or configure OSPF, so that both routers know how to reach all 3 subnets.

-Mark Williams

From: Vunnava Kesava Srinivas-B32946 [mailto:B32946 at freescale.com]
Sent: Tuesday, March 01, 2011 08:53
To: Williams, Mark; xorp-users at xorp.org
Subject: RE: Help Needed in PIM-Join Messages !!

Thanks Mark for throwing some light on the dark path.I have uncommented the fib2mrib Configuration part  &  also I have used Bootstrap Mechanism to learn the RP. I can see that DSR is learning RP through Bootstrap [<show pim rps>]. Even MRIB [<show pim mrib>] is also populated with the Path to the RP. But still ; I am unable to see PIM-JOIN Messages getting generated .

Some other Observations are ; I can see that Multicast Listener-group was registered in the DSR [<show igmp group>]when the listener sends the IGMPv2 Message. So; there is NO PROBLEM between the Listener & DSR. As per the protocol specification ; once DSR learns the Group it needs to create (*,G) state and should send the (*,G) JOIN to RP.But that's Not Happening.Is there any provision in DSR to see whether it is creating (*,G) state??  Also I have enabled only PIM-SM Communication between the RP & DSR. I  have totally disabled the IGMP between RP & DSR. When I look at the mfea dataflow [<show mfea dataflow>]., it is empty. I am suspecting if every thing went fine; this data-flow should have got some entries!!!

Any way ; would request you to suggest me Next step to move on this further.

-Thanks in advance,
VKS.
________________________________
From: Williams, Mark [william at losrios.edu]
Sent: 28 February 2011 21:53:21
To: Vunnava Kesava Srinivas-B32946; xorp-users at xorp.org
Subject: RE: Help Needed in PIM-Join Messages !!
You need to uncomment the section on fib2mrib in the configuration on your DSR. PIM routers need to use the unicast forwarding table to be able to find the reverse path back to the RP.

If you configure the RP router as a BSR and candidate RP, then let the DSR learn the RP information using bootstrap; don't configure it statically.

-Mark Williams

From: xorp-users-bounces at xorp.org [mailto:xorp-users-bounces at xorp.org] On Behalf Of Vunnava Kesava Srinivas-B32946
Sent: Monday, February 28, 2011 08:10
To: xorp-users at xorp.org
Subject: [Xorp-users] Help Needed in PIM-Join Messages !!

Hi Guys,
I have a requirement to bring up Multicast Routing [IPv4 Network] with pimsm4. The Topology that I am trying to configure is ;
"Multicast Sender <--------->RP<------------->DSR<-------------->Multicast Listener". I have connected everything Point- Point. So., No need to worry about routes.

I am seeing that Listener is sending IGMPv3 Join reports to the DSR. But even though pim-sm is running on DSR; it is NOT sending PIM-Join Messages to the RP. I have configured staticrp in the DSR & and the connectivity between the RP & DSP is Fine. I have attached the configuration file of both the RP & DSR. Please let me know what configuration am I missing !!!

Few Doubts:
1] Also another question is., If I am enabling IGMP on both the interfaces of DSR & RP will that matter & effect PIM Routing ??
2] How Plumbing effects Multicast Routing.


-Thanks in Advance,
VKS.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20110301/d5906bde/attachment-0001.html 

From jcoco at meccorp.mec.edu  Tue Mar  1 11:51:52 2011
From: jcoco at meccorp.mec.edu (Joe Coco)
Date: Tue, 1 Mar 2011 14:51:52 -0500
Subject: [Xorp-users] RFC:  New VLAN api for xorp.ct
In-Reply-To: <4D6C8D74.9090602@candelatech.com>
References: <4D6C8D74.9090602@candelatech.com>
Message-ID: <65A6944974518C4B9C0E818727B559E9397F8E7C@mecexchange2007.meccorp.mec.edu>


Ben,

Maybe it's just me but. Patch applies clean, however I can't get past this step.

For example:

create interfaces interface foo disable false

^^^ works

create interfaces interface foo vlan

^^ says

ERROR: path "interfaces interface foo vlan" is not valid

??

-- Joe


-----Original Message-----
From: xorp-users-bounces at xorp.org [mailto:xorp-users-bounces at xorp.org] On Behalf Of Ben Greear
Sent: Tuesday, March 01, 2011 1:09 AM
To: xorp-users at xorp.org; xorp
Subject: [Xorp-users] RFC: New VLAN api for xorp.ct

Here is a patch I cooked up to deal with automatically
creating/deleting VLANs, while treating them as real
interfaces.

This is totally un-tested (it does compile on Linux, at least).

Comments welcome.  I hope to test it in the next few days.

http://www.candelatech.com/~greearb/0001-vlans-Treat-vlans-as-primary-interfaces.patch

Thanks,
Ben

-- 
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 greearb at candelatech.com  Tue Mar  1 11:45:05 2011
From: greearb at candelatech.com (Ben Greear)
Date: Tue, 01 Mar 2011 11:45:05 -0800
Subject: [Xorp-users] RFC:  New VLAN api for xorp.ct
In-Reply-To: <65A6944974518C4B9C0E818727B559E9397F8E7C@mecexchange2007.meccorp.mec.edu>
References: <4D6C8D74.9090602@candelatech.com>
	<65A6944974518C4B9C0E818727B559E9397F8E7C@mecexchange2007.meccorp.mec.edu>
Message-ID: <4D6D4CC1.2080209@candelatech.com>

On 03/01/2011 11:51 AM, Joe Coco wrote:
>
> Ben,
>
> Maybe it's just me but. Patch applies clean, however I can't get past this step.
>
> For example:
>
> create interfaces interface foo disable false
>
> ^^^ works
>
> create interfaces interface foo vlan
>
> ^^ says
>
> ERROR: path "interfaces interface foo vlan" is not valid
>
> ??

Likely it's broken...I haven't had time to do any testing yet.

Trying to bring up a new web server, migrate a wiki, and
kick a new release out the door in the next few days,
so might be a bit before I can poke at xorp :)

Thanks,
Ben

>
> -- Joe
>
>
> -----Original Message-----
> From: xorp-users-bounces at xorp.org [mailto:xorp-users-bounces at xorp.org] On Behalf Of Ben Greear
> Sent: Tuesday, March 01, 2011 1:09 AM
> To: xorp-users at xorp.org; xorp
> Subject: [Xorp-users] RFC: New VLAN api for xorp.ct
>
> Here is a patch I cooked up to deal with automatically
> creating/deleting VLANs, while treating them as real
> interfaces.
>
> This is totally un-tested (it does compile on Linux, at least).
>
> Comments welcome.  I hope to test it in the next few days.
>
> http://www.candelatech.com/~greearb/0001-vlans-Treat-vlans-as-primary-interfaces.patch
>
> Thanks,
> Ben
>


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


From B32946 at freescale.com  Wed Mar  2 02:37:15 2011
From: B32946 at freescale.com (Vunnava Kesava Srinivas-B32946)
Date: Wed, 2 Mar 2011 10:37:15 +0000
Subject: [Xorp-users] Help Needed in PIM-Join Messages !!
In-Reply-To: <C025046A77B3034399C773D87A765D2E1B13C12D@LRCCD-MBX01.LRCCD.ad.losrios.edu>
References: <9D8289DE2B23FA4EBC165B4CFB3718660B3586@039-SN1MPN1-004.039d.mgd.msft.net>,
	<C025046A77B3034399C773D87A765D2E1B13BDCC@LRCCD-MBX01.LRCCD.ad.losrios.edu>
	<9D8289DE2B23FA4EBC165B4CFB3718660B367C@039-SN1MPN1-004.039d.mgd.msft.net>,
	<C025046A77B3034399C773D87A765D2E1B13C086@LRCCD-MBX01.LRCCD.ad.losrios.edu>
	<9D8289DE2B23FA4EBC165B4CFB3718660B36BA@039-SN1MPN1-004.039d.mgd.msft.net>,
	<C025046A77B3034399C773D87A765D2E1B13C12D@LRCCD-MBX01.LRCCD.ad.losrios.edu>
Message-ID: <9D8289DE2B23FA4EBC165B4CFB3718660B3750@039-SN1MPN1-004.039d.mgd.msft.net>

OK. A Big relief for me.

Now I can see DSR is sending PIMv2 Join/Prune Messages Upstream. I have enabled the PIMSM4 on the interface facing the Multicast listener side & also added a static mrib-route in the configuration file.I believe once the PIM-Join was sent by DSR ; it's primary job is done.

Another question is ; I am seeing PIM-Join Message is a Multicast Message [destined to 224.0.0.13] having the information of PIM specidifc parameters. Important parameters that I see are Up-stream neighbor & groups handled by that DSR. Was the PIM-Join Not a unicast to RP ?

Thanks all,
-VKS.

________________________________
From: Williams, Mark [william at losrios.edu]
Sent: 02 March 2011 00:31:58
To: Vunnava Kesava Srinivas-B32946; xorp-users at xorp.org
Subject: RE: Help Needed in PIM-Join Messages !!

How about running xorp_rtrmgr interactively (without ?d option), then watch the output after the client sends an IGMP join? You should see something there about why it can?t send a PIM join upstream.

-Mark Williams

From: Vunnava Kesava Srinivas-B32946 [mailto:B32946 at freescale.com]
Sent: Tuesday, March 01, 2011 09:22
To: Williams, Mark; xorp-users at xorp.org
Subject: RE: Help Needed in PIM-Join Messages !!

Ok. As I mentioned before ., RP is DIRECTLY CONNECTED to DSR (RP[10.10.10.2/24]<------------->DSR[10.10.10.1/24]). They are Back-Back connected & both are able to ping each other happily.In this scenario ; I believe there is NO Need of any unicast routing Protocol.More over if mrib is already populated with the route to RP;I guess we crossed Routing part.Becoz as per my knowledge ; unicast routing protocols are JUST Needed to populate mrib & in our case it is already done.But one thing to mention is., mfc [Multicast Forwarding cache] is empty. Is that also needed to be populated for "PIM-SM Join Messages" Generation ??

But let us say ; even if there is NO Route to RP ., will that effect generating PIM-SM Join packets ?? I think at-least should see PIM-SM JOIN packets on interface of DSR..rt ? Will some other stuff like Plumbing play some role here ??? Just a suspection........

Please bear with my questions ... ;-)

-VKS.
________________________________
From: Williams, Mark [william at losrios.edu]
Sent: 01 March 2011 22:29:20
To: Vunnava Kesava Srinivas-B32946; xorp-users at xorp.org
Subject: RE: Help Needed in PIM-Join Messages !!
When a PIM router receives an IGMP join request on and interface that is a DR, the next step is for it to send the PIM join to the RP. Make sure your DSR router knows how to get to the RP. I noticed that each of the routers has two interfaces. If the RP IP address is not on the interface on the shared link between the DSR and the RP, the DSR won?t know how to get there because you are not running a unicast routing protocol.

Next step: add static routes, or configure OSPF, so that both routers know how to reach all 3 subnets.

-Mark Williams

From: Vunnava Kesava Srinivas-B32946 [mailto:B32946 at freescale.com]
Sent: Tuesday, March 01, 2011 08:53
To: Williams, Mark; xorp-users at xorp.org
Subject: RE: Help Needed in PIM-Join Messages !!

Thanks Mark for throwing some light on the dark path.I have uncommented the fib2mrib Configuration part  &  also I have used Bootstrap Mechanism to learn the RP. I can see that DSR is learning RP through Bootstrap [<show pim rps>]. Even MRIB [<show pim mrib>] is also populated with the Path to the RP. But still ; I am unable to see PIM-JOIN Messages getting generated .

Some other Observations are ; I can see that Multicast Listener-group was registered in the DSR [<show igmp group>]when the listener sends the IGMPv2 Message. So; there is NO PROBLEM between the Listener & DSR. As per the protocol specification ; once DSR learns the Group it needs to create (*,G) state and should send the (*,G) JOIN to RP.But that's Not Happening.Is there any provision in DSR to see whether it is creating (*,G) state??  Also I have enabled only PIM-SM Communication between the RP & DSR. I  have totally disabled the IGMP between RP & DSR. When I look at the mfea dataflow [<show mfea dataflow>]., it is empty. I am suspecting if every thing went fine; this data-flow should have got some entries!!!

Any way ; would request you to suggest me Next step to move on this further.

-Thanks in advance,
VKS.
________________________________
From: Williams, Mark [william at losrios.edu]
Sent: 28 February 2011 21:53:21
To: Vunnava Kesava Srinivas-B32946; xorp-users at xorp.org
Subject: RE: Help Needed in PIM-Join Messages !!
You need to uncomment the section on fib2mrib in the configuration on your DSR. PIM routers need to use the unicast forwarding table to be able to find the reverse path back to the RP.

If you configure the RP router as a BSR and candidate RP, then let the DSR learn the RP information using bootstrap; don?t configure it statically.

-Mark Williams

From: xorp-users-bounces at xorp.org [mailto:xorp-users-bounces at xorp.org] On Behalf Of Vunnava Kesava Srinivas-B32946
Sent: Monday, February 28, 2011 08:10
To: xorp-users at xorp.org
Subject: [Xorp-users] Help Needed in PIM-Join Messages !!

Hi Guys,
I have a requirement to bring up Multicast Routing [IPv4 Network] with pimsm4. The Topology that I am trying to configure is ;
"Multicast Sender <--------->RP<------------->DSR<-------------->Multicast Listener". I have connected everything Point- Point. So., No need to worry about routes.

I am seeing that Listener is sending IGMPv3 Join reports to the DSR. But even though pim-sm is running on DSR; it is NOT sending PIM-Join Messages to the RP. I have configured staticrp in the DSR & and the connectivity between the RP & DSP is Fine. I have attached the configuration file of both the RP & DSR. Please let me know what configuration am I missing !!!

Few Doubts:
1] Also another question is., If I am enabling IGMP on both the interfaces of DSR & RP will that matter & effect PIM Routing ??
2] How Plumbing effects Multicast Routing.


-Thanks in Advance,
VKS.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20110302/3b3d21c4/attachment.html 

From jcoco at meccorp.mec.edu  Wed Mar  2 05:11:44 2011
From: jcoco at meccorp.mec.edu (Joe Coco)
Date: Wed, 2 Mar 2011 08:11:44 -0500
Subject: [Xorp-users] RFC:  New VLAN api for xorp.ct
In-Reply-To: <4D6D4CC1.2080209@candelatech.com>
References: <4D6C8D74.9090602@candelatech.com>
	<65A6944974518C4B9C0E818727B559E9397F8E7C@mecexchange2007.meccorp.mec.edu>
	<4D6D4CC1.2080209@candelatech.com>
Message-ID: <65A6944974518C4B9C0E818727B559E9397F8EA2@mecexchange2007.meccorp.mec.edu>

Good morning (here in Boston anyway),



It appears the interfaces.tp is incomplete. 

For starters, the allow-range was missing arguments, which causes xorp to fail to start.

I fixed those entries to expect a parent of eth0-eth32, vid 1-4096, and type of vlan. 

But then when attempting to start xorp, I now get the following error:

[ 2011/03/02 02:58:34.475766  ERROR xorp_rtrmgr:3660 RTRMGR rtrmgr/main_rtrmgr.cc:274 run ] Shutting down due to an init error: Found %set command in node "interfaces interface @ vif @ vlan parent-ifname" that doesn't expect value


I'll happily fix it, but I need someone to explain to me what this means ;)

-- Joe


-----Original Message-----
From: Ben Greear [mailto:greearb at candelatech.com] 
Sent: Tuesday, March 01, 2011 2:45 PM
To: Joe Coco
Cc: xorp-users at xorp.org; xorp
Subject: Re: [Xorp-users] RFC: New VLAN api for xorp.ct

On 03/01/2011 11:51 AM, Joe Coco wrote:
>
> Ben,
>
> Maybe it's just me but. Patch applies clean, however I can't get past this step.
>
> For example:
>
> create interfaces interface foo disable false
>
> ^^^ works
>
> create interfaces interface foo vlan
>
> ^^ says
>
> ERROR: path "interfaces interface foo vlan" is not valid
>
> ??

Likely it's broken...I haven't had time to do any testing yet.

Trying to bring up a new web server, migrate a wiki, and
kick a new release out the door in the next few days,
so might be a bit before I can poke at xorp :)

Thanks,
Ben

>
> -- Joe
>
>
> -----Original Message-----
> From: xorp-users-bounces at xorp.org [mailto:xorp-users-bounces at xorp.org] On Behalf Of Ben Greear
> Sent: Tuesday, March 01, 2011 1:09 AM
> To: xorp-users at xorp.org; xorp
> Subject: [Xorp-users] RFC: New VLAN api for xorp.ct
>
> Here is a patch I cooked up to deal with automatically
> creating/deleting VLANs, while treating them as real
> interfaces.
>
> This is totally un-tested (it does compile on Linux, at least).
>
> Comments welcome.  I hope to test it in the next few days.
>
> http://www.candelatech.com/~greearb/0001-vlans-Treat-vlans-as-primary-interfaces.patch
>
> Thanks,
> Ben
>


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



From M.Handley at cs.ucl.ac.uk  Wed Mar  2 16:26:32 2011
From: M.Handley at cs.ucl.ac.uk (Mark Handley)
Date: Thu, 3 Mar 2011 00:26:32 +0000
Subject: [Xorp-users] New XORP project manager: Ben Greear
Message-ID: <AANLkTi=dnKXkjqQa8Mh0Yg4SUw0rXjqUQmooBCvQi6UQ@mail.gmail.com>

As I'm sure you've noticed, for quite a while now Ben Greear's xorp.ct
branch has been the de-facto current XORP branch.  We've decided to
make this official.

Ben is now the official project manager, and the xorp.org domain name
now points at Ben's version of the XORP webserver.  XORP will of
course remain open-source under the GPL.  Many thanks to Ben for
taking over care and feeding of XORP and for all the effort's he's put
in to date.

 - Mark Handley (XORP project founder).


From greearb at candelatech.com  Wed Mar  2 17:07:59 2011
From: greearb at candelatech.com (Ben Greear)
Date: Wed, 02 Mar 2011 17:07:59 -0800
Subject: [Xorp-users] New XORP project manager: Ben Greear
In-Reply-To: <AANLkTi=dnKXkjqQa8Mh0Yg4SUw0rXjqUQmooBCvQi6UQ@mail.gmail.com>
References: <AANLkTi=dnKXkjqQa8Mh0Yg4SUw0rXjqUQmooBCvQi6UQ@mail.gmail.com>
Message-ID: <4D6EE9EF.108@candelatech.com>

On 03/02/2011 04:26 PM, Mark Handley wrote:
> As I'm sure you've noticed, for quite a while now Ben Greear's xorp.ct
> branch has been the de-facto current XORP branch.  We've decided to
> make this official.
>
> Ben is now the official project manager, and the xorp.org domain name
> now points at Ben's version of the XORP webserver.  XORP will of
> course remain open-source under the GPL.  Many thanks to Ben for
> taking over care and feeding of XORP and for all the effort's he's put
> in to date.
>
>   - Mark Handley (XORP project founder).

And thanks to Mark for getting XORP started and seeing it through
all these years!

My immediate plans are to tweak the web page (remove ".ct" for starters)
and try to get auto-created VLANs working better.

Some other folks are working on updating the docs and we should
have those links go live soon.

After that, no big plans for a while, aside from fixing bugs
and dealing with customer requests.

I'll likely leave the 'xorp.ct' repository on github as the primary
source repository, and use github's bug-tracking tools.  I could
also setup bugzilla on my web server if someone thinks that would
be better.

I'm not sure what to do about sourceforge.  Maybe just leave
the svn up for historical reasons, or perhaps see if someone
can archive it and remove it entirely.

Thanks,
Ben

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


From greearb at candelatech.com  Wed Mar  2 22:25:53 2011
From: greearb at candelatech.com (Ben Greear)
Date: Wed, 02 Mar 2011 22:25:53 -0800
Subject: [Xorp-users] Paid XORP support and the new xorp.org web site.
Message-ID: <4D6F3471.8090309@candelatech.com>

Hello!

I have been doing a bit of paid XORP support through
my company, and have updated the xorp.org web site
with a small blurb advertising the fact.

If anyone else is interested in offering other commercial
XORP related services, please let me know and we can work
out how to add that to the site as well.

And, if this or anything else on the new www.xorp.org
web site offends or needs improving, please let me
know or post to the mailing lists...

It's possible it will take another day or so for everyone's
DNS to update.  If your DNS is NOT updated yet, you can temporarily add
this to your hosts file:

208.74.158.171  www.xorp.org

It's a virtual domain in apache, so hitting the IP directly will not
function as desired.

Thanks,
Ben

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


From jcoco at meccorp.mec.edu  Thu Mar  3 07:38:08 2011
From: jcoco at meccorp.mec.edu (Joe Coco)
Date: Thu, 3 Mar 2011 10:38:08 -0500
Subject: [Xorp-users] RFC:  New VLAN api for xorp.ct
In-Reply-To: <65A6944974518C4B9C0E818727B559E9397F8EA2@mecexchange2007.meccorp.mec.edu>
References: <4D6C8D74.9090602@candelatech.com>
	<65A6944974518C4B9C0E818727B559E9397F8E7C@mecexchange2007.meccorp.mec.edu>
	<4D6D4CC1.2080209@candelatech.com>
	<65A6944974518C4B9C0E818727B559E9397F8EA2@mecexchange2007.meccorp.mec.edu>
Message-ID: <65A6944974518C4B9C0E818727B559E9397F8F87@mecexchange2007.meccorp.mec.edu>

Hello,

I removed the 'set' options from the interfaces.tp and now xorp starts. When I try to configure a VLAN, I do get an error.
I'm not sure if this is because I fouled up the range syntax in interfaces.tp, or an actual broken condition. The error is:

"Commit Failed
102 Command failed  push_config failed: Interface/Vif error on foo/foo: Failed to 
add VLAN to interface foo  reason: Unknown virtual device type:"

(notice virtual device type is blank) I'm assuming the iface_type string is not being set.


My config is:

interface foo {
	virtual-dev {
		parent-ifname: "eth1"
		iface-type: "VLAN"
		vid: "200"
	}
	vif foo {
		address 1.1.1.1 {
		prefix-length: 24
	}
  }
}


Couple of things from the interfaces.tp file.  Shouldn't the VIDve u32 not txt ?

Here is what I slightly modified in interfaces.tp which allows xorp to start:

     vlan {
                %help:  short "Configure a virtual interface";
                %create:        xrl "$(interfaces.targetname)/ifmgr/0.1/set_if_virtual?parent-iface:txt=$(interfaces.TID)&parent-ifname:txt=$(interface.@)&iface-type:txt$(@.iface-type)&vid:txt$(@.vid)";

                %mandatory:     $(@.parent-ifname), $(@.iface-type), $(@.vid);

                parent-ifname {
                    %help:      short "Parent interface this virtual belongs to.";
                    %allow-range: $(@) "eth0" "eth32" %help: "E.g, eth0";
                    %create:;
                }
                iface-type {
                    %help:      short "Interface-type:  VLAN.";
                    %allow-range: $(@) "VLAN" "VLAN" %help: "Just type vlan";
                    %create:;
                }
                vid {
                    %help:      short "Virtual Interface Identifier:  VLAN-ID for VLANs.";
                    %allow-range: $(@) "1" "4096" %help: "The VLAN ID";
                    %create:;
                }
            }


-- Joe


From greearb at candelatech.com  Thu Mar  3 09:15:28 2011
From: greearb at candelatech.com (Ben Greear)
Date: Thu, 03 Mar 2011 09:15:28 -0800
Subject: [Xorp-users] RFC:  New VLAN api for xorp.ct
In-Reply-To: <65A6944974518C4B9C0E818727B559E9397F8F87@mecexchange2007.meccorp.mec.edu>
References: <4D6C8D74.9090602@candelatech.com>	<65A6944974518C4B9C0E818727B559E9397F8E7C@mecexchange2007.meccorp.mec.edu>	<4D6D4CC1.2080209@candelatech.com>
	<65A6944974518C4B9C0E818727B559E9397F8EA2@mecexchange2007.meccorp.mec.edu>
	<65A6944974518C4B9C0E818727B559E9397F8F87@mecexchange2007.meccorp.mec.edu>
Message-ID: <4D6FCCB0.7020406@candelatech.com>

On 03/03/2011 07:38 AM, Joe Coco wrote:
> Hello,
>
> I removed the 'set' options from the interfaces.tp and now xorp starts. When I try to configure a VLAN, I do get an error.
> I'm not sure if this is because I fouled up the range syntax in interfaces.tp, or an actual broken condition. The error is:

I plan to work on this today.  I think I'll remove the
virtual-dev section and just have each of the 3 variables
as top-level interface configurables.

Thanks,
Ben

>
> "Commit Failed
> 102 Command failed  push_config failed: Interface/Vif error on foo/foo: Failed to
> add VLAN to interface foo  reason: Unknown virtual device type:"
>
> (notice virtual device type is blank) I'm assuming the iface_type string is not being set.
>
>
> My config is:
>
> interface foo {
> 	virtual-dev {
> 		parent-ifname: "eth1"
> 		iface-type: "VLAN"
> 		vid: "200"
> 	}
> 	vif foo {
> 		address 1.1.1.1 {
> 		prefix-length: 24
> 	}
>    }
> }
>
>
> Couple of things from the interfaces.tp file.  Shouldn't the VIDve u32 not txt ?
>
> Here is what I slightly modified in interfaces.tp which allows xorp to start:
>
>       vlan {
>                  %help:  short "Configure a virtual interface";
>                  %create:        xrl "$(interfaces.targetname)/ifmgr/0.1/set_if_virtual?parent-iface:txt=$(interfaces.TID)&parent-ifname:txt=$(interface.@)&iface-type:txt$(@.iface-type)&vid:txt$(@.vid)";
>
>                  %mandatory:     $(@.parent-ifname), $(@.iface-type), $(@.vid);
>
>                  parent-ifname {
>                      %help:      short "Parent interface this virtual belongs to.";
>                      %allow-range: $(@) "eth0" "eth32" %help: "E.g, eth0";
>                      %create:;
>                  }
>                  iface-type {
>                      %help:      short "Interface-type:  VLAN.";
>                      %allow-range: $(@) "VLAN" "VLAN" %help: "Just type vlan";
>                      %create:;
>                  }
>                  vid {
>                      %help:      short "Virtual Interface Identifier:  VLAN-ID for VLANs.";
>                      %allow-range: $(@) "1" "4096" %help: "The VLAN ID";
>                      %create:;
>                  }
>              }
>
>
> -- Joe


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


From B32946 at freescale.com  Thu Mar  3 09:42:17 2011
From: B32946 at freescale.com (Vunnava Kesava Srinivas-B32946)
Date: Thu, 3 Mar 2011 17:42:17 +0000
Subject: [Xorp-users] RP-Bootstrap NOT Learned for pimsm6!!
Message-ID: <9D8289DE2B23FA4EBC165B4CFB3718660B3899@039-SN1MPN1-004.039d.mgd.msft.net>

Hi Guys ,
I today played with XORP over pimsm6 and things happened Fine on the fly.

But one thing observed is ; even though BSR is advertising RP for Multicast groups via Bootstrap Messages., some how DSR is NOT LEARNING it. I didn't get this issue when worked on pimsm4. This is very specific to pimsm6. Later added static-rp[IPv6] and somehow managed the stuff.

Please clarify me about this issue !!

-Thanks in Advance,
VKS.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20110303/015c0ace/attachment.html 

From greearb at candelatech.com  Thu Mar  3 10:30:39 2011
From: greearb at candelatech.com (Ben Greear)
Date: Thu, 03 Mar 2011 10:30:39 -0800
Subject: [Xorp-users] RFC:  New VLAN api for xorp.ct
In-Reply-To: <65A6944974518C4B9C0E818727B559E9397F8F87@mecexchange2007.meccorp.mec.edu>
References: <4D6C8D74.9090602@candelatech.com>	<65A6944974518C4B9C0E818727B559E9397F8E7C@mecexchange2007.meccorp.mec.edu>	<4D6D4CC1.2080209@candelatech.com>
	<65A6944974518C4B9C0E818727B559E9397F8EA2@mecexchange2007.meccorp.mec.edu>
	<65A6944974518C4B9C0E818727B559E9397F8F87@mecexchange2007.meccorp.mec.edu>
Message-ID: <4D6FDE4F.7050304@candelatech.com>

On 03/03/2011 07:38 AM, Joe Coco wrote:
> Hello,
>
> I removed the 'set' options from the interfaces.tp and now xorp starts. When I try to configure a VLAN, I do get an error.
> I'm not sure if this is because I fouled up the range syntax in interfaces.tp, or an actual broken condition. The error is:

Please remove the old patch and apply this one instead.  It boots and
creates the interface on my test machine.  I haven't tried running
a real protocol over it, but likely it will work.

http://www.xorp.org/patches/0001-vlans-Treat-vlans-as-primary-interfaces.patch

Note the syntax has changed:


interfaces {
     interface "eth1.5" {
	parent-ifname: "eth1"
	iface-type: "VLAN"
	vid: "5"
         vif "eth1.5" {
             address 11.1.1.1 {
                 prefix-length: 24
             }
         }
     }

}


Thanks,
Ben

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


From greearb at candelatech.com  Sat Mar  5 10:27:23 2011
From: greearb at candelatech.com (Ben Greear)
Date: Sat, 05 Mar 2011 10:27:23 -0800
Subject: [Xorp-users] Anyone want to transfer bugs to the new bugzilla?
Message-ID: <4D72808B.3050207@candelatech.com>

I have installed bugzilla for zorp:
http://www.xorp.org/bugzilla

If anyone (or several) would like to add the open
bugs from sourceforge into this bugzilla, that would
be great!  It wouldn't have to be pretty..probably
a screen-scrape and paste would be sufficient.

http://sourceforge.net/apps/trac/xorp/report/1

And, if anyone would like admin privs in the xorp bugzilla,
just let me know.  It could use some work with adding new
categories, etc.

Thanks,
Ben

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


From pierre.lepropre at student.ulg.ac.be  Sat Mar  5 10:38:29 2011
From: pierre.lepropre at student.ulg.ac.be (Pierre Lepropre)
Date: Sat, 05 Mar 2011 19:38:29 +0100
Subject: [Xorp-users] Anyone want to transfer bugs to the new bugzilla?
In-Reply-To: <4D72808B.3050207@candelatech.com>
References: <4D72808B.3050207@candelatech.com>
Message-ID: <1299350309.3709.26.camel@pierre-T500>

Guys,

Now is the time to cheer up and get yourselves involved in community's
work for XORP if you're interested by it.

Ben has been working hard lately to get some things up and running since
M. Handley has given him the greenlight for xorp.ct to become xorp.org.
Bugzilla is one of these.

I would do it myself if I hadn't already my hands full with a new
documentation project for XORP, where you'll be able to get involved too
if you wish. More details about that will come in a couple of days.

Regards,

Pierre.

On Sat, 2011-03-05 at 10:27 -0800, Ben Greear wrote:
> I have installed bugzilla for zorp:
> http://www.xorp.org/bugzilla
> 
> If anyone (or several) would like to add the open
> bugs from sourceforge into this bugzilla, that would
> be great!  It wouldn't have to be pretty..probably
> a screen-scrape and paste would be sufficient.
> 
> http://sourceforge.net/apps/trac/xorp/report/1
> 
> And, if anyone would like admin privs in the xorp bugzilla,
> just let me know.  It could use some work with adding new
> categories, etc.
> 
> Thanks,
> Ben
> 



From B32946 at freescale.com  Sun Mar  6 23:08:08 2011
From: B32946 at freescale.com (Vunnava Kesava Srinivas-B32946)
Date: Mon, 7 Mar 2011 07:08:08 +0000
Subject: [Xorp-users] "targetname" directive Not getting parsed!
Message-ID: <9D8289DE2B23FA4EBC165B4CFB3718660B3971@039-SN1MPN1-004.039d.mgd.msft.net>

Hi Guys ,
I am getting a syntax error while running the xorp_rtrmgr with the "targetname" directive in the pimsm6 protocols section. This happens when we give this directive in other protocols [igmp,mld etc...] sections also. XORP user guide had the description for using it. But some how not getting parsed. Please lemme know the way to make it working and getting recognized by the parser.

Example configuration.
###################
protocols {
  pimsm6 {
    targetname: abc
   blah....blah...blah..
 }
}
#####################


-Best Wishes,
VKS.

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

From aleksandar.cvjetic at gmail.com  Tue Mar  8 00:14:18 2011
From: aleksandar.cvjetic at gmail.com (Aleksandar Cvjetic)
Date: Tue, 8 Mar 2011 09:14:18 +0100
Subject: [Xorp-users] (no subject)
Message-ID: <AANLkTinx=B+=2YJe8EmO5ddSPvfvkaLFxLSc2wkTdb_q@mail.gmail.com>


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

From greearb at candelatech.com  Tue Mar  8 09:37:19 2011
From: greearb at candelatech.com (Ben Greear)
Date: Tue, 08 Mar 2011 09:37:19 -0800
Subject: [Xorp-users] "targetname" directive Not getting parsed!
In-Reply-To: <9D8289DE2B23FA4EBC165B4CFB3718660B3971@039-SN1MPN1-004.039d.mgd.msft.net>
References: <9D8289DE2B23FA4EBC165B4CFB3718660B3971@039-SN1MPN1-004.039d.mgd.msft.net>
Message-ID: <4D76694F.4060501@candelatech.com>

On 03/06/2011 11:08 PM, Vunnava Kesava Srinivas-B32946 wrote:
> Hi Guys ,
> I am getting a syntax error while running the xorp_rtrmgr with the
> "targetname" directive in the pimsm6 protocols section. This happens
> when we give this directive in other protocols [igmp,mld etc...]
> sections also. XORP user guide had the description for using it. But
> some how not getting parsed. Please lemme know the way to make it
> working and getting recognized by the parser.
>
> Example configuration.
> ###################
> protocols {
> pimsm6 {
> targetname: abc
> blah....blah...blah..
> }
> }
> #####################

Maybe you need to quote "abc" ?

Please post the exact errors you are getting.

Thanks,
Ben

>
>
> -Best Wishes,
> VKS.
>
>
>
> _______________________________________________
> 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  Tue Mar  8 10:35:52 2011
From: greearb at candelatech.com (Ben Greear)
Date: Tue, 08 Mar 2011 10:35:52 -0800
Subject: [Xorp-users] RFC:  New VLAN api for xorp.ct
In-Reply-To: <4D6FDE4F.7050304@candelatech.com>
References: <4D6C8D74.9090602@candelatech.com>	<65A6944974518C4B9C0E818727B559E9397F8E7C@mecexchange2007.meccorp.mec.edu>	<4D6D4CC1.2080209@candelatech.com>	<65A6944974518C4B9C0E818727B559E9397F8EA2@mecexchange2007.meccorp.mec.edu>	<65A6944974518C4B9C0E818727B559E9397F8F87@mecexchange2007.meccorp.mec.edu>
	<4D6FDE4F.7050304@candelatech.com>
Message-ID: <4D767708.5070607@candelatech.com>

On 03/03/2011 10:30 AM, Ben Greear wrote:
> On 03/03/2011 07:38 AM, Joe Coco wrote:
>> Hello,
>>
>> I removed the 'set' options from the interfaces.tp and now xorp starts. When I try to configure a VLAN, I do get an error.
>> I'm not sure if this is because I fouled up the range syntax in interfaces.tp, or an actual broken condition. The error is:
>
> Please remove the old patch and apply this one instead.  It boots and
> creates the interface on my test machine.  I haven't tried running
> a real protocol over it, but likely it will work.

I've pushed the VLAN patch to the xorp.ct repo.  I've only done light
testing so far, but should get some more solid results soon.

Thanks,
Ben

>
> http://www.xorp.org/patches/0001-vlans-Treat-vlans-as-primary-interfaces.patch
>
> Note the syntax has changed:
>
>
> interfaces {
>       interface "eth1.5" {
> 	parent-ifname: "eth1"
> 	iface-type: "VLAN"
> 	vid: "5"
>           vif "eth1.5" {
>               address 11.1.1.1 {
>                   prefix-length: 24
>               }
>           }
>       }
>
> }
>
>
> Thanks,
> Ben
>


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


From greearb at candelatech.com  Tue Mar  8 15:58:23 2011
From: greearb at candelatech.com (Ben Greear)
Date: Tue, 08 Mar 2011 15:58:23 -0800
Subject: [Xorp-users] Pre-release 1.8.3 binaries available.
Message-ID: <4D76C29F.6090801@candelatech.com>

I just uploaded some beta XORP 1.8.3 builds here:

http://www.xorp.org/releases/testing/

This includes win32 binaries and some Fedora 13 RPMs.

The user-guide hasn't been updated with the latest VLAN
syntax yet, but see previous email postings or ask if
you want to try it out.

Thanks,
Ben


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


From greearb at candelatech.com  Tue Mar  8 16:09:28 2011
From: greearb at candelatech.com (Ben Greear)
Date: Tue, 08 Mar 2011 16:09:28 -0800
Subject: [Xorp-users] Things to do for the upcoming 1.8.3 release.
Message-ID: <4D76C538.8000209@candelatech.com>


Here's my list of things to do for the 1.8.3 release,
which I hope to have done before the end of March.

*  Get user-guide into the wiki that Pierre is working on.
   *  Update it with the VLAN syntax changes, at least.

*  Update xorp.org web site:
   *  Point to wiki for docs
   *  Generate PDFs for at least the user-guide, with wiki as upstream source.
   *  Fix up google search to search the wiki too.
   *  Make it easier to find example xorp config files.

* Run latest xorp code through our internal regression tests..and
   hope others do the same!

* Migrate bugs from the source-forge trac into xorp.org/bugzilla.
   (would be great to get some volunteers for this job...should be
    pretty easy, and pretty boring work.  Or, someone could write
    a clever tool to automate this and become famous!)

* Once bugs are migrated, shut down the source-forge xorp page entirely.
   I already have a backup of the old releases and the old svn source repository:
   http://www.xorp.org/releases/old/


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


From magaamgl at gmail.com  Wed Mar  9 01:14:48 2011
From: magaamgl at gmail.com (Magsarjav Terbish)
Date: Wed, 9 Mar 2011 17:14:48 +0800
Subject: [Xorp-users] About problem with xorp forward traffic
Message-ID: <AANLkTi=RhwFqqtybqiiUTWeK_1N3fc4ywnD=enUhqD2p@mail.gmail.com>

Dear sir

How are you?
i have install xorp on the ubuntu 10.10 linux.
i have only one router pc and two pc for sender, receiver. when send video
stream from VLC stream.
i have check on the router with "show pim join". i can see traffic.  and VLC
player works on the  receiver pc.
i can see on the router receivers join request with "show pim join".
but that router didn't forward that multicast traffic.

How can i debug? how can i solve problem.

Best regards
Magsarjav.T
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20110309/1d871ab5/attachment.html 

From rps at maine.edu  Wed Mar  9 05:38:26 2011
From: rps at maine.edu (Ray Soucy)
Date: Wed, 9 Mar 2011 08:38:26 -0500
Subject: [Xorp-users] About problem with xorp forward traffic
In-Reply-To: <AANLkTi=RhwFqqtybqiiUTWeK_1N3fc4ywnD=enUhqD2p@mail.gmail.com>
References: <AANLkTi=RhwFqqtybqiiUTWeK_1N3fc4ywnD=enUhqD2p@mail.gmail.com>
Message-ID: <AANLkTimu533s2oBHJxbLi_O3-8ekuvd4M3UNJcjSZ1Ey@mail.gmail.com>

Please provide a copy of your XORP configuration.

On Wed, Mar 9, 2011 at 4:14 AM, Magsarjav Terbish <magaamgl at gmail.com> wrote:
> Dear sir
>
> How are you?
> i have install xorp on the ubuntu 10.10 linux.
> i have only one router pc and two pc for sender, receiver. when send video
> stream from VLC stream.
> i have check on the router with "show pim join". i can see traffic.? and VLC
> player works on the? receiver pc.
> i can see on the router receivers join request with "show pim join".
> but that router didn't forward that multicast traffic.
>
> How can i debug? how can i solve problem.
>
> Best regards
> Magsarjav.T
>
> _______________________________________________
> Xorp-users mailing list
> Xorp-users at xorp.org
> http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users
>
>



-- 
Ray Soucy

Epic Communications Specialist

Phone: +1 (207) 561-3526

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


From greearb at candelatech.com  Wed Mar  9 06:29:15 2011
From: greearb at candelatech.com (Ben Greear)
Date: Wed, 09 Mar 2011 06:29:15 -0800
Subject: [Xorp-users] About problem with xorp forward traffic
In-Reply-To: <AANLkTi=RhwFqqtybqiiUTWeK_1N3fc4ywnD=enUhqD2p@mail.gmail.com>
References: <AANLkTi=RhwFqqtybqiiUTWeK_1N3fc4ywnD=enUhqD2p@mail.gmail.com>
Message-ID: <4D778EBB.4070808@candelatech.com>

On 03/09/2011 01:14 AM, Magsarjav Terbish wrote:
> Dear sir
>
> How are you?
> i have install xorp on the ubuntu 10.10 linux.
> i have only one router pc and two pc for sender, receiver. when send video stream from VLC stream.
> i have check on the router with "show pim join". i can see traffic.  and VLC player works on the  receiver pc.
> i can see on the router receivers join request with "show pim join".
> but that router didn't forward that multicast traffic.
>
> How can i debug? how can i solve problem.

Make sure that the TTL for the sender is greater than  the number of router
hops.

Thanks,
Ben

>
> Best regards
> Magsarjav.T
>
>
>
> _______________________________________________
> 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 Mar  9 11:35:33 2011
From: jcoco at meccorp.mec.edu (Joe Coco)
Date: Wed, 9 Mar 2011 14:35:33 -0500
Subject: [Xorp-users] Things to do for the upcoming 1.8.3 release.
In-Reply-To: <4D77CA3B.9040402@candelatech.com>
References: <4D76C538.8000209@candelatech.com>
	<65A6944974518C4B9C0E818727B559E939357C40@mecexchange2007.meccorp.mec.edu>,
	<4D76E6C2.3020909@candelatech.com>
	<65A6944974518C4B9C0E818727B559E939357C41@mecexchange2007.meccorp.mec.edu>
	<4D76EF79.30706@candelatech.com>
	<65A6944974518C4B9C0E818727B559E9398DDC51@mecexchange2007.meccorp.mec.edu>
	<4D778D85.6050002@candelatech.com>
	<65A6944974518C4B9C0E818727B559E9398DDCFE@mecexchange2007.meccorp.mec.edu>
	<4D77CA3B.9040402@candelatech.com>
Message-ID: <65A6944974518C4B9C0E818727B559E9398DDD15@mecexchange2007.meccorp.mec.edu>

Hi Ben,

Here is the XRL permissions patch. All this does is look up the uid and gid of xorp per unix98 standard
and set the permissions/owner appropriately for the XRL files. I found, at least on my system, that fea
would write the files as root:root, and xorpsh running as stripped privilege user 'xorp' could not read/write
to the xrp files in /var/tmp

If my logic is flawed, please let me know but it 'works for me' :)


--Joe




--- xorp/libxipc/xrl_pf_unix.cc-orig    2011-03-09 14:20:45.000000000 -0500
+++ xorp/libxipc/xrl_pf_unix.cc 2011-03-09 14:16:30.000000000 -0500
@@ -23,6 +23,8 @@
 #include "xrl_pf_unix.hh"
 #include "libcomm/comm_api.h"
 #include "sockutil.hh"
+#include <pwd.h>
+#include <grp.h>

 #ifndef        HOST_OS_WINDOWS

@@ -32,6 +34,11 @@
 XrlPFUNIXListener::XrlPFUNIXListener(EventLoop& e, XrlDispatcher* xr)
     : XrlPFSTCPListener(&e, xr)
 {
+
+struct passwd *pwd; /* For UID of XORP user */
+struct group *grp;  /* For GID of XORP group */
+
+
     string path = get_sock_path();

     _sock = comm_bind_unix(path.c_str(), COMM_SOCK_NONBLOCKING);
@@ -44,12 +51,50 @@
         xorp_throw(XrlPFConstructorError, comm_get_last_error_str());
     }

+
+/* This didn't quite work for my system, so I changed it to load user/group xorp per unix98 std -JC */
+
     // Make sure socket is read/write by group and owner.
-    if (chmod(path.c_str(), S_ISUID | S_IRUSR | S_IWUSR | S_IXUSR | S_IRGRP | S_IWGRP | S_IXGRP | S_IROTH ) < 0) {
-       cerr << "ERROR:  Failed chgrp on path: " << path << " error: "
-            << strerror(errno) << endl;
-       // Carry on, might turn out OK!
-    }
+    //   if (chmod(path.c_str(), S_ISUID | S_IRUSR | S_IWUSR | S_IXUSR | S_IRGRP | S_IWGRP | S_IXGRP | S_IROTH ) < 0) {
+    // cerr << "ERROR:  Failed chgrp on path: " << path << " error: "
+    //      << strerror(errno) << endl;
+    // Carry on, might turn out OK!
+    // }
+
+
+pwd = getpwnam("xorp");
+grp = getgrnam("xorp");
+
+
+       if (pwd == NULL) {
+
+                       cerr << "ERROR: Failed to get UID of xorp user!" << endl;
+                       exit(0);
+               }
+
+
+       if (grp == NULL) {
+
+                       cerr << "ERROR: Failed to get GID of xorp group!" << endl;
+                       exit(0);
+               }
+
+
+/* If we got here at least XORP user and group exist */
+
+       if (chown(path.c_str(), pwd->pw_uid, grp->gr_gid)) {
+
+               cerr << "ERROR: Failed chown on path: " << path << " error: " << strerror(errno) << endl;
+}
+
+       /* Owner read/write, group read/write, other read -JC */
+
+       if (chmod(path.c_str(), S_IWUSR| S_IRUSR| S_IWGRP| S_IRGRP| S_IROTH)) {
+               cerr << "ERROR: Failed chmod on path: " << path << " error: " << strerror(errno) << endl;
+               }
+
+/* Ok end of breaking xorp -JC */
+

     _address_slash_port = path;
     encode_address(_address_slash_port);



From magaamgl at gmail.com  Thu Mar 10 00:19:44 2011
From: magaamgl at gmail.com (Magsarjav Terbish)
Date: Thu, 10 Mar 2011 16:19:44 +0800
Subject: [Xorp-users] About problem with xorp forward traffic
In-Reply-To: <AANLkTi=AqGMj7RnZko6DY=y6vYndo=TvJWcX+ivcoFAB@mail.gmail.com>
References: <AANLkTi=RhwFqqtybqiiUTWeK_1N3fc4ywnD=enUhqD2p@mail.gmail.com>
	<4D778EBB.4070808@candelatech.com>
	<AANLkTi=AqGMj7RnZko6DY=y6vYndo=TvJWcX+ivcoFAB@mail.gmail.com>
Message-ID: <AANLkTimYFpPbyooudDvd+OaTwuUEKhDbsVjw=vW8+PiC@mail.gmail.com>

Dear Sir

Hello.

Thank you for reply.
my server work. problem is ttl was set 1.

Best regards
Magaa
On Thu, Mar 10, 2011 at 2:51 PM, Magsarjav Terbish <magaamgl at gmail.com>wrote:

> Dear sir
>
> Thank you for reply to Ray and Ben.
>
> i have attached my configure and screen shots. i have sender pc, receiver
> pc and only one xorp router.
>
> pls find attached file.
>
> Waiting your reply.
>
> Best regards
> Maagaa
>
>
> On Wed, Mar 9, 2011 at 10:29 PM, Ben Greear <greearb at candelatech.com>wrote:
>
>> On 03/09/2011 01:14 AM, Magsarjav Terbish wrote:
>>
>>> Dear sir
>>>
>>> How are you?
>>> i have install xorp on the ubuntu 10.10 linux.
>>> i have only one router pc and two pc for sender, receiver. when send
>>> video stream from VLC stream.
>>> i have check on the router with "show pim join". i can see traffic.  and
>>> VLC player works on the  receiver pc.
>>> i can see on the router receivers join request with "show pim join".
>>> but that router didn't forward that multicast traffic.
>>>
>>> How can i debug? how can i solve problem.
>>>
>>
>> Make sure that the TTL for the sender is greater than  the number of
>> router
>> hops.
>>
>> Thanks,
>> Ben
>>
>>
>>
>>> Best regards
>>> Magsarjav.T
>>>
>>>
>>>
>>> _______________________________________________
>>> 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
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20110310/512d0a6d/attachment.html 

From abazh18 at gmail.com  Thu Mar 10 00:32:04 2011
From: abazh18 at gmail.com (Achmad Basuki)
Date: Thu, 10 Mar 2011 17:32:04 +0900
Subject: [Xorp-users] RP-Bootstrap NOT Learned for pimsm6!!
In-Reply-To: <9D8289DE2B23FA4EBC165B4CFB3718660B3899@039-SN1MPN1-004.039d.mgd.msft.net>
References: <9D8289DE2B23FA4EBC165B4CFB3718660B3899@039-SN1MPN1-004.039d.mgd.msft.net>
Message-ID: <AANLkTin8KKFUNAUY3i-Dk+g3gcYKrFavM10W1Db37F3m@mail.gmail.com>

Hi VKS,

can you share your PIMSM6 section configuration?

On Fri, Mar 4, 2011 at 2:42 AM, Vunnava Kesava Srinivas-B32946
<B32946 at freescale.com> wrote:
> Hi Guys ,
> I today played with XORP over pimsm6 and things happened Fine on the fly.
>
> But one thing observed is ; even though BSR is advertising RP for Multicast
> groups via Bootstrap Messages., some how DSR is NOT LEARNING it. I didn't
> get this issue when worked on pimsm4. This is very specific to pimsm6. Later
> added static-rp[IPv6] and somehow managed the stuff.
>
> Please clarify me about this issue !!
>
> -Thanks in Advance,
> VKS.
>
> _______________________________________________
> Xorp-users mailing list
> Xorp-users at xorp.org
> http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users
>
>


From magaamgl at gmail.com  Wed Mar  9 22:51:32 2011
From: magaamgl at gmail.com (Magsarjav Terbish)
Date: Thu, 10 Mar 2011 14:51:32 +0800
Subject: [Xorp-users] About problem with xorp forward traffic
In-Reply-To: <4D778EBB.4070808@candelatech.com>
References: <AANLkTi=RhwFqqtybqiiUTWeK_1N3fc4ywnD=enUhqD2p@mail.gmail.com>
	<4D778EBB.4070808@candelatech.com>
Message-ID: <AANLkTi=AqGMj7RnZko6DY=y6vYndo=TvJWcX+ivcoFAB@mail.gmail.com>

Dear sir

Thank you for reply to Ray and Ben.

i have attached my configure and screen shots. i have sender pc, receiver pc
and only one xorp router.

pls find attached file.

Waiting your reply.

Best regards
Maagaa

On Wed, Mar 9, 2011 at 10:29 PM, Ben Greear <greearb at candelatech.com> wrote:

> On 03/09/2011 01:14 AM, Magsarjav Terbish wrote:
>
>> Dear sir
>>
>> How are you?
>> i have install xorp on the ubuntu 10.10 linux.
>> i have only one router pc and two pc for sender, receiver. when send video
>> stream from VLC stream.
>> i have check on the router with "show pim join". i can see traffic.  and
>> VLC player works on the  receiver pc.
>> i can see on the router receivers join request with "show pim join".
>> but that router didn't forward that multicast traffic.
>>
>> How can i debug? how can i solve problem.
>>
>
> Make sure that the TTL for the sender is greater than  the number of router
> hops.
>
> Thanks,
> Ben
>
>
>
>> Best regards
>> Magsarjav.T
>>
>>
>>
>> _______________________________________________
>> 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
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20110310/22fd2ddb/attachment-0001.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: config.boot
Type: application/octet-stream
Size: 3156 bytes
Desc: not available
Url : http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20110310/22fd2ddb/attachment-0001.obj 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: interface.png
Type: image/png
Size: 437972 bytes
Desc: not available
Url : http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20110310/22fd2ddb/attachment-0007.bin 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: receiver join.png
Type: image/png
Size: 94913 bytes
Desc: not available
Url : http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20110310/22fd2ddb/attachment-0008.bin 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: sender and receiver join.png
Type: image/png
Size: 131745 bytes
Desc: not available
Url : http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20110310/22fd2ddb/attachment-0009.bin 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: sender join.png
Type: image/png
Size: 128902 bytes
Desc: not available
Url : http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20110310/22fd2ddb/attachment-0010.bin 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: show_igmp_interface.png
Type: image/png
Size: 58373 bytes
Desc: not available
Url : http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20110310/22fd2ddb/attachment-0011.bin 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: show_mfea_dataflow.png
Type: image/png
Size: 55758 bytes
Desc: not available
Url : http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20110310/22fd2ddb/attachment-0012.bin 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: show_pim_mfc.png
Type: image/png
Size: 53657 bytes
Desc: not available
Url : http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20110310/22fd2ddb/attachment-0013.bin 

From B32946 at freescale.com  Fri Mar 11 05:38:36 2011
From: B32946 at freescale.com (Vunnava Kesava Srinivas-B32946)
Date: Fri, 11 Mar 2011 13:38:36 +0000
Subject: [Xorp-users] PIM-SMv2 not working when bootstrap mechanism is
	enabled
Message-ID: <9D8289DE2B23FA4EBC165B4CFB3718660B3CA8@039-SN1MPN1-004.039d.mgd.msft.net>

Hi,

We are testing XORP-V1.6  for PIMSM-V2 (IPv4) with no unicast routing protocol enabled.
It works when we use static RP.  It is not working when we select Bootstrap mechanism and specifying candiadate rp.
We observed the following two issues.

case 1:
When candidate RP and BSR are enabled on one router and DR on another (connected back to back), DR is receiving the bootstrap message which contained the multicast Group prefix and the RP's IP correctly.
But DR is not updating its active RP list with the information from bootstrap message received from BSR.But DR is able to send the same Bootstrap message back to BSR.
We used the command "show pim bootstrap rps" at DR to view its active RP list.

case 2:
When candidate RP and DR are configured on one router and BSR on another router, we have not seen the candidate RP advertisement being generated by the first router even though it identified the location of BSR which it learnt through bootstrap message from BSR.

In both cases we have  ensured mrib to contain the correct routes by manually configuring in linux kernel.

Please find the configuration  files attached.
DRconfigcase1.boot and BSRconfigcase1.boot are applicable for the first case mentioned above and the rest are for case 2 mentioned above.

Please help us in locating the problem.We believe that we are missing some thing.

Thanks
-kesava and ns murthy
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20110311/43e7899e/attachment.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: BSRconfigcase1.boot
Type: application/octet-stream
Size: 1669 bytes
Desc: BSRconfigcase1.boot
Url : http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20110311/43e7899e/attachment.obj 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: DRconfigcase1.boot
Type: application/octet-stream
Size: 1151 bytes
Desc: DRconfigcase1.boot
Url : http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20110311/43e7899e/attachment-0001.obj 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: BSRconfigcase2.boot
Type: application/octet-stream
Size: 1532 bytes
Desc: BSRconfigcase2.boot
Url : http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20110311/43e7899e/attachment-0002.obj 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: DRconfigcase2.boot
Type: application/octet-stream
Size: 1311 bytes
Desc: DRconfigcase2.boot
Url : http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20110311/43e7899e/attachment-0003.obj 

From peirce at maine.edu  Fri Mar 11 07:00:14 2011
From: peirce at maine.edu (Garry Peirce)
Date: Fri, 11 Mar 2011 10:00:14 -0500
Subject: [Xorp-users] PIM-SMv2 not working when bootstrap mechanism
	is	enabled
In-Reply-To: <9D8289DE2B23FA4EBC165B4CFB3718660B3CA8@039-SN1MPN1-004.039d.mgd.msft.net>
References: <9D8289DE2B23FA4EBC165B4CFB3718660B3CA8@039-SN1MPN1-004.039d.mgd.msft.net>
Message-ID: <02b101cbdffd$069c0800$13d41800$@maine.edu>

I can't see your addressing info from your data, but my gut reaction would
be to  check your unicast routing table.

You might check that the received BSR packets source addr is passing an RPF
check.

 

 

Description: Garry Peirce

 

From: xorp-users-bounces at xorp.org [mailto:xorp-users-bounces at xorp.org] On
Behalf Of Vunnava Kesava Srinivas-B32946
Sent: Friday, March 11, 2011 8:39 AM
To: xorp-users at xorp.org
Cc: Murthy N Srinivas-B22237
Subject: [Xorp-users] PIM-SMv2 not working when bootstrap mechanism is
enabled

 

Hi,

We are testing XORP-V1.6  for PIMSM-V2 (IPv4) with no unicast routing
protocol enabled.
It works when we use static RP.  It is not working when we select Bootstrap
mechanism and specifying candiadate rp.
We observed the following two issues.

case 1:  
When candidate RP and BSR are enabled on one router and DR on another
(connected back to back), DR is receiving the bootstrap message which
contained the multicast Group prefix and the RP's IP correctly.
But DR is not updating its active RP list with the information from
bootstrap message received from BSR.But DR is able to send the same
Bootstrap message back to BSR.
We used the command "show pim bootstrap rps" at DR to view its active RP
list.

case 2:
When candidate RP and DR are configured on one router and BSR on another
router, we have not seen the candidate RP advertisement being generated by
the first router even though it identified the location of BSR which it
learnt through bootstrap message from BSR.

In both cases we have  ensured mrib to contain the correct routes by
manually configuring in linux kernel.

Please find the configuration  files attached.
DRconfigcase1.boot and BSRconfigcase1.boot are applicable for the first case
mentioned above and the rest are for case 2 mentioned above. 

Please help us in locating the problem.We believe that we are missing some
thing.

Thanks
-kesava and ns murthy

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20110311/3e30800d/attachment-0001.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/jpeg
Size: 11359 bytes
Desc: not available
Url : http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20110311/3e30800d/attachment-0001.jpe 

From greearb at candelatech.com  Mon Mar 14 15:25:23 2011
From: greearb at candelatech.com (Ben Greear)
Date: Mon, 14 Mar 2011 15:25:23 -0700
Subject: [Xorp-users] XORP documentation wiki is online.
Message-ID: <4D7E95D3.9070302@candelatech.com>

Hello!

I have just updated the xorp.org web site to point to the
XORP Documentation wiki that Pierre Lepropre has been working
on (I did some of it too, but he did most of it).

He is still working on some of the developer
documents, but they are already better than
what we had before and likely will be fully functional
soon.

Please let us know if you have any suggestions for
improvement..or register with the wiki and make the
improvements yourself!

http://www.xorp.org/


http://xorp.run.montefiore.ulg.ac.be/start


Thanks,
Ben

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


From pierre.lepropre at student.ulg.ac.be  Mon Mar 14 17:06:16 2011
From: pierre.lepropre at student.ulg.ac.be (Pierre Lepropre)
Date: Tue, 15 Mar 2011 01:06:16 +0100
Subject: [Xorp-users] [Xorp-hackers] XORP documentation wiki is online.
In-Reply-To: <4D7E95D3.9070302@candelatech.com>
References: <4D7E95D3.9070302@candelatech.com>
Message-ID: <1300147576.2243.11.camel@pierre-T500>

Hello guys,

As Ben said, the wiki is now officially online, feel free to browse it,
bookmark your favorite topics... and register for an account if you want
to improve the documentation !

I'd just like to thank the following people who helped me to set this
up:

*Ben for his continuous thoughtful pieces of advice and suggestions.
*Paula Gonzales for some of the mistakes she already corrected 

On Mon, 2011-03-14 at 15:25 -0700, Ben Greear wrote:
> Hello!
> 
> I have just updated the xorp.org web site to point to the
> XORP Documentation wiki that Pierre Lepropre has been working
> on (I did some of it too, but he did most of it).
> 
> He is still working on some of the developer
> documents, but they are already better than
> what we had before and likely will be fully functional
> soon.
> 
> Please let us know if you have any suggestions for
> improvement..or register with the wiki and make the
> improvements yourself!
> 
> http://www.xorp.org/
> 
> 
> http://xorp.run.montefiore.ulg.ac.be/start
> 
> 
> Thanks,
> Ben
> 



From pierre.lepropre at student.ulg.ac.be  Mon Mar 14 17:13:18 2011
From: pierre.lepropre at student.ulg.ac.be (Pierre Lepropre)
Date: Tue, 15 Mar 2011 01:13:18 +0100
Subject: [Xorp-users] [Xorp-hackers] XORP documentation wiki is online.
In-Reply-To: <4D7E95D3.9070302@candelatech.com>
References: <4D7E95D3.9070302@candelatech.com>
Message-ID: <1300147998.2243.18.camel@pierre-T500>

Hello guys,

[Sorry for the duplicate mail, this is the complete one]

As Ben said, the wiki is now officially online, feel free to browse it,
bookmark your favorite topics... and register for an account if you want
to improve the documentation !

I'd just like to thank the following people who helped me to set this
up:

*Ben Greear for his continuous thoughtful pieces of advice and
suggestions.

*Ray Soucy for providing me some useful sample configurations for the
user getting started

*Paula Gonzales for some of the mistakes she already corrected in a
pre-release stage.

*Bruno Willemaers for setting up and managing the previous (internal)
wiki, a few pages of the current wiki content is inspired by it.

*Prof. Guy Leduc for his approval and encouragement.

*Cyril Soldani, our sysadmin @ ULg for taking care of all the technical
management (I'm still the guy to contact regarding the wiki management,
don't spam him or I'll probably burn in hell in a couple of days :-) ).

Thank you for your attention and sorry again about the duplicate mail.

Cheers,

Pierre.

On Mon, 2011-03-14 at 15:25 -0700, Ben Greear wrote:
> Hello!
> 
> I have just updated the xorp.org web site to point to the
> XORP Documentation wiki that Pierre Lepropre has been working
> on (I did some of it too, but he did most of it).
> 
> He is still working on some of the developer
> documents, but they are already better than
> what we had before and likely will be fully functional
> soon.
> 
> Please let us know if you have any suggestions for
> improvement..or register with the wiki and make the
> improvements yourself!
> 
> http://www.xorp.org/
> 
> 
> http://xorp.run.montefiore.ulg.ac.be/start
> 
> 
> Thanks,
> Ben
> 



From pierre.lepropre at student.ulg.ac.be  Mon Mar 14 17:27:39 2011
From: pierre.lepropre at student.ulg.ac.be (Pierre Lepropre)
Date: Tue, 15 Mar 2011 01:27:39 +0100
Subject: [Xorp-users] [Xorp-hackers] XORP documentation wiki is online.
In-Reply-To: <1300142703.27277.11.camel@matt-desktop>
References: <4D7E95D3.9070302@candelatech.com>
	<1300142703.27277.11.camel@matt-desktop>
Message-ID: <1300148859.2243.31.camel@pierre-T500>

Hi Matthew, all,

> This is great. I have just had a look through the new documentation on
> the wiki and there are some significant updates on there that should
> make peoples introduction to XORP a lot easier. 

That was/is *the* purpose I wanted to achieve and I'm kinda happy that
you're under that impression. 

There are still a lot of things to improve, off course. But at this
point, it's more or less up to the community to improve everything else:
Ben and I can't do this alone.

> In particular the
> updated documentation for writing a process that has updated the old
> Makefile information to the latest scons processes (among other things).
> This will be especially useful to people who haven't used XORP before as
> it was one thing I struggled with a bit when first using XORP.

Yeah, about that I'd like to say something important: I'm still working
(and heavily struggling...) on it. 

There are still important missing parts. I have a lot of things to add
and to specify but I can't do it right now. Indeed, as I said in a
previous 'hacker' mail (asking a question about proc and service
status), I'm trying to write a whole new xorp sample and minimal process
from scratch.

I've been at it for a couple of days now. There are many things
undocumented, even in the source files! I have been searching a lot
through the whole project... and I'm currently stuck.

> Huge thanks to both yourself and Pierre for this. Myself and Pierre are
> both working on the ECODE project from which this has come about and
> it's good to see that it has already pushed something back into the
> community.

You're welcome, I hope it's gonna help people like me trying to get into
XORP and constantly banging their heads on the same walls !

A last thing: I don't have much time for this now but if there are guys
out there doing their own ECODE-like XORP project and would like to have
their own part of the wiki for convenience and visibility purposes, that
could be arranged.

Cheers,

Pierre.

> On Mon, 2011-03-14 at 15:25 -0700, Ben Greear wrote:
> > Hello!
> > 
> > I have just updated the xorp.org web site to point to the
> > XORP Documentation wiki that Pierre Lepropre has been working
> > on (I did some of it too, but he did most of it).
> > 
> > He is still working on some of the developer
> > documents, but they are already better than
> > what we had before and likely will be fully functional
> > soon.
> > 
> > Please let us know if you have any suggestions for
> > improvement..or register with the wiki and make the
> > improvements yourself!
> > 
> > http://www.xorp.org/
> > 
> > 
> > http://xorp.run.montefiore.ulg.ac.be/start
> > 
> > 
> > Thanks,
> > Ben
> > 
> 
> 
> _______________________________________________
> Xorp-hackers mailing list
> Xorp-hackers at icir.org
> http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-hackers



From greearb at candelatech.com  Mon Mar 14 21:04:43 2011
From: greearb at candelatech.com (Ben Greear)
Date: Mon, 14 Mar 2011 21:04:43 -0700
Subject: [Xorp-users] [Xorp-hackers] XORP documentation wiki is online.
In-Reply-To: <1300142703.27277.11.camel@matt-desktop>
References: <4D7E95D3.9070302@candelatech.com>
	<1300142703.27277.11.camel@matt-desktop>
Message-ID: <4D7EE55B.90001@candelatech.com>

On 03/14/2011 03:45 PM, Matthew Jakeman wrote:
> Hi Ben, all,
>
> This is great. I have just had a look through the new documentation on
> the wiki and there are some significant updates on there that should
> make peoples introduction to XORP a lot easier. In particular the
> updated documentation for writing a process that has updated the old
> Makefile information to the latest scons processes (among other things).
> This will be especially useful to people who haven't used XORP before as
> it was one thing I struggled with a bit when first using XORP.
>
> Huge thanks to both yourself and Pierre for this. Myself and Pierre are
> both working on the ECODE project from which this has come about and
> it's good to see that it has already pushed something back into the
> community.

The documentation help is very useful and very welcome.

I am also curious about the state of your xorp modifications.  Are
they still scheduled to be publicly released?  If so, I'd like
to try to figure out how to make them part of the official
xorp tree.  Perhaps somewhere in the contrib/ directory if
it's not general purpose code.

Thanks,
Ben

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


From greearb at candelatech.com  Mon Mar 14 21:15:56 2011
From: greearb at candelatech.com (Ben Greear)
Date: Mon, 14 Mar 2011 21:15:56 -0700
Subject: [Xorp-users] Proposal to consolidate xorp mailing lists.
Message-ID: <4D7EE7FC.7090605@candelatech.com>

I'd like to propose consolidating the mailing lists:

Proposal 1:

xorp-cvs type emails (git commit messages, basically) will go to xorp-hackers instead
and we get rid of xorp-cvs.

xorp-announce type messages (product releases, etc) can be sent to both xorp-users and xorp-hackers,
and we get rid of xorp-announce.

I think there is at least one private xorp mailing list.  I'm not sure I'm even on it,
so I think we can close it.  Private communication can be through direct email, and
at any rate, I don't see much need for an official private communication channel.

So at the end, we have:

xorp-users:  General config questions, release announcements, etc.

xorp-hackers:  Any and all code related questions, roadmap discussions, bug reports, etc.


Proposal 2:

Have a single xorp-users at xorp.org mailing list.  Any and all discussion goes there.
Archive the other mailing lists for posterity.


Any opinions?

Thanks,
Ben

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


From pierre.lepropre at student.ulg.ac.be  Tue Mar 15 01:42:02 2011
From: pierre.lepropre at student.ulg.ac.be (Pierre Lepropre)
Date: Tue, 15 Mar 2011 09:42:02 +0100
Subject: [Xorp-users] [Xorp-hackers] XORP documentation wiki is online.
In-Reply-To: <4D7EE55B.90001@candelatech.com>
References: <4D7E95D3.9070302@candelatech.com>
	<1300142703.27277.11.camel@matt-desktop>
	<4D7EE55B.90001@candelatech.com>
Message-ID: <1300178522.2357.5.camel@pierre-T500>

Dear Ben, Matthew, All,

I have no idea of what the intentions are among the ECODE partners about
that but I wondered the same thing when I started to build the wiki.

I'll ask around at my university because I'm just a guy at the bottom of
the food chain when it comes to take decision about ECODE ;-).

Regards,

Pierre.
On Mon, 2011-03-14 at 21:04 -0700, Ben Greear wrote:
> On 03/14/2011 03:45 PM, Matthew Jakeman wrote:
> > Hi Ben, all,
> >
> > This is great. I have just had a look through the new documentation on
> > the wiki and there are some significant updates on there that should
> > make peoples introduction to XORP a lot easier. In particular the
> > updated documentation for writing a process that has updated the old
> > Makefile information to the latest scons processes (among other things).
> > This will be especially useful to people who haven't used XORP before as
> > it was one thing I struggled with a bit when first using XORP.
> >
> > Huge thanks to both yourself and Pierre for this. Myself and Pierre are
> > both working on the ECODE project from which this has come about and
> > it's good to see that it has already pushed something back into the
> > community.
> 
> The documentation help is very useful and very welcome.
> 
> I am also curious about the state of your xorp modifications.  Are
> they still scheduled to be publicly released?  If so, I'd like
> to try to figure out how to make them part of the official
> xorp tree.  Perhaps somewhere in the contrib/ directory if
> it's not general purpose code.
> 
> Thanks,
> Ben
> 



From pierre.lepropre at student.ulg.ac.be  Tue Mar 15 01:38:47 2011
From: pierre.lepropre at student.ulg.ac.be (Pierre Lepropre)
Date: Tue, 15 Mar 2011 09:38:47 +0100
Subject: [Xorp-users] [Xorp-hackers] Proposal to consolidate xorp
	mailing lists.
In-Reply-To: <4D7EE7FC.7090605@candelatech.com>
References: <4D7EE7FC.7090605@candelatech.com>
Message-ID: <1300178327.2357.1.camel@pierre-T500>

I'd go for Proposal 1.

Proposal 2 will have to be canceled one day if the community gets bigger
and bigger and the only remaining ML couldn't handle the load.

Regards,

Pierre.
On Mon, 2011-03-14 at 21:15 -0700, Ben Greear wrote:
> I'd like to propose consolidating the mailing lists:
> 
> Proposal 1:
> 
> xorp-cvs type emails (git commit messages, basically) will go to xorp-hackers instead
> and we get rid of xorp-cvs.
> 
> xorp-announce type messages (product releases, etc) can be sent to both xorp-users and xorp-hackers,
> and we get rid of xorp-announce.
> 
> I think there is at least one private xorp mailing list.  I'm not sure I'm even on it,
> so I think we can close it.  Private communication can be through direct email, and
> at any rate, I don't see much need for an official private communication channel.
> 
> So at the end, we have:
> 
> xorp-users:  General config questions, release announcements, etc.
> 
> xorp-hackers:  Any and all code related questions, roadmap discussions, bug reports, etc.
> 
> 
> Proposal 2:
> 
> Have a single xorp-users at xorp.org mailing list.  Any and all discussion goes there.
> Archive the other mailing lists for posterity.
> 
> 
> Any opinions?
> 
> Thanks,
> Ben
> 



From greearb at candelatech.com  Tue Mar 15 09:23:12 2011
From: greearb at candelatech.com (Ben Greear)
Date: Tue, 15 Mar 2011 09:23:12 -0700
Subject: [Xorp-users] [Xorp-hackers] XORP documentation wiki is online.
In-Reply-To: <1300193919.6744.150.camel@matt-uni>
References: <4D7E95D3.9070302@candelatech.com>	
	<1300142703.27277.11.camel@matt-desktop>
	<4D7EE55B.90001@candelatech.com>
	<1300193919.6744.150.camel@matt-uni>
Message-ID: <4D7F9270.20005@candelatech.com>

On 03/15/2011 05:58 AM, Matthew Jakeman wrote:
> On Mon, 2011-03-14 at 21:04 -0700, Ben Greear wrote:
>> On 03/14/2011 03:45 PM, Matthew Jakeman wrote:
>>> Hi Ben, all,
>>>
>>> This is great. I have just had a look through the new documentation on
>>> the wiki and there are some significant updates on there that should
>>> make peoples introduction to XORP a lot easier. In particular the
>>> updated documentation for writing a process that has updated the old
>>> Makefile information to the latest scons processes (among other things).
>>> This will be especially useful to people who haven't used XORP before as
>>> it was one thing I struggled with a bit when first using XORP.
>>>
>>> Huge thanks to both yourself and Pierre for this. Myself and Pierre are
>>> both working on the ECODE project from which this has come about and
>>> it's good to see that it has already pushed something back into the
>>> community.
>>
>> The documentation help is very useful and very welcome.
>>
>> I am also curious about the state of your xorp modifications.  Are
>> they still scheduled to be publicly released?  If so, I'd like
>> to try to figure out how to make them part of the official
>> xorp tree.  Perhaps somewhere in the contrib/ directory if
>> it's not general purpose code.
>>
>
> We are still working on our implementation and are hoping to release the
> source code into the public domain at some point down the line.
>
> One problem we have is that because the async stuff Steven has
> implemented was not originally in XORP we have implemented our prototype
> using the original XORP code. This means that if we wanted to fully
> integrate it into XORP properly, we will have the issue of porting the
> code to the new style of coding.

This is exactly why you should merge your code early and often:
Maybe he could have used your fixes, or vice versa..and either way,
both of you might be better off.

> We will be looking at this further down the line and depending on the
> project time constraints, we will see if we can integrate it in a nice
> manner within the XORP code tree as I believe it would be a nice
> addition to have in there. Obviously it would be better overall for us
> to release the code within XORP rather than releasing our branch
> separately.
>
> We will be in touch a bit further down the line and let you know how we
> progress with these issues.

About the only guarantee is that the longer you wait, the more difficult
the merge will be.  But, it's not my decision, and I hope your plans work
out fine regardless.

Thanks,
Ben

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


From greearb at candelatech.com  Tue Mar 15 09:25:00 2011
From: greearb at candelatech.com (Ben Greear)
Date: Tue, 15 Mar 2011 09:25:00 -0700
Subject: [Xorp-users] [Xorp-hackers] Proposal to consolidate xorp
	mailing lists.
In-Reply-To: <1300178327.2357.1.camel@pierre-T500>
References: <4D7EE7FC.7090605@candelatech.com>
	<1300178327.2357.1.camel@pierre-T500>
Message-ID: <4D7F92DC.5020700@candelatech.com>

On 03/15/2011 01:38 AM, Pierre Lepropre wrote:
> I'd go for Proposal 1.
>
> Proposal 2 will have to be canceled one day if the community gets bigger
> and bigger and the only remaining ML couldn't handle the load.

You should subscribe to LKML someday :)

The consensus seems to be proposal 1, so I'll pursue that.

Thanks,
Ben

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


From rps at maine.edu  Tue Mar 15 13:56:18 2011
From: rps at maine.edu (Ray Soucy)
Date: Tue, 15 Mar 2011 16:56:18 -0400
Subject: [Xorp-users] [Xorp-hackers] XORP documentation wiki is online.
In-Reply-To: <1300147576.2243.11.camel@pierre-T500>
References: <4D7E95D3.9070302@candelatech.com>
	<1300147576.2243.11.camel@pierre-T500>
Message-ID: <AANLkTiktCuXrut3kz3eSW1g2DML0wx0AJpp_B1jhAZe5@mail.gmail.com>

Pierre,

The website for the Wiki has an IPv6 DNS record (AAAA) but it appears that
the web server is not accepting requests over IPv6.  This makes those of us
with IPv6 have to wait for a timeout with each request.

I suspect it's an IPv6 firewall oversight on the server.

Ray

On Mon, Mar 14, 2011 at 8:06 PM, Pierre Lepropre <
pierre.lepropre at student.ulg.ac.be> wrote:

> Hello guys,
>
> As Ben said, the wiki is now officially online, feel free to browse it,
> bookmark your favorite topics... and register for an account if you want
> to improve the documentation !
>
> I'd just like to thank the following people who helped me to set this
> up:
>
> *Ben for his continuous thoughtful pieces of advice and suggestions.
> *Paula Gonzales for some of the mistakes she already corrected
>
> On Mon, 2011-03-14 at 15:25 -0700, Ben Greear wrote:
> > Hello!
> >
> > I have just updated the xorp.org web site to point to the
> > XORP Documentation wiki that Pierre Lepropre has been working
> > on (I did some of it too, but he did most of it).
> >
> > He is still working on some of the developer
> > documents, but they are already better than
> > what we had before and likely will be fully functional
> > soon.
> >
> > Please let us know if you have any suggestions for
> > improvement..or register with the wiki and make the
> > improvements yourself!
> >
> > http://www.xorp.org/
> >
> >
> > http://xorp.run.montefiore.ulg.ac.be/start
> >
> >
> > Thanks,
> > Ben
> >
>
>
> _______________________________________________
> Xorp-hackers mailing list
> Xorp-hackers at icir.org
> http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-hackers
>



-- 
Ray Soucy

Epic Communications Specialist

Phone: +1 (207) 561-3526

Networkmaine, a Unit of the University of Maine System
http://www.networkmaine.net/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20110315/68801984/attachment.html 

From pierre.lepropre at student.ulg.ac.be  Tue Mar 15 15:36:28 2011
From: pierre.lepropre at student.ulg.ac.be (Pierre Lepropre)
Date: Tue, 15 Mar 2011 23:36:28 +0100
Subject: [Xorp-users] [Xorp-hackers] XORP documentation wiki is online.
In-Reply-To: <AANLkTiktCuXrut3kz3eSW1g2DML0wx0AJpp_B1jhAZe5@mail.gmail.com>
References: <4D7E95D3.9070302@candelatech.com>
	<1300147576.2243.11.camel@pierre-T500>
	<AANLkTiktCuXrut3kz3eSW1g2DML0wx0AJpp_B1jhAZe5@mail.gmail.com>
Message-ID: <1300228588.2261.2.camel@pierre-T500>

Hello Ray,

Oh I'm sorry I wasn't aware of that (as we're not using IPv6 yet at our
institution as a standard).

I can't promise you anything about that as it isn't in my power to set
these things up but I'm forwarding this mail immediately to the guy in
charge.

Hope this is going to be fixed,

Pierre.

On Tue, 2011-03-15 at 16:56 -0400, Ray Soucy wrote:
> Pierre,
> 
> 
> The website for the Wiki has an IPv6 DNS record (AAAA) but it appears
> that the web server is not accepting requests over IPv6.  This makes
> those of us with IPv6 have to wait for a timeout with each request.  
> 
> 
> I suspect it's an IPv6 firewall oversight on the server.
> 
> 
> Ray
> 
> On Mon, Mar 14, 2011 at 8:06 PM, Pierre Lepropre
> <pierre.lepropre at student.ulg.ac.be> wrote:
>         Hello guys,
>         
>         As Ben said, the wiki is now officially online, feel free to
>         browse it,
>         bookmark your favorite topics... and register for an account
>         if you want
>         to improve the documentation !
>         
>         I'd just like to thank the following people who helped me to
>         set this
>         up:
>         
>         *Ben for his continuous thoughtful pieces of advice and
>         suggestions.
>         *Paula Gonzales for some of the mistakes she already corrected
>         
>         On Mon, 2011-03-14 at 15:25 -0700, Ben Greear wrote:
>         
>         > Hello!
>         >
>         > I have just updated the xorp.org web site to point to the
>         > XORP Documentation wiki that Pierre Lepropre has been
>         working
>         > on (I did some of it too, but he did most of it).
>         >
>         > He is still working on some of the developer
>         > documents, but they are already better than
>         > what we had before and likely will be fully functional
>         > soon.
>         >
>         > Please let us know if you have any suggestions for
>         > improvement..or register with the wiki and make the
>         > improvements yourself!
>         >
>         > http://www.xorp.org/
>         >
>         >
>         > http://xorp.run.montefiore.ulg.ac.be/start
>         >
>         >
>         > Thanks,
>         > Ben
>         >
>         
>         
>         
>         
>         _______________________________________________
>         Xorp-hackers mailing list
>         Xorp-hackers at icir.org
>         http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-hackers
>         
> 
> 
> 
> -- 
> Ray Soucy
> 
> Epic Communications Specialist
> 
> Phone: +1 (207) 561-3526
> 
> Networkmaine, a Unit of the University of Maine System
> http://www.networkmaine.net/
> 



From greearb at candelatech.com  Tue Mar 15 17:08:02 2011
From: greearb at candelatech.com (Ben Greear)
Date: Tue, 15 Mar 2011 17:08:02 -0700
Subject: [Xorp-users] Any reason to keep xorp sourceforge page up?
Message-ID: <4D7FFF62.6040308@candelatech.com>

I just finished doing a crude cut-n-paste transfer of all
of the xorp sourceforge trac bugs into www.xorp.org/bugzilla.  Not the most readable
thing, but most of these bugs were opened in 2006, so maybe
they aren't so critical after all :P

Anyway, I think that was the last useful thing to get from
the xorp sourceforge page.  Unless anyone has complaints,
I'm going to try to get that project page deleted.

Thanks,
Ben

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


From B32946 at freescale.com  Tue Mar 15 22:45:24 2011
From: B32946 at freescale.com (Vunnava Kesava Srinivas-B32946)
Date: Wed, 16 Mar 2011 05:45:24 +0000
Subject: [Xorp-users] warning messages generated when the daemon xorp_rtrmgr
	is run
Message-ID: <9D8289DE2B23FA4EBC165B4CFB3718660B3EAF@039-SN1MPN1-004.039d.mgd.msft.net>

Hi,



When the following command is issued ; the floowing WARNING Messages are seen in the LOG.

Can you please explain the reason for this.



Command Used : "xorp_rtrmgr -b Multicast4.boot -l log1"



WARNING xorp_rtmgr: 5175 XrlFinderTarget +407 ../xrl/targets/finder_base.cc  handle_finder_0_2_resolve_xrl ] Handling method for finder/0.21 resolve_xrl failed: XrlCmdError 102 Command Failed Target "PIMSM_4" does not exist or is not enabled"



WARNING xorp_rtmgr: 5175 XrlFinderTarget +407 ../xrl/targets/finder_base.cc  handle_finder_0_2_resolve_xrl ] Handling method for finder/0.21 resolve_xrl failed: XrlCmdError 102 Command Failed Target "IGP" does not exist or is not enabled"



Even though these warnings appear,we could see Bootstrap messages and candidate-rp message on the network.But the routers are not able to learn from these message "which router is hosting the RP".

Ofcourse traffic is not flowing.



-kesav and ns murthy
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20110316/45c88e57/attachment.html 

From pierre.lepropre at student.ulg.ac.be  Wed Mar 16 07:52:18 2011
From: pierre.lepropre at student.ulg.ac.be (Pierre Lepropre)
Date: Wed, 16 Mar 2011 15:52:18 +0100
Subject: [Xorp-users] Wiki: IPv6 access fixed
Message-ID: <1300287138.2436.11.camel@pierre-T500>

Dear all,

As previously reported by Ray Soucy, the wiki had a native IPv6
connectivity but the firewall at our institution was being too
restrictive and causing major inconvenience for IPv6 users.

It should now have been fixed by our admin.

Please, do report any trouble of the sort if ever happens again.

My apologies,

Pierre.




From greearb at candelatech.com  Wed Mar 16 08:46:38 2011
From: greearb at candelatech.com (Ben Greear)
Date: Wed, 16 Mar 2011 08:46:38 -0700
Subject: [Xorp-users] warning messages generated when the daemon
 xorp_rtrmgr is run
In-Reply-To: <9D8289DE2B23FA4EBC165B4CFB3718660B3EAF@039-SN1MPN1-004.039d.mgd.msft.net>
References: <9D8289DE2B23FA4EBC165B4CFB3718660B3EAF@039-SN1MPN1-004.039d.mgd.msft.net>
Message-ID: <4D80DB5E.8010302@candelatech.com>

On 03/15/2011 10:45 PM, Vunnava Kesava Srinivas-B32946 wrote:
> Hi,
>
> When the following command is issued ; the floowing WARNING Messages are seen in the LOG.
>
> Can you please explain the reason for this.
>
> Command Used : "xorp_rtrmgr -b Multicast4.boot -l log1"
>
> WARNING xorp_rtmgr: 5175 XrlFinderTarget +407 ../xrl/targets/finder_base.cc handle_finder_0_2_resolve_xrl ] Handling method for finder/0.21 resolve_xrl failed:
> XrlCmdError 102 Command Failed Target "PIMSM_4" does not exist or is not enabled"
>
> WARNING xorp_rtmgr: 5175 XrlFinderTarget +407 ../xrl/targets/finder_base.cc handle_finder_0_2_resolve_xrl ] Handling method for finder/0.21 resolve_xrl failed:
> XrlCmdError 102 Command Failed Target "IGP" does not exist or is not enabled"
>
> Even though these warnings appear,we could see Bootstrap messages and candidate-rp message on the network.But the routers are not able to learn from these
> message "which router is hosting the RP".

I think these messages are not important.  I see similar messages on every boot.

Could you try using the mcast* files here:
http://www.xorp.org/config/
(edited to work with your interfaces & IPs)
to create a basic multicast configuration?  I know those config files
work.  (Tested on xorp.ct some months ago, on x86 hardware).

Thanks,
Ben


>
> Ofcourse traffic is not flowing.
>
> -kesav and ns murthy
>
>
>
> _______________________________________________
> 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 jmitchell at ll.mit.edu  Wed Mar 16 09:28:22 2011
From: jmitchell at ll.mit.edu (Jeff Mitchell)
Date: Wed, 16 Mar 2011 12:28:22 -0400
Subject: [Xorp-users] Any reason to keep xorp sourceforge page up?
In-Reply-To: <4D7FFF62.6040308@candelatech.com>
References: <4D7FFF62.6040308@candelatech.com>
Message-ID: <4D80E526.1090601@ll.mit.edu>

On 3/15/2011 8:08 PM, Ben Greear wrote:
> I just finished doing a crude cut-n-paste transfer of all
> of the xorp sourceforge trac bugs into www.xorp.org/bugzilla.  Not the most readable
> thing, but most of these bugs were opened in 2006, so maybe
> they aren't so critical after all :P
>
> Anyway, I think that was the last useful thing to get from
> the xorp sourceforge page.  Unless anyone has complaints,
> I'm going to try to get that project page deleted.

I'd recommend keeping the project in SF, even if you only post releases 
there, or use it to direct people to the official site. You never know 
when their mirrors might be handy, and sometimes project names in SF can 
end up getting linked to projects elsewhere (Google Code for instance). 
So you probably don't want to give up the name, even if you don't use it 
for anything else than that.

--Jeff


From greearb at candelatech.com  Wed Mar 16 09:39:21 2011
From: greearb at candelatech.com (Ben Greear)
Date: Wed, 16 Mar 2011 09:39:21 -0700
Subject: [Xorp-users] Any reason to keep xorp sourceforge page up?
In-Reply-To: <4D80E526.1090601@ll.mit.edu>
References: <4D7FFF62.6040308@candelatech.com> <4D80E526.1090601@ll.mit.edu>
Message-ID: <4D80E7B9.8040801@candelatech.com>

On 03/16/2011 09:28 AM, Jeff Mitchell wrote:
> On 3/15/2011 8:08 PM, Ben Greear wrote:
>> I just finished doing a crude cut-n-paste transfer of all
>> of the xorp sourceforge trac bugs into www.xorp.org/bugzilla. Not the
>> most readable
>> thing, but most of these bugs were opened in 2006, so maybe
>> they aren't so critical after all :P
>>
>> Anyway, I think that was the last useful thing to get from
>> the xorp sourceforge page. Unless anyone has complaints,
>> I'm going to try to get that project page deleted.
>
> I'd recommend keeping the project in SF, even if you only post releases
> there, or use it to direct people to the official site. You never know
> when their mirrors might be handy, and sometimes project names in SF can
> end up getting linked to projects elsewhere (Google Code for instance).
> So you probably don't want to give up the name, even if you don't use it
> for anything else than that.

I plan to use github to host the official upstream source repository
and probably downloads as well (or, might just serve downloads directly
off of www.xorp.org...it's not exactly high volume).

I'll see if I can get admin rights to the xorp sourceforge page,
and at least update it a bit.  But, I think it would be confusing to have
downloads on multiple different sites, even if I somehow managed to
keep them all perfectly synch'd, so I'll have to think on that
some more.

Thanks,
Ben

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


From greearb at candelatech.com  Wed Mar 16 09:59:10 2011
From: greearb at candelatech.com (Ben Greear)
Date: Wed, 16 Mar 2011 09:59:10 -0700
Subject: [Xorp-users] warning messages generated when the daemon
 xorp_rtrmgr is run
In-Reply-To: <FED3BA17D900324AA9CB1B85F22B8DB80CEF00@039-SN1MPN1-004.039d.mgd.msft.net>
References: <9D8289DE2B23FA4EBC165B4CFB3718660B3EAF@039-SN1MPN1-004.039d.mgd.msft.net>
	<4D80DB5E.8010302@candelatech.com>
	<FED3BA17D900324AA9CB1B85F22B8DB80CEF00@039-SN1MPN1-004.039d.mgd.msft.net>
Message-ID: <4D80EC5E.90809@candelatech.com>

On 03/16/2011 09:39 AM, Murthy N Srinivas-B22237 wrote:
>
> I have seen the file multicast4.boot.It looks similar to the file we used.
>
> In our case it works with static RPs.
>
> But is not working with BSR and candidate RP on the same router.
> Similarrly it does not work when BSR and cadidate RP are on different machines.
> In the second case,the candidate RP advertisements are observed on sniffer.
> But somehow the machines are not able to learn RP dynamically.
> Boot strap messages are also observed on sniffer which contain the information related to RPs.
> In both cases no data traffic is observed.

The files I tested (and created) are.  They are using BSD and RP on
the same router, as far as I can tell:

ospf-mcast-diag.pdf
ospf-mcast-router1.conf
ospf-mcast-router2.conf

What hardware platform are you using?

Can you post a network diagram and all the xorp config files for
each system?  I'll see if I can reproduce the problem on my
setup.  Or, if you've posted this in the past, let me know
when and I'll dig through my email.

Thanks,
Ben

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


From greearb at candelatech.com  Wed Mar 16 10:22:15 2011
From: greearb at candelatech.com (Ben Greear)
Date: Wed, 16 Mar 2011 10:22:15 -0700
Subject: [Xorp-users] warning messages generated when the daemon
 xorp_rtrmgr is run
In-Reply-To: <FED3BA17D900324AA9CB1B85F22B8DB80CEF5E@039-SN1MPN1-004.039d.mgd.msft.net>
References: <9D8289DE2B23FA4EBC165B4CFB3718660B3EAF@039-SN1MPN1-004.039d.mgd.msft.net>
	<4D80DB5E.8010302@candelatech.com>
	<FED3BA17D900324AA9CB1B85F22B8DB80CEF00@039-SN1MPN1-004.039d.mgd.msft.net>
	<4D80EC5E.90809@candelatech.com>
	<FED3BA17D900324AA9CB1B85F22B8DB80CEF5E@039-SN1MPN1-004.039d.mgd.msft.net>
Message-ID: <4D80F1C7.1040005@candelatech.com>

On 03/16/2011 10:16 AM, Murthy N Srinivas-B22237 wrote:
> Our hardware is based on Freescale P2020 processors.P2020 is a big endian processor.
> We have not enabled any unicast routing protocol.We added static routes to linux kernel 2.6.32.
> I will send the other details tomorrow morning.

Please test the same configuration on x86.  It's possible there
are endian or cross-compile issues.  If it works on x86 and not on ARM, then
we know it's a compile issue (could be structure alignment
issues or similar, as well).  If it's equally broken on
both, then it's probably a logical issue with the code.

I don't have any ARM hardware to test on.  Is your hardware
platform available somewhere?

Thanks,
Ben

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


From greearb at candelatech.com  Wed Mar 16 10:53:56 2011
From: greearb at candelatech.com (Ben Greear)
Date: Wed, 16 Mar 2011 10:53:56 -0700
Subject: [Xorp-users] warning messages generated when the daemon
 xorp_rtrmgr is run
In-Reply-To: <FED3BA17D900324AA9CB1B85F22B8DB80CEF5E@039-SN1MPN1-004.039d.mgd.msft.net>
References: <9D8289DE2B23FA4EBC165B4CFB3718660B3EAF@039-SN1MPN1-004.039d.mgd.msft.net>
	<4D80DB5E.8010302@candelatech.com>
	<FED3BA17D900324AA9CB1B85F22B8DB80CEF00@039-SN1MPN1-004.039d.mgd.msft.net>
	<4D80EC5E.90809@candelatech.com>
	<FED3BA17D900324AA9CB1B85F22B8DB80CEF5E@039-SN1MPN1-004.039d.mgd.msft.net>
Message-ID: <4D80F934.6020902@candelatech.com>

On 03/16/2011 10:16 AM, Murthy N Srinivas-B22237 wrote:
> Our hardware is based on Freescale P2020 processors.P2020 is a big endian processor.
> We have not enabled any unicast routing protocol.We added static routes to linux kernel 2.6.32.
> I will send the other details tomorrow morning.

Also, you might try using a later linux kernel.  There have been bugs in it's ARM
networking code in the past, but I don't remember which kernel had the issues.

Thanks,
Ben

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


From greearb at candelatech.com  Thu Mar 17 00:14:12 2011
From: greearb at candelatech.com (Ben Greear)
Date: Thu, 17 Mar 2011 00:14:12 -0700
Subject: [Xorp-users] Release 1.8.3 is almost done, please test
Message-ID: <4D81B4C4.3060601@candelatech.com>

I've uploaded xorp 1.8.3 builds to xorp.org:

http://www.xorp.org/releases/1.8.3/

There are RPMs for recent Fedora, binary builds for all sorts of Fedora
and similar OSs, and source tarball.

If anyone can give these some quick testing to basically verify the
build and packaging scripts, that would be great help!

The naming could perhaps be better, so let me know if you think of
something that makes more sense.

I'll push these on to github and maybe sourceforge tomorrow if all
goes well.

Thanks,
Ben

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


From B32946 at freescale.com  Thu Mar 17 00:23:39 2011
From: B32946 at freescale.com (Vunnava Kesava Srinivas-B32946)
Date: Thu, 17 Mar 2011 07:23:39 +0000
Subject: [Xorp-users] warning messages generated when the daemon
 xorp_rtrmgr is run
In-Reply-To: <4D80F1C7.1040005@candelatech.com>
References: <9D8289DE2B23FA4EBC165B4CFB3718660B3EAF@039-SN1MPN1-004.039d.mgd.msft.net>
	<4D80DB5E.8010302@candelatech.com>
	<FED3BA17D900324AA9CB1B85F22B8DB80CEF00@039-SN1MPN1-004.039d.mgd.msft.net>
	<4D80EC5E.90809@candelatech.com>
	<FED3BA17D900324AA9CB1B85F22B8DB80CEF5E@039-SN1MPN1-004.039d.mgd.msft.net>,
	<4D80F1C7.1040005@candelatech.com>
Message-ID: <9D8289DE2B23FA4EBC165B4CFB3718660BB429@039-SN1MPN1-004.039d.mgd.msft.net>


Please find the config files and the network diagram attached.
We used them for our testing.

Thanks
-ns murthy and kesav
________________________________________
From: Ben Greear [greearb at candelatech.com]
Sent: 16 March 2011 22:52:15
To: Murthy N Srinivas-B22237
Cc: Vunnava Kesava Srinivas-B32946; xorp-users at xorp.org
Subject: Re: [Xorp-users] warning messages generated when the daemon xorp_rtrmgr is run

On 03/16/2011 10:16 AM, Murthy N Srinivas-B22237 wrote:
> Our hardware is based on Freescale P2020 processors.P2020 is a big endian processor.
> We have not enabled any unicast routing protocol.We added static routes to linux kernel 2.6.32.
> I will send the other details tomorrow morning.

Please test the same configuration on x86.  It's possible there
are endian or cross-compile issues.  If it works on x86 and not on ARM, then
we know it's a compile issue (could be structure alignment
issues or similar, as well).  If it's equally broken on
both, then it's probably a logical issue with the code.

I don't have any ARM hardware to test on.  Is your hardware
platform available somewhere?

Thanks,
Ben

--
Ben Greear <greearb at candelatech.com>
Candela Technologies Inc  http://www.candelatech.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: BSRConfig.boot
Type: application/octet-stream
Size: 1327 bytes
Desc: BSRConfig.boot
Url : http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20110317/1729ed39/attachment.obj 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Cand-rp.boot
Type: application/octet-stream
Size: 1548 bytes
Desc: Cand-rp.boot
Url : http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20110317/1729ed39/attachment-0001.obj 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Network.docx
Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document
Size: 11647 bytes
Desc: Network.docx
Url : http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20110317/1729ed39/attachment.bin 

From greearb at candelatech.com  Thu Mar 17 08:04:29 2011
From: greearb at candelatech.com (Ben Greear)
Date: Thu, 17 Mar 2011 08:04:29 -0700
Subject: [Xorp-users] warning messages generated when the daemon
 xorp_rtrmgr is run
In-Reply-To: <9D8289DE2B23FA4EBC165B4CFB3718660BB429@039-SN1MPN1-004.039d.mgd.msft.net>
References: <9D8289DE2B23FA4EBC165B4CFB3718660B3EAF@039-SN1MPN1-004.039d.mgd.msft.net>
	<4D80DB5E.8010302@candelatech.com>
	<FED3BA17D900324AA9CB1B85F22B8DB80CEF00@039-SN1MPN1-004.039d.mgd.msft.net>
	<4D80EC5E.90809@candelatech.com>
	<FED3BA17D900324AA9CB1B85F22B8DB80CEF5E@039-SN1MPN1-004.039d.mgd.msft.net>,
	<4D80F1C7.1040005@candelatech.com>
	<9D8289DE2B23FA4EBC165B4CFB3718660BB429@039-SN1MPN1-004.039d.mgd.msft.net>
Message-ID: <4D8222FD.90809@candelatech.com>

On 03/17/2011 12:23 AM, Vunnava Kesava Srinivas-B32946 wrote:
>
> Please find the config files and the network diagram attached.
> We used them for our testing.

Did you test the same config on x86?

Thanks,
Ben

>
> Thanks
> -ns murthy and kesav
> ________________________________________
> From: Ben Greear [greearb at candelatech.com]
> Sent: 16 March 2011 22:52:15
> To: Murthy N Srinivas-B22237
> Cc: Vunnava Kesava Srinivas-B32946; xorp-users at xorp.org
> Subject: Re: [Xorp-users] warning messages generated when the daemon xorp_rtrmgr is run
>
> On 03/16/2011 10:16 AM, Murthy N Srinivas-B22237 wrote:
>> Our hardware is based on Freescale P2020 processors.P2020 is a big endian processor.
>> We have not enabled any unicast routing protocol.We added static routes to linux kernel 2.6.32.
>> I will send the other details tomorrow morning.
>
> Please test the same configuration on x86.  It's possible there
> are endian or cross-compile issues.  If it works on x86 and not on ARM, then
> we know it's a compile issue (could be structure alignment
> issues or similar, as well).  If it's equally broken on
> both, then it's probably a logical issue with the code.
>
> I don't have any ARM hardware to test on.  Is your hardware
> platform available somewhere?
>
> Thanks,
> Ben
>
> --
> Ben Greear<greearb at candelatech.com>
> Candela Technologies Inc  http://www.candelatech.com


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


From greearb at candelatech.com  Thu Mar 17 10:23:35 2011
From: greearb at candelatech.com (Ben Greear)
Date: Thu, 17 Mar 2011 10:23:35 -0700
Subject: [Xorp-users] warning messages generated when the daemon
 xorp_rtrmgr is run
In-Reply-To: <FED3BA17D900324AA9CB1B85F22B8DB80D6AAA@039-SN1MPN1-004.039d.mgd.msft.net>
References: <9D8289DE2B23FA4EBC165B4CFB3718660B3EAF@039-SN1MPN1-004.039d.mgd.msft.net>
	<4D80DB5E.8010302@candelatech.com>
	<FED3BA17D900324AA9CB1B85F22B8DB80CEF00@039-SN1MPN1-004.039d.mgd.msft.net>
	<4D80EC5E.90809@candelatech.com>
	<FED3BA17D900324AA9CB1B85F22B8DB80CEF5E@039-SN1MPN1-004.039d.mgd.msft.net>,
	<4D80F1C7.1040005@candelatech.com>
	<9D8289DE2B23FA4EBC165B4CFB3718660BB429@039-SN1MPN1-004.039d.mgd.msft.net>
	<4D8222FD.90809@candelatech.com>
	<FED3BA17D900324AA9CB1B85F22B8DB80D6AAA@039-SN1MPN1-004.039d.mgd.msft.net>
Message-ID: <4D824397.4050109@candelatech.com>

On 03/17/2011 10:15 AM, Murthy N Srinivas-B22237 wrote:
> No.Due to resource and other constraints we have not so far tested on X86.

Well, I am trying to reproduce it now, but I'm not going to spend
much time on it.  If you want me to do that kind of work, I'll
do it for hire, but you can't expect others to do this sort of thing
for free:  When you are bringing up a proprietary system on proprietary
hardware, with some strange cross-compiler you found somewhere, it
becomes almost impossible for anyone else to replicate your environment
for testing.

That means you need to reproduce the problem on a platform that we *can*
easily test on.  And, you need to make sure that the problem is in the
code itself, and not with your kernel, hardware, cross-compiler, etc.
That is why I think you should spend the resources and deal with
the constraints so that you can test on x86.  It's not overly
difficult or expensive to do this...

Thanks,
Ben


>
> -ns murthy
>
> -----Original Message-----
> From: Ben Greear [mailto:greearb at candelatech.com]
> Sent: Thursday, March 17, 2011 8:34 PM
> To: Vunnava Kesava Srinivas-B32946
> Cc: Murthy N Srinivas-B22237; xorp-users at xorp.org
> Subject: Re: [Xorp-users] warning messages generated when the daemon xorp_rtrmgr is run
>
> On 03/17/2011 12:23 AM, Vunnava Kesava Srinivas-B32946 wrote:
>>
>> Please find the config files and the network diagram attached.
>> We used them for our testing.
>
> Did you test the same config on x86?
>
> Thanks,
> Ben
>
>>
>> Thanks
>> -ns murthy and kesav
>> ________________________________________
>> From: Ben Greear [greearb at candelatech.com]
>> Sent: 16 March 2011 22:52:15
>> To: Murthy N Srinivas-B22237
>> Cc: Vunnava Kesava Srinivas-B32946; xorp-users at xorp.org
>> Subject: Re: [Xorp-users] warning messages generated when the daemon
>> xorp_rtrmgr is run
>>
>> On 03/16/2011 10:16 AM, Murthy N Srinivas-B22237 wrote:
>>> Our hardware is based on Freescale P2020 processors.P2020 is a big endian processor.
>>> We have not enabled any unicast routing protocol.We added static routes to linux kernel 2.6.32.
>>> I will send the other details tomorrow morning.
>>
>> Please test the same configuration on x86.  It's possible there are
>> endian or cross-compile issues.  If it works on x86 and not on ARM,
>> then we know it's a compile issue (could be structure alignment issues
>> or similar, as well).  If it's equally broken on both, then it's
>> probably a logical issue with the code.
>>
>> I don't have any ARM hardware to test on.  Is your hardware platform
>> available somewhere?
>>
>> Thanks,
>> Ben
>>
>> --
>> Ben Greear<greearb at candelatech.com>
>> Candela Technologies Inc  http://www.candelatech.com
>
>
> --
> Ben Greear<greearb at candelatech.com>
> Candela Technologies Inc  http://www.candelatech.com
>


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


From greearb at candelatech.com  Thu Mar 17 15:38:32 2011
From: greearb at candelatech.com (Ben Greear)
Date: Thu, 17 Mar 2011 15:38:32 -0700
Subject: [Xorp-users] warning messages generated when the daemon
 xorp_rtrmgr is run
In-Reply-To: <FED3BA17D900324AA9CB1B85F22B8DB80D6ADE@039-SN1MPN1-004.039d.mgd.msft.net>
References: <9D8289DE2B23FA4EBC165B4CFB3718660B3EAF@039-SN1MPN1-004.039d.mgd.msft.net>
	<4D80DB5E.8010302@candelatech.com>
	<FED3BA17D900324AA9CB1B85F22B8DB80CEF00@039-SN1MPN1-004.039d.mgd.msft.net>
	<4D80EC5E.90809@candelatech.com>
	<FED3BA17D900324AA9CB1B85F22B8DB80CEF5E@039-SN1MPN1-004.039d.mgd.msft.net>,
	<4D80F1C7.1040005@candelatech.com>
	<9D8289DE2B23FA4EBC165B4CFB3718660BB429@039-SN1MPN1-004.039d.mgd.msft.net>
	<4D8222FD.90809@candelatech.com>
	<FED3BA17D900324AA9CB1B85F22B8DB80D6AAA@039-SN1MPN1-004.039d.mgd.msft.net>
	<4D824397.4050109@candelatech.com>
	<FED3BA17D900324AA9CB1B85F22B8DB80D6ADE@039-SN1MPN1-004.039d.mgd.msft.net>
Message-ID: <4D828D68.5020804@candelatech.com>

I couldn't get your config files to work on x86.  Probably
because you don't have cand-bsr and cand-rp entries in both
config files?

The attached files for a similar configuration do work
for me, however.  I have the cand-bsr and cand-rp sections
in each config file.

Thanks,
Ben

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

-------------- next part --------------
A non-text attachment was scrubbed...
Name: static-mcast-bootstrap-diagram.png
Type: image/png
Size: 17265 bytes
Desc: not available
Url : http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20110317/8b6d0c00/attachment-0001.bin 
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: static-mcast-bootstrap-r1.conf
Url: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20110317/8b6d0c00/attachment-0002.ksh 
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: static-mcast-bootstrap-r2.conf
Url: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20110317/8b6d0c00/attachment-0003.ksh 

From greearb at candelatech.com  Thu Mar 17 19:09:23 2011
From: greearb at candelatech.com (Ben Greear)
Date: Thu, 17 Mar 2011 19:09:23 -0700
Subject: [Xorp-users] warning messages generated when the daemon
 xorp_rtrmgr is run
In-Reply-To: <FED3BA17D900324AA9CB1B85F22B8DB80D6B8F@039-SN1MPN1-004.039d.mgd.msft.net>
References: <9D8289DE2B23FA4EBC165B4CFB3718660B3EAF@039-SN1MPN1-004.039d.mgd.msft.net>
	<4D80DB5E.8010302@candelatech.com>
	<FED3BA17D900324AA9CB1B85F22B8DB80CEF00@039-SN1MPN1-004.039d.mgd.msft.net>
	<4D80EC5E.90809@candelatech.com>
	<FED3BA17D900324AA9CB1B85F22B8DB80CEF5E@039-SN1MPN1-004.039d.mgd.msft.net>,
	<4D80F1C7.1040005@candelatech.com>
	<9D8289DE2B23FA4EBC165B4CFB3718660BB429@039-SN1MPN1-004.039d.mgd.msft.net>
	<4D8222FD.90809@candelatech.com>
	<FED3BA17D900324AA9CB1B85F22B8DB80D6AAA@039-SN1MPN1-004.039d.mgd.msft.net>
	<4D824397.4050109@candelatech.com>
	<FED3BA17D900324AA9CB1B85F22B8DB80D6ADE@039-SN1MPN1-004.039d.mgd.msft.net>
	<4D828D68.5020804@candelatech.com>
	<FED3BA17D900324AA9CB1B85F22B8DB80D6B8F@039-SN1MPN1-004.039d.mgd.msft.net>
Message-ID: <4D82BED3.9070309@candelatech.com>

On 03/17/2011 07:00 PM, Murthy N Srinivas-B22237 wrote:
> Thnaks for your help. It looks odd to have can-bsr and can-rp entries in each m-router in the network.
> We tried this too but did not work.

It takes a minute or two on startup before the mcast traffic passes in my
tests, but after things normalize, it passes fine.

That is the configuration I use for our virtual router network,
and it will handle dropped network links and other disturbances
(using OSPF to re-build routing trees as needed).

As always with multicast, make sure your transmitter has
a big enough TTL to get through your network.

Thanks,
Ben

>
> -ns murthy
>
> -----Original Message-----
> From: Ben Greear [mailto:greearb at candelatech.com]
> Sent: Friday, March 18, 2011 4:09 AM
> To: Murthy N Srinivas-B22237
> Cc: Vunnava Kesava Srinivas-B32946; xorp-users at xorp.org
> Subject: Re: [Xorp-users] warning messages generated when the daemon xorp_rtrmgr is run
>
> I couldn't get your config files to work on x86.  Probably because you don't have cand-bsr and cand-rp entries in both config files?
>
> The attached files for a similar configuration do work for me, however.  I have the cand-bsr and cand-rp sections in each config file.
>
> Thanks,
> Ben
>
> --
> Ben Greear<greearb at candelatech.com>
> Candela Technologies Inc  http://www.candelatech.com
>


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


From wxh585 at 126.com  Mon Mar 21 19:43:06 2011
From: wxh585 at 126.com (wxh585 at 126.com)
Date: Tue, 22 Mar 2011 10:43:06 +0800 (CST)
Subject: [Xorp-users] xorp 1.83 is not config on debian 5
Message-ID: <72151d60.e75b.12edb71b7cf.Coremail.wxh585@126.com>

admin at 55> show version
Version 1.8.3
admin at 55> configure
Entering configuration mode.
There are no other users in configuration mode.
[edit]
admin at 55# show -all
    interfaces {
        restore-original-config-on-shutdown: false
        interface eth3 {
            description: ""
            disable: false
            discard: false
            unreachable: false
            management: false
            parent-ifname: ""
            iface-type: ""
            vid: ""
            default-system-config {
            }
        }
    }
[edit]
admin at 55# set interfaces interface eth3.5 parent-ifname eth3
[edit]
admin at 55# set interfaces interface eth3.5 vid 5
[edit]
admin at 55# set interfaces interface eth3.5 iface-type VLAN
[edit]
admin at 55# commit
Commit Failed
102 Command failed  push_config failed: Interface/Vif error on eth3.5/eth3.5: Failed to add VLAN to interface eth3.5  reason: Failed to add VLAN 5 to interface eth3: Cannot create VLAN interface eth3.5 (parent = eth3 VLAN ID = 5): Network is down
[edit]
admin at 55#




--


???

???13312601392
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20110322/9c14ec05/attachment.html 

From greearb at candelatech.com  Mon Mar 21 21:13:04 2011
From: greearb at candelatech.com (Ben Greear)
Date: Mon, 21 Mar 2011 21:13:04 -0700
Subject: [Xorp-users] xorp 1.83 is not config on debian 5
In-Reply-To: <72151d60.e75b.12edb71b7cf.Coremail.wxh585@126.com>
References: <72151d60.e75b.12edb71b7cf.Coremail.wxh585@126.com>
Message-ID: <4D8821D0.9040901@candelatech.com>

On 03/21/2011 07:43 PM, wxh585 at 126.com wrote:
> admin at 55 <mailto:admin at 55>> show version
> Version 1.8.3
> admin at 55 <mailto:admin at 55>> configure
> Entering configuration mode.
> There are no other users in configuration mode.
> [edit]
> admin at 55 <mailto:admin at 55># show -all
> interfaces {
> restore-original-config-on-shutdown: false
> interface eth3 {
> description: ""
> disable: false
> discard: false
> unreachable: false
> management: false
> parent-ifname: ""
> iface-type: ""
> vid: ""
> default-system-config {
> }
> }
> }
> [edit]
> admin at 55 <mailto:admin at 55># set interfaces interface eth3.5 parent-ifname eth3
> [edit]
> admin at 55 <mailto:admin at 55># set interfaces interface eth3.5 vid 5
> [edit]
> admin at 55 <mailto:admin at 55># set interfaces interface eth3.5 iface-type VLAN
> [edit]
> admin at 55 <mailto:admin at 55># commit
> Commit Failed
> 102 Command failed push_config failed: Interface/Vif error on eth3.5/eth3.5: Failed to add VLAN to interface eth3.5 reason: Failed to add VLAN 5 to interface
> eth3: Cannot create VLAN interface eth3.5 (parent = eth3 VLAN ID = 5): Network is down
> [edit]
> admin at 55 <mailto:admin at 55>#

Thanks, I'll try to reproduce that.

Can you check outside of xorp to see if eth3 is UP?

Does this work if you explicitly set the IP instead of using default-system-config?

Thanks,
Ben

>
>
>
> --
>
> ??????
>
> ??????13312601392
>
>
>
>
>
> _______________________________________________
> 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 wxh585 at 126.com  Mon Mar 21 23:18:42 2011
From: wxh585 at 126.com (wxh585 at 126.com)
Date: Tue, 22 Mar 2011 14:18:42 +0800 (CST)
Subject: [Xorp-users] xorp is not auto start when system up,
 after config vlan , but no config vlan , it is auto work , for debian 5
Message-ID: <472ef349.110d4.12edc371cf6.Coremail.wxh585@126.com>





--


???

???13312601392
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20110322/f754545e/attachment.html 

From greearb at candelatech.com  Tue Mar 22 13:53:28 2011
From: greearb at candelatech.com (Ben Greear)
Date: Tue, 22 Mar 2011 13:53:28 -0700
Subject: [Xorp-users] xorp is not auto start when system up,
 after config vlan , but no config vlan , it is auto work , for debian 5
In-Reply-To: <472ef349.110d4.12edc371cf6.Coremail.wxh585@126.com>
References: <472ef349.110d4.12edc371cf6.Coremail.wxh585@126.com>
Message-ID: <4D890C48.4000702@candelatech.com>

On 03/21/2011 11:18 PM, wxh585 at 126.com wrote:
>
>

I tested this, and it works for me.  I used 'eth0', which
I am certain is UP before xorp starts.

I also made some modifications to the xorp start script,
but they are mostly cosmetic.

Thanks,
Ben

>
> --
>
> ??????
>
> ??????13312601392
>
>
>
>
>
> _______________________________________________
> 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  Tue Mar 22 15:33:35 2011
From: greearb at candelatech.com (Ben Greear)
Date: Tue, 22 Mar 2011 15:33:35 -0700
Subject: [Xorp-users] XORP 1.8.3 is officially released.
Message-ID: <4D8923BF.30606@candelatech.com>

I have uploaded the official XORP 1.8.3 packages to various
places:

https://sourceforge.net/projects/xorp/files/xorp/1.8.3/
https://github.com/greearb/xorp.ct/downloads
http://www.xorp.org/releases/1.8.3/

I uploaded a large number of pre-compiled binaries for various
systems.  I'm not sure if that helps or hinders.

Please let me know if you find any troubles, broken links
on the web page, etc.

Release 1.8.3 (March 16, 2011)

    *  Change the way VLANs are created.  This changes the config
       file syntax (though the original syntax didn't actually work
       right..so probably no one is actually using it.)

    *  Re-add support for XORP on Microsoft Windows.  Add instructions
       to BUILD_NOTES for cross-compiling with mingw.

    *  Add more options for disabling compile of certain modules.
       See:  scons --help

    *  Add support for IPv6 multicast with virtual routing tables.
       Requires Linux kernel 2.6.35 or higher.

    *  Support compiling with clang + llvm compiler:
       Install latest clang and llvm from their SVN repositories and:
       scons CC=clang CXX=clang++

    *  Add some changes to make it easier to support uSTL, but it does not
       actually work as uSTL had too many limitations and bugs, and didn't seem
       to gain much space improvements anyway.
       See BUILD_NOTES for more info.

    *  Support cross-compiling.  See BUILD_NOTES.

    *  BSD:  Don't crash FEA when interface disappears.

    *  BSD:  Don't fail commit if cannot remove route that doesn't exist.

    *  Add signal handling for more graceful exit.  Helps clean up /var/tmp/xrl.*
       files and lets valgrind report more useful information.

    *  timers:  Fix memory leak related to the Heap class.

    *  BGP:  Fix up tear-down logic to make sure it exits promptly in
       all cases.

    *  pim: Fix a recursive delete issue in pim code, exposed by the ability to
       gracefully shut down processes with SIGTERM.

    *  rtrmgr:  Allow starting helper processes under valgrind.  Just
       create a file called XORP_USE_VALGRIND in the working directory.
       If you want xorp_rtrmgr to use valgrind, you have to start it under
       valgrind manually.

    *  FEA:  Properly clean up all sockets and remove them from the eventloop
       callback when cleaing up io_ip_socket objects.

    *  firewall:  Support compiling netlink firewall support on Linux, if
       kernel headers are properly modified to compile with c++.

Thanks,
Ben

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


From b.mccarthy at lancaster.ac.uk  Tue Mar 22 16:49:36 2011
From: b.mccarthy at lancaster.ac.uk (Ben McCarthy)
Date: Tue, 22 Mar 2011 23:49:36 -0000
Subject: [Xorp-users] XORP on OpenWRT
Message-ID: <1f6e01cbe8eb$ccf5cad0$66e16070$@mccarthy@lancaster.ac.uk>

Hi,

 

Has anyone here ever successfully compiled XORP for OpenWRT? I have looked
around on the Internet for examples of success stories but can't find any.

 

It would be useful to be able to add XORP's multicast functionality to
OpenWRT platforms.

 

Cheers,

 

Ben

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

From greearb at candelatech.com  Tue Mar 22 16:50:04 2011
From: greearb at candelatech.com (Ben Greear)
Date: Tue, 22 Mar 2011 16:50:04 -0700
Subject: [Xorp-users] XORP on OpenWRT
In-Reply-To: <1f6e01cbe8eb$ccf5cad0$66e16070$@mccarthy@lancaster.ac.uk>
References: <1f6e01cbe8eb$ccf5cad0$66e16070$@mccarthy@lancaster.ac.uk>
Message-ID: <4D8935AC.20903@candelatech.com>

On 03/22/2011 04:49 PM, Ben McCarthy wrote:
> Hi,
>
> Has anyone here ever successfully compiled XORP for OpenWRT? I have
> looked around on the Internet for examples of success stories but can?t
> find any.
>
> It would be useful to be able to add XORP?s multicast functionality to
> OpenWRT platforms.

How much RAM and disk storage do you have?  Even when you strip out
most of xorp it is still fairly large.

If you do try it, please let us know how it goes.

Thanks,
Ben

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


From b.mccarthy at lancaster.ac.uk  Tue Mar 22 17:07:40 2011
From: b.mccarthy at lancaster.ac.uk (Ben McCarthy)
Date: Wed, 23 Mar 2011 00:07:40 -0000
Subject: [Xorp-users] XORP on OpenWRT
In-Reply-To: <4D8935AC.20903@candelatech.com>
References: <1f6e01cbe8eb$ccf5cad0$66e16070$@mccarthy@lancaster.ac.uk>
	<4D8935AC.20903@candelatech.com>
Message-ID: <1f7901cbe8ee$52fc2d70$f8f48850$@mccarthy@lancaster.ac.uk>

I use Ubiquiti Router Station Pro boards:

http://www.ubnt.com/wiki/RouterStation_Pro

They have 128Mb RAM and an SD card slot for storage. I would have thought
they'd be able to manage quite well, do you think that's enough resources?

I'll let you know if I get the chance to try it out.

Cheers,

Ben

> -----Original Message-----
> From: Ben Greear [mailto:greearb at candelatech.com]
> Sent: 22 March 2011 23:50
> To: Ben McCarthy
> Cc: xorp-users at xorp.org
> Subject: Re: [Xorp-users] XORP on OpenWRT
> 
> On 03/22/2011 04:49 PM, Ben McCarthy wrote:
> > Hi,
> >
> > Has anyone here ever successfully compiled XORP for OpenWRT? I have
> > looked around on the Internet for examples of success stories but
> can't
> > find any.
> >
> > It would be useful to be able to add XORP's multicast functionality
> to
> > OpenWRT platforms.
> 
> How much RAM and disk storage do you have?  Even when you strip out
> most of xorp it is still fairly large.
> 
> If you do try it, please let us know how it goes.
> 
> Thanks,
> Ben
> 
> --
> Ben Greear <greearb at candelatech.com>
> Candela Technologies Inc  http://www.candelatech.com


From greearb at candelatech.com  Tue Mar 22 17:05:31 2011
From: greearb at candelatech.com (Ben Greear)
Date: Tue, 22 Mar 2011 17:05:31 -0700
Subject: [Xorp-users] XORP on OpenWRT
In-Reply-To: <1f7901cbe8ee$52fc2d70$f8f48850$@mccarthy@lancaster.ac.uk>
References: <1f6e01cbe8eb$ccf5cad0$66e16070$@mccarthy@lancaster.ac.uk>
	<4D8935AC.20903@candelatech.com>
	<1f7901cbe8ee$52fc2d70$f8f48850$@mccarthy@lancaster.ac.uk>
Message-ID: <4D89394B.30504@candelatech.com>

On 03/22/2011 05:07 PM, Ben McCarthy wrote:
> I use Ubiquiti Router Station Pro boards:
>
> http://www.ubnt.com/wiki/RouterStation_Pro
>
> They have 128Mb RAM and an SD card slot for storage. I would have thought
> they'd be able to manage quite well, do you think that's enough resources?

Maybe, hard to say exactly.  You'll definately want to
disable most protocols and perhaps the tracing and logging
too.  See:  scons --help for various things you can enable/disable.

> I'll let you know if I get the chance to try it out.

Thanks,
Ben

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


From outbackdingo at gmail.com  Tue Mar 22 17:53:36 2011
From: outbackdingo at gmail.com (Outback Dingo)
Date: Tue, 22 Mar 2011 20:53:36 -0400
Subject: [Xorp-users] XORP on OpenWRT
In-Reply-To: <-2251785492491213777@unknownmsgid>
References: <4D8935AC.20903@candelatech.com>
	<-2251785492491213777@unknownmsgid>
Message-ID: <AANLkTikmTKkqW-mjbMOobOp45666n0KO__q80V63eRxp@mail.gmail.com>

On Tue, Mar 22, 2011 at 8:07 PM, Ben McCarthy <b.mccarthy at lancaster.ac.uk>wrote:

> I use Ubiquiti Router Station Pro boards:
>
> http://www.ubnt.com/wiki/RouterStation_Pro
>
> They have 128Mb RAM and an SD card slot for storage. I would have thought
> they'd be able to manage quite well, do you think that's enough resources?
>
> I'll let you know if I get the chance to try it out.
>

you might also want to get on the OpenWRT lists...... might be more info
from the users their, though im curious what your trying to accomplish



> Cheers,
>
> Ben
>
> > -----Original Message-----
> > From: Ben Greear [mailto:greearb at candelatech.com]
> > Sent: 22 March 2011 23:50
> > To: Ben McCarthy
> > Cc: xorp-users at xorp.org
> > Subject: Re: [Xorp-users] XORP on OpenWRT
> >
> > On 03/22/2011 04:49 PM, Ben McCarthy wrote:
> > > Hi,
> > >
> > > Has anyone here ever successfully compiled XORP for OpenWRT? I have
> > > looked around on the Internet for examples of success stories but
> > can't
> > > find any.
> > >
> > > It would be useful to be able to add XORP's multicast functionality
> > to
> > > OpenWRT platforms.
> >
> > How much RAM and disk storage do you have?  Even when you strip out
> > most of xorp it is still fairly large.
> >
> > If you do try it, please let us know how it goes.
> >
> > Thanks,
> > Ben
> >
> > --
> > 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
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20110322/123ea573/attachment.html