mpls-linux-general — Mailing list for general discussion about MPLS for Linux

[mpls-linux-general] mpls-linux + ATM

[<seh...@ya...>]

Hi all,
I'am using the mpls-linux impementation for academic
research and i want to know if there is an  available
version witch support  the ATM: that's mean if i can
encapsulate the label in the VPI/VCI field.

Please help.
Many thanks.

 --- "James R. Leu" <jl...@mi...> a écrit : >
On Wed, Mar 27, 2002 at 03:19:11AM -0800, Kanwar
> Deep Singh wrote:
> > hi jim,
> >   i am using latest ldp from CVS. is that ldp
> dynamic
> > i mean if i add a new route while ldp is running
> ..
> > does it going to distribute labels for it or it
> just
> > uses the route which r there in /proc/net/route at
> the
> > start of ldp_linux ..
> 
> You are correct.  This doesn't mean that
> ldp-portable doesn't know how to
> distribute new labels, it is just that the ldp_linux
> porting layer doesn't
> listen to route changes from the kernel.
> 
> Jim
> 
> 
> > thanx in advace
> > anish
> > 
> > __________________________________________________
> > Do You Yahoo!?
> > Yahoo! Movies - coverage of the 74th Academy
> Awards®
> > http://movies.yahoo.com/
> > 
> > _______________________________________________
> > mpls-linux-general mailing list
> > mpl...@li...
> >
>
https://lists.sourceforge.net/lists/listinfo/mpls-linux-general
> 
> -- 
> James R. Leu
> 
> _______________________________________________
> mpls-linux-general mailing list
> mpl...@li...
>
https://lists.sourceforge.net/lists/listinfo/mpls-linux-general 

___________________________________________________________
Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français !
Yahoo! Mail : http://fr.mail.yahoo.com

Re: [mpls-linux-general] Do I need ldp?

[Yon U. <hav...@gm...>]

Hi,

On Wed, 27 Nov 2002, Mats Ydeklew wrote:
> Hi,
>
> I'm new at mpls and have some questions.
>
> My test plan is to use mpls in a firewall environment with only the LSR
> functionality.
> Cisco routers take care of labelling the packets at the edge and my mpls
> Linux just
> watching the traffic that passes through.
>
> 1. Do I need ldp or Zebra to do this?
> 2. Have someone been testing mpls together with linux-vlan?

 I've been running mpls over linux-vlan on UML-instances. There are
problems since frames get +4 because of the VLAN-tag and +4(or more)
because of the MPLS label(s). Anything in between that doesnt like those
bigger frames will kill your network connection (NICs, NIC-drivers,
switches).

regards,
 yon

Re: [mpls-linux-general] PHP

[Yon U. <hav...@gm...>]

Hi,

On Thu, 24 Oct 2002, James R. Leu wrote:

> On Wed, Oct 23, 2002 at 11:57:11PM -0700, nitin panjwani wrote:
> > Hi James,
> > Is this implementation of MPLS supports penultimate
> > hop popping or is there way to configure it whatever
> > way we want.
> > Thanks,
> > Nitin
>
> I'm a bit torn as to how to answer this.  Maybe someone out there can
> help me decide what is the correct way to do this.  I have 2 thoughts:
>
> -PHP should be the responsibility of the signaling protocol.  If a
>  protocol receives the implicit null label, it should know not
>  to cross connect to a real label value and instead terminate that level
>  of the LSP.

 That tunnel might not terminate (label stack). This cant even be
controlled (or known) by the signaling protocol (this might be a P-LSR,
which doesnt know what the PE-LSRs have signalled between them).
 Terminating is ok for the simple LDP case, without other signaling
protocols.

> -PHP is controled by the MPLS forwarding plan.  If an outsegment is created
>  with the implicit null label it creates it's instructions in such a way
>  as to not push a label.  During outgoing processing if the packet
>  doesn't have any labels it is sent out the interface as an IP packet
>  without doing a routing lookup.  If it has labels, then it is sent out
>  the interface with out interogating the top level label.  This brings
>  up all sorts of questions though.  Like how to handle EXP and TTL?

 I like this transparency, which avoids having to consider the special
case(s) in the signalling proto to forwarding plane interface.

 I tried this setup (inlabel: POP, FWD -> outlabel: SET (no PUSH)) a few
mpls-linux releases ago, result: the IP packet is forwarded as a MPLS
frame, resulting in garbage (processing of the IP header as an MPLS header
on the receiving side).

 I think a mixed solution could work (considering ip and ipv6):
signaling sets up an inlabel of POP, FWD(outlabel) and an
outlabel of PUSH(null-label), SET(int, nh, proto).

 A 1-label packet will get POPed, and forward to the outlabel->PUSH (which
will be a NOP for the null label(s))  and then the SET, which seeing no
label at all will set the L2-frame protocol to the SET-command proto
parameter and correctly deliver the packet to the (last) nexthop for
correct processing. If the label stack is not empty, the PUSH is NOP again
and the SET seeing a non empty stack forwards the packet as a MPLS
L2-frame, ignoring the proto parameter.

 Summarizing, I suggest:

* adding a default proto for the SET instruction, modifying it to consider
the label-stack depth and modifying the L2-frame protocol field
accordingly.

* modifying the PUSH instruction to do a NOP on null-labels.

 I think this mixed approach is the most comprehensive and on the
least-surprise path for the users.

 Further, it is possible to always do a label XC, which means no need to
change the inlabel on outlabel changes, simplifying implementations. One
can effectively map the LSR-MIB objects 1:1 to the mpls-linux objects:

LSR-MIB  -> mpls-linux
 in-label     in-label POP, FWD (to XC)
 XC           out-label [PUSH,[PUSH,[...]]], FWD(to out-label)
 out-label    out-label [PUSH], SET

This might be not so efficient as doing a single in-label -> out-label XC
in terms of forwarding plane processing time.

It is efficient in change control (and signaling protocol implementation):

 * Multiple (N) in-labels might map to a single XC, changing the XC is a
single operation, not a N operation.

 * A single XC might represent a VRF-label for a remote VRF-route, or a
BGP-label for a super-route (not 2547, but bgp-mpls (rfc 3107)), a LSR
might want to directly switch the LDP labels for those subnets (N) to the
XC. Anyway, FTN-MIB maps FECs to XC-Indexes.

 * An out-label might represent an LDP or RSVP-TE label, which might
change with time (ldp<-->rsvp-te transition for the stacked lsp bottom
label or rsvp-te resignaling after a fault or te-lsp parameter change).

 Well, the mapping is not exactly 1:1, the LSR-MIB label stack object and
XC object are both mapped to a single mpls-linux out-label object

 This approach is efficient for a LSR which is using an out-label for a
remote LSR-ID to do 3 things at once:

1) vanilla LDP LER LSR-ID route/32, (FEC32 -> XC1 -> out-label-1),

