mpls-linux-general

Re: [mpls-linux-general] ldp-portable updates

[Venisa C. <vca...@ho...>]

Hi James,

Thanks for your ldp-portable updates, now I can see that mpls_in, mpls_out, 
and mpls_fec are not empty.

I use the simple configuration in file README.sample :

     lo 10.0.0.6                lo 10.0.0.5
      ---------                  ---------
     | Router2 |----------------| Router1 |
      ---------                  ---------
          |eth2  192.168.12.0/24     |eth1
     ---------------------------------------

In router1:
bash# ifconfig lo 10.0.0.5 netmask 255.255.255.255
bash# route add 10.0.0.6 gw 192.168.12.2

From inside ldp_linux:
prompt> add global 10.0.0.5
prompt> add interface eth1

In router2:
bash# ifconfig lo 10.0.0.6 netmask 255.255.255.255
bash# route add 10.0.0.5 gw 192.168.12.1

From inside ldp_linux:
prompt> add global 10.0.0.6
prompt> add interface eth2

After that I can see that mpls_in, mpls_out, and mpls_fec in each router are 
not empty.

Unfortunately, I cannot ping anymore router1 from router2 and router2 from 
router1. Before I enter ldp_linux, I can ping 10.0.0.5 from router1 and ping 
10.0.0.6 from router2. However, I can see the MPLS encapsulation using 
ethereal for ping request messages but there is no ping reply message.

Would you mind verify my configuration above and tell me what might be my 
mistakes ?


PS: I have to explicitly add the routes using route commands this time, 
because if I use zebra, I cannot use ethereal (ethereal hangs).
I still do not know the reason, it might be due to TCP/UDP conflicts.


regards,
~Venisa Cabrilla



>From: "James R. Leu" <jl...@mi...>
>Reply-To: jl...@mi...
>To: mpl...@li...
>Subject: [mpls-linux-general] ldp-portable updates
>Date: Sun, 24 Jun 2001 20:23:13 -0500
>
>Sorry to those who have been trying to use ldp-portable from CVS.
>I finnally have gotten around to fixing and testing ldp-portable.
>It's almost back to where it was before I started mucking around with PDU
>processing.  (interoping with cisco pointed out the need to handle multiple
>PDUs per TCP segment and handle one PDU spread across multiple TCP 
>segments)
>
>If you tried ldp-portable in the last 3 weeks and it was broken, try
>updating your CVS client and giving it another go.
>
>Sorry for the long delay.
>Jim
>--
>James R. Leu
>
>_______________________________________________
>mpls-linux-general mailing list
>mpl...@li...
>http://lists.sourceforge.net/lists/listinfo/mpls-linux-general

_________________________________________________________________________
Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.

Re: [mpls-linux-general] ldp-portable updates

[Venisa C. <vca...@ho...>]

Hi,

Sorry for the late response, I have to go downstair and upstair just to copy 
the contents of /proc/net/mpls_*, (my lab and my office are not in the same 
room) but I have done as fast as I can ... :-)

First, I have to inform you that since I use my computers as routers, I do 
certainly have at least three ethernet cards in my routers (that is, the 
topology that I gave you is far from complete, which will explain the 
important contents of file mpls_in) but I used only the commands that I have 
described in my last email.

In router1:
mpls_in:
40004000 gen 16 0 POP DLV
40004400 gen 17 0 POP DLV
40004800 gen 18 0 POP DLV
40004c00 gen 19 0 POP DLV
40005000 gen 20 0 POP DLV
40005400 gen 21 0 POP DLV
40005800 gen 22 0 POP DLV
mpls_out:
40004003 PUSH(gen 16) SET (eth1)
mpls_fec:
40004003 10.0.0.6/32
mpls_labelspace:
lo 0

In router2:
mpls_in:
40004000 gen 16 0 POP DLV
40004400 gen 17 0 POP DLV
40004800 gen 18 0 POP DLV
40004c00 gen 19 0 POP DLV
40005000 gen 20 0 POP DLV
40005400 gen 21 0 POP DLV
40005800 gen 22 0 POP DLV
mpls_out:
40004004 PUSH(gen 16) SET (eth2)
mpls_fec:
40004004 10.0.0.5/32
mpls_labelspace:
lo 0

There is nothing in mpls_tunnel, which is normal.


regards,
~Venisa Cabrilla



