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

[mpls-linux-general] RE: [MPLS-Linux] Bug with 2.4.0-test11, mpls 0.700 and Interphase ATM PCI x575/x52 5/x531

[Jonathan E. <je...@no...>]

> -----Original Message-----
> From: James R. Leu [mailto:jl...@mi...]
> 
> What is the physical ATM index of the card?  (more 
> /proc/net/atm/devices)

root@onc2:~> cat /proc/net/atm/devices
Itf Type    ESI/"MAC"addr AAL(TX,err,RX,err,drop) ...
  0 ia      00007794576c  0 ( 0 0 0 0 0 )  5 ( 190 0 190 0 0 )

> Can you try doing a mplsadm -d prior to running this command 
> and see if
> if gives any output?

If I use atm1 for the adapter instead of atm0, it stops crashing.  The LSP
itself doesn't seem to work though - tcpdumping either side results in plain
ping results.

> PS Please use the new mailing list (which you should have been
> subscribed to :-)

Roger dodger sir!

[mpls-linux-general] Re: [MPLS-Linux] Bug with 2.4.0-test11, mpls 0.700 and Interphase ATM PCI x575/x52 5/x531

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

On Tue, Dec 05, 2000 at 04:16:42PM -0500, Jonathan Earle wrote:
> Hi,
> 
> I can bring the ATM interface up, I can ping back and forth, I can create
> route entries for networks connected to the far side of the connection and
> ping them successfully, but if I try to bring up an LSP over the ATM link
> (using '/usr/local/bin/mplsadm -A -B -O atm:0/105:atm0 -f 10.4.99.0/24'), I
> get:
> 
> out: atm0
> out: 8
> out: 2
> out: 6881280
> out: 0.0.0.0
> Segmentation fault

What is the physical ATM index of the card?  (more /proc/net/atm/devices)

Can you try doing a mplsadm -d prior to running this command and see if
if gives any output?

> Doing anything else results in:
> 
> root@onc2:~> /usr/local/bin/mplsadm -d
> rtnl_open: Address already in use
> Netlink: Address already in use
> 
> At which point, I have to reboot with a kernel panic onscreen.  Thoughts?

Off the top of my head I'm not sure.  I'll have to look at it.

I'll create a bug report for this (on the brand-spanking new Sourceforge
MPLS for Linux project page http://sourceforge.net/projects/mpls-linux/)

I'll try to get around looking at it tonight.

Jim

PS Please use the new mailing list (which you should have been
subscribed to :-)

mpl...@li...
-- 
James R. Leu

Re: [mpls-linux-general] Re: [MPLS-Linux] measurement help

[Mudra P. <mpl...@ne...>]

Idézet "James R. Leu" <jl...@mi...>:

> On Thu, Nov 30, 2000 at 06:29:35PM +0100, Mudra Peter wrote:
> > Hi!
> > 
> 
> > The other thing: how to measure the throughput? How can i observe,
> > when mpls labeled packet go trough the network?
> 
> I'm not sure what you mean.  Do you want to see the label stack?
> Right now, I do it by hand, by using tcpdump.  Maybe ethereal
> has support for it now.
> 
> 
> Jim
> -- 
> James R. Leu
> _______________________________________________
> mpls-linux-general mailing list
> mpl...@li...
> http://lists.sourceforge.net/mailman/listinfo/mpls-linux-general
> 
> 
Hi!

I looked at the new mpls-linux version, and i see that it has more docs
than the previous versions. But i still don't know how to compare
IP best effort services to mpls services.

The point is: why or why not is mpls better/worse than IP best effort?
For this, some measurement tips would be appreciated...

Thanks in advance

Peter


---------------------------------------------------------------------
http://www.netposta.net NetPosta, E-m@il ingyen!

[mpls-linux-general] Bugs - follow up

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

I just realized that I had to setup the bug tracking
system.  I think I have it done now.  Go ahead and start
filing those bugs ....

Jim
-- 
James R. Leu

[mpls-linux-general] Re: [MPLS-Linux] measurement help

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

Hello,

(I'm also reply to the new mpls-linux-general list at sourceforge,
you should have been added, please use this list in the future)

