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

Re: [mpls-linux-general] How do you want to use TC with MPLS?

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

Hi Steven,

Steven Van den Berghe wrote:

> Hi Jim,
> 
> First of all, the label/exp classification to a diffserv per hop behaviour must be
> done in every node (not only the ingress).
> Now, about our diffserv approach, what we currently (read as experimental) do is:
> 
> * ingress node
>     netfilter ==refence to label/exp==> mpls_output ==fixed label/exp mapping to
> tc_index ==> Queueing/scheduling
> (sorry Jim, we're bypassing all your hard work on getting the labels attached to
> routing entries and go direct from iptables classification to mpls_output)
> The "direct iptables"-approach  has only been written last week, and is currently
> under test.


Just a point of clarification. Do you bypass the ip stack at ingress or 
LSR node ? In the first case, how do you handle all the normal ip stuff 
ie. ip header checking/integrity, destination adresse checking and the 
fragmentation in case of the packet become to big after adding a label ?

We have envisage to bypass this part of ip stuff - going directly from 
iptable to mpls_output (in a similar way the iptable mirror function 
call directly ip_route_output_slow). We had let down this option because 
of all the ip stack stuff included the fragmentation.

Regards,

Olivier


> 
> *core node
>     mpls_input==> mpls_output ==fixed label/exp mapping to tc_index ==>
> Queueing/scheduling
> 
> The mapping from label/exp to tc_index is done in sch_dsmark (a pseudo scheduler
> that was originally used to set tc_index based on the dscp field in the
> IP-header).
> dsmark is however no requirement (you could use u32 classifiers, ....), but it
> allows to have a uniform diffserv configuration for a combination of mpls and
> 'normal' ip traffic.
> 
> Hope this helps,
> Steven
> 
> "James R. Leu" wrote:
> 
> 
>>Hello all,
>>
>>I'm working on testing some of the feature I've added recently, and I just
>>realized I have no idea how anyone would use them.  So I'm asking all of you
>>how do you want to use the features of TC with MPLS?  Are the feature provided
>>by iptables more apt for being used with MPLS?
>>
>>One way I know people want to use TC and MPLS is with respect to
>>DiffServ.   Using the DSCP to determine which LSP (L-LSP) or which EXP/LSP
>>(E-LSP) a packet should be sent with, then mapping the LSP or EXP/LSP
>>back to a DSCP at egress.  But what about the LSRs?  Don't they need to
>>do special queuing?  How does TC accomplish special queing without MPLS?
>>How should it work with MPLS?
>>
>>Thanks,
>>Jim
>>
>>PS Yes Olivier, I'm now starting to catch up with you, soon I'll understand why
>>your iptables work is so useful :-)
>>
>>PPS Please Steven respond and explain how you made your DiffServ stuff work
>>
>>--
>>James R. Leu
>>jl...@mi...
>>
>>_______________________________________________
>>mpls-linux-general mailing list
>>mpl...@li...
>>https://lists.sourceforge.net/lists/listinfo/mpls-linux-general
>>
> 
> --
> Steven Van den Berghe
> ste...@in...
> Workgroup Broadband Communication Networks
> Department Information Technology
> Ghent University - Belgium
> Phone:  +32 (0)9 267 35 86 | Fax  :  +32 (0)9 267 35 99
> *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
> DiffServ over MPLS for Linux: http://dsmpls.atlantis.rug.ac.be
> *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
> Application has reported a 'Not My Fault' in module
> KRNL.EXE in line 0200:103F
> 
> 
> *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
> 
> 
> 
> 
> _______________________________________________
> mpls-linux-general mailing list
> mpl...@li...
> https://lists.sourceforge.net/lists/listinfo/mpls-linux-general
> 
> 


-- 
  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] How do you want to use TC with MPLS?

[Steven V. d. B. <ste...@in...>]

Hi Olivier,

good point :) seems i overlooked that one. 

Actually i didn't have a good look at your patch before (until this
afternoon--CET) and only added the direct iptables approach last week,
without looking thoroughly at all the consequences (you know, the famous
way of testing it: 'it worked for ping so it'll work for everything').

Your patch would indeed be more adequate for the job.

i think however that it would be a great thing if we could bypass the
routing from netfilter, it would add mpls support in a way that is much
more isolated from the 'standard' kernel (i.e. just touches it at L2),
making it easier to follow the kernel developments. What are the exact
requirements, i assume fragmentation is the most important one (i also
assume destination checking and ip header integrity is done at the
egress, after popping the label).

Cheers,
Steven

PS: Jim, could you send a more detailed description of your current qos
approach? Might help to get some "usage examples" and corresponding
requirements from the list. 


On Wed, 2001-11-28 at 18:52, Olivier Dugeon wrote:
> Hi Steven,
> 
> Steven Van den Berghe wrote:
> 
> > Hi Jim,
> > 
> > First of all, the label/exp classification to a diffserv per hop behaviour must be
> > done in every node (not only the ingress).
> > Now, about our diffserv approach, what we currently (read as experimental) do is:
> > 
> > * ingress node
> >     netfilter ==refence to label/exp==> mpls_output ==fixed label/exp mapping to
> > tc_index ==> Queueing/scheduling
> > (sorry Jim, we're bypassing all your hard work on getting the labels attached to
> > routing entries and go direct from iptables classification to mpls_output)
> > The "direct iptables"-approach  has only been written last week, and is currently
> > under test.
> 
> 
> Just a point of clarification. Do you bypass the ip stack at ingress or 
> LSR node ? In the first case, how do you handle all the normal ip stuff 
> ie. ip header checking/integrity, destination adresse checking and the 
> fragmentation in case of the packet become to big after adding a label ?
> 
> We have envisage to bypass this part of ip stuff - going directly from 
> iptable to mpls_output (in a similar way the iptable mirror function 
> call directly ip_route_output_slow). We had let down this option because 
> of all the ip stack stuff included the fragmentation.
> 
> Regards,
> 
> Olivier
> 
> 
> > 
> > *core node
> >     mpls_input==> mpls_output ==fixed label/exp mapping to tc_index ==>
> > Queueing/scheduling
> > 
> > The mapping from label/exp to tc_index is done in sch_dsmark (a pseudo scheduler
> > that was originally used to set tc_index based on the dscp field in the
> > IP-header).
> > dsmark is however no requirement (you could use u32 classifiers, ....), but it
> > allows to have a uniform diffserv configuration for a combination of mpls and
> > 'normal' ip traffic.
> > 
> > Hope this helps,
> > Steven
> > 
> > "James R. Leu" wrote:
> > 
> > 
> >>Hello all,
> >>
> >>I'm working on testing some of the feature I've added recently, and I just
> >>realized I have no idea how anyone would use them.  So I'm asking all of you
> >>how do you want to use the features of TC with MPLS?  Are the feature provided
> >>by iptables more apt for being used with MPLS?
> >>
> >>One way I know people want to use TC and MPLS is with respect to
> >>DiffServ.   Using the DSCP to determine which LSP (L-LSP) or which EXP/LSP
> >>(E-LSP) a packet should be sent with, then mapping the LSP or EXP/LSP
> >>back to a DSCP at egress.  But what about the LSRs?  Don't they need to
> >>do special queuing?  How does TC accomplish special queing without MPLS?
> >>How should it work with MPLS?
> >>
> >>Thanks,
> >>Jim
> >>
> >>PS Yes Olivier, I'm now starting to catch up with you, soon I'll understand why
> >>your iptables work is so useful :-)
> >>
> >>PPS Please Steven respond and explain how you made your DiffServ stuff work
> >>
> >>--
> >>James R. Leu
> >>jl...@mi...
> >>
> >>_______________________________________________
> >>mpls-linux-general mailing list
> >>mpl...@li...
> >>https://lists.sourceforge.net/lists/listinfo/mpls-linux-general
> >>
> > 
> > --
> > Steven Van den Berghe
> > ste...@in...
> > Workgroup Broadband Communication Networks
> > Department Information Technology
> > Ghent University - Belgium
> > Phone:  +32 (0)9 267 35 86 | Fax  :  +32 (0)9 267 35 99
> > *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
> > DiffServ over MPLS for Linux: http://dsmpls.atlantis.rug.ac.be
> > *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
> > Application has reported a 'Not My Fault' in module
> > KRNL.EXE in line 0200:103F
> > 
> > 
> > *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
> > 
> > 
> > 
> > 
> > _______________________________________________
> > mpls-linux-general mailing list
> > mpl...@li...
> > https://lists.sourceforge.net/lists/listinfo/mpls-linux-general
> > 
> > 
> 
> 
> -- 
>   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
> 
> 
-- 
--
Steven Van den Berghe
ste...@in...
Workgroup Broadband Communication Networks
Department Information Technology
Ghent University - Belgium
Phone:  +32 (0)9 267 35 86 | Fax  :  +32 (0)9 267 35 99
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
DiffServ over MPLS for Linux: http://dsmpls.atlantis.rug.ac.be
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
A computer is like an Old Testament god, with a lot of
rules and no mercy. - Joseph Campbell
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*