>From: "James R. Leu" <jl...@mi...>
>Reply-To: jl...@mi...
>To: Venisa Cabrilla <vca...@ho...>
>CC: mpl...@li...
>Subject: Re: [mpls-linux-general] ldp-portable updates
>Date: Tue, 26 Jun 2001 08:45:55 -0500
>
>On Tue, Jun 26, 2001 at 01:31:11PM -0000, Venisa Cabrilla wrote:
> > Hi James,
> >
> > Thanks for your ldp-portable updates, now I can see that mpls_in, 
>mpls_out,
> > and mpls_fec are not empty.
>
>Hello,
>
>I think I know the problem.  It has to do with the fact that LDP is setting 
>up
>LSPs for too many entries in the route table.  Send me the contents of
>/proc/net/mpls_* and we can verify this.
>
>My default policy of "send labels for everything" may not be valid in all
>cases.  This will be simple enough to change I just need to figure out what 
>the
>best default policy should be :-(
>
>I'll try to duplicate this setup here and see if I can figure it out as 
>well.
>
>Jim
>
> >
> > I use the simple configuration in file README.sample :
> >
> >      lo 10.0.0.6                lo 10.0.0.5
> >       ---------                  ---------
> >      | Router2 |----------------| Router1 |
> >       ---------                  ---------
> >           |eth2  192.168.12.0/24     |eth1
> >      ---------------------------------------
> >
> > In router1:
> > bash# ifconfig lo 10.0.0.5 netmask 255.255.255.255
> > bash# route add 10.0.0.6 gw 192.168.12.2
> >
> > >From inside ldp_linux:
> > prompt> add global 10.0.0.5
> > prompt> add interface eth1
> >
> > In router2:
> > bash# ifconfig lo 10.0.0.6 netmask 255.255.255.255
> > bash# route add 10.0.0.5 gw 192.168.12.1
> >
> > >From inside ldp_linux:
> > prompt> add global 10.0.0.6
> > prompt> add interface eth2
> >
> > After that I can see that mpls_in, mpls_out, and mpls_fec in each router 
>are
> > not empty.
> >
> > Unfortunately, I cannot ping anymore router1 from router2 and router2 
>from
> > router1. Before I enter ldp_linux, I can ping 10.0.0.5 from router1 and 
>ping
> > 10.0.0.6 from router2. However, I can see the MPLS encapsulation using
> > ethereal for ping request messages but there is no ping reply message.
> >
> > Would you mind verify my configuration above and tell me what might be 
>my
> > mistakes ?
> >
> >
> > PS: I have to explicitly add the routes using route commands this time,
> > because if I use zebra, I cannot use ethereal (ethereal hangs).
> > I still do not know the reason, it might be due to TCP/UDP conflicts.
> >
> >
> > regards,
> > ~Venisa Cabrilla
> >
> >
> >
> > >From: "James R. Leu" <jl...@mi...>
> > >Reply-To: jl...@mi...
> > >To: mpl...@li...
> > >Subject: [mpls-linux-general] ldp-portable updates
> > >Date: Sun, 24 Jun 2001 20:23:13 -0500
> > >
> > >Sorry to those who have been trying to use ldp-portable from CVS.
> > >I finnally have gotten around to fixing and testing ldp-portable.
> > >It's almost back to where it was before I started mucking around with 
>PDU
> > >processing.  (interoping with cisco pointed out the need to handle 
>multiple
> > >PDUs per TCP segment and handle one PDU spread across multiple TCP
> > >segments)
> > >
> > >If you tried ldp-portable in the last 3 weeks and it was broken, try
> > >updating your CVS client and giving it another go.
> > >
> > >Sorry for the long delay.
> > >Jim
> > >--
> > >James R. Leu
> > >
> > >_______________________________________________
> > >mpls-linux-general mailing list
> > >mpl...@li...
> > >http://lists.sourceforge.net/lists/listinfo/mpls-linux-general
> >
> > 
>_________________________________________________________________________
> > Get Your Private, Free E-mail from MSN Hotmail at 
>http://www.hotmail.com.
> >
> >
> > _______________________________________________
> > mpls-linux-general mailing list
> > mpl...@li...
> > http://lists.sourceforge.net/lists/listinfo/mpls-linux-general
>
>--
>James R. Leu
>
>_______________________________________________
>mpls-linux-general mailing list
>mpl...@li...
>http://lists.sourceforge.net/lists/listinfo/mpls-linux-general

_________________________________________________________________________
Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.

Re: [mpls-linux-general] ldp-portable updates

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

On Tue, Jun 26, 2001 at 02:28:11PM -0000, Venisa Cabrilla wrote:
> Hi,
> 
> Sorry for the late response, I have to go downstair and upstair just to copy 
> the contents of /proc/net/mpls_*, (my lab and my office are not in the same 
> room) but I have done as fast as I can ... :-)

Late response!  I'm used to latency on the order of days (or weeks ;-)
Your latency is spetacular! :-)

> First, I have to inform you that since I use my computers as routers, I do 
> certainly have at least three ethernet cards in my routers (that is, the 
> topology that I gave you is far from complete, which will explain the 
> important contents of file mpls_in) but I used only the commands that I have 
> described in my last email.

This is cool!  ldp-portable is actually working for someone beside me!

> In router1:
> mpls_in:
> 40004000 gen 16 0 POP DLV
> 40004400 gen 17 0 POP DLV
> 40004800 gen 18 0 POP DLV
> 40004c00 gen 19 0 POP DLV
> 40005000 gen 20 0 POP DLV
> 40005400 gen 21 0 POP DLV
> 40005800 gen 22 0 POP DLV
> mpls_out:
> 40004003 PUSH(gen 16) SET (eth1)
> mpls_fec:
> 40004003 10.0.0.6/32

Ahhhh.  Here is the culprite.

> mpls_labelspace:
> lo 0

ldp_linux doesn't set the label space for you.  You currently need to execute
the command 'mplsadm -L eth1:0' for each of the LDP speaking interfaces before
starting up ldp_linux.

I have a patch from someone at Ericsson that fixes this.

Other then the labelspace problem the rest look just fine :-)

Let me know if this fixes it.

BTW clues to this being the problem would have shown up in the MPLS kernel
debugging when you tried to ping.

On Router1:
mplsadm -d
ping 10.0.0.6
dmesg

You should see that the packet are being sent via mpls_output()

On Router2:
ping 10.0.0.5

On Router1:
dmesg

You should see info about packets arriving on interfaces without a labelspace

Jim