2) using the LSR-ID LSP to push labeled VPN-VRF packets on it
(FEC-VRF -> XC2 -> out-label-1), and

3) intermediate LSR for the remote LSR-ID (in-label -> XC1 -> out-label-1)

 In case 1&3 XC1 will be empty (just FWD), in case 2 for each VRF route
there will be different a FEC -> XC tuple and in case 3 the in-label will
be LDP distributed to other peers. In this scenario, doing a switch from
(f.e) LDP to RSVP-TE for the bottom label (out-label-1) could be a single
call to the mpls-linux kernel.

 To get back to the original subject, if the bottom label toggles between
Null and non-Null (direct-link failing and recovering) integrating the
Null-label recognition in the forwarding plane means the signaling
protocol needs not do any acrobatics on potentially a large number of
routes (worst case: BGP full table and a large number of VPN customers).

Hmm, I kept on writing, this is more than the subject was about, oh well.

regards,
 yon

Re: [mpls-linux-general] Do I need ldp?

[Atul G. _. <gh...@ee...>]

unsubscribe me please.

On Wed, 27 Nov 2002, Mats Ydeklew wrote:

> Hi,
>
> I'm new at mpls and have some questions.
>
> My test plan is to use mpls in a firewall environment with only the LSR
> functionality.
> Cisco routers take care of labelling the packets at the edge and my mpls
> Linux just
> watching the traffic that passes through.
>
> 1. Do I need ldp or Zebra to do this?
> 2. Have someone been testing mpls together with linux-vlan?
>
> Thanks,
> Mats
>
>

[mpls-linux-general] Do I need ldp?

[Mats Y. <ma...@yd...>]

Hi,

I'm new at mpls and have some questions.

My test plan is to use mpls in a firewall environment with only the LSR 
functionality.
Cisco routers take care of labelling the packets at the edge and my mpls 
Linux just
watching the traffic that passes through.

1. Do I need ldp or Zebra to do this?
2. Have someone been testing mpls together with linux-vlan?

Thanks,
Mats

[mpls-linux-general] ldp-portable-0.305

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

Those of you actively using ldp-portable (and zebra-ldp) will want to
upgrade to the latest release (0.305).  It fixes many issues seen when
the routing table is in a state of flux.  It also adds a new show command
to mplsd:  'show mpls ftn' shows what FECs LDP has established bindings for.

-- 
James R. Leu

[mpls-linux-general] mpls-testing

[nitin p. <tac...@ya...>]

Leigh,
> 
> Whilst I am here, has anybody done any performance
> tests for MPLS on 
> Linux
I am trying to do some analysis for MPLS Linux using
RSVP-TE by IBCN. I am trying tp meausre bandwidth and
throghput in MPLS network versus non-mpls.I am
surprised to see in my network of two LSRs+ Ingress+
Egress. Delay in MPLS network is around 6milliseconds,
while that in non-mpls, using ospf signalling is 2.5
milliseconds. I think this is becuase LERs (Ingress
and Egress) takes lot more  time than LSRs. James can
you please provide me some coments on this. 

What are the other tests that can be performed?

 using some
> good testing kit?
I am not sure what kind of toolkit are you looking for
I am using a traffic generating software.
 I would love to try it out against
> some 
> Juniper/Cisco/Other boxes in the lab
I will also try to do the same testing against Cisco's
3600 some day.
Thanks,
Nitin

> but the company who had the lab made me redundant
> earlier this year :(
> 
> Thanks,
> Leigh Porter


__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com

[mpls-linux-general] Re: [MPLS-OPS]: security in the MPLS label's?

[Luc De G. <lde...@ci...>]

Ramesh,

You might want to start here :

draft-behringer-mpls-security-03.txt

Analysis of the Security of the MPLS Architecture 


Luc
 
> Hi,
>   I have been discussing the pro's and con's of MPLS  and someone
> mentioned about the security in the network.
> And  i am not sure about the answer.
> 
> What if i am able to recreate the label used in the MPLS?
>  - this can result in the mis-use of the QoS in a MPLS network?
> 
> And we do not want to add any security to the MPLS label as it is "light
> weight" and dont wanna overload it.
> 
> So is there a RFC which deals with this issue?
> 
> If the MPLS is on the back-bone network  i guess it shouldnt be a problem,
> but if it is on a VPN(which is not on the backbone) then wouldnt be a
> serious security hole?
> 
> So can someone help me out with this question?
> 
> thanks in advance
> Ramesh
> 
> 
> On Tue, 26 Nov 2002, alexb wrote:
> 
> > Hi
> > 
> > IMHO if a table with MPLS labels on P router is addressed by received label
> > value than
> > it should be much faster then doing IP lookup on a IP search tree
> > 
> > alex
> > 
> > > Hi,
> > >
> > > I guess it will be faster on the P router......
> > >
> > > mainly coz now you dont switch on "destn IP " lookups on ur Forwarding
> > Table
> > > (FT), u switch on labels...
> > >
> > > and labels are 20 bit not 24 bit..
> > >
> > > seperating signalling (routing) from forwarding does help..
> > >
> > > its simple, is the router noticeably faster when you have a seperate "FT"?
> > > surely you cant dispute that.....
> > >
> > > if yes..now comes features and scalability..RSVP-TE stuff to be done (how
> > > would you do it with only 8 queues in diffserv?)...
> > > and how do you make "VPNs"?
> > >
> > > so it has to be looked at not in terms of "raw switching" but "features +
> > > raw switching" being faster...
> > >
> > > -rgds
> > > Alok
> > >
> > > ----- Original Message -----
> > > From: <st...@ne...>
> > > To: <as...@ci...>
> > > Cc: <ro...@no...>; <mpl...@mp...>
> > > Sent: Tuesday, November 26, 2002 3:12 PM
> > > Subject: Re: Fwd: [MPLS-OPS]: basic question on MPLS
> > >
> > >
> > > > > At least it is not noticeably faster :) And of course
> > > > > imposition/disposition is in fact slower than plain IP. IMHO it is
> > > > > the decoupling of forwarding and routing that allows apps like
> > > > > TE/VPNs that makes MPLS more attractive.
> > > >
> > > > Agreed. I'm simply wondering why people are still talking about
> > > > MPLS being faster when that is one of the *least* interesting
> > > > things about MPLS *if it ever was true).
> > > >
> > > > We are using MPLS for the VPN capabilities.
> > > >
> > > > Steinar Haug, Nethelp consulting, st...@ne...
> > > >
> > > > -------
> > > > The MPLS-OPS Mailing List
> > > > Subscribe/Unsubscribe:  http://www.mplsrc.com/mplsops.shtml
> > > > Archive: http://www.mplsrc.com/mpls-ops_archive.shtml
> > > >
> > >
> > > -------
> > > The MPLS-OPS Mailing List
> > > Subscribe/Unsubscribe:  http://www.mplsrc.com/mplsops.shtml
> > > Archive: http://www.mplsrc.com/mpls-ops_archive.shtml
> > >
> > 
> > -------
> > The MPLS-OPS Mailing List
> > Subscribe/Unsubscribe:  http://www.mplsrc.com/mplsops.shtml
> > Archive: http://www.mplsrc.com/mpls-ops_archive.shtml
> > 
> 
> 
> -------
> The MPLS-OPS Mailing List
> Subscribe/Unsubscribe:  http://www.mplsrc.com/mplsops.shtml
> Archive: http://www.mplsrc.com/mpls-ops_archive.shtml
> 