Re: [mpls-linux-general] How do you want to use TC with MPLS?

[Steven V. d. B. <ste...@in...>]

Hi Jim,

First of all, the label/exp classification to a diffserv per hop behaviour must be
done in every node (not only the ingress).
Now, about our diffserv approach, what we currently (read as experimental) do is:

* ingress node
    netfilter ==refence to label/exp==> mpls_output ==fixed label/exp mapping to
tc_index ==> Queueing/scheduling
(sorry Jim, we're bypassing all your hard work on getting the labels attached to
routing entries and go direct from iptables classification to mpls_output)
The "direct iptables"-approach  has only been written last week, and is currently
under test.

*core node
    mpls_input==> mpls_output ==fixed label/exp mapping to tc_index ==>
Queueing/scheduling

The mapping from label/exp to tc_index is done in sch_dsmark (a pseudo scheduler
that was originally used to set tc_index based on the dscp field in the
IP-header).
dsmark is however no requirement (you could use u32 classifiers, ....), but it
allows to have a uniform diffserv configuration for a combination of mpls and
'normal' ip traffic.

Hope this helps,
Steven

"James R. Leu" wrote:

> Hello all,
>
> I'm working on testing some of the feature I've added recently, and I just
> realized I have no idea how anyone would use them.  So I'm asking all of you
> how do you want to use the features of TC with MPLS?  Are the feature provided
> by iptables more apt for being used with MPLS?
>
> One way I know people want to use TC and MPLS is with respect to
> DiffServ.   Using the DSCP to determine which LSP (L-LSP) or which EXP/LSP
> (E-LSP) a packet should be sent with, then mapping the LSP or EXP/LSP
> back to a DSCP at egress.  But what about the LSRs?  Don't they need to
> do special queuing?  How does TC accomplish special queing without MPLS?
> How should it work with MPLS?
>
> Thanks,
> Jim
>
> PS Yes Olivier, I'm now starting to catch up with you, soon I'll understand why
> your iptables work is so useful :-)
>
> PPS Please Steven respond and explain how you made your DiffServ stuff work
>
> --
> James R. Leu
> jl...@mi...
>
> _______________________________________________
> mpls-linux-general mailing list
> mpl...@li...
> https://lists.sourceforge.net/lists/listinfo/mpls-linux-general

--
Steven Van den Berghe
ste...@in...
Workgroup Broadband Communication Networks
Department Information Technology
Ghent University - Belgium
Phone:  +32 (0)9 267 35 86 | Fax  :  +32 (0)9 267 35 99
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
DiffServ over MPLS for Linux: http://dsmpls.atlantis.rug.ac.be
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
Application has reported a 'Not My Fault' in module
KRNL.EXE in line 0200:103F


*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*

Re: [mpls-linux-general] How do you want to use TC with MPLS?

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

Hi Jim,

James R. Leu wrote:

> Hello all,
> 
> I'm working on testing some of the feature I've added recently, and I just
> realized I have no idea how anyone would use them.  So I'm asking all of you
> how do you want to use the features of TC with MPLS?  Are the feature provided
> by iptables more apt for being used with MPLS?
> 
> One way I know people want to use TC and MPLS is with respect to
> DiffServ.   Using the DSCP to determine which LSP (L-LSP) or which EXP/LSP
> (E-LSP) a packet should be sent with, then mapping the LSP or EXP/LSP
> back to a DSCP at egress.  But what about the LSRs?  Don't they need to
> do special queuing?  How does TC accomplish special queing without MPLS?
> How should it work with MPLS?
> 


We intend (and start some advanced test in a couple of week) to use MPLS 
+ TC for providing QoS support under MPLS not only DiffServ. So, we want 
to setup an LSP for a specific flow (using iptable for classification) 
and then affect a certian QoS to this flow (using TC). The next step is 
to manage all the LSP with a per-LSP queuing (using WFQ for example).

I'have allready completed a new version of our iptable+tc patch for LSR 
handle but, not yet tested (I'm waiting for new material to increase our 
test network). The two main improvment of this patch is :

- Modify tc mpls filter to hanlde both mpls_index (when setting 
CONFIG_MPLS_INGRESS_POLICING in the kernel config) and directly the 
packet label (when CONFIG_MPLS_INGRESS_POLICING is not set).

- Compute skbuff->mpls_index value with outgoing label for all incoming 
mpls packet inside an LSR node. (not sure where to put this patch)