> In router2:
> mpls_in:
> 40004000 gen 16 0 POP DLV
> 40004400 gen 17 0 POP DLV
> 40004800 gen 18 0 POP DLV
> 40004c00 gen 19 0 POP DLV
> 40005000 gen 20 0 POP DLV
> 40005400 gen 21 0 POP DLV
> 40005800 gen 22 0 POP DLV
> mpls_out:
> 40004004 PUSH(gen 16) SET (eth2)
> mpls_fec:
> 40004004 10.0.0.5/32
> mpls_labelspace:
> lo 0
> 
> There is nothing in mpls_tunnel, which is normal.
> 
> 
> regards,
> ~Venisa Cabrilla
> 
> 
> 
> >From: "James R. Leu" <jl...@mi...>
> >Reply-To: jl...@mi...
> >To: Venisa Cabrilla <vca...@ho...>
> >CC: mpl...@li...
> >Subject: Re: [mpls-linux-general] ldp-portable updates
> >Date: Tue, 26 Jun 2001 08:45:55 -0500
> >
> >On Tue, Jun 26, 2001 at 01:31:11PM -0000, Venisa Cabrilla wrote:
> > > Hi James,
> > >
> > > Thanks for your ldp-portable updates, now I can see that mpls_in, 
> >mpls_out,
> > > and mpls_fec are not empty.
> >
> >Hello,
> >
> >I think I know the problem.  It has to do with the fact that LDP is setting 
> >up
> >LSPs for too many entries in the route table.  Send me the contents of
> >/proc/net/mpls_* and we can verify this.
> >
> >My default policy of "send labels for everything" may not be valid in all
> >cases.  This will be simple enough to change I just need to figure out what 
> >the
> >best default policy should be :-(
> >
> >I'll try to duplicate this setup here and see if I can figure it out as 
> >well.
> >
> >Jim
> >
> > >
> > > I use the simple configuration in file README.sample :
> > >
> > >      lo 10.0.0.6                lo 10.0.0.5
> > >       ---------                  ---------
> > >      | Router2 |----------------| Router1 |
> > >       ---------                  ---------
> > >           |eth2  192.168.12.0/24     |eth1
> > >      ---------------------------------------
> > >
> > > In router1:
> > > bash# ifconfig lo 10.0.0.5 netmask 255.255.255.255
> > > bash# route add 10.0.0.6 gw 192.168.12.2
> > >
> > > >From inside ldp_linux:
> > > prompt> add global 10.0.0.5
> > > prompt> add interface eth1
> > >
> > > In router2:
> > > bash# ifconfig lo 10.0.0.6 netmask 255.255.255.255
> > > bash# route add 10.0.0.5 gw 192.168.12.1
> > >
> > > >From inside ldp_linux:
> > > prompt> add global 10.0.0.6
> > > prompt> add interface eth2
> > >
> > > After that I can see that mpls_in, mpls_out, and mpls_fec in each router 
> >are
> > > not empty.
> > >
> > > Unfortunately, I cannot ping anymore router1 from router2 and router2 
> >from
> > > router1. Before I enter ldp_linux, I can ping 10.0.0.5 from router1 and 
> >ping
> > > 10.0.0.6 from router2. However, I can see the MPLS encapsulation using
> > > ethereal for ping request messages but there is no ping reply message.
> > >
> > > Would you mind verify my configuration above and tell me what might be 
> >my
> > > mistakes ?
> > >
> > >
> > > PS: I have to explicitly add the routes using route commands this time,
> > > because if I use zebra, I cannot use ethereal (ethereal hangs).
> > > I still do not know the reason, it might be due to TCP/UDP conflicts.
> > >
> > >
> > > regards,
> > > ~Venisa Cabrilla
> > >
> > >
> > >
> > > >From: "James R. Leu" <jl...@mi...>
> > > >Reply-To: jl...@mi...
> > > >To: mpl...@li...
> > > >Subject: [mpls-linux-general] ldp-portable updates
> > > >Date: Sun, 24 Jun 2001 20:23:13 -0500
> > > >
> > > >Sorry to those who have been trying to use ldp-portable from CVS.
> > > >I finnally have gotten around to fixing and testing ldp-portable.
> > > >It's almost back to where it was before I started mucking around with 
> >PDU
> > > >processing.  (interoping with cisco pointed out the need to handle 
> >multiple
> > > >PDUs per TCP segment and handle one PDU spread across multiple TCP
> > > >segments)
> > > >
> > > >If you tried ldp-portable in the last 3 weeks and it was broken, try
> > > >updating your CVS client and giving it another go.
> > > >
> > > >Sorry for the long delay.
> > > >Jim
> > > >--
> > > >James R. Leu
> > > >
> > > >_______________________________________________
> > > >mpls-linux-general mailing list
> > > >mpl...@li...
> > > >http://lists.sourceforge.net/lists/listinfo/mpls-linux-general
> > >
> > > 
> >_________________________________________________________________________
> > > Get Your Private, Free E-mail from MSN Hotmail at 
> >http://www.hotmail.com.
> > >
> > >
> > > _______________________________________________
> > > mpls-linux-general mailing list
> > > mpl...@li...
> > > http://lists.sourceforge.net/lists/listinfo/mpls-linux-general
> >
> >--
> >James R. Leu
> >
> >_______________________________________________
> >mpls-linux-general mailing list
> >mpl...@li...
> >http://lists.sourceforge.net/lists/listinfo/mpls-linux-general
> 
> _________________________________________________________________________
> Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.

-- 
James R. Leu

Re: [mpls-linux-general] ldp-portable updates

[Venisa C. <vca...@ho...>]

That's it ! It works now :-D Thanks Jim ...

regards,
~Venisa Cabrilla


>From: "James R. Leu" <jl...@mi...>
>Reply-To: jl...@mi...
>To: Venisa Cabrilla <vca...@ho...>
>CC: mpl...@li...
>Subject: Re: [mpls-linux-general] ldp-portable updates
>Date: Tue, 26 Jun 2001 09:57:31 -0500
>
>On Tue, Jun 26, 2001 at 02:28:11PM -0000, Venisa Cabrilla wrote:
> > Hi,
> >
> > Sorry for the late response, I have to go downstair and upstair just to 
>copy
> > the contents of /proc/net/mpls_*, (my lab and my office are not in the 
>same
> > room) but I have done as fast as I can ... :-)
>
>Late response!  I'm used to latency on the order of days (or weeks ;-)
>Your latency is spetacular! :-)
>
> > First, I have to inform you that since I use my computers as routers, I 
>do
> > certainly have at least three ethernet cards in my routers (that is, the
> > topology that I gave you is far from complete, which will explain the
> > important contents of file mpls_in) but I used only the commands that I 
>have
> > described in my last email.
>
>This is cool!  ldp-portable is actually working for someone beside me!
>
> > In router1:
> > mpls_in:
> > 40004000 gen 16 0 POP DLV
> > 40004400 gen 17 0 POP DLV
> > 40004800 gen 18 0 POP DLV
> > 40004c00 gen 19 0 POP DLV
> > 40005000 gen 20 0 POP DLV
> > 40005400 gen 21 0 POP DLV
> > 40005800 gen 22 0 POP DLV
> > mpls_out:
> > 40004003 PUSH(gen 16) SET (eth1)
> > mpls_fec:
> > 40004003 10.0.0.6/32
>
>Ahhhh.  Here is the culprite.
>
> > mpls_labelspace:
> > lo 0
>
>ldp_linux doesn't set the label space for you.  You currently need to 
>execute
>the command 'mplsadm -L eth1:0' for each of the LDP speaking interfaces 
>before
>starting up ldp_linux.
>
>I have a patch from someone at Ericsson that fixes this.
>
>Other then the labelspace problem the rest look just fine :-)
>
>Let me know if this fixes it.
>
>BTW clues to this being the problem would have shown up in the MPLS kernel
>debugging when you tried to ping.
>
>On Router1:
>mplsadm -d
>ping 10.0.0.6
>dmesg
>
>You should see that the packet are being sent via mpls_output()
>
>On Router2:
>ping 10.0.0.5
>
>On Router1:
>dmesg
>
>You should see info about packets arriving on interfaces without a 
>labelspace
>
>Jim
>
> > In router2:
> > mpls_in:
> > 40004000 gen 16 0 POP DLV
> > 40004400 gen 17 0 POP DLV
> > 40004800 gen 18 0 POP DLV
> > 40004c00 gen 19 0 POP DLV
> > 40005000 gen 20 0 POP DLV
> > 40005400 gen 21 0 POP DLV
> > 40005800 gen 22 0 POP DLV
> > mpls_out:
> > 40004004 PUSH(gen 16) SET (eth2)
> > mpls_fec:
> > 40004004 10.0.0.5/32
> > mpls_labelspace:
> > lo 0
> >
> > There is nothing in mpls_tunnel, which is normal.
> >
> >
> > regards,
> > ~Venisa Cabrilla
> >
> >
> >
> > >From: "James R. Leu" <jl...@mi...>
> > >Reply-To: jl...@mi...
> > >To: Venisa Cabrilla <vca...@ho...>
> > >CC: mpl...@li...
> > >Subject: Re: [mpls-linux-general] ldp-portable updates
> > >Date: Tue, 26 Jun 2001 08:45:55 -0500
> > >
> > >On Tue, Jun 26, 2001 at 01:31:11PM -0000, Venisa Cabrilla wrote:
> > > > Hi James,
> > > >
> > > > Thanks for your ldp-portable updates, now I can see that mpls_in,
> > >mpls_out,
> > > > and mpls_fec are not empty.
> > >
> > >Hello,
> > >
> > >I think I know the problem.  It has to do with the fact that LDP is 
>setting
> > >up
> > >LSPs for too many entries in the route table.  Send me the contents of
> > >/proc/net/mpls_* and we can verify this.
> > >
> > >My default policy of "send labels for everything" may not be valid in 
>all
> > >cases.  This will be simple enough to change I just need to figure out 
>what
> > >the
> > >best default policy should be :-(
> > >
> > >I'll try to duplicate this setup here and see if I can figure it out as
> > >well.
> > >
> > >Jim
> > >
> > > >
> > > > I use the simple configuration in file README.sample :
> > > >
> > > >      lo 10.0.0.6                lo 10.0.0.5
> > > >       ---------                  ---------
> > > >      | Router2 |----------------| Router1 |
> > > >       ---------                  ---------
> > > >           |eth2  192.168.12.0/24     |eth1
> > > >      ---------------------------------------
> > > >
> > > > In router1:
> > > > bash# ifconfig lo 10.0.0.5 netmask 255.255.255.255
> > > > bash# route add 10.0.0.6 gw 192.168.12.2
> > > >
> > > > >From inside ldp_linux:
> > > > prompt> add global 10.0.0.5
> > > > prompt> add interface eth1
> > > >
> > > > In router2:
> > > > bash# ifconfig lo 10.0.0.6 netmask 255.255.255.255
> > > > bash# route add 10.0.0.5 gw 192.168.12.1
> > > >
> > > > >From inside ldp_linux:
> > > > prompt> add global 10.0.0.6
> > > > prompt> add interface eth2
> > > >
> > > > After that I can see that mpls_in, mpls_out, and mpls_fec in each 
>router
> > >are
> > > > not empty.
> > > >
> > > > Unfortunately, I cannot ping anymore router1 from router2 and 
>router2
> > >from
> > > > router1. Before I enter ldp_linux, I can ping 10.0.0.5 from router1 
>and
> > >ping
> > > > 10.0.0.6 from router2. However, I can see the MPLS encapsulation 
>using
> > > > ethereal for ping request messages but there is no ping reply 
>message.
> > > >
> > > > Would you mind verify my configuration above and tell me what might 
>be
> > >my
> > > > mistakes ?
> > > >
> > > >
> > > > PS: I have to explicitly add the routes using route commands this 
>time,
> > > > because if I use zebra, I cannot use ethereal (ethereal hangs).
> > > > I still do not know the reason, it might be due to TCP/UDP 
>conflicts.
> > > >
> > > >
> > > > regards,
> > > > ~Venisa Cabrilla
> > > >
> > > >
> > > >
> > > > >From: "James R. Leu" <jl...@mi...>
> > > > >Reply-To: jl...@mi...
> > > > >To: mpl...@li...
> > > > >Subject: [mpls-linux-general] ldp-portable updates
> > > > >Date: Sun, 24 Jun 2001 20:23:13 -0500
> > > > >
> > > > >Sorry to those who have been trying to use ldp-portable from CVS.
> > > > >I finnally have gotten around to fixing and testing ldp-portable.
> > > > >It's almost back to where it was before I started mucking around 
>with
> > >PDU
> > > > >processing.  (interoping with cisco pointed out the need to handle
> > >multiple
> > > > >PDUs per TCP segment and handle one PDU spread across multiple TCP
> > > > >segments)
> > > > >
> > > > >If you tried ldp-portable in the last 3 weeks and it was broken, 
>try
> > > > >updating your CVS client and giving it another go.
> > > > >
> > > > >Sorry for the long delay.
> > > > >Jim
> > > > >--
> > > > >James R. Leu
> > > > >
> > > > >_______________________________________________
> > > > >mpls-linux-general mailing list
> > > > >mpl...@li...
> > > > >http://lists.sourceforge.net/lists/listinfo/mpls-linux-general
> > > >
> > > >
> > 
> >_________________________________________________________________________
> > > > Get Your Private, Free E-mail from MSN Hotmail at
> > >http://www.hotmail.com.
> > > >
> > > >
> > > > _______________________________________________
> > > > mpls-linux-general mailing list
> > > > mpl...@li...
> > > > http://lists.sourceforge.net/lists/listinfo/mpls-linux-general
> > >
> > >--
> > >James R. Leu
> > >
> > >_______________________________________________
> > >mpls-linux-general mailing list
> > >mpl...@li...
> > >http://lists.sourceforge.net/lists/listinfo/mpls-linux-general
> >
> > 
>_________________________________________________________________________
> > Get Your Private, Free E-mail from MSN Hotmail at 
>http://www.hotmail.com.
>
>--
>James R. Leu

_________________________________________________________________________
Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.

Re: [mpls-linux-general] ldp-portable updates

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

On Tue, Jun 26, 2001 at 03:24:39PM -0000, Venisa Cabrilla wrote:
> That's it ! It works now :-D Thanks Jim ...

Ahhhh.  Another satisfied ldp-portable user ;-)