[mpls-linux-general] security in the MPLS label's?

[Ramesh M. <ra...@bo...>]

Hi,
  I have been discussing the pro's and con's of MPLS  and someone
mentioned about the security in the network.
And  i am not sure about the answer.

What if i am able to recreate the label used in the MPLS?
 - this can result in the mis-use of the QoS in a MPLS network?

And we do not want to add any security to the MPLS label as it is "light
weight" and dont wanna overload it.

So is there a RFC which deals with this issue?

If the MPLS is on the back-bone network  i guess it shouldnt be a problem,
but if it is on a VPN(which is not on the backbone) then wouldnt be a
serious security hole?

So can someone help me out with this question?

thanks in advance
Ramesh


On Tue, 26 Nov 2002, alexb wrote:

> Hi
> 
> IMHO if a table with MPLS labels on P router is addressed by received label
> value than
> it should be much faster then doing IP lookup on a IP search tree
> 
> alex
> 
> > Hi,
> >
> > I guess it will be faster on the P router......
> >
> > mainly coz now you dont switch on "destn IP " lookups on ur Forwarding
> Table
> > (FT), u switch on labels...
> >
> > and labels are 20 bit not 24 bit..
> >
> > seperating signalling (routing) from forwarding does help..
> >
> > its simple, is the router noticeably faster when you have a seperate "FT"?
> > surely you cant dispute that.....
> >
> > if yes..now comes features and scalability..RSVP-TE stuff to be done (how
> > would you do it with only 8 queues in diffserv?)...
> > and how do you make "VPNs"?
> >
> > so it has to be looked at not in terms of "raw switching" but "features +
> > raw switching" being faster...
> >
> > -rgds
> > Alok
> >
> > ----- Original Message -----
> > From: <st...@ne...>
> > To: <as...@ci...>
> > Cc: <ro...@no...>; <mpl...@mp...>
> > Sent: Tuesday, November 26, 2002 3:12 PM
> > Subject: Re: Fwd: [MPLS-OPS]: basic question on MPLS
> >
> >
> > > > At least it is not noticeably faster :) And of course
> > > > imposition/disposition is in fact slower than plain IP. IMHO it is
> > > > the decoupling of forwarding and routing that allows apps like
> > > > TE/VPNs that makes MPLS more attractive.
> > >
> > > Agreed. I'm simply wondering why people are still talking about
> > > MPLS being faster when that is one of the *least* interesting
> > > things about MPLS *if it ever was true).
> > >
> > > We are using MPLS for the VPN capabilities.
> > >
> > > Steinar Haug, Nethelp consulting, st...@ne...
> > >
> > > -------
> > > The MPLS-OPS Mailing List
> > > Subscribe/Unsubscribe:  http://www.mplsrc.com/mplsops.shtml
> > > Archive: http://www.mplsrc.com/mpls-ops_archive.shtml
> > >
> >
> > -------
> > The MPLS-OPS Mailing List
> > Subscribe/Unsubscribe:  http://www.mplsrc.com/mplsops.shtml
> > Archive: http://www.mplsrc.com/mpls-ops_archive.shtml
> >
> 
> -------
> The MPLS-OPS Mailing List
> Subscribe/Unsubscribe:  http://www.mplsrc.com/mplsops.shtml
> Archive: http://www.mplsrc.com/mpls-ops_archive.shtml
> 

Re: [mpls-linux-general] basic questions about MPLS.

[Leigh P. <le...@bl...>]

Hiya,


Both Juniper (www.juniper.net) and Cisco (www.cisco.com) have some 
really good
documents about MPLS on their web sites. Yeah they are Cisco/Juniper 
specific but they
also do a good job of explaining what the advantages of MPLS are and how 
you can use it
for fun and for profit.

Whilst I am here, has anybody done any performance tests for MPLS on 
Linux using some
good testing kit? I would love to try it out against some 
Juniper/Cisco/Other boxes in the lab
but the company who had the lab made me redundant earlier this year :(

Thanks,
Leigh Porter

Folke Aeon wrote:

>
> in my opinion, the basic distinction between mpls
> and ip is that mpls is in layer 2.5 (a layer between
> the link layer and ip layer). but more technically,
> mpls is link-oriented switching technology, and ip
> is NOT link-oriented, which means that in ip network,
> you always gets a opsf routing protocol to route your
> packets, which mean that all packets will always
> intend to route from source to destination along
> the shortest path (which normally computed by
> dijkstra algorithm ), which will intend to cause
> congestion.
>
>  but in mpls network, which is a link oriented
> network, you can setup a pre-routed link between
> the source and the destination, and indeed , you
> can setup multi-links. thus you can do
> load-balance on all these links, which will
> avoid traffic congestion.
>
>  that's what i know :-), and wish it could do
> some help.
>
>  advice you to read the following for more technical
> info.:
> rfc2702(Requirements for Traffic Engineering Over MPLS)
> rfc3031(Multiprotocol Label Switching Architecture)
> rfc3037(LDP Applicability)
> rfc3209(extensions to rsvp for lsp tunnels)
> rfc3212(Constraint-Based LSP Setup using LDP)
> rfc3270(MPLS Support of Differentiated Services)
>
> you can get them at :
> http://www.ietf.org/rfc/rfcNNNN.txt
>
> where NNNN is the RFC number prefixed
> with zeroes as necessary to make a four
> digit number.
>
> have fun :)
>
>
>
> folke
>
>>
>> Message: 2
>> Date: Mon, 25 Nov 2002 12:48:59 -0500 (EST)
>> From: Ramesh Masavarapu <ra...@bo...>
>> To: mpl...@li...
>> Subject: [mpls-linux-general] basic questions about MPLS.
>>
>>
>> Hi,
>>   I would apprecitate if someone could help me why MPLS is being 
>> used?I am
>> lost as to where i could find descent enough information about this.
>> And if someone could explain me what major advantages MPLS has (in
>> comparison with techniques used in IP ,for e.g in the area of traffic
>> engineering), i would appreciate it a lot.
>> The questions i asked may sound dumb , but i am new to MPLS and would
>> appreciate any kind of help .
>>
>> thanks in advance
>> -Ramesh Masavarapu
>
>
>
>
> _________________________________________________________________
> Help STOP SPAM with the new MSN 8 and get 2 months FREE*  
> http://join.msn.com/?page=features/junkmail
>
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: Get the new Palm Tungsten T 
> handheld. Power & Color in a compact size! 
> http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0002en
> _______________________________________________
> mpls-linux-general mailing list
> mpl...@li...
> https://lists.sourceforge.net/lists/listinfo/mpls-linux-general