With this two improvments, LSR can use TC to provide some per-LSP QoS. 
Iptable is not need because packet are allready labelled.

Starting to this, i thing implement CR-LDP and RSVP-TE with true Bandwidth

allocation is simplier. All the traffic management is handle by the kernel.



> Thanks,
> Jim
> 
> PS Yes Olivier, I'm now starting to catch up with you, soon I'll understand why
> your iptables work is so useful :-)


Thank's


> 


> PPS Please Steven respond and explain how you made your DiffServ stuff work
> 
> 

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

[mpls-linux-general] How do you want to use TC with MPLS?

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

Hello all,

I'm working on testing some of the feature I've added recently, and I just
realized I have no idea how anyone would use them.  So I'm asking all of you
how do you want to use the features of TC with MPLS?  Are the feature provided
by iptables more apt for being used with MPLS?

One way I know people want to use TC and MPLS is with respect to
DiffServ.   Using the DSCP to determine which LSP (L-LSP) or which EXP/LSP
(E-LSP) a packet should be sent with, then mapping the LSP or EXP/LSP
back to a DSCP at egress.  But what about the LSRs?  Don't they need to
do special queuing?  How does TC accomplish special queing without MPLS?
How should it work with MPLS?

Thanks,
Jim

PS Yes Olivier, I'm now starting to catch up with you, soon I'll understand why
your iptables work is so useful :-)

PPS Please Steven respond and explain how you made your DiffServ stuff work

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

[mpls-linux-general] CR-LDP

[Mrugendra S. <mru...@ya...>]

Hi All,

I was wondering if any one has tested Downstream on   
 Demand Ordered Control on the current LDP code of    
James.

Is there any way in current code to support the    
requirement of CR-LDP i.e. to have DoD Ordered Control
 to be infered from existance of any TLV defined in   
 CR-LDP. Since the present code fixes the control and 
  distribution at startup.

If anybody can help about how we can map Label request
Procedure defined in LDP Spec & CR-LDP section 3 to
present LDP code.

Also James if you could pls briefly write about
mpls-linux 1.1

Regards
Mrugendra


--- "James R. Leu" <jl...@mi...> wrote:
> I will be posting mpls-linux-1.1.tar.gz soon, which
> has a lot of
> integration for E-LSPs L-LSP and hooks to DSCP.
> 
> I hope to post more about this tomorrow morning.
> 
> Jim
> 
> On Tue, Nov 20, 2001 at 06:12:04PM -0800, Mrugendra
> Singhai wrote:
> > Hi All,
> > 
> > This is regarding implementing "MPLS support of
> > Diffserv" in current LDP code of James. 
> > 
> > I did go through the extension implemented by
> people
> > at Intec. Last I saw, it had E-LSP support using
> RSVP.
> > And the way they implemented it was by having
> changing
> > the mpls label and by changing the key to store
> label
> > to include the exp as well.
> > 
> > But this approach does not supports L-LSP. Also I
> > could not figure out how and where they were
> handling
> > the Diffserv context associated with the LSP.
> > 
> > What I was interested in knowing was
> > 
> > 1) Will it not be a better idea to store the
> entire
> > diffserv context associated with a LSP in one
> in_info
> > entry in radix tree.
> > 
> > Any other suggestions on how exactly to implement
> EXP
> > support is deeply appreciated.
> > 
> > Regards
> > Mrugendra
> > 
> > 
> > __________________________________________________
> > Do You Yahoo!?
> > Yahoo! GeoCities - quick and easy web site
> hosting, just $8.95/month.
> > http://geocities.yahoo.com/ps/info1
> > 
> > _______________________________________________
> > mpls-linux-general mailing list
> > mpl...@li...
> >
>
https://lists.sourceforge.net/lists/listinfo/mpls-linux-general
> 
> -- 
> James R. Leu


__________________________________________________
Do You Yahoo!?
Yahoo! GeoCities - quick and easy web site hosting, just $8.95/month.
http://geocities.yahoo.com/ps/info1

Re: [mpls-linux-general] Zebra-port and Linux-port

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

On Tue, Nov 27, 2001 at 06:10:02PM +0100, Kauder Thorsten wrote:
> Hi everyone,
> I still didn't make it to compile the Zebra port.
> While trying to figure out the problem I wondered what the difference
> between the two ports might be anyway.
> 
> So here comes the question:
> What exactly are these Ports.

The linux port uses linux system services to get info about routes/interfaces.
It uses its own socket and timer managment functions, the cli is custom
as well.  The zebra port tries to take advantage of as much of the zebra
achitecture as possible.

> I tried to work with the Linux-port while distributing routes with zebra.
> I don't understand how they could differ, because as far as I understand it 
> zebra works with the Kernel routing table as well and ldp shouldn't need 
> anything else.

Right now route notification are not being proccessed correctly by the linux
port.