For my next trick we'll get it working with ldp_zebra ...

This weill require a bit more code from me ....

Jim

> 
> regards,
> ~Venisa Cabrilla
> 
> 
> >From: "James R. Leu" <jl...@mi...>
> >Reply-To: jl...@mi...
> >To: Venisa Cabrilla <vca...@ho...>
> >CC: mpl...@li...
> >Subject: Re: [mpls-linux-general] ldp-portable updates
> >Date: Tue, 26 Jun 2001 09:57:31 -0500
> >
> >On Tue, Jun 26, 2001 at 02:28:11PM -0000, Venisa Cabrilla wrote:
> > > Hi,
> > >
> > > Sorry for the late response, I have to go downstair and upstair just to 
> >copy
> > > the contents of /proc/net/mpls_*, (my lab and my office are not in the 
> >same
> > > room) but I have done as fast as I can ... :-)
> >
> >Late response!  I'm used to latency on the order of days (or weeks ;-)
> >Your latency is spetacular! :-)
> >
> > > First, I have to inform you that since I use my computers as routers, I 
> >do
> > > certainly have at least three ethernet cards in my routers (that is, the
> > > topology that I gave you is far from complete, which will explain the
> > > important contents of file mpls_in) but I used only the commands that I 
> >have
> > > described in my last email.
> >
> >This is cool!  ldp-portable is actually working for someone beside me!
> >
> > > In router1:
> > > mpls_in:
> > > 40004000 gen 16 0 POP DLV
> > > 40004400 gen 17 0 POP DLV
> > > 40004800 gen 18 0 POP DLV
> > > 40004c00 gen 19 0 POP DLV
> > > 40005000 gen 20 0 POP DLV
> > > 40005400 gen 21 0 POP DLV
> > > 40005800 gen 22 0 POP DLV
> > > mpls_out:
> > > 40004003 PUSH(gen 16) SET (eth1)
> > > mpls_fec:
> > > 40004003 10.0.0.6/32
> >
> >Ahhhh.  Here is the culprite.
> >
> > > mpls_labelspace:
> > > lo 0
> >
> >ldp_linux doesn't set the label space for you.  You currently need to 
> >execute
> >the command 'mplsadm -L eth1:0' for each of the LDP speaking interfaces 
> >before
> >starting up ldp_linux.
> >
> >I have a patch from someone at Ericsson that fixes this.
> >
> >Other then the labelspace problem the rest look just fine :-)
> >
> >Let me know if this fixes it.
> >
> >BTW clues to this being the problem would have shown up in the MPLS kernel
> >debugging when you tried to ping.
> >
> >On Router1:
> >mplsadm -d
> >ping 10.0.0.6
> >dmesg
> >
> >You should see that the packet are being sent via mpls_output()
> >
> >On Router2:
> >ping 10.0.0.5
> >
> >On Router1:
> >dmesg
> >
> >You should see info about packets arriving on interfaces without a 
> >labelspace
> >
> >Jim
> >
> > > In router2:
> > > mpls_in:
> > > 40004000 gen 16 0 POP DLV
> > > 40004400 gen 17 0 POP DLV
> > > 40004800 gen 18 0 POP DLV
> > > 40004c00 gen 19 0 POP DLV
> > > 40005000 gen 20 0 POP DLV
> > > 40005400 gen 21 0 POP DLV
> > > 40005800 gen 22 0 POP DLV
> > > mpls_out:
> > > 40004004 PUSH(gen 16) SET (eth2)
> > > mpls_fec:
> > > 40004004 10.0.0.5/32
> > > mpls_labelspace:
> > > lo 0
> > >
> > > There is nothing in mpls_tunnel, which is normal.
> > >
> > >
> > > regards,
> > > ~Venisa Cabrilla
> > >
> > >
> > >
> > > >From: "James R. Leu" <jl...@mi...>
> > > >Reply-To: jl...@mi...
> > > >To: Venisa Cabrilla <vca...@ho...>
> > > >CC: mpl...@li...
> > > >Subject: Re: [mpls-linux-general] ldp-portable updates
> > > >Date: Tue, 26 Jun 2001 08:45:55 -0500
> > > >
> > > >On Tue, Jun 26, 2001 at 01:31:11PM -0000, Venisa Cabrilla wrote:
> > > > > Hi James,
> > > > >
> > > > > Thanks for your ldp-portable updates, now I can see that mpls_in,
> > > >mpls_out,
> > > > > and mpls_fec are not empty.
> > > >
> > > >Hello,
> > > >
> > > >I think I know the problem.  It has to do with the fact that LDP is 
> >setting
> > > >up
> > > >LSPs for too many entries in the route table.  Send me the contents of
> > > >/proc/net/mpls_* and we can verify this.
> > > >
> > > >My default policy of "send labels for everything" may not be valid in 
> >all
> > > >cases.  This will be simple enough to change I just need to figure out 
> >what
> > > >the
> > > >best default policy should be :-(
> > > >
> > > >I'll try to duplicate this setup here and see if I can figure it out as
> > > >well.
> > > >
> > > >Jim
> > > >
> > > > >
> > > > > I use the simple configuration in file README.sample :
> > > > >
> > > > >      lo 10.0.0.6                lo 10.0.0.5
> > > > >       ---------                  ---------
> > > > >      | Router2 |----------------| Router1 |
> > > > >       ---------                  ---------
> > > > >           |eth2  192.168.12.0/24     |eth1
> > > > >      ---------------------------------------
> > > > >
> > > > > In router1:
> > > > > bash# ifconfig lo 10.0.0.5 netmask 255.255.255.255
> > > > > bash# route add 10.0.0.6 gw 192.168.12.2
> > > > >
> > > > > >From inside ldp_linux:
> > > > > prompt> add global 10.0.0.5
> > > > > prompt> add interface eth1
> > > > >
> > > > > In router2:
> > > > > bash# ifconfig lo 10.0.0.6 netmask 255.255.255.255
> > > > > bash# route add 10.0.0.5 gw 192.168.12.1
> > > > >
> > > > > >From inside ldp_linux:
> > > > > prompt> add global 10.0.0.6
> > > > > prompt> add interface eth2
> > > > >
> > > > > After that I can see that mpls_in, mpls_out, and mpls_fec in each 
> >router
> > > >are
> > > > > not empty.
> > > > >
> > > > > Unfortunately, I cannot ping anymore router1 from router2 and 
> >router2
> > > >from
> > > > > router1. Before I enter ldp_linux, I can ping 10.0.0.5 from router1 
> >and
> > > >ping
> > > > > 10.0.0.6 from router2. However, I can see the MPLS encapsulation 
> >using
> > > > > ethereal for ping request messages but there is no ping reply 
> >message.
> > > > >
> > > > > Would you mind verify my configuration above and tell me what might 
> >be
> > > >my
> > > > > mistakes ?
> > > > >
> > > > >
> > > > > PS: I have to explicitly add the routes using route commands this 
> >time,
> > > > > because if I use zebra, I cannot use ethereal (ethereal hangs).
> > > > > I still do not know the reason, it might be due to TCP/UDP 
> >conflicts.
> > > > >
> > > > >
> > > > > regards,
> > > > > ~Venisa Cabrilla
> > > > >
> > > > >
> > > > >
> > > > > >From: "James R. Leu" <jl...@mi...>
> > > > > >Reply-To: jl...@mi...
> > > > > >To: mpl...@li...
> > > > > >Subject: [mpls-linux-general] ldp-portable updates
> > > > > >Date: Sun, 24 Jun 2001 20:23:13 -0500
> > > > > >
> > > > > >Sorry to those who have been trying to use ldp-portable from CVS.
> > > > > >I finnally have gotten around to fixing and testing ldp-portable.
> > > > > >It's almost back to where it was before I started mucking around 
> >with
> > > >PDU
> > > > > >processing.  (interoping with cisco pointed out the need to handle
> > > >multiple
> > > > > >PDUs per TCP segment and handle one PDU spread across multiple TCP
> > > > > >segments)
> > > > > >
> > > > > >If you tried ldp-portable in the last 3 weeks and it was broken, 
> >try
> > > > > >updating your CVS client and giving it another go.
> > > > > >
> > > > > >Sorry for the long delay.
> > > > > >Jim
> > > > > >--
> > > > > >James R. Leu
> > > > > >
> > > > > >_______________________________________________
> > > > > >mpls-linux-general mailing list
> > > > > >mpl...@li...
> > > > > >http://lists.sourceforge.net/lists/listinfo/mpls-linux-general
> > > > >
> > > > >
> > > 
> > >_________________________________________________________________________
> > > > > Get Your Private, Free E-mail from MSN Hotmail at
> > > >http://www.hotmail.com.
> > > > >
> > > > >
> > > > > _______________________________________________
> > > > > mpls-linux-general mailing list
> > > > > mpl...@li...
> > > > > http://lists.sourceforge.net/lists/listinfo/mpls-linux-general
> > > >
> > > >--
> > > >James R. Leu
> > > >
> > > >_______________________________________________
> > > >mpls-linux-general mailing list
> > > >mpl...@li...
> > > >http://lists.sourceforge.net/lists/listinfo/mpls-linux-general
> > >
> > > 
> >_________________________________________________________________________
> > > Get Your Private, Free E-mail from MSN Hotmail at 
> >http://www.hotmail.com.
> >
> >--
> >James R. Leu
> 
> _________________________________________________________________________
> Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.
> 
> 
> _______________________________________________
> mpls-linux-general mailing list
> mpl...@li...
> http://lists.sourceforge.net/lists/listinfo/mpls-linux-general

-- 
James R. Leu

Re: [mpls-linux-general] ldp-portable updates

[Venisa C. <vca...@ho...>]

Jim,

ldp_zebra ? Uhmmm, infact, I am still confused %-) about the real difference 
between ldp_linux and ldp_zebra (I have not tested ldp_zebra yet).