Re: [mpls-linux-general] basic questions about MPLS.

[Folke A. <aeo...@ho...>]

in my opinion, the basic distinction between mpls
and ip is that mpls is in layer 2.5 (a layer between
the link layer and ip layer). but more technically,
mpls is link-oriented switching technology, and ip
is NOT link-oriented, which means that in ip network,
you always gets a opsf routing protocol to route your
packets, which mean that all packets will always
intend to route from source to destination along
the shortest path (which normally computed by
dijkstra algorithm ), which will intend to cause
congestion.

  but in mpls network, which is a link oriented
network, you can setup a pre-routed link between
the source and the destination, and indeed , you
can setup multi-links. thus you can do
load-balance on all these links, which will
avoid traffic congestion.

  that's what i know :-), and wish it could do
some help.

  advice you to read the following for more technical
info.:
rfc2702(Requirements for Traffic Engineering Over MPLS)
rfc3031(Multiprotocol Label Switching Architecture)
rfc3037(LDP Applicability)
rfc3209(extensions to rsvp for lsp tunnels)
rfc3212(Constraint-Based LSP Setup using LDP)
rfc3270(MPLS Support of Differentiated Services)

you can get them at :
http://www.ietf.org/rfc/rfcNNNN.txt

where NNNN is the RFC number prefixed
with zeroes as necessary to make a four
digit number.

have fun :)



folke

>
>Message: 2
>Date: Mon, 25 Nov 2002 12:48:59 -0500 (EST)
>From: Ramesh Masavarapu <ra...@bo...>
>To: mpl...@li...
>Subject: [mpls-linux-general] basic questions about MPLS.
>
>
>Hi,
>   I would apprecitate if someone could help me why MPLS is being used?I am
>lost as to where i could find descent enough information about this.
>And if someone could explain me what major advantages MPLS has (in
>comparison with techniques used in IP ,for e.g in the area of traffic
>engineering), i would appreciate it a lot.
>The questions i asked may sound dumb , but i am new to MPLS and would
>appreciate any kind of help .
>
>thanks in advance
>-Ramesh Masavarapu



_________________________________________________________________
Help STOP SPAM with the new MSN 8 and get 2 months FREE*  
http://join.msn.com/?page=features/junkmail

Re: [mpls-linux-general] IPv6 status with MPLS-Linux

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

On Sat, Nov 23, 2002 at 03:44:45PM +0000, Iain Young wrote:
> Hi All,
> 
> I was wondering what the current state of IPv6 support was within
> MPLS-Linux.
> 
> I browsed thru the archives, and noticed about a year ago a thread
> between Vino Thomas, and James R. Leu, discussing the current state,
> and James stated:
> 
> > Their are two things that are not in place for the egress LER.  Here
> > the packets need to come into the MPLS stack and go out via the IPv6 
> > stack.  So the layer 3 protocol associated with the incoming label
> > needs to be IPv6.  Currently mplsadm doesn't provide a means to say
> > which layer 3 protocol should be associated with a incoming label
> > (I've assumed IPv4 uptil now).  In addition I have not tested the code
> > that rebuild the IPv6 header and sends into IPv6 land.  Both are minor
> > fixes and given some time, I could complete them in a night.  THe
> > problem is I have no idea how to test it :-)
>  
> Did this ever get done ? Has there been any further work on IPv6
> support since ?

Minimal work has been done, zero testing has been done.  The code to
be an egress LER has been added.  By using mpls tunnel interfaces you
should be able to create an ingress LER.

Another part that will need work is specifing IPv6 address as nexthop.
The fix for this will take 2 parts, fixing mplsadm and adding support
to the MPLS kernel code to bind IPv6 addresses to hardware addresses (via the
kernels neighbor cache)

ldp-portable does not have any support for IPv6.

> (I'm not sure, but I think that was in reference using mpls tunnel)
> 
> 
> I am (re)implementing my home network, using IPv6 natively, with
> part of it shown below:
> 
>                                     (IPv6/IP) tun1|   |tun0 (IPv6/IP)
>                                                   |   |
>           columbia                                c2620
>              |eth0(BGP 64512)                       |eth0(BGP 64512)
> |------------------------------------------------------------------| BGP 64512
>                                   |eth0(BGP 64512)
>                              pathfinder
>               (BGP 65097)tap0|        |tap1(BGP 65097)
>                              |        |
>               (BGP 65097)eth0|        |eth0(BGP 65097)
>                            iiigw1   iiigw2
>         (OSPF 0.0.0.97)eth1|             |eth1(OSPF 0.0.0.97)
>                            |             |
>                            |             |
>                            +----HOSTS----+
>             (OSPF 0.0.0.97)eth0   |  eth1(OSPD 0.0.0.97)
>                                   |
>                                   |dummy0
> 
> (Actually, all the routers/hosts that are shown "below" pathfinder,
> are actually user-mode-linux instances, but they have connectivity
> as shown, and partake in BGP or OSPF like any 'real' machine, using
> zebra - As yes, OSPF is giving grief at the moment :>)
> 
> Remembering that my native transport is IPv6 (So assume no IPv4
> - There is IPv4, but not a lot of it :>) how capable is MPLS-Linux ?
> What needs to be done before I can run MPLS over IPv6 natively ?

-- 
James R. Leu

Re: [mpls-linux-general] how to use mpls-linux module

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

On Mon, Nov 25, 2002 at 05:46:45PM +0800, roro wrote:
> hi,all
>    I want to use mpls-linux-1.172 ,but I don't know how to do it. Could you
> tell me the steps to install and use it ? Any help will be appreciated.Thanks
> in advance.

Inside mpls-linux-1.172.tar.gz is a file QUICK.START.  Read that and
post specific questions to the mailing list.

-- 
James R. Leu

Re: [mpls-linux-general] basic questions about MPLS.

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

That is exactly what I was gonna say :-)

On Mon, Nov 25, 2002 at 09:59:04AM -0800, nitin panjwani wrote:
> chckout mplsrc.com=20


