mpls-linux-devel — Mailig list for discussing the development of MPLS on Linux

Re: [mpls-linux-devel] A few problems with ldpd

[James R. L. <jl...@mi...>]

Good stuff.  Thank you for working with ldp-portable and taking the
time to dig into the code.  I've incorporated your fixes for the memory
leaks and I'm double checking the byte order fix you suggest.

As far as the multiple session issue, I think the fix is to never
send any 127.0.0.0/8 addresses in the address message.  One way to
accomplish this is to never register 127.0.0.0/8 addresses with
LDP by modifing ldp_interface_address_add() in ldp_zebra.c.

On Mon, Mar 24, 2008 at 04:58:20PM -0400, Scott A. Yoder wrote:
> Hi James. I've been able to get ldpd working quite well with 3 routers in my testbed. Even
> the targeted ldp sessions now appear to be working. I have a left LSR, middle, LSR and right LSR. The
> targeted session is between the left and right routers.
> 
> I've found a few problems and want to get your take on how best to fix them.
> 
> 1) The xconnect command needs to have the destination IP address stored in host byte order.
> 
> --- ldp_vty.c   Tue Mar 25 01:19:59 2008
> +++ ldp_vty-new.c       Wed Mar 19 01:55:44 2008
> @@ -1618,6 +1618,7 @@
>    dest.port = 646;
> 
>    VTY_GET_UINT32_RANGE("VCID",vcid,argv[1],0,255);
> +  dest.addr.u.ipv4 = ntohl(dest.addr.u.ipv4);
> 
>    if (ldp_remote_peer_find(ldp, &dest)) {
>      return CMD_WARNING;
> 
> 
> 2) I found a couple of memory leaks with valgrind:
> 
> --- ldp_session.c       Fri Jan  4 23:58:59 2008
> +++ ldp_session-new.c       Tue Mar 25 01:25:32 2008
> @@ -252,6 +252,8 @@
>  {
>    LDP_PRINT(NULL, "session delete");
>    MPLS_REFCNT_ASSERT(s, 0);
> +  ldp_buf_delete(s->tx_buffer);
> +  ldp_mesg_delete(s->tx_message);
>    mpls_free(s);
>  }
> 
> --- ldp_buf.c   Tue Mar 25 01:29:01 2008
> +++ ldp_buf-new.c       Fri Mar 21 21:18:06 2008
> @@ -49,6 +49,8 @@
>  void ldp_buf_delete(ldp_buf * b)
>  {
>    MPLS_ASSERT(b);
> +  if (b->buffer)
> +    mpls_free(b->buffer);
>    mpls_free(b);
>  }
> 
> 
> These 2 leaks caused ldpd to grow several megabytes per hour on my system.
> 
> 
> 3) ldpd cannot establish more than 1 session at a time.
> 
> I don't know if I have a config error but I keep getting a "ldp_addr_process: session X already advertised this address"
> error when the 2nd router attempts to start up a session. I think the address is 127.0.0.1. I tried changing the lsr-id and
> transport address but that caused ldpd to crash. The neighbor's status is stuck in the discovery state.
> 
> Just to get around this problem and keep going I stuck a return MPLS_SUCCESS in ldpd/ldp_addr.c line 315:
> 
>       /* the addr is in the tree */
>       if (addr->session) {
>         LDP_PRINT(g->user_data,
>           "ldp_addr_process: session (%d) already advertised this address\n",
>           addr->session->index);
>   return MPLS_SUCCESS;
>         return MPLS_FAILURE;
>       }
> 
> Is there something I'm missing with the config to support multiple peers?
> 
> Thanks,
> Scott Yoder
> Support Engineer
> ImageStream Internet Solutions, Inc.
> E-mail: sy...@im...
> 
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> mpls-linux-devel mailing list
> mpl...@li...
> https://lists.sourceforge.net/lists/listinfo/mpls-linux-devel

-- 
James R. Leu
jl...@mi...

[mpls-linux-devel] A few problems with ldpd

[Scott A. Y. <sy...@im...>]

Hi James. I've been able to get ldpd working quite well with 3 routers in my testbed. Even
the targeted ldp sessions now appear to be working. I have a left LSR, middle, LSR and right LSR. The
targeted session is between the left and right routers.

I've found a few problems and want to get your take on how best to fix them.

1) The xconnect command needs to have the destination IP address stored in host byte order.

--- ldp_vty.c   Tue Mar 25 01:19:59 2008
+++ ldp_vty-new.c       Wed Mar 19 01:55:44 2008
@@ -1618,6 +1618,7 @@
   dest.port = 646;

   VTY_GET_UINT32_RANGE("VCID",vcid,argv[1],0,255);
+  dest.addr.u.ipv4 = ntohl(dest.addr.u.ipv4);

   if (ldp_remote_peer_find(ldp, &dest)) {
     return CMD_WARNING;


2) I found a couple of memory leaks with valgrind:

--- ldp_session.c       Fri Jan  4 23:58:59 2008
+++ ldp_session-new.c       Tue Mar 25 01:25:32 2008
@@ -252,6 +252,8 @@
 {
   LDP_PRINT(NULL, "session delete");
   MPLS_REFCNT_ASSERT(s, 0);
+  ldp_buf_delete(s->tx_buffer);
+  ldp_mesg_delete(s->tx_message);
   mpls_free(s);
 }

--- ldp_buf.c   Tue Mar 25 01:29:01 2008
+++ ldp_buf-new.c       Fri Mar 21 21:18:06 2008
@@ -49,6 +49,8 @@
 void ldp_buf_delete(ldp_buf * b)
 {
   MPLS_ASSERT(b);
+  if (b->buffer)
+    mpls_free(b->buffer);
   mpls_free(b);
 }


These 2 leaks caused ldpd to grow several megabytes per hour on my system.


3) ldpd cannot establish more than 1 session at a time.

I don't know if I have a config error but I keep getting a "ldp_addr_process: session X already advertised this address"
error when the 2nd router attempts to start up a session. I think the address is 127.0.0.1. I tried changing the lsr-id and
transport address but that caused ldpd to crash. The neighbor's status is stuck in the discovery state.

Just to get around this problem and keep going I stuck a return MPLS_SUCCESS in ldpd/ldp_addr.c line 315:

      /* the addr is in the tree */
      if (addr->session) {
        LDP_PRINT(g->user_data,
          "ldp_addr_process: session (%d) already advertised this address\n",
          addr->session->index);
  return MPLS_SUCCESS;
        return MPLS_FAILURE;
      }

Is there something I'm missing with the config to support multiple peers?

Thanks,
Scott Yoder
Support Engineer
ImageStream Internet Solutions, Inc.
E-mail: sy...@im...

Re: [mpls-linux-devel] [mpls-linux-general] Development MPLS-Linux

[James R. L. <jl...@mi...>]

I do not have that documentation either.  I will try to get it.