Suppose that I can run ldp_linux with zebra, that is zebra will provide the 
routing information to ldp_linux, in this case what makes ldp_zebra so 
different since for making it work we also have to run zebra before (that's 
at least what I can understand from your README).

Or maybe in ldp_zebra, the relation between ldp_zebra and zebra is just like 
the relation between ospfd or bgpd with zebra ?

BTW I am trying to run ldp_linux with zebra, but I still have some problems 
with it, I'll hope I still can overcome it ...


regards,
~Venisa Cabrilla



>From: "James R. Leu" <jl...@mi...>
>Reply-To: jl...@mi...
>To: Venisa Cabrilla <vca...@ho...>
>CC: mpl...@li...
>Subject: Re: [mpls-linux-general] ldp-portable updates
>Date: Tue, 26 Jun 2001 10:44:42 -0500
>
>On Tue, Jun 26, 2001 at 03:24:39PM -0000, Venisa Cabrilla wrote:
> > That's it ! It works now :-D Thanks Jim ...
>
>Ahhhh.  Another satisfied ldp-portable user ;-)
>
>For my next trick we'll get it working with ldp_zebra ...
>
>This weill require a bit more code from me ....
>
>Jim
>
> >
> > regards,
> > ~Venisa Cabrilla
> >
> >
> > >From: "James R. Leu" <jl...@mi...>
> > >Reply-To: jl...@mi...
> > >To: Venisa Cabrilla <vca...@ho...>
> > >CC: mpl...@li...
> > >Subject: Re: [mpls-linux-general] ldp-portable updates
> > >Date: Tue, 26 Jun 2001 09:57:31 -0500
> > >
> > >On Tue, Jun 26, 2001 at 02:28:11PM -0000, Venisa Cabrilla wrote:
> > > > Hi,
> > > >
> > > > Sorry for the late response, I have to go downstair and upstair just 
>to
> > >copy
> > > > the contents of /proc/net/mpls_*, (my lab and my office are not in 
>the
> > >same
> > > > room) but I have done as fast as I can ... :-)
> > >
> > >Late response!  I'm used to latency on the order of days (or weeks ;-)
> > >Your latency is spetacular! :-)
> > >
> > > > First, I have to inform you that since I use my computers as 
>routers, I
> > >do
> > > > certainly have at least three ethernet cards in my routers (that is, 
>the
> > > > topology that I gave you is far from complete, which will explain 
>the
> > > > important contents of file mpls_in) but I used only the commands 
>that I
> > >have
> > > > described in my last email.
> > >
> > >This is cool!  ldp-portable is actually working for someone beside me!
> > >
> > > > In router1:
> > > > mpls_in:
> > > > 40004000 gen 16 0 POP DLV
> > > > 40004400 gen 17 0 POP DLV
> > > > 40004800 gen 18 0 POP DLV
> > > > 40004c00 gen 19 0 POP DLV
> > > > 40005000 gen 20 0 POP DLV
> > > > 40005400 gen 21 0 POP DLV
> > > > 40005800 gen 22 0 POP DLV
> > > > mpls_out:
> > > > 40004003 PUSH(gen 16) SET (eth1)
> > > > mpls_fec:
> > > > 40004003 10.0.0.6/32
> > >
> > >Ahhhh.  Here is the culprite.
> > >
> > > > mpls_labelspace:
> > > > lo 0
> > >
> > >ldp_linux doesn't set the label space for you.  You currently need to
> > >execute
> > >the command 'mplsadm -L eth1:0' for each of the LDP speaking interfaces
> > >before
> > >starting up ldp_linux.
> > >
> > >I have a patch from someone at Ericsson that fixes this.
> > >
> > >Other then the labelspace problem the rest look just fine :-)
> > >
> > >Let me know if this fixes it.
> > >
> > >BTW clues to this being the problem would have shown up in the MPLS 
>kernel
> > >debugging when you tried to ping.
> > >
> > >On Router1:
> > >mplsadm -d
> > >ping 10.0.0.6
> > >dmesg
> > >
> > >You should see that the packet are being sent via mpls_output()
> > >
> > >On Router2:
> > >ping 10.0.0.5
> > >
> > >On Router1:
> > >dmesg
> > >
> > >You should see info about packets arriving on interfaces without a
> > >labelspace
> > >
> > >Jim
> > >
> > > > In router2:
> > > > mpls_in:
> > > > 40004000 gen 16 0 POP DLV
> > > > 40004400 gen 17 0 POP DLV
> > > > 40004800 gen 18 0 POP DLV
> > > > 40004c00 gen 19 0 POP DLV
> > > > 40005000 gen 20 0 POP DLV
> > > > 40005400 gen 21 0 POP DLV
> > > > 40005800 gen 22 0 POP DLV
> > > > mpls_out:
> > > > 40004004 PUSH(gen 16) SET (eth2)
> > > > mpls_fec:
> > > > 40004004 10.0.0.5/32
> > > > mpls_labelspace:
> > > > lo 0
> > > >
> > > > There is nothing in mpls_tunnel, which is normal.
> > > >
> > > >
> > > > regards,
> > > > ~Venisa Cabrilla
> > > >
> > > >
> > > >
> > > > >From: "James R. Leu" <jl...@mi...>
> > > > >Reply-To: jl...@mi...
> > > > >To: Venisa Cabrilla <vca...@ho...>
> > > > >CC: mpl...@li...
> > > > >Subject: Re: [mpls-linux-general] ldp-portable updates
> > > > >Date: Tue, 26 Jun 2001 08:45:55 -0500
> > > > >
> > > > >On Tue, Jun 26, 2001 at 01:31:11PM -0000, Venisa Cabrilla wrote:
> > > > > > Hi James,
> > > > > >
> > > > > > Thanks for your ldp-portable updates, now I can see that 
>mpls_in,
> > > > >mpls_out,
> > > > > > and mpls_fec are not empty.
> > > > >
> > > > >Hello,
> > > > >
> > > > >I think I know the problem.  It has to do with the fact that LDP is
> > >setting
> > > > >up
> > > > >LSPs for too many entries in the route table.  Send me the contents 
>of
> > > > >/proc/net/mpls_* and we can verify this.
> > > > >
> > > > >My default policy of "send labels for everything" may not be valid 
>in
> > >all
> > > > >cases.  This will be simple enough to change I just need to figure 
>out
> > >what
> > > > >the
> > > > >best default policy should be :-(
> > > > >
> > > > >I'll try to duplicate this setup here and see if I can figure it 
>out as
> > > > >well.
> > > > >
> > > > >Jim
> > > > >
> > > > > >
> > > > > > I use the simple configuration in file README.sample :
> > > > > >
> > > > > >      lo 10.0.0.6                lo 10.0.0.5
> > > > > >       ---------                  ---------
> > > > > >      | Router2 |----------------| Router1 |
> > > > > >       ---------                  ---------
> > > > > >           |eth2  192.168.12.0/24     |eth1
> > > > > >      ---------------------------------------
> > > > > >
> > > > > > In router1:
> > > > > > bash# ifconfig lo 10.0.0.5 netmask 255.255.255.255
> > > > > > bash# route add 10.0.0.6 gw 192.168.12.2
> > > > > >
> > > > > > >From inside ldp_linux:
> > > > > > prompt> add global 10.0.0.5
> > > > > > prompt> add interface eth1
> > > > > >
> > > > > > In router2:
> > > > > > bash# ifconfig lo 10.0.0.6 netmask 255.255.255.255
> > > > > > bash# route add 10.0.0.5 gw 192.168.12.1
> > > > > >
> > > > > > >From inside ldp_linux:
> > > > > > prompt> add global 10.0.0.6
> > > > > > prompt> add interface eth2
> > > > > >
> > > > > > After that I can see that mpls_in, mpls_out, and mpls_fec in 
>each
> > >router
> > > > >are
> > > > > > not empty.
> > > > > >
> > > > > > Unfortunately, I cannot ping anymore router1 from router2 and
> > >router2
> > > > >from
> > > > > > router1. Before I enter ldp_linux, I can ping 10.0.0.5 from 
>router1
> > >and
> > > > >ping
> > > > > > 10.0.0.6 from router2. However, I can see the MPLS encapsulation
> > >using
> > > > > > ethereal for ping request messages but there is no ping reply
> > >message.
> > > > > >
> > > > > > Would you mind verify my configuration above and tell me what 
>might
> > >be
> > > > >my
> > > > > > mistakes ?
> > > > > >
> > > > > >
> > > > > > PS: I have to explicitly add the routes using route commands 
>this
> > >time,
> > > > > > because if I use zebra, I cannot use ethereal (ethereal hangs).
> > > > > > I still do not know the reason, it might be due to TCP/UDP
> > >conflicts.
> > > > > >
> > > > > >
> > > > > > regards,
> > > > > > ~Venisa Cabrilla
> > > > > >
> > > > > >
> > > > > >
> > > > > > >From: "James R. Leu" <jl...@mi...>
> > > > > > >Reply-To: jl...@mi...
> > > > > > >To: mpl...@li...
> > > > > > >Subject: [mpls-linux-general] ldp-portable updates
> > > > > > >Date: Sun, 24 Jun 2001 20:23:13 -0500
> > > > > > >
> > > > > > >Sorry to those who have been trying to use ldp-portable from 
>CVS.
> > > > > > >I finnally have gotten around to fixing and testing 
>ldp-portable.
> > > > > > >It's almost back to where it was before I started mucking 
>around
> > >with
> > > > >PDU
> > > > > > >processing.  (interoping with cisco pointed out the need to 
>handle
> > > > >multiple
> > > > > > >PDUs per TCP segment and handle one PDU spread across multiple 
>TCP
> > > > > > >segments)
> > > > > > >
> > > > > > >If you tried ldp-portable in the last 3 weeks and it was 
>broken,
> > >try
> > > > > > >updating your CVS client and giving it another go.
> > > > > > >
> > > > > > >Sorry for the long delay.
> > > > > > >Jim
> > > > > > >--
> > > > > > >James R. Leu
> > > > > > >
> > > > > > >_______________________________________________
> > > > > > >mpls-linux-general mailing list
> > > > > > >mpl...@li...
> > > > > > >http://lists.sourceforge.net/lists/listinfo/mpls-linux-general
> > > > > >
> > > > > >
> > > >
> > > 
> >_________________________________________________________________________
> > > > > > Get Your Private, Free E-mail from MSN Hotmail at
> > > > >http://www.hotmail.com.
> > > > > >
> > > > > >
> > > > > > _______________________________________________
> > > > > > mpls-linux-general mailing list
> > > > > > mpl...@li...
> > > > > > http://lists.sourceforge.net/lists/listinfo/mpls-linux-general
> > > > >
> > > > >--
> > > > >James R. Leu
> > > > >
> > > > >_______________________________________________
> > > > >mpls-linux-general mailing list
> > > > >mpl...@li...
> > > > >http://lists.sourceforge.net/lists/listinfo/mpls-linux-general
> > > >
> > > >
> > 
> >_________________________________________________________________________
> > > > Get Your Private, Free E-mail from MSN Hotmail at
> > >http://www.hotmail.com.
> > >
> > >--
> > >James R. Leu
> >
> > 
>_________________________________________________________________________
> > Get Your Private, Free E-mail from MSN Hotmail at 
>http://www.hotmail.com.
> >
> >
> > _______________________________________________
> > mpls-linux-general mailing list
> > mpl...@li...
> > http://lists.sourceforge.net/lists/listinfo/mpls-linux-general
>
>--
>James R. Leu
>
>_______________________________________________
>mpls-linux-general mailing list
>mpl...@li...
>http://lists.sourceforge.net/lists/listinfo/mpls-linux-general

_________________________________________________________________________
Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.

Re: [mpls-linux-general] ldp-portable updates

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

On Tue, Jun 26, 2001 at 01:31:11PM -0000, Venisa Cabrilla wrote:
> Hi James,
> 
> Thanks for your ldp-portable updates, now I can see that mpls_in, mpls_out, 
> and mpls_fec are not empty.

Hello,

I think I know the problem.  It has to do with the fact that LDP is setting up
LSPs for too many entries in the route table.  Send me the contents of
/proc/net/mpls_* and we can verify this.

My default policy of "send labels for everything" may not be valid in all
cases.  This will be simple enough to change I just need to figure out what the
best default policy should be :-(

I'll try to duplicate this setup here and see if I can figure it out as well.

Jim

> 
> I use the simple configuration in file README.sample :
> 
>      lo 10.0.0.6                lo 10.0.0.5
>       ---------                  ---------
>      | Router2 |----------------| Router1 |
>       ---------                  ---------
>           |eth2  192.168.12.0/24     |eth1
>      ---------------------------------------
> 
> In router1:
> bash# ifconfig lo 10.0.0.5 netmask 255.255.255.255
> bash# route add 10.0.0.6 gw 192.168.12.2
> 
> >From inside ldp_linux:
> prompt> add global 10.0.0.5
> prompt> add interface eth1
> 
> In router2:
> bash# ifconfig lo 10.0.0.6 netmask 255.255.255.255
> bash# route add 10.0.0.5 gw 192.168.12.1
> 
> >From inside ldp_linux:
> prompt> add global 10.0.0.6
> prompt> add interface eth2
> 
> After that I can see that mpls_in, mpls_out, and mpls_fec in each router are 
> not empty.
> 
> Unfortunately, I cannot ping anymore router1 from router2 and router2 from 
> router1. Before I enter ldp_linux, I can ping 10.0.0.5 from router1 and ping 
> 10.0.0.6 from router2. However, I can see the MPLS encapsulation using 
> ethereal for ping request messages but there is no ping reply message.
> 
> Would you mind verify my configuration above and tell me what might be my 
> mistakes ?
> 
> 
> PS: I have to explicitly add the routes using route commands this time, 
> because if I use zebra, I cannot use ethereal (ethereal hangs).
> I still do not know the reason, it might be due to TCP/UDP conflicts.
> 
> 
> regards,
> ~Venisa Cabrilla
> 
> 
> 
> >From: "James R. Leu" <jl...@mi...>
> >Reply-To: jl...@mi...
> >To: mpl...@li...
> >Subject: [mpls-linux-general] ldp-portable updates
> >Date: Sun, 24 Jun 2001 20:23:13 -0500
> >
> >Sorry to those who have been trying to use ldp-portable from CVS.
> >I finnally have gotten around to fixing and testing ldp-portable.
> >It's almost back to where it was before I started mucking around with PDU
> >processing.  (interoping with cisco pointed out the need to handle multiple
> >PDUs per TCP segment and handle one PDU spread across multiple TCP 
> >segments)
> >
> >If you tried ldp-portable in the last 3 weeks and it was broken, try
> >updating your CVS client and giving it another go.
> >
> >Sorry for the long delay.
> >Jim
> >--
> >James R. Leu
> >
> >_______________________________________________
> >mpls-linux-general mailing list
> >mpl...@li...
> >http://lists.sourceforge.net/lists/listinfo/mpls-linux-general
> 
> _________________________________________________________________________
> Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.
> 
> 
> _______________________________________________
> mpls-linux-general mailing list
> mpl...@li...
> http://lists.sourceforge.net/lists/listinfo/mpls-linux-general

-- 
James R. Leu