> 
> Here's what happens:
> after I define global objects on two machines ( LSR-ID 1 and 2) and add the 
> interfaces on both mashines ( add interface eth0 ) they establish a session.
> The machine I generated the routes on in the first place adds incomin labels in
> /proc/net/mpls-in but removes the labelspacebinding to eth0. On the other machine 
> nothing happens in the /proc/net/*
> 
> With ethereal I found out that they are exchanging mappings and wants.
> What surprises me the most is, that in the mpls-in file every line starts with
> a fec put there aren't any entries in mpls-fec.
> 
> I think that I need to get the ldp_zebra compiled....
> If anyone did manage to do that. please let me know against wich version of zebra.
> 
> Thanks for taking the time reading that.
> I would really appreciate it if anyone could help me

As soon as I get done releaseing mpls-linxu 1.106 I'll spend sometime on
ldp-portable.

Jim

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

[mpls-linux-general] Disconnected ...

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

My main development machine went belly up on me over the holiday weekend.
If you sent me any mail that you actually want a response to :-) resend
it.

Oh BTW mpls-linux 0.996 (aka 1.0) has been posted on source forge.
1.106 (aka TC enhanced) will be posted soon.

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

[mpls-linux-general] Zebra-port and Linux-port

[Kauder T. <Tho...@ic...>]

Hi everyone,
I still didn't make it to compile the Zebra port.
While trying to figure out the problem I wondered what the difference
between the two ports might be anyway.

So here comes the question:
What exactly are these Ports.

I tried to work with the Linux-port while distributing routes with zebra.
I don't understand how they could differ, because as far as I understand it 
zebra works with the Kernel routing table as well and ldp shouldn't need 
anything else.

Here's what happens:
after I define global objects on two machines ( LSR-ID 1 and 2) and add the 
interfaces on both mashines ( add interface eth0 ) they establish a session.
The machine I generated the routes on in the first place adds incomin labels in
/proc/net/mpls-in but removes the labelspacebinding to eth0. On the other machine 
nothing happens in the /proc/net/*

With ethereal I found out that they are exchanging mappings and wants.
What surprises me the most is, that in the mpls-in file every line starts with
a fec put there aren't any entries in mpls-fec.

I think that I need to get the ldp_zebra compiled....
If anyone did manage to do that. please let me know against wich version of zebra.

Thanks for taking the time reading that.
I would really appreciate it if anyone could help me

Thorsten

[mpls-linux-general] LDP-Diffserv & CR-LDP

[Mrugendra S. <mru...@ya...>]

Hi James,

I am still waiting :-) for your mail about how have
you/or planning to implement Diffserv support in
mpls-linux.

If I could have some idea about mpls-linux with
diffserv then i can start coding LDP for diffserv
TLV's.

Also please if you could write some thing about my
CR-LDP mail. I am specifically interested in having
atleast the support of traffic TLV in existing code
somehow.

This will help demonstrate BW reservation and QoS
aspects of mpls traffic engg.

Regards
Mrugendra Singhai

--- "James R. Leu" <jl...@mi...> wrote:
> I will be posting mpls-linux-1.1.tar.gz soon, which
> has a lot of
> integration for E-LSPs L-LSP and hooks to DSCP.
> 
> I hope to post more about this tomorrow morning.
> 
> Jim
> 
> On Tue, Nov 20, 2001 at 06:12:04PM -0800, Mrugendra
> Singhai wrote:
> > Hi All,
> > 
> > This is regarding implementing "MPLS support of
> > Diffserv" in current LDP code of James. 
> > 
> > I did go through the extension implemented by
> people
> > at Intec. Last I saw, it had E-LSP support using
> RSVP.
> > And the way they implemented it was by having
> changing
> > the mpls label and by changing the key to store
> label
> > to include the exp as well.
> > 
> > But this approach does not supports L-LSP. Also I
> > could not figure out how and where they were
> handling
> > the Diffserv context associated with the LSP.
> > 
> > What I was interested in knowing was
> > 
> > 1) Will it not be a better idea to store the
> entire
> > diffserv context associated with a LSP in one
> in_info
> > entry in radix tree.
> > 
> > Any other suggestions on how exactly to implement
> EXP
> > support is deeply appreciated.
> > 
> > Regards
> > Mrugendra
> > 
> > 
> > __________________________________________________
> > Do You Yahoo!?
> > Yahoo! GeoCities - quick and easy web site
> hosting, just $8.95/month.
> > http://geocities.yahoo.com/ps/info1
> > 
> > _______________________________________________
> > mpls-linux-general mailing list
> > mpl...@li...
> >
>
https://lists.sourceforge.net/lists/listinfo/mpls-linux-general
> 
> -- 
> James R. Leu


__________________________________________________
Do You Yahoo!?
Yahoo! GeoCities - quick and easy web site hosting, just $8.95/month.
http://geocities.yahoo.com/ps/info1

[mpls-linux-general] Welcome to linuxmpls

[linuxmpls M. <lin...@ya...>]

Hello,

Welcome to the linuxmpls group at Yahoo! Groups, a 
free, easy-to-use email group service. Please 
take a moment to review this message.

To learn more about the linuxmpls group, please visit
http://groups.yahoo.com/group/linuxmpls

To start sending messages to members of this group, simply 
send email to
lin...@ya...

If you do not wish to belong to linuxmpls, you may 
unsubscribe by sending an email to 
lin...@ya...

To see and modify all of your groups, go to
http://groups.yahoo.com/mygroups


Regards,

Moderator, linuxmpls

 


Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/ 

 

[mpls-linux-general] Invitation to join the linuxmpls group

[linuxmpls m. <lin...@ya...>]

Hello,

You've been invited to join the linuxmpls group,
an email group hosted by Yahoo! Groups, a free, easy-to-use email group
service.

JOIN NOW, IT'S EASY: 

1) REPLY to this email by clicking "Reply" and then "Send"
in your email program

-OR-

2) Go to the Yahoo! Groups site at
   http://groups.yahoo.com/invite/linuxmpls?email=mpls-linux-general%40lists%2Esourceforge%2Enet&iref=M3poHKpkRADhltY4SPRWgFdmy_8
By joining linuxmpls, you will be able to exchange messages
with other group members. Yahoo! Groups also makes it easy to store
photos and files, coordinate events and more.

Here's an introductory message from the group moderator:
------------------------------------------------------------------------

Hello,

Welcome to the linuxmpls group at Yahoo! Groups, a 
free, easy-to-use email group service. Please 
take a moment to review this message.

To learn more about the linuxmpls group, please visit
http://groups.yahoo.com/group/linuxmpls

To start sending messages to members of this group, simply 
send email to
lin...@ya...

If you do not wish to belong to linuxmpls, you may 
unsubscribe by sending an email to 
lin...@ya...

To see and modify all of your groups, go to
http://groups.yahoo.com/mygroups


Regards,

Moderator, linuxmpls

 

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


If you do not wish to join the linuxmpls group, please
ignore this invitation.

SPECIAL NOTE FROM Yahoo! Groups:  Because Yahoo! Groups values your privacy,
it is a violation of our service rules for moderators to abuse this 
invitation feature. If you feel this has happened, please notify us
at ab...@ya... 

Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
 

[mpls-linux-general] Netlink....

[Mrugendra S. <mru...@ya...>]

Hi Hanxi,

please refer to this link. it has got a brief howto
about netlink sockets.

http://qos.ittc.ukans.edu/netlink/netlink.pdf

hth
Mrugendra



__________________________________________________
Do You Yahoo!?
Yahoo! GeoCities - quick and easy web site hosting, just $8.95/month.
http://geocities.yahoo.com/ps/info1

[mpls-linux-general] Asking for materials on netlink socket programming

[Hanxi Z. <han...@cr...>]

Hi All:

Could any of you refer me to any good tutorials on netlink socket programming/
ioctl call that are used in mplsadm? I went through mplsadm.c and netlink.c,
but I don't totally understand how a AF_INET socket is related to a AF_NETLINK
socket.

Thanks a lot!



----------------------------------------------------------
Hanxi Zhang
Research Engineer
Broadband and Optical Networking
Communications Research Center

Tel: (613)991-2960 Fax: (613)990-8382
3701 Carling Ave, Ottawa, ON K2H 8S2
----------------------------------------------------------

Re: [mpls-linux-general] I need some help to read the codes related with MPLS patches

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

Hi,

Look at document joint. It's an update of the packet journey inside the
kernel for MPLS.

Hope you this help.

Olivier

=C1=A4=B1=E2=BF=B5 wrote:

>=20
> I've looked at the code, and i think that the binding point of=20
> mpls_output() is in route.c
>=20
> After patching mpls codes, in ./net/ipv4/route.c
>=20
> void rt_set_nexthop(struct rtable *rt, struct fib_result *res, u32 =
itag)
> {
>       struct fib_info *fi =3D res->fi;
> =20
> =A1=A6
> =20
> #ifdef CONFIG_MPLS
>       /* JLEU: we need to do this here because both
>       * ip_route_output_slow() and ip_route_output_slow()
>       * us this to finish the next hop calculations
>       */
>       if(res->proto_data[AUX_PROTO_DATA_MPLS]) {
>           struct mpls_out_info *moi;
>           int i;
> =20
>           MPLS_DEBUG(("rt_set_nexthop: adding label to dst\n"));
>           MPLS_DEBUG(("rt_set_nexthop: before - mtu =3D %d\n",
>             rt->u.dst.pmtu));
>           rt->u.dst.output =3D mpls_output; /* HERE */
>           rt->u.dst.dst_proto_data[AUX_PROTO_DATA_MPLS] =3D
>             res->proto_data[AUX_PROTO_DATA_MPLS];
>           moi =3D res->proto_data[AUX_PROTO_DATA_MPLS];
> mpls_again:
>           for(i=3D0;imoi_instruction_length;i++) {
>             switch(moi->moi_instruction[i].mi_opcode) {
>                 case MPLS_OP_FWD:
>                   moi =3D (struct mpls_out_info*)
>                     moi->moi_instruction[i].mi_data;
>                   goto mpls_again;
>                   break;
>                 case MPLS_OP_PUSH:
>                   rt->u.dst.pmtu -=3D 4;
>                   break;
>             }
>           }
>           MPLS_DEBUG(("rt_set_nexthop: after - mtu =3D %d\n",
>             rt->u.dst.pmtu));
>       }
> =20
> =A1=A6
> =20
> }
> =20
> If res->proto_data[AUX_PROTO_DATA_MPLS] have a value (not zero)
> then the output related function is binded with mpls_output()
> so the function is invoked.
> =20
> But I still try to find work that describes the structures or methods =
of=20
> MPLS in Linux .
> Is there anyone who know this? I hope to learn from him or her.
> =20
> Especially, I want to know the semantics of=20
> proto_data[AUX_PROTO_DATA_MPLS].
> =20
> Thanks, in advance.
> =20
> B.E.
> =20
> Kiyoung Jung
> -------------------------------------------------------
> Ki Young Jung (jj...@ic...)
> Information and Communications University(ICU)
> Broadband Network Laboratory(http://bnlab.icu.ac.kr)
> 58-4 Hwaam-dong, Yusong-gu, Taejon, 305-732, KOREA
> Tel)+82-42-866-6182, 016-370-1751 Fax)+82-42-866-6110
> -------------------------------------------------------
>=20
> *Your life on the net*
> <http://i.dreamwiz.com/dw/ko/n.gif>
> =
<http://ad.dreamwiz.com/BIN/adc_img.cgi?page=3Dwebdesk_ma_rt3_u&c=3Db>=20
> =
<http://ad.dreamwiz.com/BIN/jump.cgi?ad=3Ddwmail_1&page=3Dwebdesk_ma_rt3=
_u>
> <http://i.dreamwiz.com/dw/ko/n.gif>