On Thu, Nov 30, 2000 at 06:29:35PM +0100, Mudra Peter wrote:
> Hi!
> 
> I'd like to compare the mpls implementation to the "normal" best effort
> parameters. So the question is, how to measure for example the mpls
> set up time? I mean, is there a way to observe when routers
> agree about label mappings, FEC? Or am i rigth, that this is done
> when running mplsadm?

mplsadm is just a comand line utility that gives access to the
MPLS forwarding plane API.  This API would be used by LDP
or RSVP-TE (if someone chooses to implement it, hint hint)
If you want to manually setup LSPs this is the tool to use.
If you want to dynamically setup LSPs use LDP.

> The other thing: how to measure the throughput? How can i observe,
> when mpls labeled packet go trough the network?

I'm not sure what you mean.  Do you want to see the label stack?
Right now, I do it by hand, by using tcpdump.  Maybe ethereal
has support for it now.

> What is the curent configuration?
> Ex: mpls-linux0.601 + lilnux-2.4.0-test10 + ldp-portable0.060.
> Do they work together, or should i use other versions?

I would change it to mpls-linux-0.700 linux-2.4.0-test11 and the soon
to be release ldp-portable0.065 :-)

When you say "work" what do you mean? ;-)

> And what can i do when compiling the ldp_linux? How to run it ?

There is a small amount of help.  Run ldp_linux as root (hit enter
and then type ? and hit enter)

I just realize that the README for ldp_linux doesn't contain any info
how to run it.  I will write up a README and add it to ldp-portable-0.065.

For now:

Start up ldp_linux:

./ldp_linux

Add a global object:

prompt> add global 172.16.0.1

Add an interface:

prompt> add interface eth1

Show the database of sent/received labels:

prompt> show database

Show the list of established sessions:

prompt> show session

Show the list of discovered adjacencies:

prompt> show adj

That should get you started.  I will write a more complete doc.

Jim
-- 
James R. Leu

[mpls-linux-general] Bugs?

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

I know there are lots of bugs creeping up with the new features (maybe even
with long standing features).  I would like people to start creating
bug reports via the sourceforge bug tracker.  I haven't played with it much,
but I think it will help me (and others) know what needs work.

Head over to:

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

Click on "Bugs" near the top.

The people I remember having verified bugs are:
-Olivier Dugeon - ATM related
-Jordan "dancho" - MPLS tunnel related

Ofcourse if I've forgotten any ... 
well this i what we're trying to prevent :-)

Thanks,
Jim
-- 
James R. Leu

[mpls-linux-general] Re: [MPLS-Linux] Bug in mpls tunnels???

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

> Well, the problem is my linux crash/reboot  as I already  noticed after:
> 
> 'mplsadm -A -T mpls0', but that maybe is my error. I'll  try to test it
> again.

Let me know what your seeing and maybe we can fix it.

> > I would like to see it.  I used the IP in IP tunnel as my example.
> > Maybe a mix of the two will be exactly what we need.
> >
> 
> Ok, I'll send it, although it is not fully finished yet.
> I think the abstraction used in shaper is more useful, because
> it can be attached to every  real interface and doesn't require
> separate  IP address.

Great.  I'll take a look at what you've attached.

> P.S.
> I have one additional question/proposal. What do You think about idea
> to be made a mpls for some stable version of kernel, 2.2.[16-17],
> because new kernel 2.4-[xxx]-test  aren't  very useful
> in production environment?

It is a valid request.  I'm not sure what will have to change, probably not
much.  I'll give it a try.

Jim
-- 
James R. Leu

[mpls-linux-general] Re: [MPLS-Linux] Bug in mpls tunnels???

[dancho <da...@mb...>]

"James R. Leu" wrote:

> > I've nowhere seen where You apply the IP address of the interface
> > or attach it to any  real interface, is that right?
>
> Did you use ifconfig to add one?  here is what I do:
>
> mplsadm -A -T mpls0
> mplsadm -A -O gen:1024:eth1:ipv4:192.168.0.2
> mplsadm -B -O gen:1024:eth1 -T mpls0
> ifconfig mpls0 172.16.1.1 netmask 255.255.255.255
>
> The IP address si use is one that is already associated with the box.
> I use the managment address (LSRID).
>

