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

Re: [mpls-linux-general] MPLS on ATM

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

Hi Hugo,

cacote wrote:
> 
> 
> If we then make  [root@norte /root]# ping 192.168.50.20 , and if then
> use  ethereal to monitor the
> packets in the two hosts we see no MPLS and just ICMP. I should add that
> sometimes whem trying this
> scenario the machine that is being pinged just crashes with no apparent
> reason.
> 
> Is there something wrong in the setup of the scenario? Is there anybody
> that has a scenario where MPLS
> works with ATM ?
> 
Apparently, your config. is ok. I made some test with ATM at the end of
November (look at the Mail archive for the configuration and result).
What i found, is that the Fore ATM card (PCA200E not LE) fail to run
MPLS. You can establish connection but can't send any data : the kernel
crash. I change for ENI ATM card and it work well.

>     Thank you for the Help, best regards
> 
>             HUGO CACOTE
> 


I'll test the new 0.990 version in the next days and report my result
ASAP.

To have a full ping working, you need to establish a full
bi-directionnal label ie. one for each direction, but, be carrefull, you
have to choose two differents VPI/VCI : this a limitation due to the ATM
driver. You can establish a bi-directionnal connection, Input only or
Output only connection. But, when you choose Input or Output only
connection, the remaining direction become unavailable :-(

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] ldp portable

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

Hello all,

I've just submitted a lot of changes to CVS for ldp portable.
Mostly it is internal.  The major change is that now unsolicited
mode can send labels for every route, not just the lsr id.  The
default behavior is to only sent labels for the lsr id (look in
port/ldp_policy_impl.c egress)

These changes certainly break label request processing, I'll fix it soon.
For now if you want to play with ldp-portable I suggest getting it via
CVS, because I'll probably be making changes quite often.

If you run into any crashes or usablity problems, I like bug reports, but
I like patches even better :-)

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

Jim
-- 
James R. Leu

[mpls-linux-general] MPLS on ATM

[cacote <hc...@in...>]

HI

I ve been testing the new MPLS package (mpls-linux-0.990), it worked
allright in ethernet but when I
got to teste it in ATM there were problems.

My scenario is the following:



|||||||||||||||||
||||||||||||||||
  ||  norte
||
||   este  ||
  ||
||
||            ||

|||||||||||||||||
||||||||||||||||
         |   atm0
192.168.50.10                                                    |  atm0
192.168.50.20

|
|
         |------------------------------------- |

The ATM  cards I am using are the following:

ForeRunnerLe 155 mbit/s          nicstar  (chipset)

The configuration  i made on both hosts  was this:


ON norte:
[root@norte /root]# route add -host 192.168.50.20/32 gw 192.168.50.20
[root@norte /root]# mplsadm -A -O atm:0/104:atm0
[root@norte /root]# mplsadm -B -O atm:0/104:atm0 -f 192.168.50.20/32
[root@norte /root]# mplsadm -L atm0:0

If we try and check the configurations we see:

[root@norte /root]# cat /proc/net/mpls_out
80680008 PUSH(atm 0/104) SET(atm0)
[root@norte /root]# cat /proc/net/mpls_fec
80680008 192.168.50.20/32

ON este:
[root@este /root]# route add -host 192.168.50.10/32 gw 192.168.50.10
[root@este /root]# mplsadm -L atm0:0
[root@este /root]# mplsadm -A -I atm:0/104:0

If we try and check the configurations we see:

[root@este /root]# cat /proc/net/mpls_in
80680000 atm 0/104 0 POP DLV

If we then make  [root@norte /root]# ping 192.168.50.20 , and if then
use  ethereal to monitor the
packets in the two hosts we see no MPLS and just ICMP. I should add that
sometimes whem trying this
scenario the machine that is being pinged just crashes with no apparent
reason.

Is there something wrong in the setup of the scenario? Is there anybody
that has a scenario where MPLS
works with ATM ?

    Thank you for the Help, best regards

            HUGO CACOTE