--=20
 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] (no subject)

[Adithya S B. <ad...@sa...>]

Have you installed the lable space ?
mplsadm -v -L eth0:0
Regards,
-Adithya

ajit joshi wrote:

> Hi All
>
> ---------             ---------
> |   A   |             |   B   |
> ---------             ---------
>      |eth0                 |eth0
>      |17.130               |18.114
> -----------------------------------
>          128.104.16.0/22
>
> In my setup only Host A is MPLS enabled and B is normal Host.
> I run following command on host A
>    route add -host B gw B
>    mplsadm -A -B -O gen:16:eth0:ipv4:B -f B/32
>    mplsadm -A -I gen:17:0
>
> and nothing on host B.
>
> We have configured host A staticaly and not using LDP.A should think B is
> MPLS enabled , but actualy it is not. So A should send mpls packets to B. Is
> my guess correct?
>
> Thanks in advance
>
> Sahil
>
> _________________________________________________________________
> Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp
>
> _______________________________________________
> mpls-linux-general mailing list
> mpl...@li...
> https://lists.sourceforge.net/lists/listinfo/mpls-linux-general

--
Adithya S Bhat,
Software Engineer,
Sasken Communication Technologies Ltd.,
Bangalore,India.
Tel:080-5355501 ext:8251
http://www.sasken.com/

Re: [mpls-linux-general] (no subject)

[Aditya M T. <ad...@sa...>]

hi sahil,

yes, m/c A will send MPLS packets to B with label value 16.
btw, the 3rd command is superfluous.

regards,
aditya.

ajit joshi wrote:

> Hi All
> 
> ---------             ---------
> |   A   |             |   B   |
> ---------             ---------
>     |eth0                 |eth0
>     |17.130               |18.114
> -----------------------------------
>         128.104.16.0/22
> 
> In my setup only Host A is MPLS enabled and B is normal Host.
> I run following command on host A
>   route add -host B gw B
>   mplsadm -A -B -O gen:16:eth0:ipv4:B -f B/32
>   mplsadm -A -I gen:17:0
> 
> and nothing on host B.
> 
> We have configured host A staticaly and not using LDP.A should think B 
> is MPLS enabled , but actualy it is not. So A should send mpls packets 
> to B. Is my guess correct?
> 
> Thanks in advance
> 
> Sahil
> 
> _________________________________________________________________
> Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp
> 
> 
> _______________________________________________
> mpls-linux-general mailing list
> mpl...@li...
> https://lists.sourceforge.net/lists/listinfo/mpls-linux-general
> 


-- 
Aditya Thomas,
Software Engineer,
Sasken Communication Technologies Ltd.,
Bangalore,India.
Tel:080-5355501 ext:8249

You've always made the mistake of being yourself.
		-- Eugene Ionesco

[mpls-linux-general] (no subject)

[ajit j. <aji...@ho...>]

Hi All

---------             ---------
|   A   |             |   B   |
---------             ---------
     |eth0                 |eth0
     |17.130               |18.114
-----------------------------------
         128.104.16.0/22

In my setup only Host A is MPLS enabled and B is normal Host.
I run following command on host A
   route add -host B gw B
   mplsadm -A -B -O gen:16:eth0:ipv4:B -f B/32
   mplsadm -A -I gen:17:0

and nothing on host B.

We have configured host A staticaly and not using LDP.A should think B is 
MPLS enabled , but actualy it is not. So A should send mpls packets to B. Is 
my guess correct?

Thanks in advance

Sahil

_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp

[mpls-linux-general] CR-LDP Requirements...