Well, the problem is my linux crash/reboot  as I already  noticed after:

'mplsadm -A -T mpls0', but that maybe is my error. I'll  try to test it
again.


> > P.S.
> > I made one implementation of mpls tunnels using 'shaper' driver as
> > skeleton and it work for me.
>
> I would like to see it.  I used the IP in IP tunnel as my example.
> Maybe a mix of the two will be exactly what we need.
>

Ok, I'll send it, although it is not fully finished yet.
I think the abstraction used in shaper is more useful, because
it can be attached to every  real interface and doesn't require
separate  IP address.

Best Regards,
Jordan.

P.S.
I have one additional question/proposal. What do You think about idea
to be made a mpls for some stable version of kernel, 2.2.[16-17],
because new kernel 2.4-[xxx]-test  aren't  very useful
in production environment?

[mpls-linux-general] Initial CVS check-ins

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

I have checked in the inital dump of all of my code base into CVS.

If you want to keep up with all of the changes in between releases, I suggest
you introduce your self to Sourceforges CVS system.

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

Follow the lin the bottom about the CVS Repository.  It will
provide you with info how to use it.

Here are the "modules" I have created:

iproute2		-version of the standard iproute tools which is being
			 adapted to configure MPLS forwarding
ldp-portable		-the ldp-portable package
linux			-a full linux kernel with the MPLS patch applied
mpls-linux		-the mpls-linux package
zebra			-version of zerbra routing package which is being
			 modified to include LDP

NOTES:
-ldp-portable right now has changes that have note been test yet :-)
-linux and iproute2 have changes which have not yet been tested
-zebra is un-modified (directly from the zebra tar file)

Have fun :-)

Jim
-- 
James R. Leu

Re: [mpls-linux-general] Re: [MPLS-Linux] Bug in mpls tunnels???

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

> I've nowhere seen where You apply the IP address of the interface
> or attach it to any  real interface, is that right?

Did you use ifconfig to add one?  here is what I do:

mplsadm -A -T mpls0
mplsadm -A -O gen:1024:eth1:ipv4:192.168.0.2
mplsadm -B -O gen:1024:eth1 -T mpls0
ifconfig mpls0 172.16.1.1 netmask 255.255.255.255

The IP address si use is one that is already associated with the box.
I use the managment address (LSRID).

> P.S.
> I made one implementation of mpls tunnels using 'shaper' driver as
> skeleton and it work for me.

I would like to see it.  I used the IP in IP tunnel as my example.
Maybe a mix of the two will be exactly what we need.

Jim
-- 
James R. Leu

Re: [mpls-linux-general] Re: [MPLS-Linux] RSVP-TE (was: New mailing list)

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

On Fri, Dec 01, 2000 at 10:11:49AM +0530, Ramanjaneyulu Y T wrote:
<snip>
> > Are you refering to using RSVP-TE to create hierarchy, or are you refering
> > to how hierarchy works in general.
> 
> I am referring to create hierarcht.
>
> > 
> > If your refering to using RSVP-TE to create hierarchy, are you confused
> > about how to signal it or how (after it has been signaled) the ILM, NHLFE
> > are setup to actually do hierarchy?
> 
> 
> If I  remember right , hierarchy is achieved with help of PUSH and FWD
> operations in ILM and NHLFE . 
> 
>  Last night i refered some drafts and RSVP-TE supports Label stacks in
> LABEL object . My queastion is how LSR knows , how many labels pop ( i.e
> take off from) from LABEL object. Let me explain my probelm clealry.

When a LSR receives a labeled packet it extracts the label, bottotm of
stack bit, ttl, and EXP bits from the first shim.  It uses the label to
lookup in the ILM table associated with this interface.  The resulting ILM
entry contains an instruction of what to do.  If the operation is POP the
LSR POPs the top shim.  If the bottom of stack bit was set then the LSR looks
to the L3 PID stored in the ILM entry.  The ttl is coppied to the L3 header
and the packet is sent to the L3 protocol for porcessing.  If the bottom
of stack bit was not set, then the label, the bottom os stack bit, ttl and
EXP bits are exatrct from the next shim.  The process repeats until either
the bottom of stack bit is reached or an ILM entry with an intruction of
FWD is found.