Re: [mpls-linux-general] Research Topic

[Yon U. <uk...@rz...>]

On Fri, 30 Mar 2001, Sanda Dragos wrote:
> 	Thank's very much for your help. It worked but now it stops right
> after:
> ------------------------------------------------------------
> ...
> ...
> Started device management daemon for /dev
> 		Welcome to Red Hat Linux
> 	Press 'I' to enter interactive startup
> Mounting proc filesystem:
> ------------------------------------------------------------
>
> Can you help me with this one too?

 Hmmm,I'm clueless but I can speculate. I've never used RH, only
mandrake and then I just as a quick install on an alien box, where I
didn't start learning the distro, I just wanted it to work, fast.

 Which version of RH are you using? I see it is a more or less new one,
with devfs support, it might be, that it (devfs support) is not wholly
integrated into the system. Try mounting the rootfs on your host system
(losetup ...;mount ...) and check out the /dev directory, it should have
the usual devices (say ~100 files). Edit the /etc/fstab from the uml
rootfs and change the line "/dev devfs ..." to "/devfs devfs ..." and
create the /devfs dir in the rootfs-file. Umount, boot uml.

 If that works, I shall be playing in the lottery, the moon is in my
quadrant it seems. Otherwise I'm clueless.

greetings,
 yon

Re: [mpls-linux-general] Research Topic

[Sanda D. <dr...@ee...>]

	Thank's very much for your help. It worked but now it stops right
after:
------------------------------------------------------------
...
...
Started device management daemon for /dev
		Welcome to Red Hat Linux
	Press 'I' to enter interactive startup
Mounting proc filesystem:
------------------------------------------------------------

Can you help me with this one too?

Regards,
	Sanda

Re: [mpls-linux-general] Research Topic

[Yon U. <uk...@rz...>]

On Thu, 29 Mar 2001, Sanda Dragos wrote:
[snip]
> 	The problem is that I tried to install uml but I got this error:
>
> 	Kernel panic: VFS: Unable to mount root fs on 62:00

make sure your root fs file is named as described in the docs and in the
same directory as you are starting uml, a soft link to the real fs-file is
enough.

HTH, HAND
 yon

Re: [mpls-linux-general] Research Topic

[Sanda D. <dr...@ee...>]

	Hi!
	
	I am subscribed to: mpl...@li...
and I got your mail with the solution for testing MPLS.
	I am also a Ph.D. student and I am studying MPLS and this solution
suits me very well.
	The problem is that I tried to install uml but I got this error:

	Kernel panic: VFS: Unable to mount root fs on 62:00


	I know that other people had the same problem in August last year
and I read the archives from uml mailing list but they didn't helped me.

	Had anyone the same problem and can anyone help me with this
problem?

Regards,
	Sanda

On Wed, 21 Mar 2001, James R. Leu wrote:

> Hello all,
> 
> First of all, it is very cool that you are both looking to do some research
> with MPLS, go for it!
> 
> Second, you should both look into using User Mode Linux to increase the
> number of LER/LSR you have to work with.  UML allows you to run the Linux
> kernel as a set of user land threads.  THus you can run muliple copies
> of it.  I have written an ethernet driver for it, which allows you to
> network them together.  Check out:
> 
> http://user-mode-linux.sourceforge.net/
> 
> NOTE: you will want to grab the latest version of the virtual ethernet driver
> and probably contact me for help :-)  If anyone is interested in how to
> use this, e-mail the list and I will post a LONG how-to for everyone.
> 
> Third, Yon has been working on integrating LDP into Zebra.  I haven't had a
> chance to test it yet, but it sounds like he has made lot of progress.
> 
> Forth, I will be posting a "near 1.0" version of mpls-linux soon.  This will
> hopefully flush out any remaining bugs and provide a stable full feature
> MPLS implementation for people to play with.  THen the real fun begins, 
> working toward 2.0 which will scramble things up quite a bit.  I'll post
> another message with what is planned for 2.0.
> 
> Fifth, Layer 2 Cross Connects (draft-martini-l2circuit-trans-mpls-05.txt
> and draft-martini-l2circuit-encap-mpls-01.txt) and MPLS/BGP/VPNS (rfc2548bis)
> are the services ISP are clamoring to offer.  Not much has been done on the
> lines of researching for these (none that I have seen).
> 
> Sixth ... I could on for hours.  If your looking for more info
> let me know.
> 
> Jim
> 
> On Wed, Mar 21, 2001 at 02:36:15PM +0100, sk...@en... wrote:
> > 
> > > I am a MSc student who is interested in MPLS, 
> > > and would like to do my project/thesis in this
> > > area.
> > 
> > I'm almost in the same case.
> > 
> > I have here at school between 6 and 12 linux PC to
> > do some testing (they are all fitted with 2 ethernet
> > NIC and some have an ATM NIC).
> > 
> > I am currently writing a test suite to "bench" routers ;
> > it will generate network flows using tun/tap devices.
> > it will allow to simulate thousands, and up to millions,
> > of network flows with different src/dst ip addresses.
> > 
> > I plan to further experiment with LDP, to implement
> > piggybacking over BGP (zebra) and eventually look after
> > freebsd implementation. if anybody is already working
> > on one ot these points, and would like either peer review
> > (well, "newbie review" should be more appropriate) or
> > would think it woud be better to turn my efforts in
> > other directions, feel free to contact me.
> > 
> > Jerome Petazzoni <jp...@en...>
> > 
> > 
> > _______________________________________________
> > mpls-linux-general mailing list
> > mpl...@li...
> > http://lists.sourceforge.net/lists/listinfo/mpls-linux-general
> 
> -- 
> James R. Leu
> 
> _______________________________________________
> mpls-linux-general mailing list
> mpl...@li...
> http://lists.sourceforge.net/lists/listinfo/mpls-linux-general
> 

[mpls-linux-general] Getting started with ldp-portable

[Ayush T. <ayu...@ly...>]

Hello,
I wish to use ldp-portable, but am relatively out-dated on the Linux environment as it has been sometime since I used it last. Where can I find a list of to-do's to get it up and going on an Intel machine from scratch.
I will be extremely grateful for any help.
Thanks.
Ayush


Get 250 color business cards for FREE! at Lycos Mail
http://mail.lycos.com/freemail/vistaprint_index.html

Re: [mpls-linux-general] help on ldp_linux needed

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

Hello,,

On Mon, Mar 26, 2001 at 11:50:57PM -0600, Karthikeyan Nathillvar wrote:
> hi,
>    Is there any document explaining how to use ldp_linux program?.. How exactly

Yes, look in the port/ directory.  You may need to grab the latest CVS
revision to get all the docs.

(sourceforge.net/projects/mpls-linux/ follow the CVS link)

> ldp_linux interacts with mpsl_adm program..

ldp_linux does not interact with mplsadm.  You need mplsadm to set all of the
LDP interfaces to labelspace 0. (before running ldp_linux)

Make sure you have ldp_linux compiled with MPLS_LINUX flag otherwise it will
not install LSPs. (look at the Makefile in the port/ directory.)  There have
been lots of questions about this on the mailing list, make sure to check
the archive.

You may want to play around with the version that Yon has been working on that
integrates LDP and zebra.  Check the mailing list archive for more info.

Jim

> any help greatly appreciated..
> 
> regards,
> ntkarthik
> 
> ------------------------------------------------------------------------------
>                         Karthikeyan Nathillvar
> 
> 
> Office:                                                               Res.:
> -------                                                         -----
> Team Niehaus Graduate Research Assistant     
> 245 E, Nichols Hall,                                   1550, Eddingham Drive,
> 2335 Irving Hill Road,                                 Lawrence,
> Lawrence,                                                 Kansas 66046 -4037
> Kansas 66045 - 7612                                 Ph: 785-312-8001
> Ph: 785-864-7774
>                
>                          " Dare to Dream Care to Achieve"
> -------------------------------------------------------------------------------
> 
> _______________________________________________
> mpls-linux-general mailing list
> mpl...@li...
> http://lists.sourceforge.net/lists/listinfo/mpls-linux-general