[Mrugendra S. <mru...@ya...>]

Hi All,

I was wondering if any one has tested Downstream on
Demand Ordered Control on the current LDP code of
James.

Is there any way in current code to support the
requirement of CR-LDP i.e. to have DoD Ordered Control
to be infered from existance of any TLV defined in
CR-LDP. Since the present code fixes the control and
distribution at startup.

If anybody can help about how we can map Label request
Procedure defined in LDP Spec & CR-LDP section 3 to
our code.

Regards
Mrugendra

__________________________________________________
Do You Yahoo!?
Yahoo! GeoCities - quick and easy web site hosting, just $8.95/month.
http://geocities.yahoo.com/ps/info1

Re: Re: [mpls-linux-general] I need some help to read the codes related with MPLS patches

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

On Tue, Nov 20, 2001 at 03:03:17AM +0900, =C1=A4=B1=E2=BF=B5 wrote:
> Thanks for your comment, first.
> And thanks for you and other peoples that=20
> make the great job about the MPLS-Linux.

Thank you.

> Before I ask some questions, I must apology about
> my lack of English.  Actually I read the RFCs related=20
> with MPLS and LDP. But when I looked at the code, MPLS-Linux,=20
> I can't figure out the implementation of LIB tables such like
> ILM, NHLFE, FTN as descirbed in RFC 3031.
> I think that the problem I've been had is not just for
> my case. Ofcourse I read the codes.=20

ILM =3D incoming label info (mpls_in_info)
NHLFE =3D outgoing label info (mpls_out_info)
FTN =3D FIB entries -> outgoing label info (via proto_data)
LIB =3D all of the above :-)

> Anyway, I wonder the meaning of the res->proto_data[AUX_PROTO_DATA_MPLS=
]=20
> in route.c as I posted the prevoius mail. It is hard to

Heh heh.  I could give you the litteral meaning 'C' meaning :-)

> follow the code with this because the location of set the
> information of code is hard to find.

It's not hard to find it just uses lots of abstraction.

> Is there anybody explain me about that?=20

mpls_bind_out2fec() is what places MPLS info in a FIB entry.
rt_set_nexthop() which is called from ip_route_output_slow() and
ip_route_output_slow() grabs the MPLS info from the FIB entry and adds
it to a dst_entry.  Every SKB that goes through the Linux stack needs a
dst_entry to control where it goes.

>=20
>=20
>=20
> -------------------------------------------------------
> Ki Young Jung (jj...@ic...)
> Information and Communications University(ICU)
> Broadband Network Laboratory(http://bnlab.icu.ac.kr)
> 58-4 Hwaam-dong, Yusong-gu, Taejon, 305-732, KOREA
> Tel)+82-42-866-6182, 016-370-1751 Fax)+82-42-866-6110=20
> -------------------------------------------------------
>=20
> ----- Original Message -----=20
> From: James R. Leu=20
> To: Á=A2=B4=A1=BEâ=A2=AFµ=20
> Cc: mpl...@li...=20
> Sent: Tuesday, November 20, 2001 1:21 AM
> Subject: Re: [mpls-linux-general] I need some help to read the codes re=
lated with MPLS patches
>=20
>=20
> You're already using the best document there is, the code.  Keep diggin=
g
> through it, you'll figure it out.
>=20
> If you run into a road block, and have specific questions feel free to
> e-mail that list with it.  I or someone else will answer.
>=20
> Jim
>=20
> On Mon, Nov 19, 2001 at 11:58:51PM +0900, Á=A2=B4=A1=BEâ=A2=
=AFµ wrote:
> > I've looked at the code, and i think that the binding point of mpls_o=
utput() is in route.c
> >=20
> > After patching mpls codes, in ./net/ipv4/route.c
> >=20
> > void rt_set_nexthop(struct rtable *rt, struct fib_result *res, u32 it=
ag)
> > {
> >       struct fib_info *fi =3D res->fi;
> > =20
> > =A2=AE¦
> > =20
> > #ifdef CONFIG_MPLS
> >       /*  JLEU: we need to do this here because both
> >       * ip_route_output_slow() and ip_route_output_slow()
> >       * us this to finish the next hop calculations
> >       */
> >       if(res->proto_data[AUX_PROTO_DATA_MPLS]) {
> >           struct mpls_out_info *moi;
> >           int i;
> > =20
> >           MPLS_DEBUG(("rt_set_nexthop: adding label to dst\n"));
> >           MPLS_DEBUG(("rt_set_nexthop: before - mtu =3D %d\n",
> >             rt->u.dst.pmtu));
> >           rt->u.dst.output =3D mpls_output;    /* HERE */
> >           rt->u.dst.dst_proto_data[AUX_PROTO_DATA_MPLS] =3D=20
> >             res->proto_data[AUX_PROTO_DATA_MPLS];
> >           moi =3D res->proto_data[AUX_PROTO_DATA_MPLS];
> > mpls_again:
> >           for(i=3D0;i<moi->moi_instruction_length;i++) {
> >             switch(moi->moi_instruction[i].mi_opcode) {
> >                 case MPLS_OP_FWD:
> >                   moi =3D (struct mpls_out_info*)
> >                     moi->moi_instruction[i].mi_data;
> >                   goto mpls_again;
> >                   break;
> >                 case MPLS_OP_PUSH:
> >                   rt->u.dst.pmtu -=3D 4;
> >                   break;
> >             }
> >           }
> >           MPLS_DEBUG(("rt_set_nexthop: after - mtu =3D %d\n",
> >             rt->u.dst.pmtu));
> >       }
> > =20
> > =A2=AE&brvbar;
> > =20
> > }
> > =20
> > If res->proto_data[AUX_PROTO_DATA_MPLS] have a value (not zero)
> > then the output related function is binded with mpls_output()
> > so the function is invoked.
> > =20
> > But I still try to find work that describes the structures or methods=
 of MPLS in Linux .=20
> > Is there anyone who know this? I hope to learn from him or her.
> > =20
> > Especially, I want to know the semantics of proto_data[AUX_PROTO_DATA=
_MPLS].
> > =20
> > Thanks, in advance.
> > =20
> > B.E.
> > =20
> > Kiyoung Jung
> > -------------------------------------------------------
> > Ki Young Jung (jj...@ic...)
> > Information and Communications University(ICU)
> > Broadband Network Laboratory(http://bnlab.icu.ac.kr)
> > 58-4 Hwaam-dong, Yusong-gu, Taejon, 305-732, KOREA
> > Tel)+82-42-866-6182, 016-370-1751 Fax)+82-42-866-6110=20
> > -------------------------------------------------------
> > -------------------------------------------------
> > DreamWiz Free Mail @ http://www.dreamwiz.com/
> > DreamSearch Click the world!!! http://search.dreamwiz.com/
> >=20
>=20
> --=20
> James R. Leu
>=20
>=20
>=20
> -------------------------------------------------
> DreamWiz Free Mail @ http://www.dreamwiz.com/
> DreamSearch Click the world!!! http://search.dreamwiz.com/
>=20