> --- Ramesh Masavarapu <ra...@bo...>
> wrote:
> >=20
> > Hi,
> >   I would apprecitate if someone could help me why
> > MPLS is being used?I am=20
> > lost as to where i could find descent enough
> > information about this.
> > And if someone could explain me what major
> > advantages MPLS has (in
> > comparison with techniques used in IP ,for e.g in
> > the area of traffic
> > engineering), i would appreciate it a lot.
> > The questions i asked may sound dumb , but i am new
> > to MPLS and would
> > appreciate any kind of help .
> >=20
> > thanks in advance
> > -Ramesh Masavarapu
> >=20
> >=20
> >=20
> >=20
> >=20
> >
> -------------------------------------------------------
> > This SF.net email is sponsored by: Get the new Palm
> > Tungsten T=20
> > handheld. Power & Color in a compact size!=20
> >
> http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0002en
> > _______________________________________________
> > mpls-linux-general mailing list
> > mpl...@li...
> >
> https://lists.sourceforge.net/lists/listinfo/mpls-linux-general
>=20
>=20
> __________________________________________________
> Do you Yahoo!?
> Yahoo! Mail Plus =96 Powerful. Affordable. Sign up now.
> http://mailplus.yahoo.com
>=20
>=20
> -------------------------------------------------------
> This SF.net email is sponsored by: Get the new Palm Tungsten T=20
> handheld. Power & Color in a compact size!=20
> http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0002en
> _______________________________________________
> mpls-linux-general mailing list
> mpl...@li...
> https://lists.sourceforge.net/lists/listinfo/mpls-linux-general

--=20
James R. Leu

Re: [mpls-linux-general] basic questions about MPLS.

[nitin p. <tac...@ya...>]

chckout mplsrc.com 
--- Ramesh Masavarapu <ra...@bo...>
wrote:
> 
> Hi,
>   I would apprecitate if someone could help me why
> MPLS is being used?I am 
> lost as to where i could find descent enough
> information about this.
> And if someone could explain me what major
> advantages MPLS has (in
> comparison with techniques used in IP ,for e.g in
> the area of traffic
> engineering), i would appreciate it a lot.
> The questions i asked may sound dumb , but i am new
> to MPLS and would
> appreciate any kind of help .
> 
> thanks in advance
> -Ramesh Masavarapu
> 
> 
> 
> 
> 
>
-------------------------------------------------------
> This SF.net email is sponsored by: Get the new Palm
> Tungsten T 
> handheld. Power & Color in a compact size! 
>
http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0002en
> _______________________________________________
> mpls-linux-general mailing list
> mpl...@li...
>
https://lists.sourceforge.net/lists/listinfo/mpls-linux-general


__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus – Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com

[mpls-linux-general] basic questions about MPLS.

[Ramesh M. <ra...@bo...>]

Hi,
  I would apprecitate if someone could help me why MPLS is being used?I am 
lost as to where i could find descent enough information about this.
And if someone could explain me what major advantages MPLS has (in
comparison with techniques used in IP ,for e.g in the area of traffic
engineering), i would appreciate it a lot.
The questions i asked may sound dumb , but i am new to MPLS and would
appreciate any kind of help .

thanks in advance
-Ramesh Masavarapu

[mpls-linux-general] how to use mpls-linux module

[roro <mpl...@ey...>]

hi,all
   I want to use mpls-linux-1.172 ,but I don't know how to do it. Could you
tell me the steps to install and use it ? Any help will be appreciated.Thanks
in advance.

                                                          roro

                                   





--http://www.eyou.com
--Îȶ¨¿É¿¿µÄÃâ·Ñµç×ÓÐÅÏä  ÓïÒôÓʼþ  Òƶ¯ÊéÇ©  ÈÕÀú·þÎñ  ÍøÂç´æ´¢...ÒÚÓÊδ¾¡

[mpls-linux-general] IPv6 status with MPLS-Linux

[<ia...@g7...>]

Hi All,

I was wondering what the current state of IPv6 support was within
MPLS-Linux.

I browsed thru the archives, and noticed about a year ago a thread
between Vino Thomas, and James R. Leu, discussing the current state,
and James stated:

> Their are two things that are not in place for the egress LER.  Here
> the packets need to come into the MPLS stack and go out via the IPv6 
> stack.  So the layer 3 protocol associated with the incoming label
> needs to be IPv6.  Currently mplsadm doesn't provide a means to say
> which layer 3 protocol should be associated with a incoming label
> (I've assumed IPv4 uptil now).  In addition I have not tested the code
> that rebuild the IPv6 header and sends into IPv6 land.  Both are minor
> fixes and given some time, I could complete them in a night.  THe
> problem is I have no idea how to test it :-)
 
Did this ever get done ? Has there been any further work on IPv6
support since ?