-- 
James R. Leu

[mpls-linux-general] help on ldp_linux needed

[Karthikeyan N. <ntk...@it...>]

hi,
   Is there any document explaining how to use ldp_linux program?.. How exactly
ldp_linux interacts with mpsl_adm program..
any help greatly appreciated..

regards,
ntkarthik

------------------------------------------------------------------------------
                        Karthikeyan Nathillvar


Office:                                                               Res.:
-------                                                         -----
Team Niehaus Graduate Research Assistant     
245 E, Nichols Hall,                                   1550, Eddingham Drive,
2335 Irving Hill Road,                                 Lawrence,
Lawrence,                                                 Kansas 66046 -4037
Kansas 66045 - 7612                                 Ph: 785-312-8001
Ph: 785-864-7774
               
                         " Dare to Dream Care to Achieve"
-------------------------------------------------------------------------------

[mpls-linux-general] mpls-linux-0.990

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

Hello,

I just place mpls-linux-0.990 up on sourceforge:

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

From the ChangeLog:

03-24-2001	-released 0.990
		-updated to 2.4.2
		-use allocation caches for mpls_label and mpls_push_data
		-add support for Explicit NULL for IPv4
		-do range checking when creating labels
		-fixed "growing" a skb when adding shim
		-removed mpls tunnel config option, always include the mpls
		 :tunnel code
		-mpls_labelspace is now set during dev_init

From NOTE:

Outstanding issued in 0.990

-/proc/net/mpls_fec may be incorrect if a route was deleted without
 being unbound from the out label first
-mplsadm does not return errors due to usage of netlink.
-on ethernet, multiple next hops off the same interface cannot advertise the
 same label.  This is a big limitation.  I know how to fix it, I just don't
 want to deal with all of the bitching when I do change it
-router alert label (2) is not handled correctly
-mpls packets appear to be corrupted when running tcpdump or the like on
 an LER (the packets are not really corrupted, tcpdump is getting an invalid
 version of the packets) 

This is an attempt to get a polished/stable version for people to use.
There are a couple of things left to be done before 1.0:

-fix any of the above bugs that can be fixed with out major changes
-add a patch against pppd, which allows for running MPLS over PPP
-more documentation

Please test this version out and mail the list with any problems.

Thanks
Jim

PS If anyone can test the Ingress Policing and the MPLS over ATM functionality
please do, I do not have the means (or time) to.
-- 
James R. Leu

Re: [mpls-linux-general] mpls labels

[S. <j....@gm...>]

Hi James,

I've just finished a first version of setting up static mpls routes with
the help of a config file. I'm not sure if this is what you want, but it
fits the needs in my testbed.
In using this (called mplsroute) with a startscript at bootup and
shutdown time.

The programm is written in C and uses the netlink-functions of
mpls-linux (and is mostly based on mplsadm). At the moment, ATM is not
supported, because I can't extract the lines in mplsadm.c for that, and
the only thing for outgoing labels are tunneldevices (fec's are not
supported yet).

If you are interested in this, please let me know. I'm sadly don't
having a webpage for downlaodings but I can send it by mail.

J=F6rn

Wuchieh James Jong schrieb:

> hello,
>
> i'm currently manually setting up the lsp's using mplsadm.
> does anyone know whether the mpls labels remain on:
> 1)logout?
> 2)reboot/shutdown?
>
> thanks,
> james
>
> _______________________________________________
> mpls-linux-general mailing list
> mpl...@li...
> http://lists.sourceforge.net/lists/listinfo/mpls-linux-general

[mpls-linux-general] mpls labels

[Wuchieh J. J. <wj...@un...>]

hello,

i'm currently manually setting up the lsp's using mplsadm.
does anyone know whether the mpls labels remain on:
1)logout?
2)reboot/shutdown?