--=20
James R. Leu

Re: [mpls-linux-general] (no subject)

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

I will be posting mpls-linux-1.1.tar.gz soon, which has a lot of
integration for E-LSPs L-LSP and hooks to DSCP.

I hope to post more about this tomorrow morning.

Jim

On Tue, Nov 20, 2001 at 06:12:04PM -0800, Mrugendra Singhai wrote:
> Hi All,
> 
> This is regarding implementing "MPLS support of
> Diffserv" in current LDP code of James. 
> 
> I did go through the extension implemented by people
> at Intec. Last I saw, it had E-LSP support using RSVP.
> And the way they implemented it was by having changing
> the mpls label and by changing the key to store label
> to include the exp as well.
> 
> But this approach does not supports L-LSP. Also I
> could not figure out how and where they were handling
> the Diffserv context associated with the LSP.
> 
> What I was interested in knowing was
> 
> 1) Will it not be a better idea to store the entire
> diffserv context associated with a LSP in one in_info
> entry in radix tree.
> 
> Any other suggestions on how exactly to implement EXP
> support is deeply appreciated.
> 
> Regards
> Mrugendra
> 
> 
> __________________________________________________
> Do You Yahoo!?
> Yahoo! GeoCities - quick and easy web site hosting, just $8.95/month.
> http://geocities.yahoo.com/ps/info1
> 
> _______________________________________________
> mpls-linux-general mailing list
> mpl...@li...
> https://lists.sourceforge.net/lists/listinfo/mpls-linux-general

-- 
James R. Leu

Re: [mpls-linux-general] making the ldp_zebra port

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

I it has been sometime since I've tried to compile against zebra.  I
will see if I can find time to try it and work through and compile time
bugs.

I'll get back to you.

Jim

On Tue, Nov 20, 2001 at 11:03:21AM +0100, Kauder Thorsten wrote:
> Hi, my name is Thorsten Kauder and I'm doing an internship at Siemens-Germany.
> My Job is to make a Linux-machine MPLS-Ready to test routing equipment.
> 
> So far I made the mpls run and am able to manually add LSPs.
> I'm working with zebra and so I'm trying to get the Zebra-port compiled.
> 
> I Have the latest (I think ) version of zebra 0.92a.
> and downloaded mpls_linux and ldp_portable from the cvs-tree.
> 
> I also changed the ZHOME-variable to the location of my zebra installation.
> 
> Now when I try to make the zebra_port I get the following output:
> 
> ---------------------------------------------------------------------------------------------
> 
> linux:/usr/src/cvs/ldp-portable #
> linux:/usr/src/cvs/ldp-portable # make ldp_zebra
> cd zebra-port ; make libldpport.a CC=gcc CFLAGS="-g -I. -Wall  -D__LDP_LINUX__ -Werror -DMPLS_LINUX -I ../lib -I/usr/src/zebra-0.90/lib -DSYSCONFDIR=\\\"/tmp/\\\""
> make[1]: Entering directory `/usr/src/cvs/ldp-portable/zebra-port'
> gcc -g -I. -Wall  -D__LDP_LINUX__ -Werror -DMPLS_LINUX -I ../lib -I/usr/src/zebra-0.90/lib -DSYSCONFDIR=\"/tmp/\"   -c -o zldp_cli.o zldp_cli.c
> In file included from zldp_cli.c:26:
> /usr/src/zebra-0.90/lib/sockunion.h:124: conflicting types for `inet_aton'
> /usr/include/arpa/inet.h:69: previous declaration of `inet_aton'
> make[1]: *** [zldp_cli.o] Error 1
> make[1]: Leaving directory `/usr/src/cvs/ldp-portable/zebra-port'
> make: *** [ldp_zebra_port] Error 2
> linux:/usr/src/cvs/ldp-portable #
> 
> ------------------------------------------------------------------------------------------------
> 
> I would really apreciate it If someone could help me with this problem.
> 
> another question to ldp:
> 
> If I use : `add global' at the ldp-prompt, the argument behind that is the LSR-ID , right ?!
> 
> Thanks in advance.
> 
>  
> 
> _______________________________________________
> mpls-linux-general mailing list
> mpl...@li...
> https://lists.sourceforge.net/lists/listinfo/mpls-linux-general

-- 
James R. Leu

Re: [mpls-linux-general] TC <-> MPLS

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

On Tue, Nov 20, 2001 at 10:49:03AM +0100, Jens Kuehlberg wrote:
> Hi my name is Jens,

Hello Jens,

First, off.  I'm glad you're interested in MPLS for Linux, especially in
advanced feature like working with TC/DiffServ and MPLS.

Second, because these are advanced featrues they are still quite untested
and if you choose to work with it, you will run into many bugs.

Third, I'm having a hard time following your english :-)

> I have install RedHat 7.1 (Kernel 2.4.0) and mpls-patch 0.990.
> Now, I will use TC(Traffic Control) and mpls together.

The first thing you will want to do it update to kernel 2.4.13 and download
mpls-linux-1.1.tar.gz from the MPLS for Linux project page.  NOTE:
I haven't posted mpls-linux-1.1.tar.gz yet.  I will make an attempt
to do so tomorrow morning.

> Where can I help me? 
> Have someone Information about mpls and QOS for Linux.

You will need to do some reading.  Checkout:

http://diffserv.sourceforge.net/

> How work TC und mpls together. 

I will explain this when I release mpls-linux-1.1.tar.gz

Jim


> 
> Scenario:
> 
> |-------------|               |-------------|              |------------|   
>           
> |  Router1     | <=MPLS=> |  Router2     | <=MPLS=>|  Router3    |
> |-------------|               |-------------|              |------------|
>         |                                                                   
>    |        
>        IP                                                                   
>    IP      
>         |                                                                   
>    |        
> |-------------|                                                  
> |-------------|          
> |  Host1         |                                                   |     
> Host2     |
> |-------------|                                                   
> |-------------|
> 
> 
> 
>      
> 
> 
> 
> 
> 
> -- 
> GMX - Die Kommunikationsplattform im Internet.
> http://www.gmx.net
> 
> 
> _______________________________________________
> mpls-linux-general mailing list
> mpl...@li...
> https://lists.sourceforge.net/lists/listinfo/mpls-linux-general

-- 
James R. Leu

[mpls-linux-general] (no subject)

[Mrugendra S. <mru...@ya...>]

Hi All,

This is regarding implementing "MPLS support of
Diffserv" in current LDP code of James. 

I did go through the extension implemented by people
at Intec. Last I saw, it had E-LSP support using RSVP.
And the way they implemented it was by having changing
the mpls label and by changing the key to store label
to include the exp as well.

But this approach does not supports L-LSP. Also I
could not figure out how and where they were handling
the Diffserv context associated with the LSP.

What I was interested in knowing was

1) Will it not be a better idea to store the entire
diffserv context associated with a LSP in one in_info
entry in radix tree.

Any other suggestions on how exactly to implement EXP
support is deeply appreciated.

Regards
Mrugendra


__________________________________________________
Do You Yahoo!?
Yahoo! GeoCities - quick and easy web site hosting, just $8.95/month.
http://geocities.yahoo.com/ps/info1

[mpls-linux-general] making ldp again

[Kauder T. <Tho...@ic...>]

Hi, my name is Thorsten Kauder and I'm doing an internship at Siemens-Germany.
My Job is to make a Linux-machine MPLS-Ready to test routing equipment.

So far I made the mpls run and am able to manually add LSPs.
I'm working with zebra and so I'm trying to get the Zebra-port compiled.

I Have the latest (I think ) version of zebra 0.92a.
and downloaded mpls_linux and ldp_portable from the cvs-tree.

I also changed the ZHOME-variable to the location of my zebra installation.

Now when I try to make the zebra_port I get the following output:

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

linux:/usr/src/cvs/ldp-portable #
linux:/usr/src/cvs/ldp-portable # make ldp_zebra
cd zebra-port ; make libldpport.a CC=gcc CFLAGS="-g -I. -Wall  -D__LDP_LINUX__ -Werror -DMPLS_LINUX -I ../lib -I/usr/src/zebra-0.90/lib -DSYSCONFDIR=\\\"/tmp/\\\""
make[1]: Entering directory `/usr/src/cvs/ldp-portable/zebra-port'
gcc -g -I. -Wall  -D__LDP_LINUX__ -Werror -DMPLS_LINUX -I ../lib -I/usr/src/zebra-0.90/lib -DSYSCONFDIR=\"/tmp/\"   -c -o zldp_cli.o zldp_cli.c
In file included from zldp_cli.c:26:
/usr/src/zebra-0.90/lib/sockunion.h:124: conflicting types for `inet_aton'
/usr/include/arpa/inet.h:69: previous declaration of `inet_aton'
make[1]: *** [zldp_cli.o] Error 1
make[1]: Leaving directory `/usr/src/cvs/ldp-portable/zebra-port'
make: *** [ldp_zebra_port] Error 2
linux:/usr/src/cvs/ldp-portable #

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

I would really apreciate it If someone could help me with this problem.

another question to ldp:

If I use : `add global' at the ldp-prompt, the argument behind that is the LSR-ID , right ?!