On Fri, Mar 07, 2008 at 12:11:58PM +0100, =?ISO-8859-1?Q?Jes=FAs_Nubiola_ wrote:
> Hello James,
> 
> I've read in the old message in the list this mail:
> 
> >* On Tue, Jun 01, 2004 at 01:03:08AM +0300, Vadim Suraev wrote:
> *>* > Hi.
> *>* > I'd like to contribute to the Zebra users & developers'
> community several software
> *>* > modules that I've developed recently:
> *>* > RSVP-TE, TE application, TE extensions for OSPF.
> *>* > The software has been tested against CISCO.
> *>* > If you decide to try it, please read the short manuel at:
> *>* > http://www.angelfire.com/theforce/suraev/zebra/MPLS_TE_SW_manuel.txt
> *>* > The code is located at:
> *>* > http://www.angelfire.com/theforce/suraev/zebra/zebra.tar.gz
> *>* > If you have any questions, you are welcome to ask.
> *>* > Any request for any help and support is welcome.
> *>* >
> *>* > Regards,
> *>* >  Vadim.
> 
> *
> 
> The link is actually broken. I think it could be really interesting for me
> to have this documentation and I think that maybe you have a copy of that.
> 
> Regards
> 
> 
> 
> On Fri, Feb 29, 2008 at 3:23 PM, James R. Leu <jl...@mi...> wrote:
> 
> > On Fri, Feb 29, 2008 at 01:22:01PM +0100, =?ISO-8859-1?Q?Jes=FAs_Nubiola_
> > wrote:
> > > Finally I can get access to the repository :)
> > >
> > > I have created a workspace named oksi. I have downloaded quagga-mpls and
> > > look a litle bit the code of rsvpd. I am realized that is the Vadim
> > > implementation, isn't it?
> >
> > Yes most definitely.  He contributed the code a couple years back and
> > I am just now getting around to trying to integrate it.  I believe
> > all of the files that originated from his source give him credit
> > at the top, if not, they should.
> >
> > > Arrived at this point I'm lost about how can I test it or if I'm doing
> > well
> > > or not downloading this folder.
> > > Can you advice me of some test that can help and contributed the results
> > to
> > > the project?
> >
> > At this point all it does is compile, nothing further has been tested.
> >
> > My first goal is to get the RSVP-TE engine running and sending path
> > messages.  This requires VTY command work.
> >
> > After that processing of path messages will require the te_rdb engine
> > to be running.  At first I just want to get it running with just
> > shortest path routing constraints (ie no bandwidth or affinity
> > considered).
> > To do this the te_rdb code needs to be modified to do standard IPv4
> > lookups some how, either by building a patricia tree from route
> > updates that come from zebra or by issuing nexthop lookups back
> > to the main zebra daemon using the ZEBRA_IPV4_NEXTHOP_LOOKUP message.
> > I'm leaning toward the latter because I think down the road I will
> > want to move all of the CSPF calculations into the zebra daemon, this
> > will make TE info dissemination easier and will make the CSPF and TE info
> > available to other protocols that choose to use it.
> >
> > So basically, dig in and start trying to make it work.  I'm
> > hoping to finish up some LDP work, once I have LDP at least kind of
> > working again, I will switch gears and work on RSVP-TE as well.
> >
> > > Thank you very much.
> > >
> > > On Fri, Feb 29, 2008 at 12:07 PM, Jesús Nubiola <oc...@gm...>
> > wrote:
> > >
> > > > I'm not able to access to perforce server during all the morning.
> > > >
> > > > Is the server down?
> > > >
> > > >
> > > > On Tue, Feb 26, 2008 at 4:02 AM, James R. Leu <jl...@mi...>
> > wrote:
> > > >
> > > > > On Mon, Feb 25, 2008 at 01:33:49PM +0100,
> > > > > =?ISO-8859-1?Q?Jes=FAs_Nubiola_ wrote:
> > > > > > Hi James,
> > > > > >
> > > > > > I have been reading your guide to access to your perforce server
> >  (
> > > > > > http://mpls-linux.sourceforge.net/). Note: the link to the
> > developers
> > > > > guide
> > > > > > in your web is broken :(
> > > > >
> > > > > Thanks for the notice, being that it was written and host by someone
> > > > > else who is no longer helping the project I'll end up removing the
> > link.
> > > > >
> > > > > > As I was saying I think that I've be able to connect to your
> > perforce
> > > > > > following the instructions on your web but I don't see exactly the
> > > > > same you
> > > > > > put in your instructions above-named:
> > > > >
> > > > > You need to create your own workspace, and then modify the view.
> > > > > The quagga-rsvpte dir is not what you want, that is an old failed
> > > > > rsvpte implementation.  The one you want is in the quagga-mpls tree.
> > > > > You will need the entire quagga-mpls directory.
> > > > > I'm almost done porting it to quagga-0.99.9.  I haven't done any
> > testing
> > > > > with it.  It probably doesn't work at all, but I could really use
> > some
> > > > > help getting it going.
> > > > >
> > > > > > Under the heading 'Access to my development repository'.  The
> > 'view'
> > > > > > you will want is:
> > > > > >
> > > > > >    //depot/quagga/... //<client name>/quagga/...
> > > > > >    //depot/quagga-plus/... //<client name>/quagga-plus/...
> > > > > >    //depot/quagga-mpls/... //<client name>/quagga-mpls/...
> > > > > >
> > > > > > The only folder that I see is the last one (quagga-mpls), and
> > inside
> > > > > of it
> > > > > > there is another folder named rsvpd.
> > > > > > Is that folder the one that you aimed in the mail before?
> > > > > > Could you give me some advices to understand the state of the art
> > of
> > > > > that
> > > > > > code? (examples that I can prove or anything that you think it
> > could
> > > > > help me
> > > > > > to understand the code and let me to improve the integration into
> > > > > Quagga).
> > > > > >
> > > > > > Here is a snapshot of my view of your perforce server:
> > > > > >
> > http://img96.imageshack.us/my.php?image=screenshotperforcemplsro5.jpg
> > > > > >
> > > > > > The options I use to connect it are:
> > > > > >
> > > > > > server: p4.dangermen.com
> > > > > > port: 1666
> > > > > > Username: perforce (no password)
> > > > > > worksace: mplslinux (on click to browse button it appears 4
> > options:
> > > > > > esemjrpg3, /home/tmp/dep, mmbb97 and mplslinux.  thought that the
> > last
> > > > > one
> > > > > > was the correct one)
> > > > > >
> > > > > > Thank you very much and sorry for my English again ;)
> > > > > >
> > > > > > Regards
> > > > >
> > > > > >
> > > > >
> > -------------------------------------------------------------------------
> > > > > > This SF.net email is sponsored by: Microsoft
> > > > > > Defy all challenges. Microsoft(R) Visual Studio 2008.
> > > > > > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> > > > > > _______________________________________________
> > > > > > mpls-linux-general mailing list
> > > > > > mpl...@li...
> > > > > > https://lists.sourceforge.net/lists/listinfo/mpls-linux-general
> > > > >
> > > > >
> > > > > --
> > > > > James R. Leu
> > > > > jl...@mi...
> > > > >
> > > >
> > > >
> >
> > >
> > -------------------------------------------------------------------------
> > > This SF.net email is sponsored by: Microsoft
> > > Defy all challenges. Microsoft(R) Visual Studio 2008.
> > > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> > > _______________________________________________
> > > mpls-linux-devel mailing list
> > > mpl...@li...
> > > https://lists.sourceforge.net/lists/listinfo/mpls-linux-devel
> >
> >
> > --
> > James R. Leu
> > jl...@mi...
> >

-- 
James R. Leu
jl...@mi...

[mpls-linux-devel] [mpls-linux-general] Development MPLS-Linux

[J. N. <oc...@gm...>]

Hello James,

I've read in the old message in the list this mail:

>* On Tue, Jun 01, 2004 at 01:03:08AM +0300, Vadim Suraev wrote:
*>* > Hi.
*>* > I'd like to contribute to the Zebra users & developers'
community several software
*>* > modules that I've developed recently:
*>* > RSVP-TE, TE application, TE extensions for OSPF.
*>* > The software has been tested against CISCO.
*>* > If you decide to try it, please read the short manuel at:
*>* > http://www.angelfire.com/theforce/suraev/zebra/MPLS_TE_SW_manuel.txt
*>* > The code is located at:
*>* > http://www.angelfire.com/theforce/suraev/zebra/zebra.tar.gz
*>* > If you have any questions, you are welcome to ask.
*>* > Any request for any help and support is welcome.
*>* >
*>* > Regards,
*>* >  Vadim.

*

The link is actually broken. I think it could be really interesting for me
to have this documentation and I think that maybe you have a copy of that.

Regards



On Fri, Feb 29, 2008 at 3:23 PM, James R. Leu <jl...@mi...> wrote:

> On Fri, Feb 29, 2008 at 01:22:01PM +0100, =?ISO-8859-1?Q?Jes=FAs_Nubiola_
> wrote:
> > Finally I can get access to the repository :)
> >
> > I have created a workspace named oksi. I have downloaded quagga-mpls and
> > look a litle bit the code of rsvpd. I am realized that is the Vadim
> > implementation, isn't it?
>
> Yes most definitely.  He contributed the code a couple years back and
> I am just now getting around to trying to integrate it.  I believe
> all of the files that originated from his source give him credit
> at the top, if not, they should.
>
> > Arrived at this point I'm lost about how can I test it or if I'm doing
> well
> > or not downloading this folder.
> > Can you advice me of some test that can help and contributed the results
> to
> > the project?
>
> At this point all it does is compile, nothing further has been tested.
>
> My first goal is to get the RSVP-TE engine running and sending path
> messages.  This requires VTY command work.
>
> After that processing of path messages will require the te_rdb engine
> to be running.  At first I just want to get it running with just
> shortest path routing constraints (ie no bandwidth or affinity
> considered).
> To do this the te_rdb code needs to be modified to do standard IPv4
> lookups some how, either by building a patricia tree from route
> updates that come from zebra or by issuing nexthop lookups back
> to the main zebra daemon using the ZEBRA_IPV4_NEXTHOP_LOOKUP message.
> I'm leaning toward the latter because I think down the road I will
> want to move all of the CSPF calculations into the zebra daemon, this
> will make TE info dissemination easier and will make the CSPF and TE info
> available to other protocols that choose to use it.
>
> So basically, dig in and start trying to make it work.  I'm
> hoping to finish up some LDP work, once I have LDP at least kind of
> working again, I will switch gears and work on RSVP-TE as well.
>
> > Thank you very much.
> >
> > On Fri, Feb 29, 2008 at 12:07 PM, Jesús Nubiola <oc...@gm...>
> wrote:
> >
> > > I'm not able to access to perforce server during all the morning.
> > >
> > > Is the server down?
> > >
> > >
> > > On Tue, Feb 26, 2008 at 4:02 AM, James R. Leu <jl...@mi...>
> wrote:
> > >
> > > > On Mon, Feb 25, 2008 at 01:33:49PM +0100,
> > > > =?ISO-8859-1?Q?Jes=FAs_Nubiola_ wrote:
> > > > > Hi James,
> > > > >
> > > > > I have been reading your guide to access to your perforce server
>  (
> > > > > http://mpls-linux.sourceforge.net/). Note: the link to the
> developers
> > > > guide
> > > > > in your web is broken :(
> > > >
> > > > Thanks for the notice, being that it was written and host by someone
> > > > else who is no longer helping the project I'll end up removing the
> link.
> > > >
> > > > > As I was saying I think that I've be able to connect to your
> perforce
> > > > > following the instructions on your web but I don't see exactly the
> > > > same you
> > > > > put in your instructions above-named:
> > > >
> > > > You need to create your own workspace, and then modify the view.
> > > > The quagga-rsvpte dir is not what you want, that is an old failed
> > > > rsvpte implementation.  The one you want is in the quagga-mpls tree.
> > > > You will need the entire quagga-mpls directory.
> > > > I'm almost done porting it to quagga-0.99.9.  I haven't done any
> testing
> > > > with it.  It probably doesn't work at all, but I could really use
> some
> > > > help getting it going.
> > > >
> > > > > Under the heading 'Access to my development repository'.  The
> 'view'
> > > > > you will want is:
> > > > >
> > > > >    //depot/quagga/... //<client name>/quagga/...
> > > > >    //depot/quagga-plus/... //<client name>/quagga-plus/...
> > > > >    //depot/quagga-mpls/... //<client name>/quagga-mpls/...
> > > > >
> > > > > The only folder that I see is the last one (quagga-mpls), and
> inside
> > > > of it
> > > > > there is another folder named rsvpd.
> > > > > Is that folder the one that you aimed in the mail before?
> > > > > Could you give me some advices to understand the state of the art
> of
> > > > that
> > > > > code? (examples that I can prove or anything that you think it
> could
> > > > help me
> > > > > to understand the code and let me to improve the integration into
> > > > Quagga).
> > > > >
> > > > > Here is a snapshot of my view of your perforce server:
> > > > >
> http://img96.imageshack.us/my.php?image=screenshotperforcemplsro5.jpg
> > > > >
> > > > > The options I use to connect it are:
> > > > >
> > > > > server: p4.dangermen.com
> > > > > port: 1666
> > > > > Username: perforce (no password)
> > > > > worksace: mplslinux (on click to browse button it appears 4
> options:
> > > > > esemjrpg3, /home/tmp/dep, mmbb97 and mplslinux.  thought that the
> last
> > > > one
> > > > > was the correct one)
> > > > >
> > > > > Thank you very much and sorry for my English again ;)
> > > > >
> > > > > Regards
> > > >
> > > > >
> > > >
> -------------------------------------------------------------------------
> > > > > This SF.net email is sponsored by: Microsoft
> > > > > Defy all challenges. Microsoft(R) Visual Studio 2008.
> > > > > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> > > > > _______________________________________________
> > > > > mpls-linux-general mailing list
> > > > > mpl...@li...
> > > > > https://lists.sourceforge.net/lists/listinfo/mpls-linux-general
> > > >
> > > >
> > > > --
> > > > James R. Leu
> > > > jl...@mi...
> > > >
> > >
> > >
>
> >
> -------------------------------------------------------------------------
> > This SF.net email is sponsored by: Microsoft
> > Defy all challenges. Microsoft(R) Visual Studio 2008.
> > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> > _______________________________________________
> > mpls-linux-devel mailing list
> > mpl...@li...
> > https://lists.sourceforge.net/lists/listinfo/mpls-linux-devel
>
>
> --
> James R. Leu
> jl...@mi...
>

[mpls-linux-devel] Vacation reply

[<ouw...@ho...>]

<br>PLEASE START USING MY GMAIL ADDRESS, I WILL ABANDON HOTMAIL SHORTLY.<br><br><span style="font-weight:bold">t.kleiberg (at) gmail.com</span><br><br><br>THANKS.<br><br>TOM<br><br>

Re: [mpls-linux-devel] [mpls-linux-general] Development MPLS-Linux

[J. N. <oc...@gm...>]

Hello James,

I've read in the old message in the list this mail:

>* On Tue, Jun 01, 2004 at 01:03:08AM +0300, Vadim Suraev wrote:
*>* > Hi.
*>* > I'd like to contribute to the Zebra users & developers'
community several software
*>* > modules that I've developed recently:
*>* > RSVP-TE, TE application, TE extensions for OSPF.
*>* > The software has been tested against CISCO.
*>* > If you decide to try it, please read the short manuel at:
*>* > http://www.angelfire.com/theforce/suraev/zebra/MPLS_TE_SW_manuel.txt
*>* > The code is located at:
*>* > http://www.angelfire.com/theforce/suraev/zebra/zebra.tar.gz
*>* > If you have any questions, you are welcome to ask.
*>* > Any request for any help and support is welcome.
*>* >
*>* > Regards,
*>* >  Vadim.

*

The link is actually broken. I think it could be really interesting for me
to have this documentation and I think that maybe you have a copy of that.

Regards



On Fri, Feb 29, 2008 at 3:23 PM, James R. Leu <jl...@mi...> wrote:

> On Fri, Feb 29, 2008 at 01:22:01PM +0100, =?ISO-8859-1?Q?Jes=FAs_Nubiola_
> wrote:
> > Finally I can get access to the repository :)
> >
> > I have created a workspace named oksi. I have downloaded quagga-mpls and
> > look a litle bit the code of rsvpd. I am realized that is the Vadim
> > implementation, isn't it?
>
> Yes most definitely.  He contributed the code a couple years back and
> I am just now getting around to trying to integrate it.  I believe
> all of the files that originated from his source give him credit
> at the top, if not, they should.
>
> > Arrived at this point I'm lost about how can I test it or if I'm doing
> well
> > or not downloading this folder.
> > Can you advice me of some test that can help and contributed the results
> to
> > the project?
>
> At this point all it does is compile, nothing further has been tested.
>
> My first goal is to get the RSVP-TE engine running and sending path
> messages.  This requires VTY command work.
>
> After that processing of path messages will require the te_rdb engine
> to be running.  At first I just want to get it running with just
> shortest path routing constraints (ie no bandwidth or affinity
> considered).
> To do this the te_rdb code needs to be modified to do standard IPv4
> lookups some how, either by building a patricia tree from route
> updates that come from zebra or by issuing nexthop lookups back
> to the main zebra daemon using the ZEBRA_IPV4_NEXTHOP_LOOKUP message.
> I'm leaning toward the latter because I think down the road I will
> want to move all of the CSPF calculations into the zebra daemon, this
> will make TE info dissemination easier and will make the CSPF and TE info
> available to other protocols that choose to use it.
>
> So basically, dig in and start trying to make it work.  I'm
> hoping to finish up some LDP work, once I have LDP at least kind of
> working again, I will switch gears and work on RSVP-TE as well.
>
> > Thank you very much.
> >
> > On Fri, Feb 29, 2008 at 12:07 PM, Jesús Nubiola <oc...@gm...>
> wrote:
> >
> > > I'm not able to access to perforce server during all the morning.
> > >
> > > Is the server down?
> > >
> > >
> > > On Tue, Feb 26, 2008 at 4:02 AM, James R. Leu <jl...@mi...>
> wrote:
> > >
> > > > On Mon, Feb 25, 2008 at 01:33:49PM +0100,
> > > > =?ISO-8859-1?Q?Jes=FAs_Nubiola_ wrote:
> > > > > Hi James,
> > > > >
> > > > > I have been reading your guide to access to your perforce server
>  (
> > > > > http://mpls-linux.sourceforge.net/). Note: the link to the
> developers
> > > > guide
> > > > > in your web is broken :(
> > > >
> > > > Thanks for the notice, being that it was written and host by someone
> > > > else who is no longer helping the project I'll end up removing the
> link.
> > > >
> > > > > As I was saying I think that I've be able to connect to your
> perforce
> > > > > following the instructions on your web but I don't see exactly the
> > > > same you
> > > > > put in your instructions above-named:
> > > >
> > > > You need to create your own workspace, and then modify the view.
> > > > The quagga-rsvpte dir is not what you want, that is an old failed
> > > > rsvpte implementation.  The one you want is in the quagga-mpls tree.
> > > > You will need the entire quagga-mpls directory.
> > > > I'm almost done porting it to quagga-0.99.9.  I haven't done any
> testing
> > > > with it.  It probably doesn't work at all, but I could really use
> some
> > > > help getting it going.
> > > >
> > > > > Under the heading 'Access to my development repository'.  The
> 'view'
> > > > > you will want is:
> > > > >
> > > > >    //depot/quagga/... //<client name>/quagga/...
> > > > >    //depot/quagga-plus/... //<client name>/quagga-plus/...
> > > > >    //depot/quagga-mpls/... //<client name>/quagga-mpls/...
> > > > >
> > > > > The only folder that I see is the last one (quagga-mpls), and
> inside
> > > > of it
> > > > > there is another folder named rsvpd.
> > > > > Is that folder the one that you aimed in the mail before?
> > > > > Could you give me some advices to understand the state of the art
> of
> > > > that
> > > > > code? (examples that I can prove or anything that you think it
> could
> > > > help me
> > > > > to understand the code and let me to improve the integration into
> > > > Quagga).
> > > > >
> > > > > Here is a snapshot of my view of your perforce server:
> > > > >
> http://img96.imageshack.us/my.php?image=screenshotperforcemplsro5.jpg
> > > > >
> > > > > The options I use to connect it are:
> > > > >
> > > > > server: p4.dangermen.com
> > > > > port: 1666
> > > > > Username: perforce (no password)
> > > > > worksace: mplslinux (on click to browse button it appears 4
> options:
> > > > > esemjrpg3, /home/tmp/dep, mmbb97 and mplslinux.  thought that the
> last
> > > > one
> > > > > was the correct one)
> > > > >
> > > > > Thank you very much and sorry for my English again ;)
> > > > >
> > > > > Regards
> > > >
> > > > >
> > > >
> -------------------------------------------------------------------------
> > > > > This SF.net email is sponsored by: Microsoft
> > > > > Defy all challenges. Microsoft(R) Visual Studio 2008.
> > > > > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> > > > > _______________________________________________
> > > > > mpls-linux-general mailing list
> > > > > mpl...@li...
> > > > > https://lists.sourceforge.net/lists/listinfo/mpls-linux-general
> > > >
> > > >
> > > > --
> > > > James R. Leu
> > > > jl...@mi...
> > > >
> > >
> > >
>
> >
> -------------------------------------------------------------------------
> > This SF.net email is sponsored by: Microsoft
> > Defy all challenges. Microsoft(R) Visual Studio 2008.
> > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> > _______________________________________________
> > mpls-linux-devel mailing list
> > mpl...@li...
> > https://lists.sourceforge.net/lists/listinfo/mpls-linux-devel
>
>
> --
> James R. Leu
> jl...@mi...
>

Re: [mpls-linux-devel] MPLS modifications as a patch for Vanilla kernel

[Philippe F. <Phi...@eu...>]

Hi,

First of all thanks for your previous answer.
I created the patch between the default Fedora Core 6 kernel sources
(2.6.22.14-72) and the ones once MPLS modifications have been achieved.
However, it looks that between those two versions, not only MPLS has
been added but XEN features (or other ?) as well. As we are using
Real-time patch on our kernel, it conflicts (notably on kernel/sched.c
file), so we would like to remove it.
So, we thought that perhaps you can tell us what are the modifications
you did exactly on this kernel ?
(http://mpls-linux.sourceforge.net/fedora/6/sources/mpls/kernel-2.6.22.14-72.fc6.mpls.1.959.src.rpm)
Except the fact you added MPLS, did you use other patches ? If yes, is
it possible for you to tell us what are they so i can try, thanks to
them, to remove them.

Thanks in advance.
Philippe
-- 
--------------------------------------
Philippe Foubert
--------------------------------------
   INSTITUT EURECOM
      Mobile Communications Department
      2229, route des Crêtes
      B.P. 193
      06904 Sophia-Antipolis - France
   Phone : +33(0)4.93.00.82.18
   e-mail: phi...@eu...
--------------------------------------

Re: [mpls-linux-devel] [mpls-linux-general] Development MPLS-Linux

[James R. L. <jl...@mi...>]

On Fri, Feb 29, 2008 at 01:22:01PM +0100, =?ISO-8859-1?Q?Jes=FAs_Nubiola_ wrote:
> Finally I can get access to the repository :)
> 
> I have created a workspace named oksi. I have downloaded quagga-mpls and
> look a litle bit the code of rsvpd. I am realized that is the Vadim
> implementation, isn't it?

Yes most definitely.  He contributed the code a couple years back and
I am just now getting around to trying to integrate it.  I believe
all of the files that originated from his source give him credit
at the top, if not, they should.

> Arrived at this point I'm lost about how can I test it or if I'm doing well
> or not downloading this folder.
> Can you advice me of some test that can help and contributed the results to
> the project?

At this point all it does is compile, nothing further has been tested.

My first goal is to get the RSVP-TE engine running and sending path
messages.  This requires VTY command work.

After that processing of path messages will require the te_rdb engine
to be running.  At first I just want to get it running with just
shortest path routing constraints (ie no bandwidth or affinity considered).
To do this the te_rdb code needs to be modified to do standard IPv4
lookups some how, either by building a patricia tree from route
updates that come from zebra or by issuing nexthop lookups back
to the main zebra daemon using the ZEBRA_IPV4_NEXTHOP_LOOKUP message.
I'm leaning toward the latter because I think down the road I will
want to move all of the CSPF calculations into the zebra daemon, this
will make TE info dissemination easier and will make the CSPF and TE info
available to other protocols that choose to use it.

So basically, dig in and start trying to make it work.  I'm
hoping to finish up some LDP work, once I have LDP at least kind of
working again, I will switch gears and work on RSVP-TE as well.

> Thank you very much.
> 
> On Fri, Feb 29, 2008 at 12:07 PM, Jesús Nubiola <oc...@gm...> wrote:
> 
> > I'm not able to access to perforce server during all the morning.
> >
> > Is the server down?
> >
> >
> > On Tue, Feb 26, 2008 at 4:02 AM, James R. Leu <jl...@mi...> wrote:
> >
> > > On Mon, Feb 25, 2008 at 01:33:49PM +0100,
> > > =?ISO-8859-1?Q?Jes=FAs_Nubiola_ wrote:
> > > > Hi James,
> > > >
> > > > I have been reading your guide to access to your perforce server  (
> > > > http://mpls-linux.sourceforge.net/). Note: the link to the developers
> > > guide
> > > > in your web is broken :(
> > >
> > > Thanks for the notice, being that it was written and host by someone
> > > else who is no longer helping the project I'll end up removing the link.
> > >
> > > > As I was saying I think that I've be able to connect to your perforce
> > > > following the instructions on your web but I don't see exactly the
> > > same you
> > > > put in your instructions above-named:
> > >
> > > You need to create your own workspace, and then modify the view.
> > > The quagga-rsvpte dir is not what you want, that is an old failed
> > > rsvpte implementation.  The one you want is in the quagga-mpls tree.
> > > You will need the entire quagga-mpls directory.
> > > I'm almost done porting it to quagga-0.99.9.  I haven't done any testing
> > > with it.  It probably doesn't work at all, but I could really use some
> > > help getting it going.
> > >
> > > > Under the heading 'Access to my development repository'.  The 'view'
> > > > you will want is:
> > > >
> > > >    //depot/quagga/... //<client name>/quagga/...
> > > >    //depot/quagga-plus/... //<client name>/quagga-plus/...
> > > >    //depot/quagga-mpls/... //<client name>/quagga-mpls/...
> > > >
> > > > The only folder that I see is the last one (quagga-mpls), and inside
> > > of it
> > > > there is another folder named rsvpd.
> > > > Is that folder the one that you aimed in the mail before?
> > > > Could you give me some advices to understand the state of the art of
> > > that
> > > > code? (examples that I can prove or anything that you think it could
> > > help me
> > > > to understand the code and let me to improve the integration into
> > > Quagga).
> > > >
> > > > Here is a snapshot of my view of your perforce server:
> > > > http://img96.imageshack.us/my.php?image=screenshotperforcemplsro5.jpg
> > > >
> > > > The options I use to connect it are:
> > > >
> > > > server: p4.dangermen.com
> > > > port: 1666
> > > > Username: perforce (no password)
> > > > worksace: mplslinux (on click to browse button it appears 4 options:
> > > > esemjrpg3, /home/tmp/dep, mmbb97 and mplslinux.  thought that the last
> > > one
> > > > was the correct one)
> > > >
> > > > Thank you very much and sorry for my English again ;)
> > > >
> > > > Regards
> > >
> > > >
> > > -------------------------------------------------------------------------
> > > > This SF.net email is sponsored by: Microsoft
> > > > Defy all challenges. Microsoft(R) Visual Studio 2008.
> > > > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> > > > _______________________________________________
> > > > mpls-linux-general mailing list
> > > > mpl...@li...
> > > > https://lists.sourceforge.net/lists/listinfo/mpls-linux-general
> > >
> > >
> > > --
> > > James R. Leu
> > > jl...@mi...
> > >
> >
> >

> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> mpls-linux-devel mailing list
> mpl...@li...
> https://lists.sourceforge.net/lists/listinfo/mpls-linux-devel


-- 
James R. Leu
jl...@mi...

Re: [mpls-linux-devel] [mpls-linux-general] Development MPLS-Linux

[J. N. <oc...@gm...>]

Finally I can get access to the repository :)

I have created a workspace named oksi. I have downloaded quagga-mpls and
look a litle bit the code of rsvpd. I am realized that is the Vadim
implementation, isn't it?
Arrived at this point I'm lost about how can I test it or if I'm doing well
or not downloading this folder.
Can you advice me of some test that can help and contributed the results to
the project?

Thank you very much.

On Fri, Feb 29, 2008 at 12:07 PM, Jesús Nubiola <oc...@gm...> wrote:

> I'm not able to access to perforce server during all the morning.
>
> Is the server down?
>
>
> On Tue, Feb 26, 2008 at 4:02 AM, James R. Leu <jl...@mi...> wrote:
>
> > On Mon, Feb 25, 2008 at 01:33:49PM +0100,
> > =?ISO-8859-1?Q?Jes=FAs_Nubiola_ wrote:
> > > Hi James,
> > >
> > > I have been reading your guide to access to your perforce server  (
> > > http://mpls-linux.sourceforge.net/). Note: the link to the developers
> > guide
> > > in your web is broken :(
> >
> > Thanks for the notice, being that it was written and host by someone
> > else who is no longer helping the project I'll end up removing the link.
> >
> > > As I was saying I think that I've be able to connect to your perforce
> > > following the instructions on your web but I don't see exactly the
> > same you
> > > put in your instructions above-named:
> >
> > You need to create your own workspace, and then modify the view.
> > The quagga-rsvpte dir is not what you want, that is an old failed
> > rsvpte implementation.  The one you want is in the quagga-mpls tree.
> > You will need the entire quagga-mpls directory.
> > I'm almost done porting it to quagga-0.99.9.  I haven't done any testing
> > with it.  It probably doesn't work at all, but I could really use some
> > help getting it going.
> >
> > > Under the heading 'Access to my development repository'.  The 'view'
> > > you will want is:
> > >
> > >    //depot/quagga/... //<client name>/quagga/...
> > >    //depot/quagga-plus/... //<client name>/quagga-plus/...
> > >    //depot/quagga-mpls/... //<client name>/quagga-mpls/...
> > >
> > > The only folder that I see is the last one (quagga-mpls), and inside
> > of it
> > > there is another folder named rsvpd.
> > > Is that folder the one that you aimed in the mail before?
> > > Could you give me some advices to understand the state of the art of
> > that
> > > code? (examples that I can prove or anything that you think it could
> > help me
> > > to understand the code and let me to improve the integration into
> > Quagga).
> > >
> > > Here is a snapshot of my view of your perforce server:
> > > http://img96.imageshack.us/my.php?image=screenshotperforcemplsro5.jpg
> > >
> > > The options I use to connect it are:
> > >
> > > server: p4.dangermen.com
> > > port: 1666
> > > Username: perforce (no password)
> > > worksace: mplslinux (on click to browse button it appears 4 options:
> > > esemjrpg3, /home/tmp/dep, mmbb97 and mplslinux.  thought that the last
> > one
> > > was the correct one)
> > >
> > > Thank you very much and sorry for my English again ;)
> > >
> > > Regards
> >
> > >
> > -------------------------------------------------------------------------
> > > This SF.net email is sponsored by: Microsoft
> > > Defy all challenges. Microsoft(R) Visual Studio 2008.
> > > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> > > _______________________________________________
> > > mpls-linux-general mailing list
> > > mpl...@li...
> > > https://lists.sourceforge.net/lists/listinfo/mpls-linux-general
> >
> >
> > --
> > James R. Leu
> > jl...@mi...
> >
>
>

[mpls-linux-devel] Vacation reply

[<ouw...@ho...>]

<br>PLEASE START USING MY GMAIL ADDRESS, I WILL ABANDON HOTMAIL SHORTLY.<br><br><span style="font-weight:bold">t.kleiberg (at) gmail.com</span><br><br><br>THANKS.<br><br>TOM<br><br>

Re: [mpls-linux-devel] [mpls-linux-general] Development MPLS-Linux

[J. N. <oc...@gm...>]

I'm not able to access to perforce server during all the morning.

Is the server down?

On Tue, Feb 26, 2008 at 4:02 AM, James R. Leu <jl...@mi...> wrote:

> On Mon, Feb 25, 2008 at 01:33:49PM +0100, =?ISO-8859-1?Q?Jes=FAs_Nubiola_
> wrote:
> > Hi James,
> >
> > I have been reading your guide to access to your perforce server  (
> > http://mpls-linux.sourceforge.net/). Note: the link to the developers
> guide
> > in your web is broken :(
>
> Thanks for the notice, being that it was written and host by someone
> else who is no longer helping the project I'll end up removing the link.
>
> > As I was saying I think that I've be able to connect to your perforce
> > following the instructions on your web but I don't see exactly the same
> you
> > put in your instructions above-named:
>
> You need to create your own workspace, and then modify the view.
> The quagga-rsvpte dir is not what you want, that is an old failed
> rsvpte implementation.  The one you want is in the quagga-mpls tree.
> You will need the entire quagga-mpls directory.
> I'm almost done porting it to quagga-0.99.9.  I haven't done any testing
> with it.  It probably doesn't work at all, but I could really use some
> help getting it going.
>
> > Under the heading 'Access to my development repository'.  The 'view'
> > you will want is:
> >
> >    //depot/quagga/... //<client name>/quagga/...
> >    //depot/quagga-plus/... //<client name>/quagga-plus/...
> >    //depot/quagga-mpls/... //<client name>/quagga-mpls/...
> >
> > The only folder that I see is the last one (quagga-mpls), and inside of
> it
> > there is another folder named rsvpd.
> > Is that folder the one that you aimed in the mail before?
> > Could you give me some advices to understand the state of the art of
> that
> > code? (examples that I can prove or anything that you think it could
> help me
> > to understand the code and let me to improve the integration into
> Quagga).
> >
> > Here is a snapshot of my view of your perforce server:
> > http://img96.imageshack.us/my.php?image=screenshotperforcemplsro5.jpg
> >
> > The options I use to connect it are:
> >
> > server: p4.dangermen.com
> > port: 1666
> > Username: perforce (no password)
> > worksace: mplslinux (on click to browse button it appears 4 options:
> > esemjrpg3, /home/tmp/dep, mmbb97 and mplslinux.  thought that the last
> one
> > was the correct one)
> >
> > Thank you very much and sorry for my English again ;)
> >
> > Regards
>
> >
> -------------------------------------------------------------------------
> > This SF.net email is sponsored by: Microsoft
> > Defy all challenges. Microsoft(R) Visual Studio 2008.
> > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> > _______________________________________________
> > mpls-linux-general mailing list
> > mpl...@li...
> > https://lists.sourceforge.net/lists/listinfo/mpls-linux-general
>
>
> --
> James R. Leu
> jl...@mi...
>

Re: [mpls-linux-devel] MPLS modifications as a patch for Vanilla kernel

[James R. L. <jl...@mi...>]

You should be able to build a diff from:

    http://download.fedora.redhat.com/pub/fedora/linux/core/updates/6/SRPMS/kernel-2.6.22.14-72.fc6.src.rpm

and

    http://mpls-linux.sourceforge.net/fedora/6/sources/mpls/kernel-2.6.22.14-72.fc6.mpls.1.959.src.rpm

On Wed, Feb 27, 2008 at 06:36:39PM +0100, Philippe Foubert wrote:
> Hi all,
> 
> We are using MPLS project on our platform and we would have question 
> about it.
> 
> First of all, we are using Ubuntu (both 6.06 7.10 versions) as linux 
> distribution. As we have to achieve modifications on our kernels, we 
> choose to start from Vanilla ones (from www.kernel.org). Our kernel 
> modifications are among other things, RTAI (Real-time feature), 
> BIGPHYSAREA, etc ...
> We noticed that the 2.6.22.5 kernel sources which are proposed on 
> sourceforge.net website, are actually the default Fedora Core 6 
> distribution kernel that you certainly patched/modified.
> Our main issue is that we are not able to apply our patches directly on 
> these MPLS kernel sources (as patches are generally made to be applied 
> on vanilla kernel)
> Basically our best solution will be to transform all the MPLS 
> modifications that have been done into a patch file.
> In order to achieve this, we have been advised to create a patch between 
> the default Fedora Core source kernel and the same one after MPLS 
> modifications (So this one -> kernel-2.6.22.5-49.fc6.mpls.1.958.src.rpm).
> 
> However, I've checked on all the RPM repositories websites and I was 
> unsuccessful to find the kernel sources for a 2.6.22.5-49 from Fedora 
> Core 6. So I'm not able to create such a patch for Vanilla kernel.
> Could somebody help me ?
> 
> Best regards,
> Philippe
> -- 
> --------------------------------------
> Philippe Foubert
> --------------------------------------
>   INSTITUT EURECOM
>      Mobile Communications Department
>      2229, route des Crêtes
>      B.P. 193
>      06904 Sophia-Antipolis - France
>   Phone : +33(0)4.93.00.82.18
>   e-mail: phi...@eu...
> --------------------------------------
> 
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> mpls-linux-devel mailing list
> mpl...@li...
> https://lists.sourceforge.net/lists/listinfo/mpls-linux-devel

-- 
James R. Leu
jl...@mi...

[mpls-linux-devel] MPLS modifications as a patch for Vanilla kernel

[Philippe F. <Phi...@eu...>]

Hi all,

We are using MPLS project on our platform and we would have question 
about it.

First of all, we are using Ubuntu (both 6.06 7.10 versions) as linux 
distribution. As we have to achieve modifications on our kernels, we 
choose to start from Vanilla ones (from www.kernel.org). Our kernel 
modifications are among other things, RTAI (Real-time feature), 
BIGPHYSAREA, etc ...
We noticed that the 2.6.22.5 kernel sources which are proposed on 
sourceforge.net website, are actually the default Fedora Core 6 
distribution kernel that you certainly patched/modified.
Our main issue is that we are not able to apply our patches directly on 
these MPLS kernel sources (as patches are generally made to be applied 
on vanilla kernel)
Basically our best solution will be to transform all the MPLS 
modifications that have been done into a patch file.
In order to achieve this, we have been advised to create a patch between 
the default Fedora Core source kernel and the same one after MPLS 
modifications (So this one -> kernel-2.6.22.5-49.fc6.mpls.1.958.src.rpm).

However, I've checked on all the RPM repositories websites and I was 
unsuccessful to find the kernel sources for a 2.6.22.5-49 from Fedora 
Core 6. So I'm not able to create such a patch for Vanilla kernel.
Could somebody help me ?

Best regards,
Philippe
-- 
--------------------------------------
Philippe Foubert
--------------------------------------
  INSTITUT EURECOM
     Mobile Communications Department
     2229, route des Crêtes
     B.P. 193
     06904 Sophia-Antipolis - France
  Phone : +33(0)4.93.00.82.18
  e-mail: phi...@eu...
--------------------------------------

Re: [mpls-linux-devel] [mpls-linux-general] Development MPLS-Linux

[James R. L. <jl...@mi...>]

On Mon, Feb 25, 2008 at 01:33:49PM +0100, =?ISO-8859-1?Q?Jes=FAs_Nubiola_ wrote:
> Hi James,
> 
> I have been reading your guide to access to your perforce server  (
> http://mpls-linux.sourceforge.net/). Note: the link to the developers guide
> in your web is broken :(

Thanks for the notice, being that it was written and host by someone
else who is no longer helping the project I'll end up removing the link.

> As I was saying I think that I've be able to connect to your perforce
> following the instructions on your web but I don't see exactly the same you
> put in your instructions above-named:

You need to create your own workspace, and then modify the view.
The quagga-rsvpte dir is not what you want, that is an old failed
rsvpte implementation.  The one you want is in the quagga-mpls tree.
You will need the entire quagga-mpls directory.
I'm almost done porting it to quagga-0.99.9.  I haven't done any testing
with it.  It probably doesn't work at all, but I could really use some
help getting it going.

> Under the heading 'Access to my development repository'.  The 'view'
> you will want is:
> 
>    //depot/quagga/... //<client name>/quagga/...
>    //depot/quagga-plus/... //<client name>/quagga-plus/...
>    //depot/quagga-mpls/... //<client name>/quagga-mpls/...
> 
> The only folder that I see is the last one (quagga-mpls), and inside of it
> there is another folder named rsvpd.
> Is that folder the one that you aimed in the mail before?
> Could you give me some advices to understand the state of the art of that
> code? (examples that I can prove or anything that you think it could help me
> to understand the code and let me to improve the integration into Quagga).
> 
> Here is a snapshot of my view of your perforce server:
> http://img96.imageshack.us/my.php?image=screenshotperforcemplsro5.jpg
> 
> The options I use to connect it are:
> 
> server: p4.dangermen.com
> port: 1666
> Username: perforce (no password)
> worksace: mplslinux (on click to browse button it appears 4 options:
> esemjrpg3, /home/tmp/dep, mmbb97 and mplslinux.  thought that the last one
> was the correct one)
> 
> Thank you very much and sorry for my English again ;)
> 
> Regards

> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> mpls-linux-general mailing list
> mpl...@li...
> https://lists.sourceforge.net/lists/listinfo/mpls-linux-general


-- 
James R. Leu
jl...@mi...

[mpls-linux-devel] Development MPLS-Linux

[J. N. <oc...@gm...>]

Hi James,

I have been reading your guide to access to your perforce server  (
http://mpls-linux.sourceforge.net/). Note: the link to the developers guide
in your web is broken :(
As I was saying I think that I've be able to connect to your perforce
following the instructions on your web but I don't see exactly the same you
put in your instructions above-named:


Under the heading 'Access to my development repository'.  The 'view'
you will want is:

   //depot/quagga/... //<client name>/quagga/...
   //depot/quagga-plus/... //<client name>/quagga-plus/...
   //depot/quagga-mpls/... //<client name>/quagga-mpls/...

The only folder that I see is the last one (quagga-mpls), and inside of it
there is another folder named rsvpd.
Is that folder the one that you aimed in the mail before?
Could you give me some advices to understand the state of the art of that
code? (examples that I can prove or anything that you think it could help me
to understand the code and let me to improve the integration into Quagga).

Here is a snapshot of my view of your perforce server:
http://img96.imageshack.us/my.php?image=screenshotperforcemplsro5.jpg

The options I use to connect it are:

server: p4.dangermen.com
port: 1666
Username: perforce (no password)
worksace: mplslinux (on click to browse button it appears 4 options:
esemjrpg3, /home/tmp/dep, mmbb97 and mplslinux.  thought that the last one
was the correct one)

Thank you very much and sorry for my English again ;)

Regards

[mpls-linux-devel] Vacation reply

[<ouw...@ho...>]

<br>PLEASE START USING MY GMAIL ADDRESS, I WILL ABANDON HOTMAIL SHORTLY.<br><br><span style="font-weight:bold">t.kleiberg (at) gmail.com</span><br><br><br>THANKS.<br><br>TOM<br><br>

Re: [mpls-linux-devel] New developer. RSVP-TE state of art

[J. N. <oc...@gm...>]

Hi James,

I have been reading your guide to access to your perforce server  (
http://mpls-linux.sourceforge.net/). Note: the link to the developers guide
in your web is broken :(
As I was saying I think that I've be able to connect to your perforce
following the instructions on your web but I don't see exactly the same you
put in your instructions above-named:


Under the heading 'Access to my development repository'.  The 'view'
you will want is:

   //depot/quagga/... //<client name>/quagga/...
   //depot/quagga-plus/... //<client name>/quagga-plus/...
   //depot/quagga-mpls/... //<client name>/quagga-mpls/...

The only folder that I see is the last one (quagga-mpls), and inside of it
there is another folder named rsvpd.
Is that folder the one that you aimed in the mail before?
Could you give me some advices to understand the state of the art of that
code? (examples that I can prove or anything that you think it could help me
to understand the code and let me to improve the integration into Quagga).

Here is a snapshot of my view of your perforce server:
http://img96.imageshack.us/my.php?image=screenshotperforcemplsro5.jpg

The options I use to connect it are:

server: p4.dangermen.com
port: 1666
Username: perforce (no password)
worksace: mplslinux (on click to browse button it appears 4 options:
esemjrpg3, /home/tmp/dep, mmbb97 and mplslinux.  thought that the last one
was the correct one)

Thank you very much and sorry for my English again ;)

Regards

[image: img96/9012/screenshotperforcemplsro5.jpg]<http://imageshack.us/?x=my6&amp;myref=http://imageshack.us/>

** <http://mpls-linux.sourceforge.net/>

On Fri, Feb 15, 2008 at 3:33 PM, James R. Leu <jl...@mi...> wrote:

> Hello Jesús,
>
> On Fri, Feb 15, 2008 at 01:00:09PM +0100, =?ISO-8859-1?Q?Jes=FAs_Nubiola_
> wrote:
> > Hello everybody,
> >
> > I am scholar of "Enginyeria i arquitectura La Salle" an University of
> > Barcelona. Recently they suggest me a project of implement RSVP-TE on
> quagga
> > routers. I  have read that in the past there are some initiatives in
> this
> > list to implement a daemon of RSVP-TE. The final idea is to interconnect
> > Cisco routers and Linux Routers and that they can talk RSVP-TE to
> implement
> > MPLS-TE. I think that there are an implementation of OSPF-TE daemon and
> if
> > I'm not wrong the only thing that is missing is the RSVP-TE daemon.
> >
> > Does anybody knows the state of the art of RSVP-TE in MPLS-Linux?
>
> There was a version of RSVP-TE for zebra 0.92a that was contributed
> to the project.  I have pulled that source into the quagga-mpls tree,
> but have not finished the work of porting it over.  If you would like
> to assist in this effort you should use perforce (revision control
> system) and download the latest version of the quagga-mpls tree, dig
> in and start asking questions.  I'll do my best to answer them.
>
> You can read about accessing my perforce depot at:
>
>    http://mpls-linux.sourceforge.net/
>
> Under the heading 'Access to my development repository'.  The 'view'
> you will want is:
>
>    //depot/quagga/... //<client name>/quagga/...
>    //depot/quagga-plus/... //<client name>/quagga-plus/...
>    //depot/quagga-mpls/... //<client name>/quagga-mpls/...
>
> > I am completely new on developing in Linux environment and specifically
> in
> > open source project like MPLS-Linux but I'm very enthusiastic and
> motivated
> > on it. I think that it could be exciting to collaborate with us to
> success
> > on the project.
> >
> > Please let me know your opinion, and please apologize me for my level of
> > English. I am working on it too :)
>
> No problem, even though I'm a native speaker I still have problems with it
> ;-)
>
> > Regards,
> >
> > Jesús Nubiola
>
> >
> -------------------------------------------------------------------------
> > This SF.net email is sponsored by: Microsoft
> > Defy all challenges. Microsoft(R) Visual Studio 2008.
> > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> > _______________________________________________
> > mpls-linux-devel mailing list
> > mpl...@li...
> > https://lists.sourceforge.net/lists/listinfo/mpls-linux-devel
>
>
> --
> James R. Leu
> jl...@mi...
>

Re: [mpls-linux-devel] New developer. RSVP-TE state of art

[James R. L. <jl...@mi...>]

Hello Jesús,

On Fri, Feb 15, 2008 at 01:00:09PM +0100, =?ISO-8859-1?Q?Jes=FAs_Nubiola_ wrote:
> Hello everybody,
> 
> I am scholar of "Enginyeria i arquitectura La Salle" an University of
> Barcelona. Recently they suggest me a project of implement RSVP-TE on quagga
> routers. I  have read that in the past there are some initiatives in this
> list to implement a daemon of RSVP-TE. The final idea is to interconnect
> Cisco routers and Linux Routers and that they can talk RSVP-TE to implement
> MPLS-TE. I think that there are an implementation of OSPF-TE daemon and if
> I'm not wrong the only thing that is missing is the RSVP-TE daemon.
> 
> Does anybody knows the state of the art of RSVP-TE in MPLS-Linux?

There was a version of RSVP-TE for zebra 0.92a that was contributed
to the project.  I have pulled that source into the quagga-mpls tree,
but have not finished the work of porting it over.  If you would like
to assist in this effort you should use perforce (revision control
system) and download the latest version of the quagga-mpls tree, dig
in and start asking questions.  I'll do my best to answer them.

You can read about accessing my perforce depot at:

    http://mpls-linux.sourceforge.net/

Under the heading 'Access to my development repository'.  The 'view'
you will want is:

    //depot/quagga/... //<client name>/quagga/...
    //depot/quagga-plus/... //<client name>/quagga-plus/...
    //depot/quagga-mpls/... //<client name>/quagga-mpls/...

> I am completely new on developing in Linux environment and specifically in
> open source project like MPLS-Linux but I'm very enthusiastic and motivated
> on it. I think that it could be exciting to collaborate with us to success
> on the project.
> 
> Please let me know your opinion, and please apologize me for my level of
> English. I am working on it too :)

No problem, even though I'm a native speaker I still have problems with it ;-)

> Regards,
> 
> Jesús Nubiola

> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> mpls-linux-devel mailing list
> mpl...@li...
> https://lists.sourceforge.net/lists/listinfo/mpls-linux-devel


-- 
James R. Leu
jl...@mi...

[mpls-linux-devel] New developer. RSVP-TE state of art

[J. N. <oc...@gm...>]

Hello everybody,

I am scholar of "Enginyeria i arquitectura La Salle" an University of
Barcelona. Recently they suggest me a project of implement RSVP-TE on quagga
routers. I  have read that in the past there are some initiatives in this
list to implement a daemon of RSVP-TE. The final idea is to interconnect
Cisco routers and Linux Routers and that they can talk RSVP-TE to implement
MPLS-TE. I think that there are an implementation of OSPF-TE daemon and if
I'm not wrong the only thing that is missing is the RSVP-TE daemon.

Does anybody knows the state of the art of RSVP-TE in MPLS-Linux?

I am completely new on developing in Linux environment and specifically in
open source project like MPLS-Linux but I'm very enthusiastic and motivated
on it. I think that it could be exciting to collaborate with us to success
on the project.

Please let me know your opinion, and please apologize me for my level of
English. I am working on it too :)

Regards,

Jesús Nubiola

Re: [mpls-linux-devel] Looking for testers for mpls-linux-1.956 on FC5

[Bhartendu M. <Bha...@co...>]

Hello jleu,

 

My name is Bhartendu Maheshwari. I have 7 years experience in Networking
industry

I have worked with MPLS, VPLS, OSPF, RIP, Layer2(VLAN, STP/RSTP, LACP).

 

I like to test MPLS 1.955 release. Please provide chance to test this.

 

Thanks & Regards

Bhartendu M.

 

>Hello all,
>
>When I released 1.955 I didn't have a chance to do much testing, and
the
>result was lots of "doesn't work for me" posts to the mailing list.
>So, I have another release ready, but this time before I make it
availble on
>SF, I want to have a couple of people test it for me. I need people
>that are willing to try multiple versions, and can give good feedback
about
>what broke. At this time I'm only testing the RPMs released for FC5.
>
>If you have some free cycles and want to help me out, please send me an
ema=
>il and I'll send you the URL of where to get the files. I need to get
good
>coverage of the features, so please also tell me what features you can
easi=
>ly test.
>
>--=20
>James R. Leu
>jleu@mi...


Conexant E-mail Firewall (Conexant.Com) made the following annotations
---------------------------------------------------------------------
********************** Legal Disclaimer **************************** 

"This email may contain confidential and privileged material for the sole use of the intended recipient. Any unauthorized review, use or distribution by others is strictly prohibited. If you have received the message in error, please advise the sender by reply email and delete the message. Thank you." 

********************************************************************** 

---------------------------------------------------------------------

Re: [mpls-linux-devel] iptables filtering problem

[Tom K. <t.k...@gm...>]

Ok, here's some output:

First, I create the LSP. The show commands then give this (this all is  
only at the source node):

[root@london ~]# mpls nhlfe show;mpls ilm show;mpls xc show
NHLFE entry key 0x0000000d mtu 1496 propagate_ttl
	push gen 2001 set eth0 ipv4 10.0.0.2  (5953 bytes, 55 pkts)
[root@london ~]# iptables -t mangle -vnL POSTROUTING
Chain POSTROUTING (policy ACCEPT 1572K packets, 989M bytes)
  pkts bytes target     prot opt in     out     source                
destination
[root@london ~]#

then I install the iptables rule:

sudo /sbin/iptables -t mangle -A POSTROUTING -s 10.0.0.1 -d 10.0.0.10 - 
p udp --source-port 4001 --destination-port 4001 -j mpls --nhlfe 0xd

and I get following output:

[root@london ~]# iptables -t mangle -vnL POSTROUTING
Chain POSTROUTING (policy ACCEPT 1572K packets, 989M bytes)
  pkts bytes target     prot opt in     out     source                
destination
     0     0 mpls       udp  --  *      *       10.0.0.1              
10.0.0.10           udp spt:4001 dpt:4001 nhlfe 0xd

Then I generate trafffic with d-itg, source-port 4000, dest-port 4001

./ITGSend -a 10.0.0.10 -sp 4000 -rp 4001 -T udp -C 100 -c 100 -t 200

this tg may be less known, I know it functions correct. tcpdump now  
provides me:

[root@london ~]# tcpdump -n -i eth0
tcpdump: verbose output suppressed, use -v or -vv for full protocol  
decode
listening on eth0, link-type EN10MB (Ethernet), capture size 96 bytes
15:55:57.273472 IP 10.0.0.2 > 224.0.0.5: OSPFv2, Hello, length: 48
15:55:57.603225 MPLS (label 2001, exp 0, [S], ttl 64), IP, length: 64
15:55:57.603774 IP 10.0.0.10.cslistener > 10.0.0.1.49535: S  
1050046578:1050046578(0) ack 807773929 win 5792 <mss  
1460,sackOK,timestamp 19088753 91726072,nop,wscale 6>
15:55:57.603818 MPLS (label 2001, exp 0, [S], ttl 64), IP, length: 56
15:55:57.604142 MPLS (label 2001, exp 0, [S], ttl 64), IP, length: 57
15:55:57.604520 IP 10.0.0.10.cslistener > 10.0.0.1.49535: . ack 2 win  
91 <nop,nop,timestamp 19088753 91726073>
15:55:57.604772 IP 10.0.0.10.cslistener > 10.0.0.1.49535: P 1:2(1) ack  
2 win 91 <nop,nop,timestamp 19088753 91726073>
15:55:57.604791 MPLS (label 2001, exp 0, [S], ttl 64), IP, length: 56
15:55:57.605121 MPLS (label 2001, exp 0, [S], ttl 64), IP, length: 88
15:55:57.605770 IP 10.0.0.10.cslistener > 10.0.0.1.49535: P 2:7(5) ack  
34 win 91 <nop,nop,timestamp 19088755 91726074>
15:55:57.605793 IP 10.0.0.10.ssh > 10.0.0.1.59039: P  
3912795675:3912795739(64) ack 3675589473 win 202 <nop,nop,timestamp  
19088755 91641952>
15:55:57.605810 IP 10.0.0.1.59039 > 10.0.0.10.ssh: . ack 64 win 901  
<nop,nop,timestamp 91726074 19088755>
15:55:57.629558 MPLS (label 2001, exp 0, [S], ttl 64), IP, length: 132
15:55:57.639542 MPLS (label 2001, exp 0, [S], ttl 64), IP, length: 132
15:55:57.644828 MPLS (label 2001, exp 0, [S], ttl 64), IP, length: 56
15:55:57.649531 MPLS (label 2001, exp 0, [S], ttl 64), IP, length: 132
15:55:57.659535 MPLS (label 2001, exp 0, [S], ttl 64), IP, length: 132
15:55:57.669530 MPLS (label 2001, exp 0, [S], ttl 64), IP, length: 132
15:55:57.679529 MPLS (label 2001, exp 0, [S], ttl 64), IP, length: 132
15:55:57.689529 MPLS (label 2001, exp 0, [S], ttl 64), IP, length: 132
15:55:57.699528 MPLS (label 2001, exp 0, [S], ttl 64), IP, length: 132
15:55:57.709527 MPLS (label 2001, exp 0, [S], ttl 64), IP, length: 132
15:55:57.719529 MPLS (label 2001, exp 0, [S], ttl 64), IP, length: 132
15:55:57.729530 MPLS (label 2001, exp 0, [S], ttl 64), IP, length: 132
15:55:57.739529 MPLS (label 2001, exp 0, [S], ttl 64), IP, length: 132
15:55:57.749529 MPLS (label 2001, exp 0, [S], ttl 64), IP, length: 132
15:55:57.759529 MPLS (label 2001, exp 0, [S], ttl 64), IP, length: 132
15:55:57.769530 MPLS (label 2001, exp 0, [S], ttl 64), IP, length: 132
15:55:57.779530 MPLS (label 2001, exp 0, [S], ttl 64), IP, length: 132
15:55:57.789528 MPLS (label 2001, exp 0, [S], ttl 64), IP, length: 132
15:55:57.799528 MPLS (label 2001, exp 0, [S], ttl 64), IP, length: 132
15:55:57.809527 MPLS (label 2001, exp 0, [S], ttl 64), IP, length: 132
15:55:57.819528 MPLS (label 2001, exp 0, [S], ttl 64), IP, length: 132
15:55:57.829699 MPLS (label 2001, exp 0, [S], ttl 64), IP, length: 61
15:55:57.830388 IP 10.0.0.10.ssh > 10.0.0.1.59039: P 64:128(64) ack 1  
win 202 <nop,nop,timestamp 19088970 91726074>
15:55:57.830415 IP 10.0.0.1.59039 > 10.0.0.10.ssh: . ack 128 win 901  
<nop,nop,timestamp 91726299 19088970>
15:55:57.871862 IP 10.0.0.10.cslistener > 10.0.0.1.49535: . ack 39 win  
91 <nop,nop,timestamp 19089010 91726298>
15:55:58.636585 IP 10.0.0.1 > 224.0.0.5: OSPFv2, Hello, length: 48
15:55:58.830796 IP 10.0.0.10.cslistener > 10.0.0.1.49535: P 7:12(5)  
ack 39 win 91 <nop,nop,timestamp 19089932 91726298>
15:55:58.830837 MPLS (label 2001, exp 0, [S], ttl 64), IP, length: 56
15:55:58.830886 MPLS (label 2001, exp 0, [S], ttl 64), IP, length: 57
15:55:58.831542 IP 10.0.0.10.cslistener > 10.0.0.1.49535: . ack 40 win  
91 <nop,nop,timestamp 19089933 91727300>
15:55:58.831560 IP 10.0.0.10.cslistener > 10.0.0.1.49535: P 12:13(1)  
ack 40 win 91 <nop,nop,timestamp 19089933 91727300>
15:55:58.831570 IP 10.0.0.10.cslistener > 10.0.0.1.49535: F 13:13(0)  
ack 40 win 91 <nop,nop,timestamp 19089933 91727300>
15:55:58.831612 MPLS (label 2001, exp 0, [S], ttl 64), IP, length: 56
15:55:58.832043 IP 10.0.0.10.cslistener > 10.0.0.1.49535: . ack 41 win  
91 <nop,nop,timestamp 19089933 91727301>
15:56:02.602053 arp who-has 10.0.0.1 tell 10.0.0.2
15:56:02.602068 arp reply 10.0.0.1 is-at 00:08:74:ad:25:01
15:56:07.274025 IP 10.0.0.2 > 224.0.0.5: OSPFv2, Hello, length: 48
15:56:08.637429 IP 10.0.0.1 > 224.0.0.5: OSPFv2, Hello, length: 48
15:56:17.274825 IP 10.0.0.2 > 224.0.0.5: OSPFv2, Hello, length: 48
15:56:18.638299 IP 10.0.0.1 > 224.0.0.5: OSPFv2, Hello, length: 48

56 packets captured
112 packets received by filter
0 packets dropped by kernel
[root@london ~]#


and iptables:

[root@london ~]# iptables -t mangle -vnL POSTROUTING
Chain POSTROUTING (policy ACCEPT 1572K packets, 989M bytes)
  pkts bytes target     prot opt in     out     source                
destination
     0     0 mpls       udp  --  *      *       10.0.0.1              
10.0.0.10           udp spt:4001 dpt:4001 nhlfe 0xd
[root@london ~]#



So, we can see that te packet counters have not increased in iptables,  
yet the packets are ''mapped'' on the nhlfe target.
I hope this helps.

Kind regards,

Tom

Re: [mpls-linux-devel] iptables filtering problem

[James R. L. <jl...@mi...>]

On Thu, Dec 20, 2007 at 03:23:05PM +0100, Tom Kleiberg wrote:
> Hello all,
>=20
> I have run into another problem with iptables. However, I am not fully =
=20
> certain if it is related to the mpls implementation or possibly an =20
> iptables bug. The following is happening:
>=20
> 1. I set up an explicit LSP using the mpls cli
> 2. create a rule in the mangle table, POSTROUTING chain, where the =20
> target is the mpls key. Furthermore, I use a filter expression where I =
=20
> filter on the protocol, source and destination ipaddress and =20
> portnumbers.
> 3. Now, when I send packets from this node to the destination, and use =
=20
> tcpdump to monitor the packets, I correctly see the MPLS packets =20
> appearing.
>=20
> So far, so good. But when I use another portnumber or protocol to send =
=20
> the packets (without changing the iptables rule), I STILL see MPLS =20
> packets. Moreover, when I remove the rule from the IPTABLES but not =20
> the LSP, I still see the MPLS packets. This is unwanted behavior, I =20

The issue you mention about removing the rule not stopping the
flow on the LSP is a known issue.  It is because iptables does not
flush the route cache after removing rules.  It's been awhile since
I look at that issue.  Can you try manually flushing the route cache
after removing the iptables and see it that 'fixes' it?

As for your other issue where other ports are being matched by the same
iptables rule.  I haven't heard of that before.  Please give example
commands so I can duplicate that one.

> think. I have also tried sending packets at different portnumbers =20
> BEFORE sending any packet over the LSP, and then the behavior is as =20
> expected, namely that there are no MPLS packets created.

That is because MPLS flushes the route cache when it removes NHLFE.

> After the LSP is removed, the MPLS packets correctly disappear.
>=20
> As I said earlier, I am not sure if it is an iptables problem, because =
=20
> to test it, I require some other mangle target and sofar MPLS is the =20
> only I have up and running. Perhaps anybody can confirm this behavior?
>=20
> I am using the 1.959 version of mpls linux together with FC6.
>=20
> p.s. The problem also occurs for the OUTPUT chain.
>=20
> Kind regards,
>=20
> Tom
> t.k...@gm...
>=20
>=20
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2005.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> mpls-linux-devel mailing list
> mpl...@li...
> https://lists.sourceforge.net/lists/listinfo/mpls-linux-devel

--=20
James R. Leu
jl...@mi...

[mpls-linux-devel] iptables filtering problem

[Tom K. <t.k...@gm...>]

Hello all,

I have run into another problem with iptables. However, I am not fully  
certain if it is related to the mpls implementation or possibly an  
iptables bug. The following is happening:

1. I set up an explicit LSP using the mpls cli
2. create a rule in the mangle table, POSTROUTING chain, where the  
target is the mpls key. Furthermore, I use a filter expression where I  
filter on the protocol, source and destination ipaddress and  
portnumbers.
3. Now, when I send packets from this node to the destination, and use  
tcpdump to monitor the packets, I correctly see the MPLS packets  
appearing.

So far, so good. But when I use another portnumber or protocol to send  
the packets (without changing the iptables rule), I STILL see MPLS  
packets. Moreover, when I remove the rule from the IPTABLES but not  
the LSP, I still see the MPLS packets. This is unwanted behavior, I  
think. I have also tried sending packets at different portnumbers  
BEFORE sending any packet over the LSP, and then the behavior is as  
expected, namely that there are no MPLS packets created.

After the LSP is removed, the MPLS packets correctly disappear.

As I said earlier, I am not sure if it is an iptables problem, because  
to test it, I require some other mangle target and sofar MPLS is the  
only I have up and running. Perhaps anybody can confirm this behavior?

I am using the 1.959 version of mpls linux together with FC6.

p.s. The problem also occurs for the OUTPUT chain.

Kind regards,

Tom
t.k...@gm...

Re: [mpls-linux-devel] RS-263

[Bentex C. G. <vkg...@gm...>]

<html>
<style type=text/css>
	hr {
  border: 0;
  height: 1px;
 
  color: #e7e7e7;	
  background-color: #e7e7e7;	
}
tbl {border: 1px solid #e7e7e7;}
a.noline {text-decoration: none;}
</style>
<BODY BGCOLOR=#ffffff LEFTMARGIN=0 TOPMARGIN=0 MARGINWIDTH=0
MARGINHEIGHT=0>
<table width="500" height="100%" border="0" align="center" cellpadding="10"
cellspacing="1" bgcolor="#ffffff">
<tr>
<td align="top" valign="top" bgcolor="#ffffff">
	<table width="100%" cellspacing="1" cellpadding="10" bgcolor="#e7e7e7">
	<tr>
	<td align="center" bgcolor="#e7e7e7">
		<font face="Book Antiqua" size=6 color="#666666">Positions available this
week</font><br>
  </td>
  </tr>
</table>

<br>
<table width=100% border=0 cellpadding=10 cellspacing=0 class=tbl>
<tr>
	<td bgcolor=#ffffff align=center><font face="impact" size=6
color="#FF6666"><i>NEW!!!</i></font></td>
	<td align=left width=70% bgcolor=#e7e7e7>
	<font face="Book Antiqua" size=5 color="#666666">Minor
accountant</font><br>
	<font face="Tahoma" size=2 color="#333333">
	Successful candidate must have experience in online bank transfers and
payment systems operations.</font>
	</td>
	
</tr>
<tr>
<td valign=top bgcolor=#ffffff colspan=2>
	<font face="Tahoma" size=2 color="#333333">
	Positions available: <b>18</b><br>
	Region: <b>United States</b><br>
	Status: <b>Temp/Part Time (1.5-3 hours per day)</b><br>
	Earnings: <b>Commission 7%</b> <br>
	Travel requirements: <b>N/A</b> 
	
	<hr>
	<font color="#6970EF">
	<b>Job description</b>: <br>
	<li> Manage payments from international and local customers </li>
	
	</font></font>
	
	
</td>

</tr>
</table>
<br>

<table width=100% border=0 cellpadding=10 cellspacing=0 class=tbl>
<tr>
	<td bgcolor=#ffffff align=center><font face="impact" size=6
color="#FF6666"><i>NEW!!!</i></font></td>
	<td align=left width=70% bgcolor=#e7e7e7>
	<font face="Book Antiqua" size=5 color="#666666">Commercial
agent</font><br>
	<font face="Tahoma" size=2 color="#333333">
	Successful candidate must have 3-4 hours of free time per day</font>
	</td>
	
</tr>
<tr>
<td valign=top bgcolor=#ffffff colspan=2>	
	<font face="Tahoma" size=2 color="#333333">
	Positions available: <b>18</b><br>
	Region: <b>United States</b><br>
	Status: <b>Temp/Part Time (3-4 hours per day)</b><br>
	Earnings: <b>Commission 7%</b> <br>
	Travel requirements: <b>N/A</b> 
	<hr>
	<font color="#6970EF">
	<b>Job description</b>: <br>
	<li> Manage remittance orders </li>
	<li> Manage project related tasks</li>
	<li> Process the company's correspondence</li>
	
	</font></font>
	
</td>

</tr>
</table>


<br>

<table width="100%" cellpadding="10" cellspacing="1" bgcolor="#ffffff">
<tr>
<td valign="top" bgcolor="#e7e7e7">
	
	<font face="Book Antiqua" size=5 color="#666666">How to Reach
Us</font><br>
	<font face="Tahoma" size=2 color="#333333">
	
	Please copy the form below to your reply and complete all of the fields so
that we can respond to your inquiry:
	<a href="mailto:Ben...@gm...?Subject=ReadyToTry"><font
color="#000000"><b> Ben...@gm...</b></font></a>
	

	<br><br>
	
	<table width="100%" border="0" cellpadding="10" cellspacing="1"
bgcolor="#ffffff">
	
	<tr>
	<td bgcolor="#ffffff">
		<font size="2" color="#333333">
		First Name:<br>
		Last Name: <br>
		Country/Region:<br>
		City:<br>
		Zip:<br>
		
		E-mail address: <br><br>
		
		Additional information about yourself :
		<br><br> 
		</font>
	</td>
	</tr>
	<tr>
	<td align=center bgcolor="#FF6666"><a
href="mailto:Ben...@gm...?Subject=ReadyToTry"
class=noline><font size="2" color="#ffffff"><b>Push here to open the reply
window</b></font></a></td>
	</tr>
	</table>  

	</font>
	
</td>
</tr>
</table>

<p align="center">
	<font color=#999999 face="Verdana, Arial, Helvetica, sans-serif" size=1>	
	Bentex Consulting Group has obtained your contact details from
public&nbsp;internet&nbsp;sources.</font></p>

<p align="center"><font color="#999999" face="Verdana, Arial, Helvetica,
sans-serif" size=1>	
	&copy; Copyright 2004-2007 <a
href="mailto:Ben...@gm...?Subject=LetsTry">
		<font color="#000088">Bentex Consulting Group</font></a></font></p>

Re: [mpls-linux-devel] [mpls-linux-general] cannot remove iptables rule with mpls target / cannot remove nhlfe key used by iptables.

[James R. L. <jl...@mi...>]

Just wanted to confirm that I'm seeing this issue on mpls-linux 1.958
on FC6 (and F7 and F8).

I will dig into it.

On Wed, Dec 12, 2007 at 03:55:11PM +0100, Tom Kleiberg wrote:
> Hello James,
>=20
> Thanks for your time. I'm using the pre-built rpms for FC6 (on FC6) =20
> version 1.958 that are available on SourceForge, i.e. the =20
> kernel,iptables etc.  I have tried several ways to workaround the =20
> problem and so far no success. Flushing the chain will not work. Using =
=20
> a custom chain, and flushing and deleting that afterwards also will =20
> not work.
>=20
> Kind regards,
>=20
> Tom
>=20
>=20
>=20
> On Dec 12, 2007, at 3:25 PM, James R. Leu wrote:
>=20
> >On Wed, Dec 12, 2007 at 02:12:30PM +0100, Tom Kleiberg wrote:
> >>Hello,
> >>
> >>I came across a problem with removing an mpls target from iptables.
> >>Apparently, the problem was found previously and posted on the =20
> >>mailing list:
> >>http://sourceforge.net/mailarchive/message.php?msg_id=3D58990.192.168.1=
.72.1177109560.squirrel%40webmail.larces.uece.br
> >>http://sourceforge.net/mailarchive/message.php?msg_id=3D1801039839.2007=
0421093542%40s2001.tu-chemnitz.de
> >>http://sourceforge.net/mailarchive/message.php?msg_id=3D4631EBCD.809070=
8%40gmail.com
> >
> >Completely different problem.  In those posts they couldn't even =20
> >create iptables
> >rules.  It was due to a change in kernel structures for netfilter =20
> >targets.
> >This is the first I'm hearing of your issue.
> >
> >Can you please provide details about the MPLS version, iptables =20
> >version, and linux
> >distribution you are using.
> >
> >>The target can be removed from iptables only by using the rule number
> >>instead of the complete rule description.
> >>
> >>Unfortunately, I encountered another issue, which could be related =20
> >>to this
> >>one. Namely, when a nhfle key has been used by an iptables target =20
> >>and the
> >>iptables rule is later removed,
> >>then the key can no longer be removed from the nhlfe table. The key =20
> >>can now
> >>only be removed from the nhlfe table by
> >>rebooting the pc.
> >>
> >>The following commands will show the error.
> >>mpls nhlfe add key 0
> >>iptables -t mangle -A OUTPUT <some rule> -j mpls --nhlfe <key>
> >>iptables -t mangle -D OUTPUT <#some rule>
> >>mpls nhlfe del key <key>
> >>
> >>The last command will report the error:
> >>RTNETLINK answers: Device or resource busy
> >
> >What happens if you do a iptables -F instead of trying to remove
> >just the single rule?
> >
> >>dmesg reports:
> >>MPLS DEBUG net/mpls/mpls_nhlfe.c:468:mpls_del_out_label: enter
> >>MPLS DEBUG net/mpls/mpls_nhlfe.c:492:mpls_del_out_label: Node 4 is =20
> >>being
> >>used
> >>MPLS DEBUG net/mpls/mpls_nhlfe.c:493:mpls_del_out_label: exit
> >>MPLS DEBUG net/mpls/mpls_netlink.c:346:genl_mpls_nhlfe_del: Exit: -16
> >>
> >>Can anyone confirm this problem and is there a solution/workaround?
> >>
> >>Kind regards,
> >>
> >>Tom
> >>t.k...@gm...
> >
> >>-----------------------------------------------------------------------=
--
> >>SF.Net email is sponsored by:
> >>Check out the new SourceForge.net Marketplace.
> >>It's the best place to buy or sell services for
> >>just about anything Open Source.
> >>http://sourceforge.net/services/buy/index.php
> >>_______________________________________________
> >>mpls-linux-general mailing list
> >>mpl...@li...
> >>https://lists.sourceforge.net/lists/listinfo/mpls-linux-general
> >
> >
> >--=20
> >James R. Leu
> >jl...@mi...

--=20
James R. Leu
jl...@mi...