(I'm not sure, but I think that was in reference using mpls tunnel)


I am (re)implementing my home network, using IPv6 natively, with
part of it shown below:

                                    (IPv6/IP) tun1|   |tun0 (IPv6/IP)
                                                  |   |
          columbia                                c2620
             |eth0(BGP 64512)                       |eth0(BGP 64512)
|------------------------------------------------------------------| BGP 64512
                                  |eth0(BGP 64512)
                             pathfinder
              (BGP 65097)tap0|        |tap1(BGP 65097)
                             |        |
              (BGP 65097)eth0|        |eth0(BGP 65097)
                           iiigw1   iiigw2
        (OSPF 0.0.0.97)eth1|             |eth1(OSPF 0.0.0.97)
                           |             |
                           |             |
                           +----HOSTS----+
            (OSPF 0.0.0.97)eth0   |  eth1(OSPD 0.0.0.97)
                                  |
                                  |dummy0

(Actually, all the routers/hosts that are shown "below" pathfinder,
are actually user-mode-linux instances, but they have connectivity
as shown, and partake in BGP or OSPF like any 'real' machine, using
zebra - As yes, OSPF is giving grief at the moment :>)

Remembering that my native transport is IPv6 (So assume no IPv4
- There is IPv4, but not a lot of it :>) how capable is MPLS-Linux ?
What needs to be done before I can run MPLS over IPv6 natively ?


Best Regards

Iain

[mpls-linux-general] testing PPPD in MPLS-Linux platform

[<pa...@vs...>]

hi
i am Ms.Pathma Rathinavelu, am working on an mpls  enhanced linux platform. i am performing a simple experiment on PPPD which is MPLS enhanced. the set up is very simple and it is as follws . i have connected 2 machines with RS-232 cable, and both are operating in Linux - MPLS enabled platform. i have patched the file ppp-2.4.1-mpls.diff file. how do i test for the serial communication between the 2 computers ?? . for MPLS operatability i tested using 'ethereal' packet analyser. what is the way for testing PPPD -serial communication , are there any emulators available ?? or ones like "ethereal"

kindly help me out.
thanks in advance
pathma

[mpls-linux-general] question about cr-ldp in TODO list

[Kwangwoo L. <ji...@ko...>]

SGVsbG8hDQpJIHNhdyBDUi1leHRlbnRpb25zIGZvciBMRFAgZW50cnkgaW4gVE9ETyBsaXN0Lg0K
QW5kIEkga25vdyBsZHAtcG9ydGFibGUgcGFja2FnZSBpbmNsdWRlcyBub3J0ZWwgbmV0d29ya3Mn
cyBjci1sZHAgY29kZXMuDQoNCmlmIGxkcC1wb3J0YWJsZSBkb24ndCBzdXBwb3J0IGNyLWxkcCBm
ZWF0dXJlLA0KYW5kDQppZiB5b3VyIGdyb3VwIGludGVuZCB0byByZXdyaXRlIHRoZSBub3J0ZWwg
bmV0d29ya3MncyBjci1sZHAgY29kZXMgb2YgbGRwLXBvcnRhYmxlIHBhY2thZ2UgdG8gR05VIGxp
ZW5jZSwNCndlIHdvdWxkIGxpa2UgdG8ga25vdyBhYm91dCB0aGUgc2l0dWF0aW9uIG9mIGltcGxl
bWVudGF0aW9uIG9mIGNyLWxkcCBmZWF0dXJlLiA6KQ0KDQp3ZSBhcmUgc3R1ZGVudHMgd2hvIGFy
ZSBpbnRlcmVzdGVkIGluIG1wbHMuDQpzbywgd2Ugd291bGQgbGlrZSB0byBpbXBsZW1lbnQgY3It
bGRwIGJhc2VkIG9uIGxkcC1wb3J0YWJsZS4NCg0KaWYgcG9zc2libGUsIHNlbmQgYW55IGluZm9y
bWF0aW9uIHRvIHVzLi4gDQoNCmhhdmUgYSBnb29kIHRpbWUuDQo=

Re: [mpls-linux-general] mpls sniffer

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

If you can do any sort of coding try this:

Designate a Linux box as the "test equiptment".  Deisignate other boxes
as the "devices under test".

Connect them like this:


                ------         ------        ------
        -------| DUT1 |-------| DUT2 |------| DUT3 |------
       |        ------         ------        ------       |
       |                       ------                     |
        ----------------------| TEST |--------------------
                             1 ------ 3

Download and install linux-vrf (virtual routing and forwarding for linux)
from http://sf.net/projects/linux-vrf/  Put interface 1 and 3 on TEST int=
o
seperate VRFs.

Create an application that opens 2 UDP sockets, one bound to the VRF
associated with interface 1 on TEST, and the other bound to the VRF
associated with interface 3 on TEST. Then send packets from one to the ot=
her
via "sendto".  You can add whatever level of timing by adding time stamps=
 in
the payload of the packets you are sending.  Maye sure to calibrate your
test gear (ie figure out how long it takes to send packets through the
application by connecting port 1  and 3 directly to each other).

So, the short answer is: I do not know of any open source software to
do this, but that shouldn't stop you from writing some and turning it
into an open source project of your own :-)


On Thu, Nov 21, 2002 at 01:46:34AM -0800, nitin panjwani wrote:
> Hi James,
>=20
> I am looking for any sniffer which can recognixe the
> MPLS packet as well as meaure the time upto
> microsecond level.
>=20
> I know ethereal can recognize, but it displays the
> time at .1ms level. Do you any other freely available
> sniffer.=20
>=20
> I am trying to measure how much processing mpls LSR
> takes compare to L3, in processing a packate from
> incomming to outgoing interface. Is there any other
> way to do it.=20
>=20
> Thanks,
> Nitin=20
>=20
>=20
>=20
>=20
>=20
>=20
>=20
>=20
> __________________________________________________
> Do you Yahoo!?
> Yahoo! Mail Plus =96 Powerful. Affordable. Sign up now.
> http://mailplus.yahoo.com
>=20
>=20
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> mpls-linux-general mailing list
> mpl...@li...
> https://lists.sourceforge.net/lists/listinfo/mpls-linux-general

--=20
James R. Leu

[mpls-linux-general] mpls sniffer

[nitin p. <tac...@ya...>]

Hi James,

I am looking for any sniffer which can recognixe the
MPLS packet as well as meaure the time upto
microsecond level.

I know ethereal can recognize, but it displays the
time at .1ms level. Do you any other freely available
sniffer. 

I am trying to measure how much processing mpls LSR
takes compare to L3, in processing a packate from
incomming to outgoing interface. Is there any other
way to do it. 

Thanks,
Nitin 








__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus – Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com

Re: [mpls-linux-general] New releases CRASH

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

Can you turn on tracing and duplicate?

try:

mpls ldp
  trace all

on the top level config.