>    LER1             LER21        LER22 ....   LER 2
>   |-----|          |-----| . .  | ----|       |-----|  
>   |     |----------|     |------|     |-------|     | 
>   |-----|          |-----|      |-----|       |-----|
> 
> 
> 
> 
> 
>        LER21 and LER22 is one MPLS domain. Suppose LER1 want to
> establish LSP to LER2. If one allows Hierarchy setting , it should make
> use of LSP between LER21 and LER22. when LER2 responded with RESV message, 
> How this RESV message is treated in MPLS domain ( beteen LSR21 and LER22)
> ?. IN normal case each LSR gets one new label for previous hop and it
> binds this with next hop label , which he got from next hop. , then it
> propagets to previous hop.
> 
>   If we r setting hierarchial lSPs , only resource reseravtion done at
> each LSR when RESV messagae comes. No label storing abd getting new label
> at each core LSRs in MPLS domain 1 , except at edge routers. So how core
> LSrs will ignore to store label info ? .

I'm a little unclear as to what you question is.  I'll give it my best shot:

      |------------EDGE TO EGDE Tunneled LSP ---------|

   ------                                           ------
  |      |                                         |      |
  |  PE  |                                         |  PE  |
  |  1   |---.  -----                   -----  .---|  2   |
   ------     \|     |                 |     |/     ------
               |  P  |-- . . . . . . --|  P  |
               |  1  |                 |  2  |
                -----                   -----

                  |----- CORE TE LSP -----|


In the above picture the core of the network is traffic engineered with RSVP-TE
with signalling starting at the P routers.  The ER HOP lists are made up of
the LSRIDs of each LSR the LSPs should traverse.

The Edge to Egde LSPs could be setup with many protocols.  So far I have
only seen providers design networks that would use LDP to build the edge to
egde LSPs.  You asked about RSVP-TE I'm 100% sure, but I know the basic
idea.

RSVP-TE signalling is initiated at the PE routes.  The ER HOP lists are
composed of LSRIDs until it reaches the core of the network, and is supposed
to tunnel inside of an existing LSP.  At which point the ER HOP is the IP
address associated with forwarding adjacency (term defined in
draft-kompella-mpls-bundle). After thet the ER HOP list is again composed
of LSRIDs.

When RSVP-TE receives a PATH message that has a top ER HOP which is associated
with a forwarding adjacency it is supposed to send the PATH message directly
to the remote LSR associated with the forwarding adjacency via normal unicast
routing. (I do not know all of the details of how that works or how the new
LSR knows that this incoming PATH message is assocaited with an FA-LSP).  When
it comes time for the RESV message, the remote LSR allocates a label and sends
it directly to this LSR via normal unicast routing.  This LSR know that the
RESV is associated with a forwarding adjacency (which is associated with an LSP)
and installes the outgoing label with the instruction to PUSH the new label
then PUSH on the label of the FA-LSP.

I hope I didn't get it too wrong :-)

Jim
-- 
James R. Leu

Re: [mpls-linux-general] Re: [MPLS-Linux] mpls-linux-0.700 : ATM tests & bugs

[Olivier D. <Oli...@rd...>]