thanks,
james

[mpls-linux-general] user mode linux

[Fredrik S. <fre...@sm...>]

Hi, i am interested in using User Mode Linux to get more LSRs to
experiment with. So it would be very helpful if you could post a
how-to describing the setup.

/Fredrik Sundstr=F6m

Re: [mpls-linux-general] mpls labels in ethernet destination address : silly or interesting ?

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

Hello,

In te early days of MPLS there was a suggestion to extend the ethernet header
to do this, but I don't think the idea ever took.

On Wed, Mar 21, 2001 at 03:37:24PM +0100, sk...@en... wrote:
> 
> has anybody thought about embedding MPLS labels in ethernet headers,
> instead of using a shim ? I thought about using last four bytes of
> destination MAC address to carry MPLS labels. it would require
> the receiver to work in promiscuous mode, or to set the multi/broad
> cast bit of the destination MAC address, or to find some hack in
> the NIC driver code to allow some kind of filtering.

You can't really just grab the last 4 octects because the resulting
MAC (after overwritting wit the label) might be a valid MAC used by a machine
on the network.

Jim

> 
> would there be some interest in doing that way, or is there
> some major pitfall I did not think of ?
> 
> 
> _______________________________________________
> mpls-linux-general mailing list
> mpl...@li...
> http://lists.sourceforge.net/lists/listinfo/mpls-linux-general

-- 
James R. Leu

[mpls-linux-general] mpls labels in ethernet destination address : silly or interesting ?

[<sk...@en...>]

has anybody thought about embedding MPLS labels in ethernet headers,
instead of using a shim ? I thought about using last four bytes of
destination MAC address to carry MPLS labels. it would require
the receiver to work in promiscuous mode, or to set the multi/broad
cast bit of the destination MAC address, or to find some hack in
the NIC driver code to allow some kind of filtering.

would there be some interest in doing that way, or is there
some major pitfall I did not think of ?

Re: [mpls-linux-general] Research Topic

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

Hello all,

First of all, it is very cool that you are both looking to do some research
with MPLS, go for it!

Second, you should both look into using User Mode Linux to increase the
number of LER/LSR you have to work with.  UML allows you to run the Linux
kernel as a set of user land threads.  THus you can run muliple copies
of it.  I have written an ethernet driver for it, which allows you to
network them together.  Check out:

http://user-mode-linux.sourceforge.net/

NOTE: you will want to grab the latest version of the virtual ethernet driver
and probably contact me for help :-)  If anyone is interested in how to
use this, e-mail the list and I will post a LONG how-to for everyone.

Third, Yon has been working on integrating LDP into Zebra.  I haven't had a
chance to test it yet, but it sounds like he has made lot of progress.

Forth, I will be posting a "near 1.0" version of mpls-linux soon.  This will
hopefully flush out any remaining bugs and provide a stable full feature
MPLS implementation for people to play with.  THen the real fun begins, 
working toward 2.0 which will scramble things up quite a bit.  I'll post
another message with what is planned for 2.0.

Fifth, Layer 2 Cross Connects (draft-martini-l2circuit-trans-mpls-05.txt
and draft-martini-l2circuit-encap-mpls-01.txt) and MPLS/BGP/VPNS (rfc2548bis)
are the services ISP are clamoring to offer.  Not much has been done on the
lines of researching for these (none that I have seen).

Sixth ... I could on for hours.  If your looking for more info
let me know.

Jim