On Tue, Nov 19, 2002 at 02:54:37PM -0600, James R. Leu wrote:
> Did you grab the newest version via CVS or via the new tar file?
>=20
> On Tue, Nov 19, 2002 at 04:37:00PM -0200, Pl=EDnio de Paula wrote:
> > Hello James,
> >=20
> > I am testing the new MPLS and LDP + Zebra and there=B4s a seg fault (=
apparently) when peers exchanges labels...
> >=20
> > Here=B4s the latest messages from mplsd error and the backtrace:
> >=20
> > ldp_label_mapping_with_xc: enter
> > before: type 0 label 0
> > after: type 1 label 16
> > ldp_label_mapping_with_xc: exit
> > _ldp_global_add_outlabel
> >=20
> > Program received signal SIGSEGV, Segmentation fault.
> > 0x0806c481 in ldp_outlabel_create_complete (g=3D0x80b6698, s=3D0x80bb=
da0, nh=3D0x1c,
> >     a=3D0x80c0320) at ldp_outlabel.c:55
> > 55          memcpy(&out->info.nexthop.u.ipif.ip,
> >=20
> >=20
> > BACKTRACE:
> >=20
> > #0  0x0806c481 in ldp_outlabel_create_complete (g=3D0x80b6698, s=3D0x=
80bbda0,
> >     nh=3D0x1c, a=3D0x80c0320) at ldp_outlabel.c:55
> > #1  0x0805f33b in ldp_label_mapping_process (g=3D0x80b6698, s=3D0x80b=
bda0, a=3D0x0,
> >     e=3D0x0, r_attr=3D0x80c0320, fec=3D0xbfffb7b0) at ldp_label_mappi=
ng.c:910
> > #2  0x0806fb4c in ldp_state_process (g=3D0x80b6698, s=3D0x80bbda0, a=3D=
0x0, e=3D0x0,
> >     event=3D5, msg=3D0x80c0320, from=3D0xbffff9b0) at ldp_state_funcs=
.c:346
> > #3  0x08070780 in ldp_state_machine (g=3D0x80b6698, session=3D0x80bbd=
a0, adj=3D0x0,
> >     entity=3D0x0, event=3D5, msg=3D0xbfffb8c0, from=3D0xbffff9b0)
> >     at ldp_state_machine.c:265
> > #4  0x08070a93 in ldp_buf_process (g=3D0x80b6698, socket=3D0x80b5c28,
> >     buf=3D0x809c620, extra=3D0x80bbda0, event=3DLDP_EVENT_LABEL,
> >     local_from=3D0xbffff9b0, more=3D0xbfffd95c) at ldp_state_machine.=
c:481
> > #5  0x08070228 in ldp_event (handle=3D0x80b6698, socket=3D0x80b5c28,
> >     user_from=3D0x0, if_handle=3D0x0, buf=3D0x0, extra=3D0x80bbda0,
> >     event=3DLDP_EVENT_TCP_DATA) at ldp_state_machine.c:134
> > #6  0x0804a6f7 in mplsd_read (thread=3D0x1) at impl_socket.c:75
> > #7  0x0807d58c in thread_call (thread=3D0xbffffab0) at thread.c:647
> > #8  0x0804c267 in main (argc=3D3, argv=3D0xbffffab0) at mpls_main.c:2=
24
> > #9  0x420158d4 in __libc_start_main () from /lib/i686/libc.so.6
> >=20
> > Thanks!
> > Pl=EDnio de Paula
> > UNICAMP/Brazil
> >=20
> > -----Mensagem original-----
> > De: James R. Leu [mailto:jl...@mi...]
> > Enviada em: ter=E7a-feira, 19 de novembro de 2002 05:25
> > Para: mpl...@li...
> > Assunto: [mpls-linux-general] New releases
> >=20
> >=20
> > Take a look at the ChangeLogs for info about the releases:
> >=20
> > http://osdn.dl.sourceforge.net/sourceforge/mpls-linux/ldp-portable-0.=
300.tar.gz
> > http://sourceforge.net/project/shownotes.php?release_id=3D123060
> >=20
> > http://osdn.dl.sourceforge.net/sourceforge/mpls-linux/mpls-linux-1.17=
2.tar.gz
> > http://sourceforge.net/project/shownotes.php?release_id=3D122264
> >=20
> > --=20
> > James R. Leu
> >=20
> >=20
> > -------------------------------------------------------
> > This sf.net email is sponsored by: To learn the basics of securing=20
> > your web site with SSL, click here to get a FREE TRIAL of a Thawte=20
> > Server Certificate: http://www.gothawte.com/rd524.html
> > _______________________________________________
> > mpls-linux-general mailing list
> > mpl...@li...
> > https://lists.sourceforge.net/lists/listinfo/mpls-linux-general
> >=20
> >=20
> > -------------------------------------------------------
> > This sf.net email is sponsored by: To learn the basics of securing=20
> > your web site with SSL, click here to get a FREE TRIAL of a Thawte=20
> > Server Certificate: http://www.gothawte.com/rd524.html
> > _______________________________________________
> > mpls-linux-general mailing list
> > mpl...@li...
> > https://lists.sourceforge.net/lists/listinfo/mpls-linux-general
>=20
> --=20
> James R. Leu

--=20
James R. Leu

RES: [mpls-linux-general] New releases CRASH

[<pp...@cp...>]

New tar files in sf.net.

Pl=EDnio de Paula
UNICAMP/Brazil=20

-----Mensagem original-----
De: James R. Leu [mailto:jl...@mi...]
Enviada em: ter=E7a-feira, 19 de novembro de 2002 17:55
Para: Pl=EDnio de Paula
Assunto: Re: [mpls-linux-general] New releases CRASH


Did you grab the newest version via CVS or via the new tar file?

On Tue, Nov 19, 2002 at 04:37:00PM -0200, Pl=EDnio de Paula wrote:
> Hello James,
>=20
> I am testing the new MPLS and LDP + Zebra and there=B4s a seg fault =
(apparently) when peers exchanges labels...
>=20
> Here=B4s the latest messages from mplsd error and the backtrace:
>=20
> ldp_label_mapping_with_xc: enter
> before: type 0 label 0
> after: type 1 label 16
> ldp_label_mapping_with_xc: exit
> _ldp_global_add_outlabel
>=20
> Program received signal SIGSEGV, Segmentation fault.
> 0x0806c481 in ldp_outlabel_create_complete (g=3D0x80b6698, =
s=3D0x80bbda0, nh=3D0x1c,
>     a=3D0x80c0320) at ldp_outlabel.c:55
> 55          memcpy(&out->info.nexthop.u.ipif.ip,
>=20
>=20
> BACKTRACE:
>=20
> #0  0x0806c481 in ldp_outlabel_create_complete (g=3D0x80b6698, =
s=3D0x80bbda0,
>     nh=3D0x1c, a=3D0x80c0320) at ldp_outlabel.c:55
> #1  0x0805f33b in ldp_label_mapping_process (g=3D0x80b6698, =
s=3D0x80bbda0, a=3D0x0,
>     e=3D0x0, r_attr=3D0x80c0320, fec=3D0xbfffb7b0) at =
ldp_label_mapping.c:910
> #2  0x0806fb4c in ldp_state_process (g=3D0x80b6698, s=3D0x80bbda0, =
a=3D0x0, e=3D0x0,
>     event=3D5, msg=3D0x80c0320, from=3D0xbffff9b0) at =
ldp_state_funcs.c:346
> #3  0x08070780 in ldp_state_machine (g=3D0x80b6698, =
session=3D0x80bbda0, adj=3D0x0,
>     entity=3D0x0, event=3D5, msg=3D0xbfffb8c0, from=3D0xbffff9b0)
>     at ldp_state_machine.c:265
> #4  0x08070a93 in ldp_buf_process (g=3D0x80b6698, socket=3D0x80b5c28,
>     buf=3D0x809c620, extra=3D0x80bbda0, event=3DLDP_EVENT_LABEL,
>     local_from=3D0xbffff9b0, more=3D0xbfffd95c) at =
ldp_state_machine.c:481
> #5  0x08070228 in ldp_event (handle=3D0x80b6698, socket=3D0x80b5c28,
>     user_from=3D0x0, if_handle=3D0x0, buf=3D0x0, extra=3D0x80bbda0,
>     event=3DLDP_EVENT_TCP_DATA) at ldp_state_machine.c:134
> #6  0x0804a6f7 in mplsd_read (thread=3D0x1) at impl_socket.c:75
> #7  0x0807d58c in thread_call (thread=3D0xbffffab0) at thread.c:647
> #8  0x0804c267 in main (argc=3D3, argv=3D0xbffffab0) at =
mpls_main.c:224
> #9  0x420158d4 in __libc_start_main () from /lib/i686/libc.so.6
>=20
> Thanks!
> Pl=EDnio de Paula
> UNICAMP/Brazil
>=20
> -----Mensagem original-----
> De: James R. Leu [mailto:jl...@mi...]
> Enviada em: ter=E7a-feira, 19 de novembro de 2002 05:25
> Para: mpl...@li...
> Assunto: [mpls-linux-general] New releases
>=20
>=20
> Take a look at the ChangeLogs for info about the releases:
>=20
> =
http://osdn.dl.sourceforge.net/sourceforge/mpls-linux/ldp-portable-0.300.=
tar.gz
> http://sourceforge.net/project/shownotes.php?release_id=3D123060
>=20
> =
http://osdn.dl.sourceforge.net/sourceforge/mpls-linux/mpls-linux-1.172.ta=
r.gz
> http://sourceforge.net/project/shownotes.php?release_id=3D122264
>=20
> --=20
> James R. Leu
>=20
>=20
> -------------------------------------------------------
> This sf.net email is sponsored by: To learn the basics of securing=20
> your web site with SSL, click here to get a FREE TRIAL of a Thawte=20
> Server Certificate: http://www.gothawte.com/rd524.html
> _______________________________________________
> mpls-linux-general mailing list
> mpl...@li...
> https://lists.sourceforge.net/lists/listinfo/mpls-linux-general
>=20
>=20
> -------------------------------------------------------
> This sf.net email is sponsored by: To learn the basics of securing=20
> your web site with SSL, click here to get a FREE TRIAL of a Thawte=20
> Server Certificate: http://www.gothawte.com/rd524.html
> _______________________________________________
> mpls-linux-general mailing list
> mpl...@li...
> https://lists.sourceforge.net/lists/listinfo/mpls-linux-general