"James R. Leu" wrote:
> 
> On Thu, Nov 30, 2000 at 12:50:54PM +0100, Olivier Dugeon wrote:
> > Hi all,
> >
> > I just finish some test with mpls-0.700 over ATM.
> >
> > 1/ The code doesn't work like 0.601 for the FORE 200E atm card. You can
> > establish connection but when you try to send data (ie. ping) the kernel
> > crash :-(( with :
> >
> > Nov 30 11:21:20 lat4272 kernel: Unable to handle kernel paging request
> > at virtual address 00000084
> 
> Do you get an EIP?  Send me the output if you have it, it might be in your
> log file /var/log/message
> 

Unfortunatly, NO. The kernel hang and panic before to have time to write
msg. into the /var/log/message file. On the screen i see once an eip
message, but the kernel message push it out the screen and i don't have
time to write it. What i mentioned previously is copy by hand from the
console output.

> > 2/ The code work with ENI ATM card, even though i notice some bug.
> >
> > - When i send ping, there is some info in the kern.log file about
> > unknown protocol :
> >
> > Nov 30 11:19:24 lat4272 kernel: mpls_output: unknown protocol(0400)
> > Nov 30 11:19:25 lat4272 kernel: mpls_output: unknown protocol(0608)
> > Nov 30 11:19:26 lat4272 kernel: mpls_output: unknown protocol(3781)
> > Nov 30 11:19:27 lat4272 kernel: mpls_output: unknown protocol(3781)
> > Nov 30 11:19:28 lat4272 kernel: mpls_output: unknown protocol(0608)
> 
> This has been an annoyance for sometime now.  The IP stack doesn't
> always set the SKB protocol before sending it on.  I need to find
> the common path in the IPv4 stack to set that, thus fixing the problem.
> 

Yes, not all the packet generate this error. For a ping there is around
60% of the packet with a bad SKB protocol.

> > - When i try to delete an incomming label it fail :
> >
> > # mplsadm -v -D -I atm:0/50:0
> > In label input: atm:0/50:0
> > Segmentation fault
> >
> > kern.log says :
> >
> > Nov 30 13:17:09 lat4271 kernel: mpls_del_in_label: enter
> > Nov 30 13:17:09 lat4271 kernel: __mpls_del_in_label: enter
> > Nov 30 13:17:09 lat4271 kernel: mpls_atm_push: enter
> > Nov 30 13:17:09 lat4271 kernel: Unable to handle kernel NULL pointer
> > dereference at virtual address 00000084
> > Nov 30 13:17:09 lat4271 kernel:  printing eip:
> > Nov 30 13:17:09 lat4271 kernel: c024073d
> > Nov 30 13:17:09 lat4271 kernel: *pde = 00000000
> > Nov 30 13:17:09 lat4271 kernel: Oops: 0000
> > Nov 30 13:17:09 lat4271 kernel: CPU:    0
> >
> > And the netlink socket is busy :
> 
> Very useful.  I will look into this one.  Could you very that it is
> reproducable?

Yes, each time i try to delete.
 
I not mentioned that after an eip message all the syslog output ie
/var/log/message, /var/log/kernel tty12 (i use Mandrake 7.1 which put
all the syslog message to tty12)
are completely freeze. A kill -UP to syslogd just send a message saying
that syslog restart but it's all. The next message is when you reboot
the system.

Hope you this help,

Olivier

-- 
 FTR&D/DAC/CPN
 Technopole Anticipa     | mailto:Oli...@fr...
 2, Avenue Pierre Marzin | Phone:  +(33) 2 96 05 28 80
 F-22307 LANNION         | Fax:    +(33) 2 96 05 18 52

Re: [mpls-linux-general] Re: [MPLS-Linux] RSVP-TE (was: New mailing list)

[Ramanjaneyulu Y T <yt...@cs...>]

On Thu, 30 Nov 2000, James R. Leu wrote:

> On Thu, Nov 30, 2000 at 10:52:30PM +0530, Ramanjaneyulu Y T wrote:
> > Hi James ,
> >   This is really good job. I appreciate your efforts. Are u doing any work
> > related to RSVP-TE ?.
> 
> Not as part of MPLS for Linux yet.  I have done some work with RSVP-TE 
> for my employeer.  Because of that fact I can't be the one to start working
> on RSVP-TE for Linux, but if some else "starts" it I'll make it part
> of MPLS for Linux ;-)
> 
> >   I have one queastion related to LSP hierarchy. How LSRs distinguish
> > label stack ?. How remote LSR knows it label from other side , if
> > hierarchy is permited ?. 
> 
> First, I guess we need to get a few things sorted out, before I can
> answer that question.
> 
> Are you refering to using RSVP-TE to create hierarchy, or are you refering
> to how hierarchy works in general.

I am referring to create hierarcht.


> 
> If your refering to using RSVP-TE to create hierarchy, are you confused
> about how to signal it or how (after it has been signaled) the ILM, NHLFE
> are setup to actually do hierarchy?


If I  remember right , hierarchy is achieved with help of PUSH and FWD
operations in ILM and NHLFE . 


 Last night i refered some drafts and RSVP-TE supports Label stacks in
LABEL object . My queastion is how LSR knows , how many labels pop ( i.e
take off from) from LABEL object. Let me explain my probelm clealry.

  

   LER1             LER21        LER22 ....   LER 2
  |-----|          |-----| . .  | ----|       |-----|  
  |     |----------|     |------|     |-------|     | 
  |-----|          |-----|      |-----|       |-----|





       LER21 and LER22 is one MPLS domain. Suppose LER1 want to
establish LSP to LER2. If one allows Hierarchy setting , it should make
use of LSP between LER21 and LER22. when LER2 responded with RESV message, 
How this RESV message is treated in MPLS domain ( beteen LSR21 and LER22)
?. IN normal case each LSR gets one new label for previous hop and it
binds this with next hop label , which he got from next hop. , then it
propagets to previous hop.

  If we r setting hierarchial lSPs , only resource reseravtion done at
each LSR when RESV messagae comes. No label storing abd getting new label
at each core LSRs in MPLS domain 1 , except at edge routers. So how core
LSrs will ignore to store label info ? .

  I think I am clear now.    





> 
> Sorry to answer you question with questions.
> 
> Jim
> 
> BTW "First post" :-)
> 