On Wed, Mar 21, 2001 at 02:36:15PM +0100, sk...@en... wrote:
> 
> > I am a MSc student who is interested in MPLS, 
> > and would like to do my project/thesis in this
> > area.
> 
> I'm almost in the same case.
> 
> I have here at school between 6 and 12 linux PC to
> do some testing (they are all fitted with 2 ethernet
> NIC and some have an ATM NIC).
> 
> I am currently writing a test suite to "bench" routers ;
> it will generate network flows using tun/tap devices.
> it will allow to simulate thousands, and up to millions,
> of network flows with different src/dst ip addresses.
> 
> I plan to further experiment with LDP, to implement
> piggybacking over BGP (zebra) and eventually look after
> freebsd implementation. if anybody is already working
> on one ot these points, and would like either peer review
> (well, "newbie review" should be more appropriate) or
> would think it woud be better to turn my efforts in
> other directions, feel free to contact me.
> 
> Jerome Petazzoni <jp...@en...>
> 
> 
> _______________________________________________
> mpls-linux-general mailing list
> mpl...@li...
> http://lists.sourceforge.net/lists/listinfo/mpls-linux-general

-- 
James R. Leu

RE: [mpls-linux-general] Research Topic

[<sk...@en...>]

> I am a MSc student who is interested in MPLS, 
> and would like to do my project/thesis in this
> area.

I'm almost in the same case.

I have here at school between 6 and 12 linux PC to
do some testing (they are all fitted with 2 ethernet
NIC and some have an ATM NIC).

I am currently writing a test suite to "bench" routers ;
it will generate network flows using tun/tap devices.
it will allow to simulate thousands, and up to millions,
of network flows with different src/dst ip addresses.

I plan to further experiment with LDP, to implement
piggybacking over BGP (zebra) and eventually look after
freebsd implementation. if anybody is already working
on one ot these points, and would like either peer review
(well, "newbie review" should be more appropriate) or
would think it woud be better to turn my efforts in
other directions, feel free to contact me.

Jerome Petazzoni <jp...@en...>

[mpls-linux-general] Research Topic

[Wenbiao Z. <wz...@cs...>]

Hi, everyone:

I am a MSc student who is interested in MPLS, 
and would like to do my project/thesis in this
area.

I am new to MPLS, and run into problem when
I decide the topics. I would like to receive
any useful advice from you. Following is 

Currently, I have 2 choices for my topic with
this software
1. implementation of MPLS 
   Install it on Linux and run it, then
   get the traffic to do analysis.
 
   There are following disadvantage for this option:
   1.1 limited LSRs
   Due to limited resource, I could only have 2 Linux 
   hosts at home (connecting to internet through Cable 
   modem) and 1 or 2 Linux PCs at the school. Since only 
   3 or 4 LSRs, will the traffic be good enough for analysis?
   
   1.2 do not know what to analysis
   Even the problem 1.1 does not exist, what kind of analysis
   could I perform based on the traffic

2. Traffic Engineering 
In a MPLS seminar by Juniper, a guru suggested me to work
on traffic Angering.  Due to limited resource, I could only
do a little in traffic Angering. For example, in the software,
RSVP is not implemented in the software. Once it is implemented, 
how could I test it to find out it works or not?

Before I decide to choose one from above 2 options, would any of 
you please answer the questions raised in each of the options and
give me some advice?

Any useful feedback will be highly appreciated.

William Zhang
School of Computing Science
Simon Fraser University
Burnaby, BC
V5A 1S6

[mpls-linux-general] ldp_linux commands

[narsi p. <na...@ho...>]

hi,
   Can some body  provide me with some examples for a setup(ingress,egress 
and a core router)using ldp_linux commands. I would also like to know 
whether ldp_linux commands have to be used in conjunction with mplsadm 
commands or can be used independently.

thanks in advance

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

Re: [mpls-linux-general] mplsadm error 0.802

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

/usr/src/linux-whatever/include/linux is not automaticly in the include
path of gcc. Either use a symbolic link from /usr/include/linux to this
directory or add a "-I/usr/src/linux-whatever/include" to the Makefile
flags in the utils directory

Best regards,
Steven

Wuchieh James Jong wrote:

> Hello,
>
> When compiling mplsadm.c, I get an error:
> gcc -g -Wall   -c -o netlink.o netlink.c
> netlink.c:9:24: linux/mpls.h: No such file or directory
> make: *** [netlink.o] Error 1
>
> I've checked to make sure the mpls patch is in and scanning the
> 2.4.1 source tree I see the files:
> include/linux/mpls.h
> include/net/mpls.h
> include/config/mpls.h
>
> I've also checked the kernel configuration and to make sure the mpls
> option is included.  I get the same error on two separate machines.
>
> Thanks for any help,
> James
>
> _______________________________________________
> mpls-linux-general mailing list
> mpl...@li...
> http://lists.sourceforge.net/lists/listinfo/mpls-linux-general

--
Steven Van den Berghe
ste...@in...
Workgroup Broadband-Networks
Department Information Technology
Ghent University - Belgium
Phone:  +32 (0)9 267 35 86 | Fax  :  +32 (0)9 267 35 99
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
"Law of Cybernetic Entomology" There is always one more
bug.


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

[mpls-linux-general] mplsadm error 0.802

[Wuchieh J. J. <wj...@un...>]

Hello,

When compiling mplsadm.c, I get an error:
gcc -g -Wall   -c -o netlink.o netlink.c
netlink.c:9:24: linux/mpls.h: No such file or directory
make: *** [netlink.o] Error 1

I've checked to make sure the mpls patch is in and scanning the
2.4.1 source tree I see the files:
include/linux/mpls.h
include/net/mpls.h
include/config/mpls.h

I've also checked the kernel configuration and to make sure the mpls
option is included.  I get the same error on two separate machines.

Thanks for any help,
James

Re: [mpls-linux-general] VPNs using MPLS-Linux/LDP-Portable

[Yon U. <uk...@rz...>]

On Tue, 20 Feb 2001, James R. Leu wrote:

> >  I have started on 3, it is a mess, doesn't do anything useful
> > yet, as I have problems understanding ldp-portable (to be
> > precise: I don't want to learn how ldp-portable works,
> > need-to-know is my keyword here).
>
> This would be great!  How can I help.  I can explain any of the ldp-portable
> API for you, what needs to be provided to ldp-portable, and how things
> need to be stored.

 Well, as things go on, I'll have more questions. I've put the little
monster up for grabbing at:

http://wwwstud.informatik.uni-karlsruhe.de/~s_uriart/zldpd.tgz

 Take a look at it, if you want to. I guess it could be made to run
with direct mpls-linux access, but everything else running over
zebra.


 I haven't quite tested it. It compiles, and runs a bit without
crashing. If you don't start zebra before starting it, it will
crash (on an assert). No need to run zebra as root, btw, just
start it, so zldpd will know about interfaces (and later routes).


> I have time to answer question, just not time to do the port
> myself :-)

 Fine! As it goes on, I'll ask you precise questions. At the
moment I just wanted to get the ball rolling and take a look
at the mpls/ldp thingie. Your code looks really professional.



enjoy & HAND,
 yon


PS: forgot to put a sample configuration file in the tgz.
  I attach it.

Re: [mpls-linux-general] VPNs using MPLS-Linux/LDP-Portable

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

I think Yon has all of the info here, it's just a bit scattered ;-)

Requirements:

-you need to have a kernel that support mutiple "forwarding" tables.
 Linux 2.2 and 2.4 have this.  One forwarding table per VPN per edge rout=
er.
-you need to be able to add MPLS labels to the route entries in these
 "forwarding table" on the ingress routers and have MPLS labels point
 you to a "forwarding table" on the egress routers
-You need to have a route daemon that can run mulitple instances of
 lightwiegh protocol like RIPv2 or OSPF (or even static routes) and assoc=
iates
 the routes learned via this protocol to one of the "forwarding tables"
-you need a BGP implementation that con distribute routes for the VPN:IPV=
4
 address family and MPLS labels per route (could be the same label value)
-you need a MPLS signaling protocol that will create "tunnel" LSPs that
 span from edge router to edge router (across the core).  LDP protable co=
uld
 be used to do this, running in "juniper" mode.
-you then need some intelligence to tie the routes learned via BGP to
 and LSPs that cross the core.

Desired result:

-on ingress router a packet comes in a custoemr interface and a route
 lookup is done in it's vpn forwarding table.  There is a MPLS label
 associated with this route entry (learned via BGP) and the route entry
 has an LSP as the outgoing interface (an  MPLS tunnel setup via LDP to
 be exact).  The MPLS label associated with the route entry is pushed on
 the packet, then the MPLS label associated with the MPLS tunnel is pushe=
d
 on the label and is forwarded across the core.
-at the egress the label used to corss the core is popped off, the second
 label points to a "forwarding table".  The packet is delived to the
 vpn forwarding table were a IP lookup is done which will deliver the pac=
ket
 to a custoemr interface.

Most of the pieces to this puzzle exist, they just need to be tied togeth=
er.

Jim


On Tue, Feb 20, 2001 at 05:20:02PM +0100, Yon Uriarte wrote:
> On Tue, 20 Feb 2001, Arm=E9nio Pinto wrote:
> > Hi there,
>=20
> Hi hi,
>=20
>=20
> >      Has anyone tried to implement any kind of VPN using
> > MPLS-Linux/LDP-Portable packages? Thanks in advance.
>=20
>=20
> There is (was?) support for BGP-MPLS in zebra.
>=20
>  For LDP you need:
>=20
> 1) mpls support in zebra (zebra <-> kernel interface)
> 2) mpls support in zebra protocol (zebra <-> daemons)
> 3) port ldp-portable to zebra
>=20
>=20
>  For 1&2 you could just split Mr. Leu's mpls API (portability
> layer) in two, translating it to the zebra framework, mantaining
> the general function calls (just serializing them over the
> zebra protocol). For 1, you have to write some kind of
> mpls LIB manager, too.
>=20
>  I have started on 3, it is a mess, doesn't do anything useful
> yet, as I have problems understanding ldp-portable (to be
> precise: I don't want to learn how ldp-portable works,
> need-to-know is my keyword here).
>=20
>  So I have some cut'n'pasted code. It is quite basic, yet.
> I might start (paid) work soon, so I guess I'll put it up
> for grabs. I'll mail you.
>=20
>=20
>  Now, you wanted VPN, if you want to emulate cisco's vpn
> code, you need VRF, that is:
> 1) different packet forwarding tables in zebra
> 2) a way to attach such vrf to an interface
> 3) a way to route routes from such vrfs to/from routing processes
>=20
>=20
> 1 might be easy, maybe. Look at zebra/lib/table.h and
> zebra/lib/rib.* (at least). I'm no zebra expert.
>=20
> 2 is kernel dependent, linux 2.[2|4] could do it.
> For linux you'll have to clean the "local"
> table, too, or you will have problems, and
> anyway, I guess there are some other details. Just
> abstract this into a portable api for zebra.
>=20
> 3 zebra internals, see 1. Extend zebra protocol?
>=20
>=20
> Oh, and you want different routing processes (per VPN,
> at least, if not per interface), which isn't trivial
> with zebra at the moment, though it is possible,
> i've been told.
>=20
>=20
>  Afterward, mpls-linux will do all you want, no need to
> patch it, I guess.
>=20
>=20
> Disclaimer: I'm no expert at anything, this are just ideas
>   from my "a little knowledge and curiosity" standpoint.
>=20
>=20
> Have fun,
>  yon
>=20
>=20
>=20
>=20
> _______________________________________________
> mpls-linux-general mailing list
> mpl...@li...
> http://lists.sourceforge.net/lists/listinfo/mpls-linux-general

--=20
James R. Leu

Re: [mpls-linux-general] VPNs using MPLS-Linux/LDP-Portable

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

>  I have started on 3, it is a mess, doesn't do anything useful
> yet, as I have problems understanding ldp-portable (to be
> precise: I don't want to learn how ldp-portable works,
> need-to-know is my keyword here).

This would be great!  How can I help.  I can explain any of the ldp-portable
API for you, what needs to be provided to ldp-portable, and how things
need to be stored.

I have time to answer question, just not time to do the port
myself :-)

Jim
-- 
James R. Leu