Thanks in advance.
Thorsten

------------------------------------------------------------------------------------------------------------------------------------
hi again
I just commented out the definition for 'inet_aton' in /usr/src/zebra-0.90/lib/sockunion.h:124
and now Idon't get the conflict anymore. but here comes the next problem:

now at the linking- process there are some functions missing

linux:/usr/src/cvs/ldp-portable #
linux:/usr/src/cvs/ldp-portable # make ldp_zebra
cd zebra-port ; make libldpport.a CC=gcc CFLAGS="-g -I. -Wall  -D__LDP_LINUX__ -Werror -DMPLS_LINUX -I ../lib -I/usr/src/zebra-0.90/lib -DSYSCONFDIR=\\\"/tmp/\\\""
make[1]: Entering directory `/usr/src/cvs/ldp-portable/zebra-port'
make[1]: `libldpport.a' is up to date.
make[1]: Leaving directory `/usr/src/cvs/ldp-portable/zebra-port'
cd lib ; make libldp.a CC=gcc CFLAGS="-g -I. -Wall  -D__LDP_LINUX__ -Werror -DMPLS_LINUX -I ../zebra-port -I/usr/src/zebra-0.90/lib"
make[1]: Entering directory `/usr/src/cvs/ldp-portable/lib'
make[1]: `libldp.a' is up to date.
make[1]: Leaving directory `/usr/src/cvs/ldp-portable/lib'
gcc -o ldp_zebra zebra-port/ldp_zebra.o lib/libldp.a zebra-port/libldpport.a -L/usr/src/zebra-0.90/lib -lzebra -lcrypt
zebra-port/libldpport.a(zldp_mpls_impl.o): In function `ldp_mpls_open':
/usr/src/cvs/ldp-portable/zebra-port/zldp_mpls_impl.c:58: undefined reference to `rtnl_open'
zebra-port/libldpport.a(zldp_mpls_impl.o): In function `ldp_mpls_outlabel_add':
/usr/src/cvs/ldp-portable/zebra-port/zldp_mpls_impl.c:87: undefined reference to `send_nhlfe'
zebra-port/libldpport.a(zldp_mpls_impl.o): In function `ldp_mpls_outlabel_del':
/usr/src/cvs/ldp-portable/zebra-port/zldp_mpls_impl.c:107: undefined reference to `send_nhlfe'
zebra-port/libldpport.a(zldp_mpls_impl.o): In function `ldp_mpls_inlabel_add':
/usr/src/cvs/ldp-portable/zebra-port/zldp_mpls_impl.c:126: undefined reference to `send_ilm'
zebra-port/libldpport.a(zldp_mpls_impl.o): In function `ldp_mpls_inlabel_del':
/usr/src/cvs/ldp-portable/zebra-port/zldp_mpls_impl.c:143: undefined reference to `send_ilm'
zebra-port/libldpport.a(zldp_mpls_impl.o): In function `ldp_mpls_in2out_add':
/usr/src/cvs/ldp-portable/zebra-port/zldp_mpls_impl.c:177: undefined reference to `send_xc'
zebra-port/libldpport.a(zldp_mpls_impl.o): In function `ldp_mpls_in2out_del':
/usr/src/cvs/ldp-portable/zebra-port/zldp_mpls_impl.c:213: undefined reference to `send_xc'
zebra-port/libldpport.a(zldp_mpls_impl.o): In function `ldp_mpls_fec2out_add':
/usr/src/cvs/ldp-portable/zebra-port/zldp_mpls_impl.c:237: undefined reference to `send_ftn'
zebra-port/libldpport.a(zldp_mpls_impl.o): In function `ldp_mpls_fec2out_del':
/usr/src/cvs/ldp-portable/zebra-port/zldp_mpls_impl.c:259: undefined reference to `send_ftn'
collect2: ld returned 1 exit status
make: *** [ldp_zebra] Error 1
linux:/usr/src/cvs/ldp-portable #        


where's my problem ?

If anyone knows, I would be very thankful for any help.
greetings

Thorsten Kauder