[mpls-linux-general] Re: [MPLS-Linux] mpls-linux-0.700 : ATM tests & bugs

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

On Thu, Nov 30, 2000 at 12:50:54PM +0100, Olivier Dugeon wrote:
> Hi all,
> 
> I just finish some test with mpls-0.700 over ATM.
> 
> 1/ The code doesn't work like 0.601 for the FORE 200E atm card. You can
> establish connection but when you try to send data (ie. ping) the kernel
> crash :-(( with :
> 
> Nov 30 11:21:20 lat4272 kernel: Unable to handle kernel paging request
> at virtual address 00000084

Do you get an EIP?  Send me the output if you have it, it might be in your
log file /var/log/message

> 2/ The code work with ENI ATM card, even though i notice some bug.
> 
> - When i send ping, there is some info in the kern.log file about
> unknown protocol :
> 
> Nov 30 11:19:24 lat4272 kernel: mpls_output: unknown protocol(0400) 
> Nov 30 11:19:25 lat4272 kernel: mpls_output: unknown protocol(0608) 
> Nov 30 11:19:26 lat4272 kernel: mpls_output: unknown protocol(3781) 
> Nov 30 11:19:27 lat4272 kernel: mpls_output: unknown protocol(3781) 
> Nov 30 11:19:28 lat4272 kernel: mpls_output: unknown protocol(0608) 

This has been an annoyance for sometime now.  The IP stack doesn't
always set the SKB protocol before sending it on.  I need to find
the common path in the IPv4 stack to set that, thus fixing the problem.

> - When i try to delete an incomming label it fail :
> 
> # mplsadm -v -D -I atm:0/50:0
> In label input: atm:0/50:0
> Segmentation fault
> 
> kern.log says :
> 
> Nov 30 13:17:09 lat4271 kernel: mpls_del_in_label: enter 
> Nov 30 13:17:09 lat4271 kernel: __mpls_del_in_label: enter 
> Nov 30 13:17:09 lat4271 kernel: mpls_atm_push: enter 
> Nov 30 13:17:09 lat4271 kernel: Unable to handle kernel NULL pointer
> dereference at virtual address 00000084 
> Nov 30 13:17:09 lat4271 kernel:  printing eip: 
> Nov 30 13:17:09 lat4271 kernel: c024073d 
> Nov 30 13:17:09 lat4271 kernel: *pde = 00000000 
> Nov 30 13:17:09 lat4271 kernel: Oops: 0000 
> Nov 30 13:17:09 lat4271 kernel: CPU:    0 
> 
> And the netlink socket is busy :

Very useful.  I will look into this one.  Could you very that it is
reproducable?

> # mplsadm -v -D -I atm:0/50:0
> rtnl_open: Address already in use
> Netlink: Address already in use
> 
> The incoming label is present both in /proc/net/atm/pvc and
> /proc/net/mpls_in but the LSP is no longer usable.
> 
> - cat /proc/net/atm/svc or cat /proc/net/atm/vc resulted in seg. fault.
> 
> I think there is some pb in the mpls_atm_push routine both for the ENI
> card for LSP deletion and for the FORE 200E card to send data.

I'm tending to agree.

This is a great bug report.  It has everything I need to rtry and tackle
it.  If you could look for the EIP from the FORE crash, I could try and tackle
that as well.

Thanks,
Jim


> Olivier
> 
> P.S. My test scenario and config
> 
> MPLS were compile with TUNNEL and INGRESS POLICY on. ATM card are in the
> kernel no module.
> 
>  ---------             ---------
>  | atm1  |             | atm2  |
>  ---------             ---------
>      |atm0                 |atm0
>      |.31                  |.32
>      +---------------------+
>          192.168.56.0/24
> 
> On atm1:
>   route add -host atm2 gw atm2
>   mplsadm -L atm0:0
>   mplsadm -A -I atm:0/40:0
>   mplsadm -A -B -O atm:0/50:atm0:ipv4:atm2 -f atm2/32
> 
> On B:
>   route add -host atm1 gw atm1
>   mplsadm -L atm0:0
>   mplsadm -A -I atm:0/50:0
>   mplsadm -A -B -O atm:0/40:atm0:ipv4:atm1 -f atm1/32
> 
> -- 
>  FTR&D/DAC/CPN
>  Technopole Anticipa     | mailto:Oli...@fr...
>  2, Avenue Pierre Marzin | Phone:  +(33) 2 96 05 28 80
>  F-22307 LANNION         | Fax:    +(33) 2 96 05 18 52
> 
> ---------------------------------------- 
> To unsubscribe, send mail to maj...@ne... with
> a subject of 'unsubscribe mpls-linux'  

-- 
James R. Leu

[mpls-linux-general] Re: [MPLS-Linux] Bug in mpls tunnels???

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

On Thu, Nov 30, 2000 at 03:00:47PM +0200, dancho wrote:
> Hello all,
> 
> I found bug? with tunnel in  mpls-0.700 or
> in other words tunnel doesn't work for me,
> it just lock my system.
> 
> It is happened after:
> mplsadm    -A -O gen:1024:eth0:ipv4:B
> mplsadm  -A -T mpls0
> and all the system is locked.

Could you try to do this with mplsadm -d turned on.  Also check your
kernel log (type 'dmesg' from the shell)

I haven't seen this yet, but it wouldn't suprise me :-)

Jim
-- 
James R. Leu

[mpls-linux-general] Re: [MPLS-Linux] RSVP-TE (was: New mailing list)

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

On Thu, Nov 30, 2000 at 10:52:30PM +0530, Ramanjaneyulu Y T wrote:
> Hi James ,
>   This is really good job. I appreciate your efforts. Are u doing any work
> related to RSVP-TE ?.

Not as part of MPLS for Linux yet.  I have done some work with RSVP-TE 
for my employeer.  Because of that fact I can't be the one to start working
on RSVP-TE for Linux, but if some else "starts" it I'll make it part
of MPLS for Linux ;-)

>   I have one queastion related to LSP hierarchy. How LSRs distinguish
> label stack ?. How remote LSR knows it label from other side , if
> hierarchy is permited ?. 

First, I guess we need to get a few things sorted out, before I can
answer that question.

Are you refering to using RSVP-TE to create hierarchy, or are you refering
to how hierarchy works in general.

If your refering to using RSVP-TE to create hierarchy, are you confused
about how to signal it or how (after it has been signaled) the ILM, NHLFE
are setup to actually do hierarchy?

Sorry to answer you question with questions.

Jim

BTW "First post" :-)
-- 
James R. Leu