mpls-linux-devel Mailing List for MPLS for Linux (Page 19)
Status: Beta
Brought to you by:
jleu
Menu
▾
▴
mpls-linux-devel — Mailig list for discussing the development of MPLS on Linux
You can subscribe to this list here.
| 2003 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(7) |
Dec
(8) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2004 |
Jan
(5) |
Feb
(73) |
Mar
(22) |
Apr
(21) |
May
|
Jun
|
Jul
(3) |
Aug
(5) |
Sep
(4) |
Oct
(4) |
Nov
(2) |
Dec
(6) |
| 2005 |
Jan
(5) |
Feb
|
Mar
(6) |
Apr
(11) |
May
(6) |
Jun
(5) |
Jul
(4) |
Aug
(1) |
Sep
(1) |
Oct
|
Nov
(9) |
Dec
(15) |
| 2006 |
Jan
(11) |
Feb
(7) |
Mar
(4) |
Apr
(1) |
May
(2) |
Jun
(2) |
Jul
(7) |
Aug
|
Sep
(8) |
Oct
(9) |
Nov
(10) |
Dec
(14) |
| 2007 |
Jan
(11) |
Feb
(9) |
Mar
(39) |
Apr
(7) |
May
(4) |
Jun
(2) |
Jul
(5) |
Aug
(6) |
Sep
(6) |
Oct
(1) |
Nov
(1) |
Dec
(8) |
| 2008 |
Jan
|
Feb
(13) |
Mar
(19) |
Apr
(11) |
May
(16) |
Jun
(6) |
Jul
(2) |
Aug
(4) |
Sep
|
Oct
(5) |
Nov
|
Dec
(16) |
| 2009 |
Jan
(13) |
Feb
(5) |
Mar
|
Apr
|
May
(11) |
Jun
(7) |
Jul
(3) |
Aug
|
Sep
(2) |
Oct
(8) |
Nov
(16) |
Dec
(15) |
| 2010 |
Jan
(6) |
Feb
(5) |
Mar
(1) |
Apr
(14) |
May
(42) |
Jun
(4) |
Jul
(1) |
Aug
(1) |
Sep
|
Oct
|
Nov
(4) |
Dec
(1) |
| 2011 |
Jan
(3) |
Feb
|
Mar
|
Apr
(7) |
May
(1) |
Jun
(2) |
Jul
(4) |
Aug
(19) |
Sep
(9) |
Oct
(13) |
Nov
(4) |
Dec
(3) |
| 2012 |
Jan
(2) |
Feb
(3) |
Mar
|
Apr
|
May
|
Jun
(11) |
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
(3) |
Dec
(2) |
| 2013 |
Jan
(4) |
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2014 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
(7) |
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
|
| 2015 |
Jan
(1) |
Feb
|
Mar
|
Apr
(2) |
May
|
Jun
(2) |
Jul
(2) |
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
(2) |
| 2016 |
Jan
(6) |
Feb
(2) |
Mar
(1) |
Apr
|
May
|
Jun
(2) |
Jul
|
Aug
(1) |
Sep
(1) |
Oct
|
Nov
|
Dec
|
| 2017 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(4) |
Dec
|
| 2021 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: <gsr...@al...> - 2007-02-26 22:41:02
|
Hi James! I've installed the revised RPMs for FC4. I got kernel panic after = rebooting the system that I solved by typing "enforcing=3D0" at = grub.conf. I have some problems with the wheel of the mouse or the USB = ports but in general it works right. I'm able to create MPLS static = configurations. In this version the "mpls" module has disappeared so I = only load "mpls4". I launch zebra, ospfd and ldpd but I make the whole = configuration by vtysh. OSPF works well but I can't put most of the ldpd = commands, in fact, the only one that appears with "show running-config" = is "mpls labelspace 0" in the corresponding interface, Neither "mpls = ldp" nor "mpls ip". Are these problems solved in FC5? If that's it I = would like to work with FC5. Thanks, Gonzalo. I updated the FC4 kernel RPMs. Can you please try them? On Mon, Feb 19, 2007 at 11:47:24AM +0100, Sienes Rodr?guez Gonzalo = wrote: > Hi James: >=20 > I'm trying to install your new software for FC4 but I have some = problems. > When I try to install the kernel-2.6.18 from Source Forge for FC4 it = makes me install lots of RPMs, most of them can be installed by "yum = update" but I can't find the libraries libc.so.6(GLIBC_2.4) and = libpcap.so.0.9.3 anywhere for FC4. I search for them and people talks = about 64 architecture and I'm working with Intel(R) Pentium(R) D CPU = 3.00GHz. Could you provide them to me? Witch OS are you using? Should I = install FC5? =20 >=20 > Thanks in advance. >=20 > P.D.: These are the outputs I get. >=20 > [root@PE3 mpls-linux-1.955]# rpm -ivh = kernel-2.6.18-1.2257.fc4.mpls.1.955.i686.rpm > error: Failed dependencies: > mkinitrd >=3D 4.2.21-1 is needed by = kernel-2.6.18-1.2257.fc4.mpls.1.955.i686 > isdn4k-utils < 3.2-32 conflicts with = kernel-2.6.18-1.2257.fc4.mpls.1.955.i686 > kudzu < 1.2.5 conflicts with = kernel-2.6.18-1.2257.fc4.mpls.1.955.i686 >=20 > [root@PE3 Requeridos]# rpm -ivh mkinitrd-4.2.21-1.i386.rpm > error: Failed dependencies: > libc.so.6(GLIBC_2.4) is needed by mkinitrd-4.2.21-1.i386 >=20 > [root@PE3 Requeridos]# rpm -ivh isdn4k-utils-3.2-32.i386.rpm > error: Failed dependencies: > libc.so.6(GLIBC_2.4) is needed by isdn4k-utils-3.2-32.i386 > libpcap.so.0.9.3 is needed by isdn4k-utils-3.2-32.i386 >=20 --=20 James R. Leu jl...@mi... |
|
From: James R. L. <jl...@mi...> - 2007-02-26 14:11:58
|
On Mon, Feb 26, 2007 at 11:32:15AM +0100, Sienes Rodr?guez Gonzalo wrote: > Hi James! >=20 > I've installed the revised RPMs for FC4. I got kernel panic after rebooti= ng the system that I solved by typing "enforcing=3D0" at grub.conf. I have = some problems with the wheel of the mouse or the USB ports but in general i= t works right. I'm able to create MPLS static configurations. In this versi= on the "mpls" module has disappeared so I only load "mpls4". I launch zebra= , ospfd and ldpd but I make the whole configuration by vtysh. OSPF works we= ll but I can't put most of the ldpd commands, in fact, the only one that ap= pears with "show running-config" is "mpls labelspace 0" in the correspondin= g interface, Neither "mpls ldp" nor "mpls ip". Are these problems solved in= FC5? If that's it I would like to work with FC5. Can you manually create MPLS segments with the 'mpls' command? I'll look into the issue with no ldp command in vtysh. > Thanks, >=20 > Gonzalo. >=20 > I updated the FC4 kernel RPMs. Can you please try them? >=20 > On Mon, Feb 19, 2007 at 11:47:24AM +0100, Sienes Rodr?guez Gonzalo wrote: > > Hi James: > >=20 > > I'm trying to install your new software for FC4 but I have some problem= s. > > When I try to install the kernel-2.6.18 from Source Forge for FC4 it ma= kes me install lots of RPMs, most of them can be installed by "yum update" = but I can't find the libraries libc.so.6(GLIBC_2.4) and libpcap.so.0.9.3 an= ywhere for FC4. I search for them and people talks about 64 architecture an= d I'm working with Intel(R) Pentium(R) D CPU 3.00GHz. Could you provide the= m to me? Witch OS are you using? Should I install FC5? =20 > >=20 > > Thanks in advance. > >=20 > > P.D.: These are the outputs I get. > >=20 > > [root@PE3 mpls-linux-1.955]# rpm -ivh kernel-2.6.18-1.2257.fc4.mpls.1.9= 55.i686.rpm > > error: Failed dependencies: > > mkinitrd >=3D 4.2.21-1 is needed by kernel-2.6.18-1.2257.fc4.mp= ls.1.955.i686 > > isdn4k-utils < 3.2-32 conflicts with kernel-2.6.18-1.2257.fc4.m= pls.1.955.i686 > > kudzu < 1.2.5 conflicts with kernel-2.6.18-1.2257.fc4.mpls.1.95= 5.i686 > >=20 > > [root@PE3 Requeridos]# rpm -ivh mkinitrd-4.2.21-1.i386.rpm > > error: Failed dependencies: > > libc.so.6(GLIBC_2.4) is needed by mkinitrd-4.2.21-1.i386 > >=20 > > [root@PE3 Requeridos]# rpm -ivh isdn4k-utils-3.2-32.i386.rpm > > error: Failed dependencies: > > libc.so.6(GLIBC_2.4) is needed by isdn4k-utils-3.2-32.i386 > > libpcap.so.0.9.3 is needed by isdn4k-utils-3.2-32.i386 > >=20 >=20 >=20 >=20 > --=20 > James R. Leu > jl...@mi... >=20 >=20 >=20 --=20 James R. Leu jl...@mi... |
|
From: James R. L. <jl...@mi...> - 2007-02-22 03:50:11
|
I updated the FC4 kernel RPMs. Can you please try them? On Mon, Feb 19, 2007 at 11:47:24AM +0100, Sienes Rodr?guez Gonzalo wrote: > Hi James: >=20 > I'm trying to install your new software for FC4 but I have some problems. > When I try to install the kernel-2.6.18 from Source Forge for FC4 it make= s me install lots of RPMs, most of them can be installed by "yum update" bu= t I can't find the libraries libc.so.6(GLIBC_2.4) and libpcap.so.0.9.3 anyw= here for FC4. I search for them and people talks about 64 architecture and = I'm working with Intel(R) Pentium(R) D CPU 3.00GHz. Could you provide them = to me? Witch OS are you using? Should I install FC5? =20 >=20 > Thanks in advance. >=20 > P.D.: These are the outputs I get. >=20 > [root@PE3 mpls-linux-1.955]# rpm -ivh kernel-2.6.18-1.2257.fc4.mpls.1.955= .i686.rpm > error: Failed dependencies: > mkinitrd >=3D 4.2.21-1 is needed by kernel-2.6.18-1.2257.fc4.mpls= .1.955.i686 > isdn4k-utils < 3.2-32 conflicts with kernel-2.6.18-1.2257.fc4.mpl= s.1.955.i686 > kudzu < 1.2.5 conflicts with kernel-2.6.18-1.2257.fc4.mpls.1.955.= i686 >=20 > [root@PE3 Requeridos]# rpm -ivh mkinitrd-4.2.21-1.i386.rpm > error: Failed dependencies: > libc.so.6(GLIBC_2.4) is needed by mkinitrd-4.2.21-1.i386 >=20 > [root@PE3 Requeridos]# rpm -ivh isdn4k-utils-3.2-32.i386.rpm > error: Failed dependencies: > libc.so.6(GLIBC_2.4) is needed by isdn4k-utils-3.2-32.i386 > libpcap.so.0.9.3 is needed by isdn4k-utils-3.2-32.i386 >=20 --=20 James R. Leu jl...@mi... |
|
From: James R. L. <jl...@mi...> - 2007-02-19 13:54:21
|
My main development plateform is FC5 on i386. The FC4 RPMs I've released are just FC5 RPMs compiled in a FC4 environment. You're best bet is to use FC5 for testing/development of mpls-linux. With that being said, I will still try to fix the FC4 RPMs. On Mon, Feb 19, 2007 at 11:47:24AM +0100, Sienes Rodr?guez Gonzalo wrote: > Hi James: >=20 > I'm trying to install your new software for FC4 but I have some problems. > When I try to install the kernel-2.6.18 from Source Forge for FC4 it make= s me install lots of RPMs, most of them can be installed by "yum update" bu= t I can't find the libraries libc.so.6(GLIBC_2.4) and libpcap.so.0.9.3 anyw= here for FC4. I search for them and people talks about 64 architecture and = I'm working with Intel(R) Pentium(R) D CPU 3.00GHz. Could you provide them = to me? Witch OS are you using? Should I install FC5? =20 >=20 > Thanks in advance. >=20 > P.D.: These are the outputs I get. >=20 > [root@PE3 mpls-linux-1.955]# rpm -ivh kernel-2.6.18-1.2257.fc4.mpls.1.955= .i686.rpm > error: Failed dependencies: > mkinitrd >=3D 4.2.21-1 is needed by kernel-2.6.18-1.2257.fc4.mpls= .1.955.i686 > isdn4k-utils < 3.2-32 conflicts with kernel-2.6.18-1.2257.fc4.mpl= s.1.955.i686 > kudzu < 1.2.5 conflicts with kernel-2.6.18-1.2257.fc4.mpls.1.955.= i686 >=20 > [root@PE3 Requeridos]# rpm -ivh mkinitrd-4.2.21-1.i386.rpm > error: Failed dependencies: > libc.so.6(GLIBC_2.4) is needed by mkinitrd-4.2.21-1.i386 >=20 > [root@PE3 Requeridos]# rpm -ivh isdn4k-utils-3.2-32.i386.rpm > error: Failed dependencies: > libc.so.6(GLIBC_2.4) is needed by isdn4k-utils-3.2-32.i386 > libpcap.so.0.9.3 is needed by isdn4k-utils-3.2-32.i386 >=20 >=20 > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share y= our > opinions on IT & business topics through brief surveys-and earn cash > http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3D= DEVDEV > _______________________________________________ > mpls-linux-devel mailing list > mpl...@li... > https://lists.sourceforge.net/lists/listinfo/mpls-linux-devel --=20 James R. Leu jl...@mi... |
|
From: <gsr...@al...> - 2007-02-19 11:00:01
|
Hi James:
I'm trying to install your new software for FC4 but I have some =
problems.
When I try to install the kernel-2.6.18 from Source Forge for FC4 it =
makes me install lots of RPMs, most of them can be installed by "yum =
update" but I can't find the libraries libc.so.6(GLIBC_2.4) and =
libpcap.so.0.9.3 anywhere for FC4. I search for them and people talks =
about 64 architecture and I'm working with Intel(R) Pentium(R) D CPU =
3.00GHz. Could you provide them to me? Witch OS are you using? Should I =
install FC5? =20
Thanks in advance.
P.D.: These are the outputs I get.
[root@PE3 mpls-linux-1.955]# rpm -ivh =
kernel-2.6.18-1.2257.fc4.mpls.1.955.i686.rpm
error: Failed dependencies:
mkinitrd >=3D 4.2.21-1 is needed by =
kernel-2.6.18-1.2257.fc4.mpls.1.955.i686
isdn4k-utils < 3.2-32 conflicts with =
kernel-2.6.18-1.2257.fc4.mpls.1.955.i686
kudzu < 1.2.5 conflicts with =
kernel-2.6.18-1.2257.fc4.mpls.1.955.i686
[root@PE3 Requeridos]# rpm -ivh mkinitrd-4.2.21-1.i386.rpm
error: Failed dependencies:
libc.so.6(GLIBC_2.4) is needed by mkinitrd-4.2.21-1.i386
[root@PE3 Requeridos]# rpm -ivh isdn4k-utils-3.2-32.i386.rpm
error: Failed dependencies:
libc.so.6(GLIBC_2.4) is needed by isdn4k-utils-3.2-32.i386
libpcap.so.0.9.3 is needed by isdn4k-utils-3.2-32.i386
|
|
From: <pra...@gm...> - 2007-02-17 20:01:54
|
hey, go here and we both get a free video ipod pretty pretty please :) http://www.getitfree.net/xbhjwroshc http://www.getitfree.net/xbhjwroshc This was sent by pra...@gm... via GetItFree, Box 8156, San Jose CA 95155 Visit this page http://www.getitfree.net/index.php?target=unsubscribe&u=bhjwroshc&mid=1171742496749576 to unsubscribe from all future GetItFree.net email |
|
From: James R. L. <jl...@mi...> - 2007-02-12 13:43:27
|
The AMD classification is incorrrect. I will fix this. On Mon, Feb 12, 2007 at 11:03:12AM +0100, Sienes Rodr?guez Gonzalo wrote: > Hi James! >=20 > Now that I've finished my exams I wish to take up working with your MPLS-= Linux project. I had some problems with the software from your repository. = If you could remember I work with FC4 and teh following RPMs: >=20 > [root@PE2 ~]# rpm -qa | grep mpls > iproute-2.6.11-1_mpls_90.1162552079 > quagga-0.99.6-2007010801_mpls_0.1168246002 > iptables-1.3.0-2_mpls_1.950d > kernel-2.6.15-1.1831_FC4mpls_1.950 > glibc-kernheaders-3.0-5.2_mpls0.1162999872 > quagga-devel-0.99.6-2007010801_mpls_0.1168246002 > quagga-contrib-0.99.6-2007010801_mpls_0.1168246002 > kernel-devel-2.6.15-1.1831_FC4mpls_1.950 > quagga-debuginfo-0.99.6-2007010801_mpls_0.1168246002 >=20 > Now that you have released new versions at Source Forge I wonder if I sho= uld keep on working with my current scenario or begin even installing the n= ew kernel. However, it seems that the new kernel RPMs are only for AMD64 wh= ile I have Intel(R) Pentium(R) D CPU 3.00GHz. I've only seen one kernel RPM= for "none" architecture but none kernel .src.rpm to get the source code. W= hat should I do? >=20 > Thanks in advance, >=20 > Gonzalo. >=20 > ------------------------------------------------------------------------- > Using Tomcat but need to do more? Need to support web services, security? > Get stuff done quickly with pre-integrated technology to make your job ea= sier. > Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo > http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D120709&bid=3D263057&dat= =3D121642 > _______________________________________________ > mpls-linux-devel mailing list > mpl...@li... > https://lists.sourceforge.net/lists/listinfo/mpls-linux-devel --=20 James R. Leu jl...@mi... |
|
From: <gsr...@al...> - 2007-02-12 10:05:54
|
Hi James! Now that I've finished my exams I wish to take up working with your = MPLS-Linux project. I had some problems with the software from your = repository. If you could remember I work with FC4 and teh following = RPMs: [root@PE2 ~]# rpm -qa | grep mpls iproute-2.6.11-1_mpls_90.1162552079 quagga-0.99.6-2007010801_mpls_0.1168246002 iptables-1.3.0-2_mpls_1.950d kernel-2.6.15-1.1831_FC4mpls_1.950 glibc-kernheaders-3.0-5.2_mpls0.1162999872 quagga-devel-0.99.6-2007010801_mpls_0.1168246002 quagga-contrib-0.99.6-2007010801_mpls_0.1168246002 kernel-devel-2.6.15-1.1831_FC4mpls_1.950 quagga-debuginfo-0.99.6-2007010801_mpls_0.1168246002 Now that you have released new versions at Source Forge I wonder if I = should keep on working with my current scenario or begin even installing = the new kernel. However, it seems that the new kernel RPMs are only for = AMD64 while I have Intel(R) Pentium(R) D CPU 3.00GHz. I've only seen one = kernel RPM for "none" architecture but none kernel .src.rpm to get the = source code. What should I do? Thanks in advance, Gonzalo. |
|
From: James R. L. <jl...@mi...> - 2007-01-19 15:15:22
|
What glibc-kernheaders are you using? If you are using the ones from sourceforge with quagga-mpls from my tree, you will produce an invalid binary. I suggest building a glibc-kernheaders RPM from my development tree. As far as build options, take a look at the quagga.spec file in quagga-mpls/redhat for details about how I compile quagga-mpls (alternatively you could use the 'make-rpm-jleu' script to build a quagga-mpls RPM. AS far as commands not showing up in vtysh, there are a multitude of possible reasons for this. I would suggest worrying about vtysh after you have gotten the rest of the system to work. Please note that I have added some commands to ldpd to start the process of implementing Ethernet over MPLS. If you are planning on working on this as well, I'm sure we can work out a quick development plan to make sure the= re is no duplication of work. On Fri, Jan 19, 2007 at 12:25:45PM +0530, Sajeesh P N wrote: >=20 > Hi, > We are doing pseudowire extensions with the mpls-linux code. We > took the latest mpls-linux kernel, ldp-portable and quagga. But when we > compile the code, changes made in the LDP code is not reflected. We have > installed the mpls enabled kernel and installed all other rpms (like > iptables, ebtables... etc). Below are the steps followed: >=20 > 1) ./configure --enable-vtysh --enable-mpls --enable-netlink > 2) make >=20 > After "make", the ldpd binary file is not created in the ldpd > directory. We have to do separate "make" in the ldpd directory for creat= ing > it. But the changes are not reflected in the "vtysh" command prompt. >=20 > Is there any other way to compile ldp, so that ldp and vtysh > communication can happen ? We tried with "telnet 127.0.0.1 <PORT>", but t= he > "mpls ldp" command is throwing an exception as "Connection closed by remo= te > host". >=20 >=20 > Thanks and Regards, > Sajeesh P.N. >=20 >=20 > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share y= our > opinions on IT & business topics through brief surveys - and earn cash > http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3D= DEVDEV > _______________________________________________ > mpls-linux-devel mailing list > mpl...@li... > https://lists.sourceforge.net/lists/listinfo/mpls-linux-devel --=20 James R. Leu jl...@mi... |
|
From: Sajeesh P N <saj...@ta...> - 2007-01-19 07:04:18
|
Hi,
We are doing pseudowire extensions with the mpls-linux code. We
took the latest mpls-linux kernel, ldp-portable and quagga. But when we
compile the code, changes made in the LDP code is not reflected. We have
installed the mpls enabled kernel and installed all other rpms (like
iptables, ebtables... etc). Below are the steps followed:
1) ./configure --enable-vtysh --enable-mpls --enable-netlink
2) make
After "make", the ldpd binary file is not created in the ldpd
directory. We have to do separate "make" in the ldpd directory for creating
it. But the changes are not reflected in the "vtysh" command prompt.
Is there any other way to compile ldp, so that ldp and vtysh
communication can happen ? We tried with "telnet 127.0.0.1 <PORT>", but the
"mpls ldp" command is throwing an exception as "Connection closed by remote
host".
Thanks and Regards,
Sajeesh P.N.
|
|
From: Sajeesh P N <saj...@ta...> - 2007-01-19 06:54:50
|
Hi,
We are doing pseudowire extensions with the mpls-linux code. We
took the latest mpls-linux kernel, ldp-portable and quagga. But when we
compile the code, changes made in the LDP code is not reflected. We have
installed the mpls enabled kernel and installed all other rpms (like
iptables, ebtables... etc). Below are the steps followed:
1) ./configure --enable-vtysh --enable-mpls --enable-netlink
2) make
After "make", the ldpd binary file is not created in the ldpd
directory. We have to do separate "make" in the ldpd directory for creating
it. But the changes are not reflected in the "vtysh" command prompt.
Is there any other way to compile ldp, so that ldp and vtysh
communication can happen ? We tried with "telnet 127.0.0.1 <PORT>", but the
"mpls ldp" command is throwing an exception as "Connection closed by remote
host".
Thanks and Regards,
Sajeesh P.N.
|
|
From: tommy <ema...@fr...> - 2007-01-16 20:32:44
|
I am using FC 4 with the 2.6.15.1 kernel from sourceforge. When I find some time I will see if I can setup the same config and try what you adviced. Regards, tommy James R. Leu wrote: > I've added tommy <ema...@fr...> to the CC list because he is seeing the > same issues as you are Gonzalo. > > So it looks like configuring the interfaces via vtysh had no affect. The > last thing that differs between your setup and mine is the kernel. > I assume your using fedora. Are you using fedora 4? If so I will > try building an up-to-date FC4 kernel with the latest patches. > (tommy what kernel and distribution are you using?) > > In the meantime. Lets dig into the zebra/kernel communication a little bit. > > Here is the debugging I have configured: > > log file /var/log/monkey2 > debug zebra kernel > > In addition lets try a very controlled test and see is that yields a > difference result: > > - Add the above config to your LERs > - Remove all MPLS/LDP commands from the config > - Save the configs > - Stop the OSPF/LDP/zebra daemons > - Clean out all MPLS entities with the 'mpls' utility > - Restart the OSPF/LDP/zebra daemons > - Wait for OSPF to converge > - Add the MPLS/LDP config > > Once LDP establishes, send me the result of the show commands, and the > relevant output from the log file you configure. (preferably different log > files for each node) > > Hopefully this will help me figure out where the problem is occurring. > > On Fri, Jan 12, 2007 at 05:35:03PM +0100, Sienes Rodr?guez Gonzalo wrote: > >> Hi James, thanks for your answer. >> >> [root@PE2 ~]# rpm -qa | grep mpls | sort >> glibc-kernheaders-3.0-5.2_mpls0.1162999872 >> iproute-2.6.11-1_mpls_90.1162552079 >> iptables-1.3.0-2_mpls_1.950d >> kernel-2.6.15-1.1831_FC4mpls_1.950 >> kernel-devel-2.6.15-1.1831_FC4mpls_1.950 >> quagga-0.99.6-2007010801_mpls_0.1168246002 >> quagga-contrib-0.99.6-2007010801_mpls_0.1168246002 >> quagga-debuginfo-0.99.6-2007010801_mpls_0.1168246002 >> quagga-devel-0.99.6-2007010801_mpls_0.1168246002 >> >> I tried what you told me in this scenario: >> >> 12.0.0.1 .1 10.0.0.0/24 .2 11.0.0.1 >> --------------PE1---------------------PE2-------------- >> eth1 | eth0 eth1 | eth0 >> | | >> dummy0 (17.1) dummy0 (15.1) >> >> >> These are all the configuration parameters I type in by vtysh (on PE2): >> >> ! >> hostname PE2 >> ! >> service integrated-vtysh-config >> ! >> debug zebra events >> debug zebra kernel >> ! >> password root >> ! >> interface dummy0 >> ip address 15.0.0.1/32 >> ipv6 nd suppress-ra >> ! >> interface eth0 >> ip address 11.0.0.1/32 >> ipv6 nd suppress-ra >> ! >> interface eth1 >> ip address 10.0.0.2/32 >> ipv6 nd suppress-ra >> mpls ip >> mpls labelspace 0 >> ! >> interface lo >> ! >> interface sit0 >> ipv6 nd suppress-ra >> ! >> mpls ldp >> egress connected >> ! >> router ospf >> passive-interface dummy >> network 10.0.0.0/24 area 0.0.0.0 >> network 11.0.0.0/24 area 0.0.0.0 >> network 15.0.0.0/24 area 0.0.0.0 >> ! >> ip forwarding >> ! >> line vty >> ! >> >> And these are the outputs related to mpls and ldp: >> >> PE2# sh mpls for >> Insegments: >> Lbl Spc Label Owner >> 0 10004 ldp >> 0 10005 ldp >> 0 10006 ldp >> 0 10007 ldp >> Total 4 >> >> Outsegments: >> Interface Label Next Hop Owner >> eth1 10003 10.0.0.1 ldp >> Total 1 >> >> Cross Connects: >> >> Total 0 >> >> PE2# sh mpls for >> Insegments: >> Lbl Spc Label Owner >> 0 10004 ldp >> 0 10005 ldp >> 0 10006 ldp >> 0 10007 ldp >> Total 4 >> >> Outsegments: >> Interface Label Next Hop Owner >> eth1 10003 10.0.0.1 ldp >> Total 1 >> >> Cross Connects: >> >> Total 0 >> >> PE2# sh ip route >> Codes: K - kernel route, C - connected, S - static, R - RIP, O - OSPF, >> I - ISIS, B - BGP, > - selected route, * - FIB route >> >> K>* 0.0.0.0/0 via 172.29.16.1, eth0 >> O 10.0.0.0/24 [110/10] is directly connected, eth1, 00:18:30 >> C>* 10.0.0.0/24 is directly connected, eth1 >> C>* 10.0.0.2/32 is directly connected, eth1 >> O 11.0.0.1/32 [110/10] is directly connected, eth0, 00:18:20 >> C>* 11.0.0.1/32 is directly connected, eth0 >> O>* 12.0.0.0/24 [110/20] via 10.0.0.1, eth1, 00:12:07 >> C>* 127.0.0.0/8 is directly connected, lo >> K>* 169.254.0.0/16 is directly connected, eth1 >> C>* 172.29.16.0/22 is directly connected, eth0 >> >> PE2# sh ldp >> LSR-ID: 11.0.0.1 Admin State: ENABLED >> Transport Address: 0.0.0.0 >> Control Mode: ORDERED Repair Mode: GLOBAL >> Propogate Release: TRUE Label Merge: TRUE >> Retention Mode: LIBERAL Loop Detection Mode: NONE >> TTL-less-domain: FALSE >> Local TCP Port: 646 Local UDP Port: 646 >> Keep-alive Time: 45 Keep-alive Interval: 15 >> Hello Time: 15 Hello Interval: 5 >> >> PE2# sh ldp add >> Addr: 1 ac1d113c >> 0 >> 0 >> 1 >> Addr: 2 0b000001 >> 0 >> 0 >> 1 >> Addr: 3 0a000002 >> 0 >> 0 >> 2 >> Addr: 4 ac1d1001 >> 0 >> 1 >> 0 >> Addr: 5 0a000001 >> 2 >> 7 >> 0 >> Addr: 8 0c000001 >> 2 >> 0 >> 0 >> Addr: 9 0d000001 >> 2 >> 0 >> 161461200 >> >> PE2# sh ldp neig >> Peer LDP Ident: 12.0.0.1:0; Local LDP Ident: 11.0.0.1:0 >> TCP connection: 10.0.0.2.33193 - 10.0.0.1.646 >> State: OPERATIONAL; Msgs sent/recv: 17/43; UNSOLICITED >> Up time: 00:02:04 >> LDP discovery sources: >> eth1 >> Addresses bound to peer: >> 10.0.0.1 12.0.0.1 >> >> PE2# sh ldp disc >> >> Local LSR Identifier: 11.0.0.1 >> >> Interface Discovery Sources: >> eth1: xmit/recv >> LDP Id: 12.0.0.1:0 >> >> Targeted Discovery Sources: >> No configured peers >> >> PE2# sh ldp fec >> FEC: 1 0.0.0.0/0 >> 1 172.29.16.1 0 >> FEC: 2 169.254.0.0/16 >> 2 0.0.0.0 0 >> FEC: 3 10.0.0.0/24 >> 3 0.0.0.0 1 >> FEC: 4 10.0.0.2/32 >> 4 0.0.0.0 1 >> FEC: 5 11.0.0.1/32 >> 5 0.0.0.0 1 >> FEC: 6 172.29.16.0/22 >> 6 0.0.0.0 1 >> FEC: 9 10.0.0.1/32 >> FEC: 10 12.0.0.1/32 >> >> PE2# sh ldp ses >> 2 1.0.0.0 45 OPERATIONAL >> 10.0.0.1 >> 12.0.0.1 >> 13.0.0.1 >> >> The problem persists. I'm not able to send labeled ICMP packets between ldp peers, any idea? >> >> [root@PE2 ~]# mpls ilm >> ILM entry label gen 10007 labelspace 0 proto ipv4 >> pop peek (0 bytes, 0 pkts) >> ILM entry label gen 10006 labelspace 0 proto ipv4 >> pop peek (0 bytes, 0 pkts) >> ILM entry label gen 10005 labelspace 0 proto ipv4 >> pop peek (0 bytes, 0 pkts) >> ILM entry label gen 10004 labelspace 0 proto ipv4 >> pop peek (0 bytes, 0 pkts) >> >> [root@PE2 ~]# mpls nhlfe >> NHLFE entry key 0x00000003 mtu 1496 propagate_ttl >> push gen 10003 set eth1 ipv4 10.0.0.1 (0 bytes, 0 pkts) >> >> Thanks for your time and effort, >> >> Gonzalo. >> >> >> >> ------------------------------------------------------------------------- >> Take Surveys. Earn Cash. Influence the Future of IT >> Join SourceForge.net's Techsay panel and you'll get the chance to share your >> opinions on IT & business topics through brief surveys - and earn cash >> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV >> _______________________________________________ >> mpls-linux-devel mailing list >> mpl...@li... >> https://lists.sourceforge.net/lists/listinfo/mpls-linux-devel >> > > |
|
From: James R. L. <jl...@mi...> - 2007-01-16 02:02:43
|
I've added tommy <ema...@fr...> to the CC list because he is seeing =
the
same issues as you are Gonzalo.
So it looks like configuring the interfaces via vtysh had no affect. The
last thing that differs between your setup and mine is the kernel.
I assume your using fedora. Are you using fedora 4? If so I will
try building an up-to-date FC4 kernel with the latest patches.
(tommy what kernel and distribution are you using?)
In the meantime. Lets dig into the zebra/kernel communication a little bit.
Here is the debugging I have configured:
log file /var/log/monkey2
debug zebra kernel
In addition lets try a very controlled test and see is that yields a
difference result:
- Add the above config to your LERs
- Remove all MPLS/LDP commands from the config
- Save the configs
- Stop the OSPF/LDP/zebra daemons
- Clean out all MPLS entities with the 'mpls' utility
- Restart the OSPF/LDP/zebra daemons
- Wait for OSPF to converge
- Add the MPLS/LDP config
Once LDP establishes, send me the result of the show commands, and the
relevant output from the log file you configure. (preferably different log
files for each node)
Hopefully this will help me figure out where the problem is occurring.
On Fri, Jan 12, 2007 at 05:35:03PM +0100, Sienes Rodr?guez Gonzalo wrote:
> Hi James, thanks for your answer.
>=20
> [root@PE2 ~]# rpm -qa | grep mpls | sort
> glibc-kernheaders-3.0-5.2_mpls0.1162999872
> iproute-2.6.11-1_mpls_90.1162552079
> iptables-1.3.0-2_mpls_1.950d
> kernel-2.6.15-1.1831_FC4mpls_1.950
> kernel-devel-2.6.15-1.1831_FC4mpls_1.950
> quagga-0.99.6-2007010801_mpls_0.1168246002
> quagga-contrib-0.99.6-2007010801_mpls_0.1168246002
> quagga-debuginfo-0.99.6-2007010801_mpls_0.1168246002
> quagga-devel-0.99.6-2007010801_mpls_0.1168246002
>=20
> I tried what you told me in this scenario:=20
>=20
> 12.0.0.1 .1 10.0.0.0/24 .2 11.0.0.1
> --------------PE1---------------------PE2--------------
> eth1 | eth0 eth1 | eth0
> | |
> dummy0 (17.1) dummy0 (15.1)=09
>=20
>=20
> These are all the configuration parameters I type in by vtysh (on PE2):
>=20
> !
> hostname PE2
> !
> service integrated-vtysh-config
> !
> debug zebra events
> debug zebra kernel
> !
> password root
> !
> interface dummy0
> ip address 15.0.0.1/32
> ipv6 nd suppress-ra
> !
> interface eth0
> ip address 11.0.0.1/32
> ipv6 nd suppress-ra
> !
> interface eth1
> ip address 10.0.0.2/32
> ipv6 nd suppress-ra
> mpls ip
> mpls labelspace 0
> !
> interface lo
> !
> interface sit0
> ipv6 nd suppress-ra
> !
> mpls ldp
> egress connected
> !
> router ospf
> passive-interface dummy
> network 10.0.0.0/24 area 0.0.0.0
> network 11.0.0.0/24 area 0.0.0.0
> network 15.0.0.0/24 area 0.0.0.0
> !
> ip forwarding
> !
> line vty
> !
>=20
> And these are the outputs related to mpls and ldp:
>=20
> PE2# sh mpls for
> Insegments:
> Lbl Spc Label Owner
> 0 10004 ldp
> 0 10005 ldp
> 0 10006 ldp
> 0 10007 ldp
> Total 4
>=20
> Outsegments:
> Interface Label Next Hop Owner
> eth1 10003 10.0.0.1 ldp
> Total 1
>=20
> Cross Connects:
>=20
> Total 0
>=20
> PE2# sh mpls for
> Insegments:
> Lbl Spc Label Owner
> 0 10004 ldp
> 0 10005 ldp
> 0 10006 ldp
> 0 10007 ldp
> Total 4
>=20
> Outsegments:
> Interface Label Next Hop Owner
> eth1 10003 10.0.0.1 ldp
> Total 1
>=20
> Cross Connects:
>=20
> Total 0
>=20
> PE2# sh ip route
> Codes: K - kernel route, C - connected, S - static, R - RIP, O - OSPF,
> I - ISIS, B - BGP, > - selected route, * - FIB route
>=20
> K>* 0.0.0.0/0 via 172.29.16.1, eth0
> O 10.0.0.0/24 [110/10] is directly connected, eth1, 00:18:30
> C>* 10.0.0.0/24 is directly connected, eth1
> C>* 10.0.0.2/32 is directly connected, eth1
> O 11.0.0.1/32 [110/10] is directly connected, eth0, 00:18:20
> C>* 11.0.0.1/32 is directly connected, eth0
> O>* 12.0.0.0/24 [110/20] via 10.0.0.1, eth1, 00:12:07
> C>* 127.0.0.0/8 is directly connected, lo
> K>* 169.254.0.0/16 is directly connected, eth1
> C>* 172.29.16.0/22 is directly connected, eth0
>=20
> PE2# sh ldp
> LSR-ID: 11.0.0.1 Admin State: ENABLED
> Transport Address: 0.0.0.0
> Control Mode: ORDERED Repair Mode: GLOBAL
> Propogate Release: TRUE Label Merge: TRUE
> Retention Mode: LIBERAL Loop Detection Mode: NONE
> TTL-less-domain: FALSE
> Local TCP Port: 646 Local UDP Port: 646
> Keep-alive Time: 45 Keep-alive Interval: 15
> Hello Time: 15 Hello Interval: 5
>=20
> PE2# sh ldp add
> Addr: 1 ac1d113c
> 0
> 0
> 1
> Addr: 2 0b000001
> 0
> 0
> 1
> Addr: 3 0a000002
> 0
> 0
> 2
> Addr: 4 ac1d1001
> 0
> 1
> 0
> Addr: 5 0a000001
> 2
> 7
> 0
> Addr: 8 0c000001
> 2
> 0
> 0
> Addr: 9 0d000001
> 2
> 0
> 161461200
>=20
> PE2# sh ldp neig
> Peer LDP Ident: 12.0.0.1:0; Local LDP Ident: 11.0.0.1:0
> TCP connection: 10.0.0.2.33193 - 10.0.0.1.646
> State: OPERATIONAL; Msgs sent/recv: 17/43; UNSOLICITED
> Up time: 00:02:04
> LDP discovery sources:
> eth1
> Addresses bound to peer:
> 10.0.0.1 12.0.0.1
>=20
> PE2# sh ldp disc
>=20
> Local LSR Identifier: 11.0.0.1
>=20
> Interface Discovery Sources:
> eth1: xmit/recv
> LDP Id: 12.0.0.1:0
>=20
> Targeted Discovery Sources:
> No configured peers
>=20
> PE2# sh ldp fec
> FEC: 1 0.0.0.0/0
> 1 172.29.16.1 0
> FEC: 2 169.254.0.0/16
> 2 0.0.0.0 0
> FEC: 3 10.0.0.0/24
> 3 0.0.0.0 1
> FEC: 4 10.0.0.2/32
> 4 0.0.0.0 1
> FEC: 5 11.0.0.1/32
> 5 0.0.0.0 1
> FEC: 6 172.29.16.0/22
> 6 0.0.0.0 1
> FEC: 9 10.0.0.1/32
> FEC: 10 12.0.0.1/32
>=20
> PE2# sh ldp ses
> 2 1.0.0.0 45 OPERATIONAL
> 10.0.0.1
> 12.0.0.1
> 13.0.0.1
>=20
> The problem persists. I'm not able to send labeled ICMP packets between l=
dp peers, any idea?
>=20
> [root@PE2 ~]# mpls ilm
> ILM entry label gen 10007 labelspace 0 proto ipv4
> pop peek (0 bytes, 0 pkts)
> ILM entry label gen 10006 labelspace 0 proto ipv4
> pop peek (0 bytes, 0 pkts)
> ILM entry label gen 10005 labelspace 0 proto ipv4
> pop peek (0 bytes, 0 pkts)
> ILM entry label gen 10004 labelspace 0 proto ipv4
> pop peek (0 bytes, 0 pkts)
>=20
> [root@PE2 ~]# mpls nhlfe
> NHLFE entry key 0x00000003 mtu 1496 propagate_ttl
> push gen 10003 set eth1 ipv4 10.0.0.1 (0 bytes, 0 pkts)
>=20
> Thanks for your time and effort,
>=20
> Gonzalo.
>=20
>=20
>=20
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share y=
our
> opinions on IT & business topics through brief surveys - and earn cash
> http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3D=
DEVDEV
> _______________________________________________
> mpls-linux-devel mailing list
> mpl...@li...
> https://lists.sourceforge.net/lists/listinfo/mpls-linux-devel
--=20
James R. Leu
jl...@mi...
|
|
From: <gsr...@al...> - 2007-01-12 16:38:00
|
Hi James, thanks for your answer.
[root@PE2 ~]# rpm -qa | grep mpls | sort
glibc-kernheaders-3.0-5.2_mpls0.1162999872
iproute-2.6.11-1_mpls_90.1162552079
iptables-1.3.0-2_mpls_1.950d
kernel-2.6.15-1.1831_FC4mpls_1.950
kernel-devel-2.6.15-1.1831_FC4mpls_1.950
quagga-0.99.6-2007010801_mpls_0.1168246002
quagga-contrib-0.99.6-2007010801_mpls_0.1168246002
quagga-debuginfo-0.99.6-2007010801_mpls_0.1168246002
quagga-devel-0.99.6-2007010801_mpls_0.1168246002
I tried what you told me in this scenario:=20
12.0.0.1 .1 10.0.0.0/24 .2 11.0.0.1
--------------PE1---------------------PE2--------------
eth1 | eth0 eth1 | eth0
| |
dummy0 (17.1) dummy0 (15.1)=09
These are all the configuration parameters I type in by vtysh (on PE2):
!
hostname PE2
!
service integrated-vtysh-config
!
debug zebra events
debug zebra kernel
!
password root
!
interface dummy0
ip address 15.0.0.1/32
ipv6 nd suppress-ra
!
interface eth0
ip address 11.0.0.1/32
ipv6 nd suppress-ra
!
interface eth1
ip address 10.0.0.2/32
ipv6 nd suppress-ra
mpls ip
mpls labelspace 0
!
interface lo
!
interface sit0
ipv6 nd suppress-ra
!
mpls ldp
egress connected
!
router ospf
passive-interface dummy
network 10.0.0.0/24 area 0.0.0.0
network 11.0.0.0/24 area 0.0.0.0
network 15.0.0.0/24 area 0.0.0.0
!
ip forwarding
!
line vty
!
And these are the outputs related to mpls and ldp:
PE2# sh mpls for
Insegments:
Lbl Spc Label Owner
0 10004 ldp
0 10005 ldp
0 10006 ldp
0 10007 ldp
Total 4
Outsegments:
Interface Label Next Hop Owner
eth1 10003 10.0.0.1 ldp
Total 1
Cross Connects:
Total 0
PE2# sh mpls for
Insegments:
Lbl Spc Label Owner
0 10004 ldp
0 10005 ldp
0 10006 ldp
0 10007 ldp
Total 4
Outsegments:
Interface Label Next Hop Owner
eth1 10003 10.0.0.1 ldp
Total 1
Cross Connects:
Total 0
PE2# sh ip route
Codes: K - kernel route, C - connected, S - static, R - RIP, O - OSPF,
I - ISIS, B - BGP, > - selected route, * - FIB route
K>* 0.0.0.0/0 via 172.29.16.1, eth0
O 10.0.0.0/24 [110/10] is directly connected, eth1, 00:18:30
C>* 10.0.0.0/24 is directly connected, eth1
C>* 10.0.0.2/32 is directly connected, eth1
O 11.0.0.1/32 [110/10] is directly connected, eth0, 00:18:20
C>* 11.0.0.1/32 is directly connected, eth0
O>* 12.0.0.0/24 [110/20] via 10.0.0.1, eth1, 00:12:07
C>* 127.0.0.0/8 is directly connected, lo
K>* 169.254.0.0/16 is directly connected, eth1
C>* 172.29.16.0/22 is directly connected, eth0
PE2# sh ldp
LSR-ID: 11.0.0.1 Admin State: ENABLED
Transport Address: 0.0.0.0
Control Mode: ORDERED Repair Mode: GLOBAL
Propogate Release: TRUE Label Merge: TRUE
Retention Mode: LIBERAL Loop Detection Mode: NONE
TTL-less-domain: FALSE
Local TCP Port: 646 Local UDP Port: 646
Keep-alive Time: 45 Keep-alive Interval: 15
Hello Time: 15 Hello Interval: 5
PE2# sh ldp add
Addr: 1 ac1d113c
0
0
1
Addr: 2 0b000001
0
0
1
Addr: 3 0a000002
0
0
2
Addr: 4 ac1d1001
0
1
0
Addr: 5 0a000001
2
7
0
Addr: 8 0c000001
2
0
0
Addr: 9 0d000001
2
0
161461200
PE2# sh ldp neig
Peer LDP Ident: 12.0.0.1:0; Local LDP Ident: 11.0.0.1:0
TCP connection: 10.0.0.2.33193 - 10.0.0.1.646
State: OPERATIONAL; Msgs sent/recv: 17/43; UNSOLICITED
Up time: 00:02:04
LDP discovery sources:
eth1
Addresses bound to peer:
10.0.0.1 12.0.0.1
PE2# sh ldp disc
Local LSR Identifier: 11.0.0.1
Interface Discovery Sources:
eth1: xmit/recv
LDP Id: 12.0.0.1:0
Targeted Discovery Sources:
No configured peers
PE2# sh ldp fec
FEC: 1 0.0.0.0/0
1 172.29.16.1 0
FEC: 2 169.254.0.0/16
2 0.0.0.0 0
FEC: 3 10.0.0.0/24
3 0.0.0.0 1
FEC: 4 10.0.0.2/32
4 0.0.0.0 1
FEC: 5 11.0.0.1/32
5 0.0.0.0 1
FEC: 6 172.29.16.0/22
6 0.0.0.0 1
FEC: 9 10.0.0.1/32
FEC: 10 12.0.0.1/32
PE2# sh ldp ses
2 1.0.0.0 45 OPERATIONAL
10.0.0.1
12.0.0.1
13.0.0.1
The problem persists. I'm not able to send labeled ICMP packets between =
ldp peers, any idea?
[root@PE2 ~]# mpls ilm
ILM entry label gen 10007 labelspace 0 proto ipv4
pop peek (0 bytes, 0 pkts)
ILM entry label gen 10006 labelspace 0 proto ipv4
pop peek (0 bytes, 0 pkts)
ILM entry label gen 10005 labelspace 0 proto ipv4
pop peek (0 bytes, 0 pkts)
ILM entry label gen 10004 labelspace 0 proto ipv4
pop peek (0 bytes, 0 pkts)
[root@PE2 ~]# mpls nhlfe
NHLFE entry key 0x00000003 mtu 1496 propagate_ttl
push gen 10003 set eth1 ipv4 10.0.0.1 (0 bytes, 0 pkts)
Thanks for your time and effort,
Gonzalo.
|
|
From: James R. L. <jl...@mi...> - 2007-01-12 04:22:17
|
Hello Julien, My comments are inline ... On Wed, Jan 10, 2007 at 04:59:31PM +0100, Julien Bisconti wrote: > Hello James, >=20 > Please, see my answer below. >=20 > On 12/12/06, James R. Leu <jl...@mi...> wrote: > > > >Excellent to here from you. I'm glad you've made it this far. Now > >lets dig in and start to understand what already exists. > > > >First let me start by explaining that ldp-portable is just a library. > >It relies upon something called a "porting layer" to provide the low > >level primitive and infrastructure to build a working implementation > >of LDP (or CR-LDP in your case). Here is a diagram of the layers involv= ed > >and the types of things handled in that layer: > > > >--------------------------------- > > user interface > > - protocol configuration > > - maintain configuration state > > - status queries > > - error notification > >--------------------------------- > > ldp-portable > > - packet encode/decode > > - message processing > >--------------------------------- > > porting layer > > - socket activity: read/write, multicast > > - timers > > - memory allocation > > - routing interaction > > - interface interaction > >--------------------------------- > > > >The API that needs to be filled in by the porting layer is defined in > >ldp-portable/common/*_impl.h >=20 >=20 > I don't really understand what is needed to be filled in. The files impl_= *.c > seem to fill the API completely. Could you explain me what is needed to be > filled in, If someone were trying to port ldp-portable to another routing system (XORP for example) these files would need to be re-implemented. I've already done the "heavy lifting" of porting ldp-portable to quagga. I was pointing out these files merely to give you an overview of how ldp-portable relates to quagga. > ldp-portable provides an API to the user interface (and the porting > >layer for some OS driven actions), which is defined in > >ldp-portable/ldp/ldp_cfg.c. This is called the configuration API. >=20 >=20 > OK. >=20 > quagga-mpls is a just one porting layer that exists (by far the most > >mature). So that is our next step, lets look at how quagga-mpls interac= ts > >with the configuration API defined in ldp_cfg.c. >=20 >=20 > I read the Zebra Hacking Howto to understand how an implementation of a > protocol works. Now, I understand how to interact with a protocol by the > VTY. Great. Understanding the quagga vty is very important. > Most of the actual user interface for quagga's usage of ldp-portable > >is defined in quagga-mpls/ldpd/ldp_vty.c. It relies upon the utilities > >and structure implemented in ldp_interface.c, ldp.c and ldp_remote_peer.c > >to maintain the configuration state for ldpd. It makes calls to the > >configuration API to actually make ldp-portable do something. In > >addition, > >the code in ldp_zebra.c is responsible to feeding routing and interface > >changes into ldp-portable. > > > >So for your first task, you'll need to figure out how you want the > >user to configure CR-LDP. Most of the work is done. The user can alrea= dy > >configure LDP at the global and interface level, all that is needed is > >a way to tell ldp-portable that we want to create a "tunnel" and configu= re > >the details of the tunnel, like where it should terminate, and what > >path to take to get there. There already exists the configuration > >API for these components, but it is untested, and doesn't really > >do anything. So that is what the 2nd (3rd, 4th, 5th ..... :-) step will > >be. >=20 >=20 > I think my first task is done. I figured out how the user can configure > CR-LDP. I looked at the code, I saw that Nortel also wrote two files > (ldp_nortel.[ch]) with a lot of accurate information in it concerning the > CR-LDP protocol. I noticed that in the configuration API, the functions to > create a "tunnel" already exist : Good. As you can see all of the necessary encodes/decodes for CR related TLVs exist. At the simplest level all you need to do is figure out how to trigger these encodes and decodes :-) Take a look at ldp_buf.c (ldp_encode_one_mesg) to understand how ldp-portable utilizes ldp_nortel.c > extern mpls_return_enum ldp_cfg_tunnel_set(mpls_cfg_handle handle, > ldp_tunnel * r, uint32_t flag); > extern mpls_return_enum ldp_cfg_tunnel_test(mpls_cfg_handle handle, > ldp_tunnel * r, uint32_t flag); > extern mpls_return_enum ldp_cfg_tunnel_get(mpls_cfg_handle handle, > ldp_tunnel * r, uint32_t flag); >=20 > The files ldp_tunnel.[ch] contain few functions to deal with tunnels. So, > now what you want me to do? The API in ldp_cfg tries to mimic the LDP-MIB and the TE-MIB. I believe I've implemented trivial code for creating all of the structures laid forth in the TE-MIB. So your task is to create the quagga vty interface that creates the structures in the TE-MIB and then fiddles the correct bits in the ldp_mesg data that is being sent to ldp_encode_one_mesg. Of course there will be additional work involved in processing packets you receive with the CR TLVs, but we'll worry about that after you can send packets with CR TLVs :-) > I know this was a lot to digest, look at the code, ask questions and > >hopefully we'll get you writting code shortly. >=20 >=20 > I hope so! >=20 > Again, thanks for your interest, I'm really happy that you're willing > >to contribute and work on this aspect of mpls-linux. >=20 >=20 > My pleasure ! >=20 > I hope to hear from you soon. >=20 >=20 > I'm sorry not to reply sooner but with the holidays and complexity of the > project, sometimes I got lost into the code. >=20 > Thank you for your help >=20 > Julien >=20 >=20 >=20 > On Mon, Dec 11, 2006 at 04:10:54PM +0100, Julien Bisconti wrote: > >> Hello Sir, > >> > >> This email is to let you know that I can compile everything on the > >> repository. So I am available to help you. I keep digging into > >quagga-mpls > >> now that I finally managed to install it. > >> > >> I hope to hear from you. > >> > >> Regards, > >> > >> Julien > >> > >> On 12/4/06, Julien Bisconti <jul...@gm...> wrote: > >> > > >> > Hello Sir, > >> > > >> >James R. Leu wrote: > >> > > >> >Hello Julien, > >> > > >> >Would you mind if we moved this discussion to the mpls-linux-genernal > >> >mailing list? > >> > > >> > I just solved the problem of the gnu autotool (Murphy's law) so I > >don't > >> >think that moving this discussion will be necessary. But if you want = to > >> >move > >> >the _whole_ discussion concerning the development of dynamic LSPs then > >I > >> >fully agree with you. > >> > > >> >Thank you again for the help. > >> > > >> >Here are the versions of auto tools I use on my development machine: > >> > > >> > autorun-3.18-1.2 > >> > automake-1.9.6-2 > >> > autoconf-2.59-7 > >> > > >> >In addition I do not believe you should be using 'update-autotools' > >> >Instead you should just issue a: > >> > > >> > ./cleanup-jleu > >> > autoreconf > >> > ./configure > >> > > >> >from the quagga-mpls directory. > >> > > >> >On Mon, Dec 04, 2006 at 03:14:40PM +0100, Julien Bisconti wrote: > >> > > >> > Sir, > >> > > >> >As asked, I compiled every program on the repository except quagga-mp= ls > >> >(the > >> >one I think I really need) > >> >The problem is I can't even try to compile, I never managed to get to > >> >configure script with the gnu autotool. > >> > > >> >I googled the whole weekend to find out what is the error, apparently > >it > >> >seems to be a problem with the macro of aclocal. I re-pulled the code > >of > >> >quagga-mpls from perforce specifying that I want to keep the > >modification > >> >time of the original file, no way to get the configure script. > >> > > >> >Here is the error I get from autoreconf, from "aclocal -I m4" or from > >the > >> >update-autotools script) > >> > > >> >/usr/bin/m4:configure.ac:1416: ERROR: recursion limit of 1024 exceede= d, > >use > >> >-L<N> to change it > >> >autom4te-2.60: /usr/bin/m4 failed with exit status: 1 > >> >aclocal-1.9: autom4te failed with exit status: 1 > >> >autoreconf-2.60: aclocal failed with exit status: 1 > >> > > >> >I'm really stuck at this point. Everything else is allright. I tried = to > >> >compile the original version of quagga-0.99.5 (downloaded from the ma= in > >web > >> >site) and I have the *same error*. I'm currently using Gentoo 2006.1a= nd > >> >here is the version of gnu autotool I use : > >> > > >> >autoheader (GNU Autoconf) 2.60 > >> >autoconf (GNU Autoconf) 2.60 > >> >ltmain.sh (GNU libtool) 1.5.22 (1.1220.2.365 2005/12/18 22:14:06) > >> >libtoolize (GNU libtool) 1.5.22 > >> >aclocal (GNU automake) 1.9.6 > >> >automake (GNU automake) 1.9.6 > >> > > >> >I would really appreciate your help on this because no one else seems > >to > >> >have the same problem as I do. > >> > > >> >Thank you in advance. > >> > > >> >Julien > >> > > >> >On 12/1/06, James R. Leu <jl...@mi...> <jl...@mi...> > >wrote: > >> > > >> > Hello, > >> > > >> >I'm glad to here your interested in helping with mpls-linux. > >> >The best way to get involved is to pull the code from my > >> >development tree via P4. Once you have that, make sure you know > >> >how to build and install the software from the trees. Once you have > >that > >> >figured out, then we can start looking at the code and figuring out > >were > >> >you need to make changes. > >> > > >> >I use Fedora 5 as my development plateform. Other then that I use go= od > >> >ol' > >> >vi and gcc. For testing I use xen instances networked together via > >bridge > >> >interfaces. > >> > > >> >Let me know how you're progressing on pulling the code from P4 and > >> >building > >> >and installing the programs. > >> > > >> >On Tue, Nov 28, 2006 at 03:08:37PM +0100, Julien Bisconti wrote: > >> > > >> > Sir, > >> > > >> >My name is Julien Bisconti, I am currently a student in computer > >science > >> > > >> > and > >> > > >> > I aim to test the dynamic configuration of LSP on a testbed. > >> > > >> >It is said in ldp-portable FAQ that it not implemented yet but > >> > > >> > everything is > >> > > >> > ready for it.Maybe I can help you with that. > >> >Could you give a hint by telling me how (where in the code) can I > >> > > >> > implement > >> > > >> > CR-LDP? The development guide doesn't speak about LDP. > >> > > >> >By the way, I managed to install LDP (quagga/ldp-portable) and MPLS > >> > > >> > (kernel > >> > > >> > + iptables/iproute/ebtables) and I would like to know which software > >do > >> > > >> > you > >> > > >> > use to develop those, in case I would code something. Because they a= re > >a > >> > > >> > lot > >> > > >> > of files and I'm not used to it. > >> > > >> >I hope to ear from you soon. > >> > > >> >Regards, > >> > > >> >Julien Bisconti > >> > > >> >PS: I also sent a mail to the mailing list on SourceForge > >> > > >> > > >> >-- > >> >-------------------------------------------- > >> >Julien BISCONTI <julien.bisconti(at)student.fundp.ac.be> > >> >M.Sc. student in Computer Science, University of Namur > >> >FUNDP, Belgium > >> >Traineeship: UPC (Barcelona, Spain) > >> > > >> > -- > >> >James R. Leu > >> >jl...@mi... > >> > > >> > > >> > > >> > -- > >> >-------------------------------------------- > >> >Julien BISCONTI <julien.bisconti(at)student.fundp.ac.be> > >> >M.Sc. student in Computer Science, University of Namur > >> >FUNDP, Belgium > >> >Traineeship: UPC (Barcelona, Spain) > >> >GSM BELGIQUE: +32 474 598 418 > >> >GSM ESPA?A: +34 671 168 458 > >> > > >> > > >> >-- > >> >-------------------------------------------- > >> >Julien BISCONTI <jul...@st...> > >> ><jul...@st...>M.Sc. student in Computer Scienc= e, > >> >University of Namur > >> >FUNDP, Belgium > >> >GSM BELGIQUE: +32 474 598 418 > >> >GSM ESPA?A: +34 671 168 458 > >> > > >> > > >> > >> > >> -- > >> -------------------------------------------- > >> Julien BISCONTI <julien.bisconti(at)student.fundp.ac.be> > >> M.Sc. student in Computer Science, University of Namur > >> FUNDP, Belgium > >> Traineeship: UPC (Barcelona, Spain) > >> GSM BELGIQUE: +32 474 598 418 > >> GSM ESPA?A: +34 671 168 458 > > > >-- > >James R. Leu > >jl...@mi... > > > > > > >=20 >=20 > --=20 > -------------------------------------------- > Julien BISCONTI <julien.bisconti(at)student.fundp.ac.be> > M.Sc. student in Computer Science, University of Namur > FUNDP, Belgium > Traineeship: UPC (Barcelona, Spain) > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share y= our > opinions on IT & business topics through brief surveys - and earn cash > http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3D= DEVDEV > _______________________________________________ > mpls-linux-devel mailing list > mpl...@li... > https://lists.sourceforge.net/lists/listinfo/mpls-linux-devel --=20 James R. Leu jl...@mi... |
|
From: James R. L. <jl...@mi...> - 2007-01-12 04:05:40
|
Looking closer at your configs and comparing to mine, there are two differences I notice. First, I configure all of my routing/MPLS interface IP addresses via vtysh. (ie the system does not configure them via /etc/sysconfig/network-scripts/ifcfg-*) Second, I always use a dummy0 interface to establish my router-id/lsr-id Here is the important parts of my config: interface dummy0 ip address 192.168.3.2/32 ipv6 nd suppress-ra ! interface eth0 ipv6 nd suppress-ra ! interface eth1 ip address 192.168.2.2/30 ipv6 nd suppress-ra mpls ip mpls labelspace 0 ! interface eth2 ip address 192.168.4.2/29 ipv6 nd suppress-ra mpls ip mpls labelspace 0 ! mpls ldp egress connected ! router ospf passive-interface dummy0 network 192.168.2.0/30 area 0.0.0.0 network 192.168.3.2/32 area 0.0.0.0 network 192.168.4.0/29 area 0.0.0.0 You'll notice that eth0 does not have an IP in the config. This is the only interface I configure via the system. This is so that if zebra is not running I can still login to the box. But all other routing/MPLS/LDP interfaces are configured via vtysh. Give my suggestions a try and see if either fix things for you. Please let me know the results! On Mon, Jan 08, 2007 at 12:51:10PM +0100, Sienes Rodr?guez Gonzalo wrote: > Hi James: >=20 > You'll have to forgive me, I had some important business to finish before= christmas. >=20 > I've downloaded the latest quagga-mpls and ldp-portable from your P4 repo= sitory and >=20 > test it in a simple scenario with two PCs. >=20 > =20 >=20 > 13.0.0.1 .1 10.0.0.0/24 .2 11.0.0.1 >=20 > --------------PE1---------------------PE2-------------- >=20 > eth1 eth0 eth1 eth0 >=20 > And these are the versions of the RPMs related to MPLS and QUAGGA and the= modules I load: >=20 > [root@PE2]# rpm -qa | grep mpls | sort >=20 > glibc-kernheaders-3.0-5.2_mpls0.1162999872 >=20 > iproute-2.6.11-1_mpls_90.1162552079 >=20 > iptables-1.3.0-2_mpls_1.950d >=20 > kernel-2.6.15-1.1831_FC4mpls_1.950 >=20 > kernel-devel-2.6.15-1.1831_FC4mpls_1.950 >=20 > quagga-0.99.6-2007010801_mpls_0.1168246002 >=20 > quagga-contrib-0.99.6-2007010801_mpls_0.1168246002 >=20 > quagga-debuginfo-0.99.6-2007010801_mpls_0.1168246002 >=20 > quagga-devel-0.99.6-2007010801_mpls_0.1168246002 >=20 > [root@PE2]# lsmod | grep mpls >=20 > mpls4 5953 0 >=20 > mpls 78209 2 mpls4 >=20 > Now I show you the configuration and output of some commands in PE2 (anal= ogue in PE1): >=20 > PE2# sh run >=20 > Building configuration... >=20 > Current configuration: >=20 > ! >=20 > hostname PE2 >=20 > ! >=20 > service integrated-vtysh-config >=20 > ! >=20 > debug zebra events >=20 > debug zebra kernel >=20 > ! >=20 > password root >=20 > ! >=20 > interface eth0 >=20 > description 11.0.0.1 netmask 255.255.255.0 broadcast 11.0.0.255 >=20 > ipv6 nd suppress-ra >=20 > ! >=20 > interface eth1 >=20 > description 10.0.0.2 netmask 255.255.255.0 broadcast 10.0.0.255 >=20 > ipv6 nd suppress-ra >=20 > mpls ip >=20 > mpls labelspace 0 >=20 > ! >=20 > ! >=20 > mpls ldp >=20 > egress connected >=20 > ! >=20 > router ospf >=20 > network 10.0.0.0/24 area 0.0.0.0 >=20 > network 11.0.0.0/24 area 0.0.0.0 >=20 > network 15.0.0.0/24 area 0.0.0.0 >=20 > ! >=20 > ip forwarding >=20 > ! >=20 > line vty >=20 > ! >=20 > PE2# sh ldp >=20 > LSR-ID: 10.0.0.2 Admin State: ENABLED >=20 > Transport Address: 0.0.0.0 >=20 > Control Mode: ORDERED Repair Mode: GLOBAL >=20 > Propogate Release: TRUE Label Merge: TRUE >=20 > Retention Mode: LIBERAL Loop Detection Mode: NONE >=20 > TTL-less-domain: FALSE >=20 > Local TCP Port: 646 Local UDP Port: 646 >=20 > Keep-alive Time: 45 Keep-alive Interval: 15 >=20 > Hello Time: 15 Hello Interval: 5 >=20 > PE2# sh ldp dis >=20 > Local LSR Identifier: 10.0.0.2 >=20 > Interface Discovery Sources: >=20 > eth1: xmit/recv >=20 > LDP Id: 13.0.0.1:0 >=20 > Targeted Discovery Sources: >=20 > No configured peers >=20 > PE2# sh ldp fec >=20 > FEC: 1 169.254.0.0/16 >=20 > 1 0.0.0.0 0 >=20 > FEC: 2 10.0.0.0/24 >=20 > 2 0.0.0.0 1 >=20 > PE2# sh ldp dat >=20 > 10.0.0.0/24 local binding: label: gen 10001 >=20 > 10.0.0.0/24 remote binding: label: gen 10001 lsr: 13.0.0.1:0 ingress >=20 > PE2# sh mpls for >=20 > Insegments: >=20 > Lbl Spc Label Owner >=20 > 0 10001 ldp >=20 > Total 1 >=20 > Outsegments: >=20 > Interface Label Next Hop Owner >=20 > eth1 10001 10.0.0.1 ldp >=20 > Total 1 >=20 > Cross Connects: >=20 > Total 0 >=20 > PE2# sh ip route >=20 > Codes: K - kernel route, C - connected, S - static, R - RIP, O - OSPF, >=20 > I - ISIS, B - BGP, > - selected route, * - FIB route >=20 > O 10.0.0.0/24 [110/10] is directly connected, eth1, 00:06:05 >=20 > C>* 10.0.0.0/24 is directly connected, eth1 >=20 > O 11.0.0.0/24 [110/10] is directly connected, eth0, 00:06:05 >=20 > C>* 11.0.0.0/24 is directly connected, eth0 >=20 > O>* 13.0.0.0/24 [110/20] via 10.0.0.1, eth1, 00:05:12 >=20 > C>* 127.0.0.0/8 is directly connected, lo >=20 > K>* 169.254.0.0/16 is directly connected, eth1 >=20 > PE2# sh ldp ses >=20 > 2 1.0.0.0 45 OPERATIONAL >=20 > 10.0.0.1 >=20 > 13.0.0.1 >=20 > PE2# sh ldp dis >=20 > Local LSR Identifier: 10.0.0.2 >=20 > Interface Discovery Sources: >=20 > eth1: xmit/recv >=20 > LDP Id: 13.0.0.1:0 >=20 > Targeted Discovery Sources: >=20 > No configured peers >=20 > PE2# sh ldp neig >=20 > Peer LDP Ident: 13.0.0.1:0; Local LDP Ident: 10.0.0.2:0 >=20 > TCP connection: 10.0.0.2.39560 - 10.0.0.1.646 >=20 > State: OPERATIONAL; Msgs sent/recv: 26/78; UNSOLICITED >=20 > Up time: 00:05:18 >=20 > LDP discovery sources: >=20 > eth1 >=20 > Addresses bound to peer: >=20 > 10.0.0.1 13.0.0.1 >=20 > PE2# sh mpls hard >=20 > MPLS-Linux: 1.950 netlink control >=20 > PE2# sh mpls ver >=20 > Version 1.950 >=20 > [root@PE2]# mpls ilm >=20 > ILM entry label gen 10001 labelspace 0 proto ipv4 >=20 > pop peek (0 bytes, 0 pkts) >=20 > [root@PE2]# mpls nhlfe >=20 > NHLFE entry key 0x00000003 mtu 1496 propagate_ttl >=20 > push gen 10001 set eth1 ipv4 10.0.0.1 (0 bytes, 0 pkts) >=20 > [root@PE2]# ip route >=20 > 10.0.0.0/24 dev eth1 proto kernel scope link src 10.0.0.2 >=20 > 11.0.0.0/24 dev eth0 proto kernel scope link src 11.0.0.1 >=20 > 13.0.0.0/24 via 10.0.0.1 dev eth1 proto zebra metric 20 >=20 > The result is that, althaugh the NHLFE and ILM tables add a new entry for= 10.0.0.0/24 subnet,=20 >=20 > I'm not able to send labeled packets from one host to another because IP = table doesn't change=20 >=20 > to route the packets via mpls. >=20 > I think we're very close to solve it, but I need your help. >=20 > Thanks in advange, >=20 > Gonzalo >=20 >=20 > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share y= our > opinions on IT & business topics through brief surveys - and earn cash > http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3D= DEVDEV > _______________________________________________ > mpls-linux-devel mailing list > mpl...@li... > https://lists.sourceforge.net/lists/listinfo/mpls-linux-devel --=20 James R. Leu jl...@mi... |
|
From: Julien B. <jul...@gm...> - 2007-01-10 15:59:37
|
Hello James, Please, see my answer below. On 12/12/06, James R. Leu <jl...@mi...> wrote: > > Excellent to here from you. I'm glad you've made it this far. Now > lets dig in and start to understand what already exists. > > First let me start by explaining that ldp-portable is just a library. > It relies upon something called a "porting layer" to provide the low > level primitive and infrastructure to build a working implementation > of LDP (or CR-LDP in your case). Here is a diagram of the layers involved > and the types of things handled in that layer: > > --------------------------------- > user interface > - protocol configuration > - maintain configuration state > - status queries > - error notification > --------------------------------- > ldp-portable > - packet encode/decode > - message processing > --------------------------------- > porting layer > - socket activity: read/write, multicast > - timers > - memory allocation > - routing interaction > - interface interaction > --------------------------------- > > The API that needs to be filled in by the porting layer is defined in > ldp-portable/common/*_impl.h I don't really understand what is needed to be filled in. The files impl_*.c seem to fill the API completely. Could you explain me what is needed to be filled in, ldp-portable provides an API to the user interface (and the porting > layer for some OS driven actions), which is defined in > ldp-portable/ldp/ldp_cfg.c. This is called the configuration API. OK. quagga-mpls is a just one porting layer that exists (by far the most > mature). So that is our next step, lets look at how quagga-mpls interacts > with the configuration API defined in ldp_cfg.c. I read the Zebra Hacking Howto to understand how an implementation of a protocol works. Now, I understand how to interact with a protocol by the VTY. Most of the actual user interface for quagga's usage of ldp-portable > is defined in quagga-mpls/ldpd/ldp_vty.c. It relies upon the utilities > and structure implemented in ldp_interface.c, ldp.c and ldp_remote_peer.c > to maintain the configuration state for ldpd. It makes calls to the > configuration API to actually make ldp-portable do something. In > addition, > the code in ldp_zebra.c is responsible to feeding routing and interface > changes into ldp-portable. > > So for your first task, you'll need to figure out how you want the > user to configure CR-LDP. Most of the work is done. The user can already > configure LDP at the global and interface level, all that is needed is > a way to tell ldp-portable that we want to create a "tunnel" and configure > the details of the tunnel, like where it should terminate, and what > path to take to get there. There already exists the configuration > API for these components, but it is untested, and doesn't really > do anything. So that is what the 2nd (3rd, 4th, 5th ..... :-) step will > be. I think my first task is done. I figured out how the user can configure CR-LDP. I looked at the code, I saw that Nortel also wrote two files (ldp_nortel.[ch]) with a lot of accurate information in it concerning the CR-LDP protocol. I noticed that in the configuration API, the functions to create a "tunnel" already exist : extern mpls_return_enum ldp_cfg_tunnel_set(mpls_cfg_handle handle, ldp_tunnel * r, uint32_t flag); extern mpls_return_enum ldp_cfg_tunnel_test(mpls_cfg_handle handle, ldp_tunnel * r, uint32_t flag); extern mpls_return_enum ldp_cfg_tunnel_get(mpls_cfg_handle handle, ldp_tunnel * r, uint32_t flag); The files ldp_tunnel.[ch] contain few functions to deal with tunnels. So, now what you want me to do? I know this was a lot to digest, look at the code, ask questions and > hopefully we'll get you writting code shortly. I hope so! Again, thanks for your interest, I'm really happy that you're willing > to contribute and work on this aspect of mpls-linux. My pleasure ! I hope to hear from you soon. I'm sorry not to reply sooner but with the holidays and complexity of the project, sometimes I got lost into the code. Thank you for your help Julien On Mon, Dec 11, 2006 at 04:10:54PM +0100, Julien Bisconti wrote: > > Hello Sir, > > > > This email is to let you know that I can compile everything on the > > repository. So I am available to help you. I keep digging into > quagga-mpls > > now that I finally managed to install it. > > > > I hope to hear from you. > > > > Regards, > > > > Julien > > > > On 12/4/06, Julien Bisconti <jul...@gm...> wrote: > > > > > > Hello Sir, > > > > > >James R. Leu wrote: > > > > > >Hello Julien, > > > > > >Would you mind if we moved this discussion to the mpls-linux-genernal > > >mailing list? > > > > > > I just solved the problem of the gnu autotool (Murphy's law) so I > don't > > >think that moving this discussion will be necessary. But if you want to > > >move > > >the _whole_ discussion concerning the development of dynamic LSPs then > I > > >fully agree with you. > > > > > >Thank you again for the help. > > > > > >Here are the versions of auto tools I use on my development machine: > > > > > > autorun-3.18-1.2 > > > automake-1.9.6-2 > > > autoconf-2.59-7 > > > > > >In addition I do not believe you should be using 'update-autotools' > > >Instead you should just issue a: > > > > > > ./cleanup-jleu > > > autoreconf > > > ./configure > > > > > >from the quagga-mpls directory. > > > > > >On Mon, Dec 04, 2006 at 03:14:40PM +0100, Julien Bisconti wrote: > > > > > > Sir, > > > > > >As asked, I compiled every program on the repository except quagga-mpls > > >(the > > >one I think I really need) > > >The problem is I can't even try to compile, I never managed to get to > > >configure script with the gnu autotool. > > > > > >I googled the whole weekend to find out what is the error, apparently > it > > >seems to be a problem with the macro of aclocal. I re-pulled the code > of > > >quagga-mpls from perforce specifying that I want to keep the > modification > > >time of the original file, no way to get the configure script. > > > > > >Here is the error I get from autoreconf, from "aclocal -I m4" or from > the > > >update-autotools script) > > > > > >/usr/bin/m4:configure.ac:1416: ERROR: recursion limit of 1024 exceeded, > use > > >-L<N> to change it > > >autom4te-2.60: /usr/bin/m4 failed with exit status: 1 > > >aclocal-1.9: autom4te failed with exit status: 1 > > >autoreconf-2.60: aclocal failed with exit status: 1 > > > > > >I'm really stuck at this point. Everything else is allright. I tried to > > >compile the original version of quagga-0.99.5 (downloaded from the main > web > > >site) and I have the *same error*. I'm currently using Gentoo 2006.1and > > >here is the version of gnu autotool I use : > > > > > >autoheader (GNU Autoconf) 2.60 > > >autoconf (GNU Autoconf) 2.60 > > >ltmain.sh (GNU libtool) 1.5.22 (1.1220.2.365 2005/12/18 22:14:06) > > >libtoolize (GNU libtool) 1.5.22 > > >aclocal (GNU automake) 1.9.6 > > >automake (GNU automake) 1.9.6 > > > > > >I would really appreciate your help on this because no one else seems > to > > >have the same problem as I do. > > > > > >Thank you in advance. > > > > > >Julien > > > > > >On 12/1/06, James R. Leu <jl...@mi...> <jl...@mi...> > wrote: > > > > > > Hello, > > > > > >I'm glad to here your interested in helping with mpls-linux. > > >The best way to get involved is to pull the code from my > > >development tree via P4. Once you have that, make sure you know > > >how to build and install the software from the trees. Once you have > that > > >figured out, then we can start looking at the code and figuring out > were > > >you need to make changes. > > > > > >I use Fedora 5 as my development plateform. Other then that I use good > > >ol' > > >vi and gcc. For testing I use xen instances networked together via > bridge > > >interfaces. > > > > > >Let me know how you're progressing on pulling the code from P4 and > > >building > > >and installing the programs. > > > > > >On Tue, Nov 28, 2006 at 03:08:37PM +0100, Julien Bisconti wrote: > > > > > > Sir, > > > > > >My name is Julien Bisconti, I am currently a student in computer > science > > > > > > and > > > > > > I aim to test the dynamic configuration of LSP on a testbed. > > > > > >It is said in ldp-portable FAQ that it not implemented yet but > > > > > > everything is > > > > > > ready for it.Maybe I can help you with that. > > >Could you give a hint by telling me how (where in the code) can I > > > > > > implement > > > > > > CR-LDP? The development guide doesn't speak about LDP. > > > > > >By the way, I managed to install LDP (quagga/ldp-portable) and MPLS > > > > > > (kernel > > > > > > + iptables/iproute/ebtables) and I would like to know which software > do > > > > > > you > > > > > > use to develop those, in case I would code something. Because they are > a > > > > > > lot > > > > > > of files and I'm not used to it. > > > > > >I hope to ear from you soon. > > > > > >Regards, > > > > > >Julien Bisconti > > > > > >PS: I also sent a mail to the mailing list on SourceForge > > > > > > > > >-- > > >-------------------------------------------- > > >Julien BISCONTI <julien.bisconti(at)student.fundp.ac.be> > > >M.Sc. student in Computer Science, University of Namur > > >FUNDP, Belgium > > >Traineeship: UPC (Barcelona, Spain) > > > > > > -- > > >James R. Leu > > >jl...@mi... > > > > > > > > > > > > -- > > >-------------------------------------------- > > >Julien BISCONTI <julien.bisconti(at)student.fundp.ac.be> > > >M.Sc. student in Computer Science, University of Namur > > >FUNDP, Belgium > > >Traineeship: UPC (Barcelona, Spain) > > >GSM BELGIQUE: +32 474 598 418 > > >GSM ESPA?A: +34 671 168 458 > > > > > > > > >-- > > >-------------------------------------------- > > >Julien BISCONTI <jul...@st...> > > ><jul...@st...>M.Sc. student in Computer Science, > > >University of Namur > > >FUNDP, Belgium > > >GSM BELGIQUE: +32 474 598 418 > > >GSM ESPA?A: +34 671 168 458 > > > > > > > > > > > > -- > > -------------------------------------------- > > Julien BISCONTI <julien.bisconti(at)student.fundp.ac.be> > > M.Sc. student in Computer Science, University of Namur > > FUNDP, Belgium > > Traineeship: UPC (Barcelona, Spain) > > GSM BELGIQUE: +32 474 598 418 > > GSM ESPA?A: +34 671 168 458 > > -- > James R. Leu > jl...@mi... > > > -- -------------------------------------------- Julien BISCONTI <julien.bisconti(at)student.fundp.ac.be> M.Sc. student in Computer Science, University of Namur FUNDP, Belgium Traineeship: UPC (Barcelona, Spain) |
|
From: <gsr...@al...> - 2007-01-08 11:53:26
|
Hi James: You'll have to forgive me, I had some important business to finish = before christmas. I've downloaded the latest quagga-mpls and ldp-portable from your P4 = repository and test it in a simple scenario with two PCs. =20 13.0.0.1 .1 10.0.0.0/24 .2 11.0.0.1 --------------PE1---------------------PE2-------------- eth1 eth0 eth1 eth0 And these are the versions of the RPMs related to MPLS and QUAGGA and = the modules I load: [root@PE2]# rpm -qa | grep mpls | sort glibc-kernheaders-3.0-5.2_mpls0.1162999872 iproute-2.6.11-1_mpls_90.1162552079 iptables-1.3.0-2_mpls_1.950d kernel-2.6.15-1.1831_FC4mpls_1.950 kernel-devel-2.6.15-1.1831_FC4mpls_1.950 quagga-0.99.6-2007010801_mpls_0.1168246002 quagga-contrib-0.99.6-2007010801_mpls_0.1168246002 quagga-debuginfo-0.99.6-2007010801_mpls_0.1168246002 quagga-devel-0.99.6-2007010801_mpls_0.1168246002 [root@PE2]# lsmod | grep mpls mpls4 5953 0 mpls 78209 2 mpls4 Now I show you the configuration and output of some commands in PE2 = (analogue in PE1): PE2# sh run Building configuration... Current configuration: ! hostname PE2 ! service integrated-vtysh-config ! debug zebra events debug zebra kernel ! password root ! interface eth0 description 11.0.0.1 netmask 255.255.255.0 broadcast 11.0.0.255 ipv6 nd suppress-ra ! interface eth1 description 10.0.0.2 netmask 255.255.255.0 broadcast 10.0.0.255 ipv6 nd suppress-ra mpls ip mpls labelspace 0 ! ! mpls ldp egress connected ! router ospf network 10.0.0.0/24 area 0.0.0.0 network 11.0.0.0/24 area 0.0.0.0 network 15.0.0.0/24 area 0.0.0.0 ! ip forwarding ! line vty ! PE2# sh ldp LSR-ID: 10.0.0.2 Admin State: ENABLED Transport Address: 0.0.0.0 Control Mode: ORDERED Repair Mode: GLOBAL Propogate Release: TRUE Label Merge: TRUE Retention Mode: LIBERAL Loop Detection Mode: NONE TTL-less-domain: FALSE Local TCP Port: 646 Local UDP Port: 646 Keep-alive Time: 45 Keep-alive Interval: 15 Hello Time: 15 Hello Interval: 5 PE2# sh ldp dis Local LSR Identifier: 10.0.0.2 Interface Discovery Sources: eth1: xmit/recv LDP Id: 13.0.0.1:0 Targeted Discovery Sources: No configured peers PE2# sh ldp fec FEC: 1 169.254.0.0/16 1 0.0.0.0 0 FEC: 2 10.0.0.0/24 2 0.0.0.0 1 PE2# sh ldp dat 10.0.0.0/24 local binding: label: gen 10001 10.0.0.0/24 remote binding: label: gen 10001 lsr: 13.0.0.1:0 ingress PE2# sh mpls for Insegments: Lbl Spc Label Owner 0 10001 ldp Total 1 Outsegments: Interface Label Next Hop Owner eth1 10001 10.0.0.1 ldp Total 1 Cross Connects: Total 0 PE2# sh ip route Codes: K - kernel route, C - connected, S - static, R - RIP, O - OSPF, I - ISIS, B - BGP, > - selected route, * - FIB route O 10.0.0.0/24 [110/10] is directly connected, eth1, 00:06:05 C>* 10.0.0.0/24 is directly connected, eth1 O 11.0.0.0/24 [110/10] is directly connected, eth0, 00:06:05 C>* 11.0.0.0/24 is directly connected, eth0 O>* 13.0.0.0/24 [110/20] via 10.0.0.1, eth1, 00:05:12 C>* 127.0.0.0/8 is directly connected, lo K>* 169.254.0.0/16 is directly connected, eth1 PE2# sh ldp ses 2 1.0.0.0 45 OPERATIONAL 10.0.0.1 13.0.0.1 PE2# sh ldp dis Local LSR Identifier: 10.0.0.2 Interface Discovery Sources: eth1: xmit/recv LDP Id: 13.0.0.1:0 Targeted Discovery Sources: No configured peers PE2# sh ldp neig Peer LDP Ident: 13.0.0.1:0; Local LDP Ident: 10.0.0.2:0 TCP connection: 10.0.0.2.39560 - 10.0.0.1.646 State: OPERATIONAL; Msgs sent/recv: 26/78; UNSOLICITED Up time: 00:05:18 LDP discovery sources: eth1 Addresses bound to peer: 10.0.0.1 13.0.0.1 PE2# sh mpls hard MPLS-Linux: 1.950 netlink control PE2# sh mpls ver Version 1.950 [root@PE2]# mpls ilm ILM entry label gen 10001 labelspace 0 proto ipv4 pop peek (0 bytes, 0 pkts) [root@PE2]# mpls nhlfe NHLFE entry key 0x00000003 mtu 1496 propagate_ttl push gen 10001 set eth1 ipv4 10.0.0.1 (0 bytes, 0 pkts) [root@PE2]# ip route 10.0.0.0/24 dev eth1 proto kernel scope link src 10.0.0.2 11.0.0.0/24 dev eth0 proto kernel scope link src 11.0.0.1 13.0.0.0/24 via 10.0.0.1 dev eth1 proto zebra metric 20 The result is that, althaugh the NHLFE and ILM tables add a new entry = for 10.0.0.0/24 subnet,=20 I'm not able to send labeled packets from one host to another because IP = table doesn't change=20 to route the packets via mpls. I think we're very close to solve it, but I need your help. Thanks in advange, Gonzalo |
|
From: prachi g. <pra...@gm...> - 2007-01-06 08:12:24
|
We patched ldp-portable with Quagga 0.96.4 on FC5..this is the error we got after running configuration script : configure: creating ./config.status config.status: creating Makefile config.status: creating lib/Makefile config.status: creating zebra/Makefile config.status: creating ripd/Makefile config.status: creating ripngd/Makefile config.status: creating ldpd/Makefile config.status: error: cannot find input file: ldpd/Makefile.in We also tried the following.... [root@localhost ldpd]# automake Makefile.am automake: no Automake input file found for `Makefile.am' automake: no input file found among supplied arguments [root@localhost ldpd]# Files such as Makefile.in and Makefile are not created in the ldpd directory of quagga...... please help.... regards , Prachi |
|
From: James R. L. <jl...@mi...> - 2006-12-29 14:39:57
|
ldp-portable should provide you the framework you need to build on. You will probably want to use it in combination with quagga-mpls, which provides an environment integrated with routing protocols. At this time a new release of quagga-mpls + ldp-portable is being prepared. I encourage you to download the latest version from my development archive (see http://mpls-linux.sf.net for more info). Feel free to post questions about the code to this list. On Fri, Dec 29, 2006 at 04:10:25PM +0530, prachi gaikwad wrote: > I would like to know if you are aware of any softwares that completely > support LDP-MPLS . > As a final year engineering project our aim is to develop an extension to > LDP to provide point-to-multipoint forwarding. > please help in this regard.... > thank you... > -prachi > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share y= our > opinions on IT & business topics through brief surveys - and earn cash > http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3D= DEVDEV > _______________________________________________ > mpls-linux-devel mailing list > mpl...@li... > https://lists.sourceforge.net/lists/listinfo/mpls-linux-devel --=20 James R. Leu jl...@mi... |
|
From: prachi g. <pra...@gm...> - 2006-12-29 10:40:28
|
I would like to know if you are aware of any softwares that completely support LDP-MPLS . As a final year engineering project our aim is to develop an extension to LDP to provide point-to-multipoint forwarding. please help in this regard.... thank you... -prachi |
|
From: James R. L. <jl...@mi...> - 2006-12-28 14:26:03
|
Please search the mailing list archive and you will find posts describing the techniques for mapping QoS to MPLS LSPs. On Wed, Dec 27, 2006 at 10:50:11PM -0800, Manoj Kumar wrote: > Hello Everyone, >=20 > We have downloaded and sucessfully installed the mpls forwarding plane mp= ls-linux-1.950. It works fine with normal forwarding and label switching. >=20 > Now we would like to test IP QOS functionalites using Diffserv and QOS su= pported in linux. Hence we would like to know if there is any qos support i= n mpls-linux.1.950 or even older versions. >=20 > Being specific is there support in mpls-linux-1.950 to map IPDiffserv fie= lds (DSCP) to EXP bits in mpls shim header and give preferential treatment = based on the values in EXP bits. Further, enqeue the packets to different Q= OS queues in the low layers. >=20 > If so pls, inform me how to configure the same. so that i can test with y= ou. >=20 > Thank you, > Manoj > __________________________________________________ > Do You Yahoo!? > Tired of spam? Yahoo! Mail has the best spam protection around=20 > http://mail.yahoo.com=20 > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share y= our > opinions on IT & business topics through brief surveys - and earn cash > http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3D= DEVDEV > _______________________________________________ > mpls-linux-devel mailing list > mpl...@li... > https://lists.sourceforge.net/lists/listinfo/mpls-linux-devel --=20 James R. Leu jl...@mi... |
|
From: Manoj K. <man...@ya...> - 2006-12-28 06:57:03
|
Hello Everyone, We have downloaded and sucessfully installed the mpls forwarding plane mpls-linux-1.950. It works fine with normal forwarding and label switching. Now we would like to test IP QOS functionalites using Diffserv and QOS supported in linux. Hence we would like to know if there is any qos support in mpls-linux.1.950 or even older versions. Being specific is there support in mpls-linux-1.950 to map IPDiffserv fields (DSCP) to EXP bits in mpls shim header and give preferential treatment based on the values in EXP bits. Further, enqeue the packets to different QOS queues in the low layers. If so pls, inform me how to configure the same. so that i can test with you. Thank you, Manoj __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com |
|
From: Julien B. <jul...@gm...> - 2006-12-19 11:31:06
|
Hello sir,
The more I dive into the code (of quagga, not ldp) the more I found it
really really tricky. The most difficult part was to understand how
the interface worked. And I figured out that DEFUN was used :
/* DEFUN for vty command interafce. Little bit hacky ;-). */
#define DEFUN(funcname, cmdname, cmdstr, helpstr) \
DEFUN_CMD_FUNC_DECL(funcname) \
DEFUN_CMD_ELEMENT(funcname, cmdname, cmdstr, helpstr, 0, 0) \
DEFUN_CMD_FUNC_TEXT(funcname)
Which means :
#define DEFUN_CMD_FUNC_DECL(funcname) \
static int funcname (struct cmd_element *, struct vty *, int, const char *[]);
#define DEFUN_CMD_ELEMENT(funcname, cmdname, cmdstr, helpstr, attrs, dnum) \
struct cmd_element cmdname = \
{ \
.string = cmdstr, \
.func = funcname, \
.doc = helpstr, \
.attr = attrs, \
.daemon = dnum, \
};
#define DEFUN_CMD_FUNC_TEXT(funcname) \
static int funcname \
(struct cmd_element *self __attribute__ ((unused)), \
struct vty *vty __attribute__ ((unused)), \
int argc __attribute__ ((unused)), \
const char *argv[] __attribute__ ((unused)) )
To see how the macro is used according to the interface for quagga's
usage of ldp-portable, maybe an example would be nice :
This is the first example you can find in quagga-mpls/ldpd/ldp_vty.c
DEFUN (mpls_ldp,
mpls_ldp_cmd,
"mpls ldp",
"Global MPLS configuration\n"
"Dynamic Label distribution via LDP\n")
{
vty->node = LDP_NODE;
vty->index = ldp_get();
if (!vty->index) {
if (!(vty->index = ldp_new())) {
vty_out (vty, "Unable to create LDP instance.%s", VTY_NEWLINE);
return CMD_WARNING;
}
}
return CMD_SUCCESS;
}
And my question is : what is "mpls_ldp" or any other functions
declared by the DEFUN macro? Is this a command we can use on the
interface?
Thank you for your help.
Julien
--
--------------------------------------------
Julien BISCONTI <julien.bisconti(at)student.fundp.ac.be>
M.Sc. student in Computer Science, University of Namur
FUNDP, Belgium
Traineeship: UPC (Barcelona, Spain)
|
|
From: Julien B. <jul...@gm...> - 2006-12-18 14:31:04
|
Hello everybody, On 12/14/06, James R. Leu <jl...@mi...> wrote: > > Hello, > > Basically MPLS LDP (quagga-mpls + ldp-portable) is only ready for > people who are willing to help debug. So far I think there are three > people besides me who have had some level of success using it. All of > them > downloaded the code from my development tree and compiled it themselves. I'm on Gentoo with a kernel 2.6.18.2 MPLS (downloaded from the repository) and GCC 4.1.1 (Gentoo 4.1.1-r1). I would to say that I had to "modify" the code to compile everything cleanly. For example, If you have an error like this : ../lib/prefix.h:40: error: expected specifier-qualifier-list before 'u_char= ' ../lib/prefix.h:61: error: expected specifier-qualifier-list before 'u_char= ' ../lib/prefix.h:70: error: expected specifier-qualifier-list before 'u_char= ' ../lib/prefix.h:78: error: expected specifier-qualifier-list before 'u_char= ' ../lib/prefix.h:87: error: expected specifier-qualifier-list before 'u_char= ' ../lib/prefix.h:157: error: expected '=3D', ',', ';', 'asm' or '__attribute= __' before 'ip_masklen' This SHOULD be solve by adding: #include <linux/types.h> but it didn't work for me (don't know why). So I add them manually (it's ugly, I know) I created a patch to show you what are my changes : http://www.info.fundp.ac.be/~jbiscont/file/patch_compile_quagga-mpls.patch<= http://www.info.fundp.ac.be/%7Ejbiscont/file/patch_compile_quagga-mpls.patc= h> This was made according to the latest version of quagga-mpls. And this is the script to use aclocal, automake, autoconf, blablabla... ---------------------------------------------------------------------------= ------------------- #!/bin/sh # These commands are working on gentoo with gcc-4.1.1 (Gentoo 4.1.1-r1) and #autoheader (GNU Autoconf) 2.60 #autoconf (GNU Autoconf) 2.60 #ltmain.sh (GNU libtool) 1.5.22 (1.1220.2.365 2005/12/18 22:14:06) #libtoolize (GNU libtool) 1.5.22 #aclocal (GNU automake) 1.9.6 #automake (GNU automake) 1.9.6 echo "TOOLS VERIONS:" for tool in autoheader autoconf libtool libtoolize aclocal automake; do $tool --version | head -1 done aclocal libtoolize --copy --force --automake aclocal autoconf autoheader automake --add-missing --copy ---------------------------------------------------------------------------= --------------- Until I get more feed back from people about them being able to successfull= y > use MPLS LDP, I will not release a new version. I hope it helps and don't forget to create the links for ldp-portable (it's so obvious that you are able to forget about it ;-) ) Sincerely, Julien On Thu, Dec 14, 2006 at 09:09:45AM +0530, Neha Singh wrote: > > Hello, > > > > Thank you for your response. > > > > I also want to know if the user version of MPLS LDP is available just > like > > the user version for the MPLS Forwarding Plane. If it is available > please > > provide me the link for the same. > > > > Regards > > > > Neha Singh. > > > > > > > > On 12/13/06, James R. Leu <jl...@mi...> wrote: > > > > > >A quick search of the archives will show that the version of > > >LDP in the current quagga-mpls release is not designed for users (it > > >was a development release). > > > > > >If you are interested in work with LDP and are willing to help > > >in the debugging process, please download the lastest quagga-mpls from > > >my development tree (see http://mpls-linux.sf.net for more info) > > > > > >Make sure to search the archive before posting to the mailing list. > > > > > >On Wed, Dec 13, 2006 at 02:25:35PM +0530, Neha Singh wrote: > > >> Hello, > > >> > > >> We have downloaded and installed mpls (1.950) with all other > utilities > > >give > > >> in the sourceforge site. > > >> > > >> The mpls forwarding engine works fine. we tested the same using > "mpls" > > >> command suite provided in iproute2 for mpls 1.950. > > >> > > >> Now we are trying to atuomate this using LDP > > >> > > >> When we start ldpd it runs as shown below :- > > >> > > >> quagga 11410 11319 0 13:39 pts/1 00:00:00 /usr/sbin/ldpd -f > > >> /etc/quagga/ldpd.conf > > >> > > >> > > >> when we give the following command:- > > >> > > >> VPLS22> en > > >> Password: > > >> VPLS22# con > > >> VPLS22# configure t > > >> VPLS22# configure terminal > > >> VPLS22(config)# mpl > > >> VPLS22(config)# mpls ld > > >> VPLS22(config)# mpls ldp > > >> VPLS22(config-ldp)# > > >> > > >> > > >> The LDPD daemon/process used to crash abruptly. Upon debugging we > found > > >that > > >> "creation of ldp hello socket fails with bind error : bind failed : > : > > >> Permission denied". > > >> > > >> > > >> As you can see the user id with which the ldpd runs is quagga ... > > >> > > >> > > >> We had tried the old version of ldp which runs with root as userid . > it > > >> starts with no problem and also exchanges the labels. but has > problems > > >in > > >> communicating with kernel. > > >> > > >> Hence we downloaded the latest LDPD and mpls package (1.950) as give= n > in > > >> sourceforge website. > > >> > > >> However when we run the ldpd it fails with the error stated above. > > >> > > >> Please suggest us what is to be done to over come this problem. and > get > > >ldp > > >> going :-) > > >> > > >> > > >> Thank you > > > > > >> > > > >------------------------------------------------------------------------= - > > >> Take Surveys. Earn Cash. Influence the Future of IT > > >> Join SourceForge.net's Techsay panel and you'll get the chance to > share > > >your > > >> opinions on IT & business topics through brief surveys - and earn > cash > > >> > > > > http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3D= DEVDEV > > >> _______________________________________________ > > >> mpls-linux-devel mailing list > > >> mpl...@li... > > >> https://lists.sourceforge.net/lists/listinfo/mpls-linux-devel > > > > > > > > >-- > > >James R. Leu > > >jl...@mi... > > > > > > > > > > > > > ------------------------------------------------------------------------- > > Take Surveys. Earn Cash. Influence the Future of IT > > Join SourceForge.net's Techsay panel and you'll get the chance to share > your > > opinions on IT & business topics through brief surveys - and earn cash > > > http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3D= DEVDEV > > _______________________________________________ > > mpls-linux-devel mailing list > > mpl...@li... > > https://lists.sourceforge.net/lists/listinfo/mpls-linux-devel > > > -- > James R. Leu > jl...@mi... > > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share > your > opinions on IT & business topics through brief surveys - and earn cash > http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3D= DEVDEV > > _______________________________________________ > mpls-linux-devel mailing list > mpl...@li... > https://lists.sourceforge.net/lists/listinfo/mpls-linux-devel > > > > --=20 -------------------------------------------- Julien BISCONTI <julien.bisconti(at)student.fundp.ac.be> M.Sc. student in Computer Science, University of Namur FUNDP, Belgium Traineeship: UPC (Barcelona, Spain) GSM BELGIQUE: +32 474 598 418 GSM ESPA=D1A: +34 671 168 458 |
14 messages has been excluded from this view by a project administrator.