--=20
James R. Leu

RES: [mpls-linux-general] New releases CRASH

[<pp...@cp...>]

Great.

PS: I'm working with mixed versions (one machine with MPLS 1.170 + LDP =
0.250 and other with new versions)

Pl=EDnio de Paula
UNICAMP/Brazil

-----Mensagem original-----
De: James R. Leu [mailto:jl...@mi...]
Enviada em: ter=E7a-feira, 19 de novembro de 2002 17:45
Para: Pl=EDnio de Paula
Assunto: Re: [mpls-linux-general] New releases CRASH


Thanks for the report.  I'll work on it this evening.

On Tue, Nov 19, 2002 at 04:37:00PM -0200, Pl=EDnio de Paula wrote:
> Hello James,
>=20
> I am testing the new MPLS and LDP + Zebra and there=B4s a seg fault =
(apparently) when peers exchanges labels...
>=20
> Here=B4s the latest messages from mplsd error and the backtrace:
>=20
> ldp_label_mapping_with_xc: enter
> before: type 0 label 0
> after: type 1 label 16
> ldp_label_mapping_with_xc: exit
> _ldp_global_add_outlabel
>=20
> Program received signal SIGSEGV, Segmentation fault.
> 0x0806c481 in ldp_outlabel_create_complete (g=3D0x80b6698, =
s=3D0x80bbda0, nh=3D0x1c,
>     a=3D0x80c0320) at ldp_outlabel.c:55
> 55          memcpy(&out->info.nexthop.u.ipif.ip,
>=20
>=20
> BACKTRACE:
>=20
> #0  0x0806c481 in ldp_outlabel_create_complete (g=3D0x80b6698, =
s=3D0x80bbda0,
>     nh=3D0x1c, a=3D0x80c0320) at ldp_outlabel.c:55
> #1  0x0805f33b in ldp_label_mapping_process (g=3D0x80b6698, =
s=3D0x80bbda0, a=3D0x0,
>     e=3D0x0, r_attr=3D0x80c0320, fec=3D0xbfffb7b0) at =
ldp_label_mapping.c:910
> #2  0x0806fb4c in ldp_state_process (g=3D0x80b6698, s=3D0x80bbda0, =
a=3D0x0, e=3D0x0,
>     event=3D5, msg=3D0x80c0320, from=3D0xbffff9b0) at =
ldp_state_funcs.c:346
> #3  0x08070780 in ldp_state_machine (g=3D0x80b6698, =
session=3D0x80bbda0, adj=3D0x0,
>     entity=3D0x0, event=3D5, msg=3D0xbfffb8c0, from=3D0xbffff9b0)
>     at ldp_state_machine.c:265
> #4  0x08070a93 in ldp_buf_process (g=3D0x80b6698, socket=3D0x80b5c28,
>     buf=3D0x809c620, extra=3D0x80bbda0, event=3DLDP_EVENT_LABEL,
>     local_from=3D0xbffff9b0, more=3D0xbfffd95c) at =
ldp_state_machine.c:481
> #5  0x08070228 in ldp_event (handle=3D0x80b6698, socket=3D0x80b5c28,
>     user_from=3D0x0, if_handle=3D0x0, buf=3D0x0, extra=3D0x80bbda0,
>     event=3DLDP_EVENT_TCP_DATA) at ldp_state_machine.c:134
> #6  0x0804a6f7 in mplsd_read (thread=3D0x1) at impl_socket.c:75
> #7  0x0807d58c in thread_call (thread=3D0xbffffab0) at thread.c:647
> #8  0x0804c267 in main (argc=3D3, argv=3D0xbffffab0) at =
mpls_main.c:224
> #9  0x420158d4 in __libc_start_main () from /lib/i686/libc.so.6
>=20
> Thanks!
> Pl=EDnio de Paula
> UNICAMP/Brazil
>=20
> -----Mensagem original-----
> De: James R. Leu [mailto:jl...@mi...]
> Enviada em: ter=E7a-feira, 19 de novembro de 2002 05:25
> Para: mpl...@li...
> Assunto: [mpls-linux-general] New releases
>=20
>=20
> Take a look at the ChangeLogs for info about the releases:
>=20
> =
http://osdn.dl.sourceforge.net/sourceforge/mpls-linux/ldp-portable-0.300.=
tar.gz
> http://sourceforge.net/project/shownotes.php?release_id=3D123060
>=20
> =
http://osdn.dl.sourceforge.net/sourceforge/mpls-linux/mpls-linux-1.172.ta=
r.gz
> http://sourceforge.net/project/shownotes.php?release_id=3D122264
>=20
> --=20
> James R. Leu
>=20
>=20
> -------------------------------------------------------
> This sf.net email is sponsored by: To learn the basics of securing=20
> your web site with SSL, click here to get a FREE TRIAL of a Thawte=20
> Server Certificate: http://www.gothawte.com/rd524.html
> _______________________________________________
> mpls-linux-general mailing list
> mpl...@li...
> https://lists.sourceforge.net/lists/listinfo/mpls-linux-general
>=20
>=20
> -------------------------------------------------------
> This sf.net email is sponsored by: To learn the basics of securing=20
> your web site with SSL, click here to get a FREE TRIAL of a Thawte=20
> Server Certificate: http://www.gothawte.com/rd524.html
> _______________________________________________
> mpls-linux-general mailing list
> mpl...@li...
> https://lists.sourceforge.net/lists/listinfo/mpls-linux-general

--=20
James R. Leu