mpls-linux-devel — Mailig list for discussing the development of MPLS on Linux

[mpls-linux-devel] Quagga-MPLS

[<gsr...@al...>]

Hi!

I've been working with quagga and ldp portable from Source Forge but now =
I'm trying to test your Quagga-MPLS and LDP-Portable from your P4 =
repository. I got some problems during installation.=20

To generate configure file from configure.ac I use AUTOCONF, but this is =
what I get:

'is already registered with AC_CONFIG_FILES
autoconf /status.m4:848: AC_CONFIG_FILES is expanded from...
configure.ac:1389: the top level=20
autom4te:/usr/bin/m4 failed with exit status 1

If I use automake to create Makefile.in (then executinc ./configure =
should create Makefile's of each component)I got the same.
I upgraded M4 and the problem persist, any idea?

Anything about how you installed it would be very useful, thanks!

[mpls-linux-devel] ldp-portable update

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

Just a quick note to anyone who is working with LDP portable and
quagga-mpls from my development tree, you will want to update your
ldp-portable and quagga-mpls trees.

I have been doing some significant bug hunting that fixes many
of the outstanding issues with quagga-mpls and it's use of ldp-portable.

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

Re: [mpls-linux-devel] LDP-Portable

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

You have the correct version of ldp-portable, I haven't made an official
release in quite sometime, maybe I should fix that :-)

Did you find the 'create-links' script is the quagga-mpls/ldpd directory?
You need to run that to make symbolic links to the files in ldp-portable.
If you use an RPM based system you can use the 'make-rpm-jleu' script at the
top of the quagga-mpls tree to build a RPM from the contents of that tree.

Let me know when you hit problems :-)

On Fri, Sep 29, 2006 at 01:04:53PM +0200, Sienes Rodr?guez Gonzalo wrote:
> Hi!
> =20
> As you told me I downloaded Quagga-MPLS and LDP-Portable (in both, P4 and=
 SF, the file "version" of LDP-Portable shows this: ldp-portable version 0.=
800 (@784),?have I downloaded a wrong file? I guess not) from your P4 repos=
itory, so I have installed this 2 packets instead of the Quagga version und=
er Linux-MPLS-1.950 tree on Source Forge. Now I will test this configuratio=
n in my lab net.
> =20
> Thanks for your help.
>=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...

[mpls-linux-devel] LDP-Portable

[<gsr...@al...>]

Hi!
=20
As you told me I downloaded Quagga-MPLS and LDP-Portable (in both, P4 =
and SF, the file "version" of LDP-Portable shows this: ldp-portable =
version 0.800 (@784),=BFhave I downloaded a wrong file? I guess not) =
from your P4 repository, so I have installed this 2 packets instead of =
the Quagga version under Linux-MPLS-1.950 tree on Source Forge. Now I =
will test this configuration in my lab net.
=20
Thanks for your help.

Re: [mpls-linux-devel] UDEV problems on FC4

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

You will want to grab the latest quagga-mpls and ldp-portable from my
development tree.  I've made significant bug fixes to LDP and the MPLS
framework as a whole.  Start out by reading the instructions on
http://mpls-linux.sf.net/

Let me know if you have any questions about accessing my development tree.

On Thu, Sep 28, 2006 at 12:22:16PM +0200, Sienes Rodr?guez Gonzalo wrote:
> I upgraded udev with the version you told me, and installed module-init-t=
ools required from FC4 upgrades repository. Now it seems to work properly. =
Actually I'm working on Quagga to integrate LDP.
> =20
> Thanks!
> =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...

Re: [mpls-linux-devel] UDEV problems on FC4

[<gsr...@al...>]

I upgraded udev with the version you told me, and installed =
module-init-tools required from FC4 upgrades repository. Now it seems to =
work properly. Actually I'm working on Quagga to integrate LDP.
=20
Thanks!
=20

Re: [mpls-linux-devel] UDEV problems on FC4

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

what version of udev do you have installed?

I'm running FC4 with a MPLS kernel on my laptop:

[jleu jleu-laptop 9:12am] ~-> rpm -qa | grep -E 'mpls|udev'
iptables-ipv6-1.3.0-2_mpls_1.950a
quagga-0.99.2-1_mpls_0.1146448865
quagga-debuginfo-0.99.2-1_mpls_0.1143084500
udev-071-0.FC4.3
kernel-2.6.16-1.2096_FC4mpls1_950a
iptables-1.3.0-2_mpls_1.950a
glibc-kernheaders-3.0-5.2_mpls0.1146448504
iproute-2.6.15-1.2_mpls_0.1146447579
[jleu jleu-laptop 9:13am] ~->


On Wed, Sep 27, 2006 at 12:04:24PM +0200, Sienes Rodr?guez Gonzalo wrote:
> Hi!
> =20
> I'm trying to install mpls-linux kernel on Fedora Core 4, when installing=
 rpm I got an error message: udev, package not found; but when I start Linu=
x udev loads. Does anybody know about this?
> =20
> Thanks!
>=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...

[mpls-linux-devel] UDEV problems on FC4

[<gsr...@al...>]

Hi!
=20
I'm trying to install mpls-linux kernel on Fedora Core 4, when =
installing rpm I got an error message: udev, package not found; but when =
I start Linux udev loads. Does anybody know about this?
=20
Thanks!

Re: [mpls-linux-devel] help on LDP protocol for Quagga.

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

As part of the mpls-linux project I have an implementation of
LDP (ldp-portable).  I have a package called quagga-mpls which includes
LDP.  If you would like to look at the latest work with this, you will need
to pull it from my development repository.  Please see http://mpls-linux.sf=
.net
for more info.

On Sat, Sep 09, 2006 at 03:06:07PM +0530, prachi gaikwad wrote:
> Hello...Im a student of Final Year Computer engineering.
> As part of our curiculum we have to implement a project..me and my
> team-members have decided to implement LDP protocol for Quagga routing
> suite.
> Is the MPLS architecture support needed for quagga or do we have to use s=
ome
> utility to have quagga support MPLS ?
> What does it mean when we say that a router or routing software is MPLS
> enabled ? ..
> please help.....

> -------------------------------------------------------------------------
> 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...

[mpls-linux-devel] help on LDP protocol for Quagga.

[prachi g. <pra...@gm...>]

Hello...Im a student of Final Year Computer engineering.
As part of our curiculum we have to implement a project..me and my
team-members have decided to implement LDP protocol for Quagga routing
suite.
Is the MPLS architecture support needed for quagga or do we have to use some
utility to have quagga support MPLS ?
What does it mean when we say that a router or routing software is MPLS
enabled ? ..
please help.....

[mpls-linux-devel] LDP & CISCO

[GONZALO S. R. <gsr...@al...>]

Hi:
=20
We have a three (Fedora Core 2) routers environment with =
mpls-linux-1.946 from a previous project with a load balancing =
application . Actually we want to work on LDP with quagga, using its =
OSPF daemon, and develope its full funcionality. Besides we expect to =
make it compatible with Cisco routers. So we need to know the real state =
of LDP development and where we have to work to be useful for you, as =
well as the ideal environment to carry out our project.
=20
Thanks.

Re: [mpls-linux-devel] MPLS & linux kernel 2.6.16.2

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

On Wed, Jul 12, 2006 at 08:16:12PM +0200, Marina Mariano wrote:
> Hi James,
>=20
> actually I compiled MPLS as a part of the kernel, not as a Module (by
> chosing Yes in .config). I tried also to compile and load it as a separate
> module but it didn't work.
>=20
> I also loaded as separate modules mpls4 and ipt_mpls.
> Is that enough to include IPv4 binding or I'm still missing something??

I'm not sure having MPLS compiled in and mpls4 as a module will work
(I've never tried it).  If your going to compile MPLS into the kernel you
probably should compile mpls4 in as well.  ipt_mpls is not needed
unless your going to use iptables to map traffic onto LSPs.  mpls and mpls4
allow for using the iproute2 commands to map traffic onto a LSP.

BTW if your interested in contributing your research back to the project
I might have some suggestions as to where you should hook into the
mpls stack.

> Thanks a lot for your precious information,
> Marina
>=20
>=20
> 2006/7/11, James R. Leu <jl...@mi...>:
> >
> >Hello Marina,
> >
> >Did you compile MPLS as a module?  Did you include IPv4 bindings for MPL=
S?
> >Did you load the mpls4 module?
> >
> >On Tue, Jul 11, 2006 at 10:30:55PM +0200, Marina Mariano wrote:
> >> Hi Mr. Leu, hi everybody,
> >>
> >> I'm a Computer Software Engineer student and I'm developing my
> >dissertation
> >> on Load Balancing with MPLS routing.
> >>
> >> I'm trying to use the version 1.950 of the MPLS routing, but I'm facing
> >some
> >> configuration problem after compiling the patch from the sources; I
> >kindly
> >> ask you to help me in this phase.
> >>
> >> I'm using a Debian distribution with the following items:
> >> * Linux kernel v. 2.6.16.2
> >> * iproute2-2.6.16-060323
> >> * iptables-1.3.5
> >> * ebtables-v2.0.8-rc2
> >> * quagga-0.99.4
> >> and, of course, mpls-linux-1.950.
> >>
> >> I applied the patches to the kernel in the indicated order; I found so=
me
> >> rejections (.rej), but I "easily" solved them by hands by slightly
> >modifying
> >> the source code (adding header files, removing ".owner"...)
> >>
> >> My configuration correctly shows the MPLS module as present; I compiled
> >with
> >> no error and installed the new MPLS-powered kernel.
> >>
> >> Despite that, on invoking any MPLS operation (like mpls add nhlfe 0...=
).
> >I
> >> get this message:
> >> RTNETLINK answers: invalid argument
> >>
> >> I'm sure that I'm missing something tremendously obvious!
> >>
> >> In the following, the systrace output for "mpls nhlfe add key 0" - hope
> >it
> >> helps.
> >>
> >> Thank you in advance for any help.
> >> Best regards,
> >> Marina Mariano
> >>
> >> systrace begins....
> >>
> >> execve("/sbin/mpls", ["mpls", "nhlfe", "add", "key", "0"], [/* 28 vars
> >*/])
> >> =3D 0
> >> uname({sys=3D"Linux", node=3D"debian", ...}) =3D 0
> >> brk(0)                                  =3D 0x8053000
> >> old_mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS,
> >-1, 0)
> >> =3D 0xb7f1c000
> >> access("/etc/ld.so.nohwcap", F_OK)      =3D -1 ENOENT (No such file or
> >> directory)
> >> open("/etc/ld.so.preload", O_RDONLY)    =3D -1 ENOENT (No such file or
> >> directory)
> >> open("/etc/ld.so.cache", O_RDONLY)      =3D 3
> >> fstat64(3, {st_mode=3DS_IFREG|0777, st_size=3D55830, ...}) =3D 0
> >> old_mmap(NULL, 55830, PROT_READ, MAP_PRIVATE, 3, 0) =3D 0xb7f0e000
> >> close(3)                                =3D 0
> >> access("/etc/ld.so.nohwcap", F_OK)      =3D -1 ENOENT (No such file or
> >> directory)
> >> open("/lib/tls/libm.so.6", O_RDONLY)    =3D 3
> >> read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\00005\0\000"...,
> >512)
> >> =3D 512
> >> fstat64(3, {st_mode=3DS_IFREG|0777, st_size=3D134496, ...}) =3D 0
> >> old_mmap(NULL, 136976, PROT_READ|PROT_EXEC, MAP_PRIVATE, 3, 0) =3D
> >0xb7eec000
> >> old_mmap(0xb7f0d000, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED,
> >3,
> >> 0x20000) =3D 0xb7f0d000
> >> close(3)                                =3D 0
> >> access("/etc/ld.so.nohwcap", F_OK)      =3D -1 ENOENT (No such file or
> >> directory)
> >> open("/lib/tls/libresolv.so.2", O_RDONLY) =3D 3
> >> read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0\220)\0"...,
> >512) =3D
> >> 512
> >> fstat64(3, {st_mode=3DS_IFREG|0777, st_size=3D64924, ...}) =3D 0
> >> old_mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS,
> >-1, 0)
> >> =3D 0xb7eeb000
> >> old_mmap(NULL, 73640, PROT_READ|PROT_EXEC, MAP_PRIVATE, 3, 0) =3D
> >0xb7ed9000
> >> old_mmap(0xb7ee8000, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED,
> >3,
> >> 0xf000) =3D 0xb7ee8000
> >> old_mmap(0xb7ee9000, 8104, PROT_READ|PROT_WRITE,
> >> MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) =3D 0xb7ee9000
> >> close(3)                                =3D 0
> >> access("/etc/ld.so.nohwcap", F_OK)      =3D -1 ENOENT (No such file or
> >> directory)
> >> open("/lib/tls/libc.so.6", O_RDONLY)    =3D 3
> >> read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0`Z\1\000"...,
> >512) =3D
> >> 512
> >> fstat64(3, {st_mode=3DS_IFREG|0777, st_size=3D1254468, ...}) =3D 0
> >> old_mmap(NULL, 1264780, PROT_READ|PROT_EXEC, MAP_PRIVATE, 3, 0) =3D
> >0xb7da4000
> >> old_mmap(0xb7ece000, 36864, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXE=
D,
> >3,
> >> 0x129000) =3D 0xb7ece000
> >> old_mmap(0xb7ed7000, 7308, PROT_READ|PROT_WRITE,
> >> MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) =3D 0xb7ed7000
> >> close(3)                                =3D 0
> >> set_thread_area({entry_number:-1 -> 6, base_addr:0xb7eebb80,
> >limit:1048575,
> >> seg_32bit:1, contents:0, read_exec_only:0, limit_in_pages:1,
> >> seg_not_present:0, useable:1}) =3D 0
> >> munmap(0xb7f0e000, 55830)               =3D 0
> >> socket(PF_NETLINK, SOCK_RAW, 0)         =3D 3
> >> setsockopt(3, SOL_SOCKET, SO_SNDBUF, [32768], 4) =3D 0
> >> setsockopt(3, SOL_SOCKET, SO_RCVBUF, [32768], 4) =3D 0
> >> bind(3, {sa_family=3DAF_NETLINK, pid=3D0, groups=3D00000000}, 12) =3D 0
> >> getsockname(3, {sa_family=3DAF_NETLINK, pid=3D5298, groups=3D00000000}=
, [12])
> >=3D 0
> >> time(NULL)                              =3D 1152646179
> >> sendto(3, "\24\0\0\0\22\0\1\3$\374\263D\0\0\0\0\0\200\0\0", 20, 0,
> >> {sa_family=3DAF_NETLINK, pid=3D0, groups=3D00000000}, 12) =3D 20
> >> recvmsg(3, {msg_name(12)=3D{sa_family=3DAF_NETLINK, pid=3D0, groups=3D=
00000000},
> >>
> >msg_iov(1)=3D[{"\344\0\0\0\20\0\2\0$\374\263D\262\24\0\0\0\0\4\3\1\0\0".=
..,
> >> 16384}], msg_controllen=3D0, msg_flags=3D0}, 0) =3D 896
> >> brk(0)                                  =3D 0x8053000
> >> brk(0x8074000)                          =3D 0x8074000
> >> brk(0)                                  =3D 0x8074000
> >> recvmsg(3, {msg_name(12)=3D{sa_family=3DAF_NETLINK, pid=3D0, groups=3D=
00000000},
> >>
> >msg_iov(1)=3D[{"\24\0\0\0\3\0\2\0$\374\263D\262\24\0\0\0\0\0\0\1\0\0\0".=
..,
> >> 16384}], msg_controllen=3D0, msg_flags=3D0}, 0) =3D 20
> >> sendmsg(3, {msg_name(12)=3D{sa_family=3DAF_NETLINK, pid=3D0, groups=3D=
00000000},
> >>
> >msg_iov(1)=3D[{"\204\10\0\0\20\0\1\4%\374\263D\0\0\0\0\36\0\0\0\0\0\0\0"=
...,
> >> 2180}], msg_controllen=3D0, msg_flags=3D0}, 0) =3D 2180
> >> recvmsg(3, {msg_name(12)=3D{sa_family=3DAF_NETLINK, pid=3D0, groups=3D=
00000000},
> >>
> >msg_iov(1)=3D[{"$\0\0\0\2\0\0\0%\374\263D\262\24\0\0\352\377\377\377\204=
"...,
> >> 16384}], msg_controllen=3D0, msg_flags=3D0}, 0) =3D 36
> >> dup(2)                                  =3D 4
> >> fcntl64(4, F_GETFL)                     =3D 0x2 (flags O_RDWR)
> >> fstat64(4, {st_mode=3DS_IFCHR|0620, st_rdev=3Dmakedev(136, 1), ...}) =
=3D 0
> >> mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
> >0) =3D
> >> 0xb7f1b000
> >> _llseek(4, 0, 0xbf92b508, SEEK_CUR)     =3D -1 ESPIPE (Illegal seek)
> >> write(4, "RTNETLINK answers: Invalid argum"..., 36) =3D 36
> >> close(4)                                =3D 0
> >> munmap(0xb7f1b000, 4096)                =3D 0
> >> exit_group(2)                           =3D ?
> >
> >>
> >>
> >-------------------------------------------------------------------------
> >> 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
> >easier
> >> 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&da=
t=3D121642
> >
> >> _______________________________________________
> >> mpls-linux-devel mailing list
> >> mpl...@li...
> >> https://lists.sourceforge.net/lists/listinfo/mpls-linux-devel
> >
> >
> >--
> >James R. Leu
> >jl...@mi...
> >
> >
> >

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

Re: [mpls-linux-devel] MPLS & linux kernel 2.6.16.2

[Marina M. <mac...@gm...>]

Hi James,

actually I compiled MPLS as a part of the kernel, not as a Module (by
chosing Yes in .config). I tried also to compile and load it as a separate
module but it didn't work.

I also loaded as separate modules mpls4 and ipt_mpls.
Is that enough to include IPv4 binding or I'm still missing something??

Thanks a lot for your precious information,
Marina


2006/7/11, James R. Leu <jl...@mi...>:
>
> Hello Marina,
>
> Did you compile MPLS as a module?  Did you include IPv4 bindings for MPLS?
> Did you load the mpls4 module?
>
> On Tue, Jul 11, 2006 at 10:30:55PM +0200, Marina Mariano wrote:
> > Hi Mr. Leu, hi everybody,
> >
> > I'm a Computer Software Engineer student and I'm developing my
> dissertation
> > on Load Balancing with MPLS routing.
> >
> > I'm trying to use the version 1.950 of the MPLS routing, but I'm facing
> some
> > configuration problem after compiling the patch from the sources; I
> kindly
> > ask you to help me in this phase.
> >
> > I'm using a Debian distribution with the following items:
> > * Linux kernel v. 2.6.16.2
> > * iproute2-2.6.16-060323
> > * iptables-1.3.5
> > * ebtables-v2.0.8-rc2
> > * quagga-0.99.4
> > and, of course, mpls-linux-1.950.
> >
> > I applied the patches to the kernel in the indicated order; I found some
> > rejections (.rej), but I "easily" solved them by hands by slightly
> modifying
> > the source code (adding header files, removing ".owner"...)
> >
> > My configuration correctly shows the MPLS module as present; I compiled
> with
> > no error and installed the new MPLS-powered kernel.
> >
> > Despite that, on invoking any MPLS operation (like mpls add nhlfe 0...).
> I
> > get this message:
> > RTNETLINK answers: invalid argument
> >
> > I'm sure that I'm missing something tremendously obvious!
> >
> > In the following, the systrace output for "mpls nhlfe add key 0" - hope
> it
> > helps.
> >
> > Thank you in advance for any help.
> > Best regards,
> > Marina Mariano
> >
> > systrace begins....
> >
> > execve("/sbin/mpls", ["mpls", "nhlfe", "add", "key", "0"], [/* 28 vars
> */])
> > = 0
> > uname({sys="Linux", node="debian", ...}) = 0
> > brk(0)                                  = 0x8053000
> > old_mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS,
> -1, 0)
> > = 0xb7f1c000
> > access("/etc/ld.so.nohwcap", F_OK)      = -1 ENOENT (No such file or
> > directory)
> > open("/etc/ld.so.preload", O_RDONLY)    = -1 ENOENT (No such file or
> > directory)
> > open("/etc/ld.so.cache", O_RDONLY)      = 3
> > fstat64(3, {st_mode=S_IFREG|0777, st_size=55830, ...}) = 0
> > old_mmap(NULL, 55830, PROT_READ, MAP_PRIVATE, 3, 0) = 0xb7f0e000
> > close(3)                                = 0
> > access("/etc/ld.so.nohwcap", F_OK)      = -1 ENOENT (No such file or
> > directory)
> > open("/lib/tls/libm.so.6", O_RDONLY)    = 3
> > read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\00005\0\000"...,
> 512)
> > = 512
> > fstat64(3, {st_mode=S_IFREG|0777, st_size=134496, ...}) = 0
> > old_mmap(NULL, 136976, PROT_READ|PROT_EXEC, MAP_PRIVATE, 3, 0) =
> 0xb7eec000
> > old_mmap(0xb7f0d000, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED,
> 3,
> > 0x20000) = 0xb7f0d000
> > close(3)                                = 0
> > access("/etc/ld.so.nohwcap", F_OK)      = -1 ENOENT (No such file or
> > directory)
> > open("/lib/tls/libresolv.so.2", O_RDONLY) = 3
> > read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0\220)\0"...,
> 512) =
> > 512
> > fstat64(3, {st_mode=S_IFREG|0777, st_size=64924, ...}) = 0
> > old_mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS,
> -1, 0)
> > = 0xb7eeb000
> > old_mmap(NULL, 73640, PROT_READ|PROT_EXEC, MAP_PRIVATE, 3, 0) =
> 0xb7ed9000
> > old_mmap(0xb7ee8000, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED,
> 3,
> > 0xf000) = 0xb7ee8000
> > old_mmap(0xb7ee9000, 8104, PROT_READ|PROT_WRITE,
> > MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0xb7ee9000
> > close(3)                                = 0
> > access("/etc/ld.so.nohwcap", F_OK)      = -1 ENOENT (No such file or
> > directory)
> > open("/lib/tls/libc.so.6", O_RDONLY)    = 3
> > read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0`Z\1\000"...,
> 512) =
> > 512
> > fstat64(3, {st_mode=S_IFREG|0777, st_size=1254468, ...}) = 0
> > old_mmap(NULL, 1264780, PROT_READ|PROT_EXEC, MAP_PRIVATE, 3, 0) =
> 0xb7da4000
> > old_mmap(0xb7ece000, 36864, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED,
> 3,
> > 0x129000) = 0xb7ece000
> > old_mmap(0xb7ed7000, 7308, PROT_READ|PROT_WRITE,
> > MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0xb7ed7000
> > close(3)                                = 0
> > set_thread_area({entry_number:-1 -> 6, base_addr:0xb7eebb80,
> limit:1048575,
> > seg_32bit:1, contents:0, read_exec_only:0, limit_in_pages:1,
> > seg_not_present:0, useable:1}) = 0
> > munmap(0xb7f0e000, 55830)               = 0
> > socket(PF_NETLINK, SOCK_RAW, 0)         = 3
> > setsockopt(3, SOL_SOCKET, SO_SNDBUF, [32768], 4) = 0
> > setsockopt(3, SOL_SOCKET, SO_RCVBUF, [32768], 4) = 0
> > bind(3, {sa_family=AF_NETLINK, pid=0, groups=00000000}, 12) = 0
> > getsockname(3, {sa_family=AF_NETLINK, pid=5298, groups=00000000}, [12])
> = 0
> > time(NULL)                              = 1152646179
> > sendto(3, "\24\0\0\0\22\0\1\3$\374\263D\0\0\0\0\0\200\0\0", 20, 0,
> > {sa_family=AF_NETLINK, pid=0, groups=00000000}, 12) = 20
> > recvmsg(3, {msg_name(12)={sa_family=AF_NETLINK, pid=0, groups=00000000},
> >
> msg_iov(1)=[{"\344\0\0\0\20\0\2\0$\374\263D\262\24\0\0\0\0\4\3\1\0\0"...,
> > 16384}], msg_controllen=0, msg_flags=0}, 0) = 896
> > brk(0)                                  = 0x8053000
> > brk(0x8074000)                          = 0x8074000
> > brk(0)                                  = 0x8074000
> > recvmsg(3, {msg_name(12)={sa_family=AF_NETLINK, pid=0, groups=00000000},
> >
> msg_iov(1)=[{"\24\0\0\0\3\0\2\0$\374\263D\262\24\0\0\0\0\0\0\1\0\0\0"...,
> > 16384}], msg_controllen=0, msg_flags=0}, 0) = 20
> > sendmsg(3, {msg_name(12)={sa_family=AF_NETLINK, pid=0, groups=00000000},
> >
> msg_iov(1)=[{"\204\10\0\0\20\0\1\4%\374\263D\0\0\0\0\36\0\0\0\0\0\0\0"...,
> > 2180}], msg_controllen=0, msg_flags=0}, 0) = 2180
> > recvmsg(3, {msg_name(12)={sa_family=AF_NETLINK, pid=0, groups=00000000},
> >
> msg_iov(1)=[{"$\0\0\0\2\0\0\0%\374\263D\262\24\0\0\352\377\377\377\204"...,
> > 16384}], msg_controllen=0, msg_flags=0}, 0) = 36
> > dup(2)                                  = 4
> > fcntl64(4, F_GETFL)                     = 0x2 (flags O_RDWR)
> > fstat64(4, {st_mode=S_IFCHR|0620, st_rdev=makedev(136, 1), ...}) = 0
> > mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
> 0) =
> > 0xb7f1b000
> > _llseek(4, 0, 0xbf92b508, SEEK_CUR)     = -1 ESPIPE (Illegal seek)
> > write(4, "RTNETLINK answers: Invalid argum"..., 36) = 36
> > close(4)                                = 0
> > munmap(0xb7f1b000, 4096)                = 0
> > exit_group(2)                           = ?
>
> >
> >
> -------------------------------------------------------------------------
> > 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
> easier
> > Download IBM WebSphere Application Server v.1.0.1 based on Apache
> Geronimo
> > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
>
> > _______________________________________________
> > mpls-linux-devel mailing list
> > mpl...@li...
> > https://lists.sourceforge.net/lists/listinfo/mpls-linux-devel
>
>
> --
> James R. Leu
> jl...@mi...
>
>
>

Re: [mpls-linux-devel] MPLS & linux kernel 2.6.16.2

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

Hello Marina,

Did you compile MPLS as a module?  Did you include IPv4 bindings for MPLS?
Did you load the mpls4 module?

On Tue, Jul 11, 2006 at 10:30:55PM +0200, Marina Mariano wrote:
> Hi Mr. Leu, hi everybody,
>=20
> I'm a Computer Software Engineer student and I'm developing my dissertati=
on
> on Load Balancing with MPLS routing.
>=20
> I'm trying to use the version 1.950 of the MPLS routing, but I'm facing s=
ome
> configuration problem after compiling the patch from the sources; I kindly
> ask you to help me in this phase.
>=20
> I'm using a Debian distribution with the following items:
> * Linux kernel v. 2.6.16.2
> * iproute2-2.6.16-060323
> * iptables-1.3.5
> * ebtables-v2.0.8-rc2
> * quagga-0.99.4
> and, of course, mpls-linux-1.950.
>=20
> I applied the patches to the kernel in the indicated order; I found some
> rejections (.rej), but I "easily" solved them by hands by slightly modify=
ing
> the source code (adding header files, removing ".owner"...)
>=20
> My configuration correctly shows the MPLS module as present; I compiled w=
ith
> no error and installed the new MPLS-powered kernel.
>=20
> Despite that, on invoking any MPLS operation (like mpls add nhlfe 0...). I
> get this message:
> RTNETLINK answers: invalid argument
>=20
> I'm sure that I'm missing something tremendously obvious!
>=20
> In the following, the systrace output for "mpls nhlfe add key 0" - hope it
> helps.
>=20
> Thank you in advance for any help.
> Best regards,
> Marina Mariano
>=20
> systrace begins....
>=20
> execve("/sbin/mpls", ["mpls", "nhlfe", "add", "key", "0"], [/* 28 vars */=
])
> =3D 0
> uname({sys=3D"Linux", node=3D"debian", ...}) =3D 0
> brk(0)                                  =3D 0x8053000
> old_mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1,=
 0)
> =3D 0xb7f1c000
> access("/etc/ld.so.nohwcap", F_OK)      =3D -1 ENOENT (No such file or
> directory)
> open("/etc/ld.so.preload", O_RDONLY)    =3D -1 ENOENT (No such file or
> directory)
> open("/etc/ld.so.cache", O_RDONLY)      =3D 3
> fstat64(3, {st_mode=3DS_IFREG|0777, st_size=3D55830, ...}) =3D 0
> old_mmap(NULL, 55830, PROT_READ, MAP_PRIVATE, 3, 0) =3D 0xb7f0e000
> close(3)                                =3D 0
> access("/etc/ld.so.nohwcap", F_OK)      =3D -1 ENOENT (No such file or
> directory)
> open("/lib/tls/libm.so.6", O_RDONLY)    =3D 3
> read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\00005\0\000"..., 5=
12)
> =3D 512
> fstat64(3, {st_mode=3DS_IFREG|0777, st_size=3D134496, ...}) =3D 0
> old_mmap(NULL, 136976, PROT_READ|PROT_EXEC, MAP_PRIVATE, 3, 0) =3D 0xb7ee=
c000
> old_mmap(0xb7f0d000, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED, 3,
> 0x20000) =3D 0xb7f0d000
> close(3)                                =3D 0
> access("/etc/ld.so.nohwcap", F_OK)      =3D -1 ENOENT (No such file or
> directory)
> open("/lib/tls/libresolv.so.2", O_RDONLY) =3D 3
> read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0\220)\0"..., 512)=
 =3D
> 512
> fstat64(3, {st_mode=3DS_IFREG|0777, st_size=3D64924, ...}) =3D 0
> old_mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1,=
 0)
> =3D 0xb7eeb000
> old_mmap(NULL, 73640, PROT_READ|PROT_EXEC, MAP_PRIVATE, 3, 0) =3D 0xb7ed9=
000
> old_mmap(0xb7ee8000, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED, 3,
> 0xf000) =3D 0xb7ee8000
> old_mmap(0xb7ee9000, 8104, PROT_READ|PROT_WRITE,
> MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) =3D 0xb7ee9000
> close(3)                                =3D 0
> access("/etc/ld.so.nohwcap", F_OK)      =3D -1 ENOENT (No such file or
> directory)
> open("/lib/tls/libc.so.6", O_RDONLY)    =3D 3
> read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0`Z\1\000"..., 512=
) =3D
> 512
> fstat64(3, {st_mode=3DS_IFREG|0777, st_size=3D1254468, ...}) =3D 0
> old_mmap(NULL, 1264780, PROT_READ|PROT_EXEC, MAP_PRIVATE, 3, 0) =3D 0xb7d=
a4000
> old_mmap(0xb7ece000, 36864, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED, =
3,
> 0x129000) =3D 0xb7ece000
> old_mmap(0xb7ed7000, 7308, PROT_READ|PROT_WRITE,
> MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) =3D 0xb7ed7000
> close(3)                                =3D 0
> set_thread_area({entry_number:-1 -> 6, base_addr:0xb7eebb80, limit:104857=
5,
> seg_32bit:1, contents:0, read_exec_only:0, limit_in_pages:1,
> seg_not_present:0, useable:1}) =3D 0
> munmap(0xb7f0e000, 55830)               =3D 0
> socket(PF_NETLINK, SOCK_RAW, 0)         =3D 3
> setsockopt(3, SOL_SOCKET, SO_SNDBUF, [32768], 4) =3D 0
> setsockopt(3, SOL_SOCKET, SO_RCVBUF, [32768], 4) =3D 0
> bind(3, {sa_family=3DAF_NETLINK, pid=3D0, groups=3D00000000}, 12) =3D 0
> getsockname(3, {sa_family=3DAF_NETLINK, pid=3D5298, groups=3D00000000}, [=
12]) =3D 0
> time(NULL)                              =3D 1152646179
> sendto(3, "\24\0\0\0\22\0\1\3$\374\263D\0\0\0\0\0\200\0\0", 20, 0,
> {sa_family=3DAF_NETLINK, pid=3D0, groups=3D00000000}, 12) =3D 20
> recvmsg(3, {msg_name(12)=3D{sa_family=3DAF_NETLINK, pid=3D0, groups=3D000=
00000},
> msg_iov(1)=3D[{"\344\0\0\0\20\0\2\0$\374\263D\262\24\0\0\0\0\4\3\1\0\0"..=
.,
> 16384}], msg_controllen=3D0, msg_flags=3D0}, 0) =3D 896
> brk(0)                                  =3D 0x8053000
> brk(0x8074000)                          =3D 0x8074000
> brk(0)                                  =3D 0x8074000
> recvmsg(3, {msg_name(12)=3D{sa_family=3DAF_NETLINK, pid=3D0, groups=3D000=
00000},
> msg_iov(1)=3D[{"\24\0\0\0\3\0\2\0$\374\263D\262\24\0\0\0\0\0\0\1\0\0\0"..=
.,
> 16384}], msg_controllen=3D0, msg_flags=3D0}, 0) =3D 20
> sendmsg(3, {msg_name(12)=3D{sa_family=3DAF_NETLINK, pid=3D0, groups=3D000=
00000},
> msg_iov(1)=3D[{"\204\10\0\0\20\0\1\4%\374\263D\0\0\0\0\36\0\0\0\0\0\0\0".=
..,
> 2180}], msg_controllen=3D0, msg_flags=3D0}, 0) =3D 2180
> recvmsg(3, {msg_name(12)=3D{sa_family=3DAF_NETLINK, pid=3D0, groups=3D000=
00000},
> msg_iov(1)=3D[{"$\0\0\0\2\0\0\0%\374\263D\262\24\0\0\352\377\377\377\204"=
...,
> 16384}], msg_controllen=3D0, msg_flags=3D0}, 0) =3D 36
> dup(2)                                  =3D 4
> fcntl64(4, F_GETFL)                     =3D 0x2 (flags O_RDWR)
> fstat64(4, {st_mode=3DS_IFCHR|0620, st_rdev=3Dmakedev(136, 1), ...}) =3D 0
> mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0)=
 =3D
> 0xb7f1b000
> _llseek(4, 0, 0xbf92b508, SEEK_CUR)     =3D -1 ESPIPE (Illegal seek)
> write(4, "RTNETLINK answers: Invalid argum"..., 36) =3D 36
> close(4)                                =3D 0
> munmap(0xb7f1b000, 4096)                =3D 0
> exit_group(2)                           =3D ?

>=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...

[mpls-linux-devel] MPLS & linux kernel 2.6.16.2

[Marina M. <mac...@gm...>]

 Hi Mr. Leu, hi everybody,

I'm a Computer Software Engineer student and I'm developing my dissertation
on Load Balancing with MPLS routing.

I'm trying to use the version 1.950 of the MPLS routing, but I'm facing some
configuration problem after compiling the patch from the sources; I kindly
ask you to help me in this phase.

I'm using a Debian distribution with the following items:
 * Linux kernel v. 2.6.16.2
 * iproute2-2.6.16-060323
 * iptables-1.3.5
 * ebtables-v2.0.8-rc2
 * quagga-0.99.4
and, of course, mpls-linux-1.950.

I applied the patches to the kernel in the indicated order; I found some
rejections (.rej), but I "easily" solved them by hands by slightly modifying
the source code (adding header files, removing ".owner"...)

My configuration correctly shows the MPLS module as present; I compiled with
no error and installed the new MPLS-powered kernel.

Despite that, on invoking any MPLS operation (like mpls add nhlfe 0...). I
get this message:
RTNETLINK answers: invalid argument

I'm sure that I'm missing something tremendously obvious!

In the following, the systrace output for "mpls nhlfe add key 0" - hope it
helps.

Thank you in advance for any help.
Best regards,
Marina Mariano

systrace begins....

execve("/sbin/mpls", ["mpls", "nhlfe", "add", "key", "0"], [/* 28 vars */])
= 0
uname({sys="Linux", node="debian", ...}) = 0
brk(0)                                  = 0x8053000
old_mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0)
= 0xb7f1c000
access("/etc/ld.so.nohwcap", F_OK)      = -1 ENOENT (No such file or
directory)
open("/etc/ld.so.preload", O_RDONLY)    = -1 ENOENT (No such file or
directory)
open("/etc/ld.so.cache", O_RDONLY)      = 3
fstat64(3, {st_mode=S_IFREG|0777, st_size=55830, ...}) = 0
old_mmap(NULL, 55830, PROT_READ, MAP_PRIVATE, 3, 0) = 0xb7f0e000
close(3)                                = 0
access("/etc/ld.so.nohwcap", F_OK)      = -1 ENOENT (No such file or
directory)
open("/lib/tls/libm.so.6", O_RDONLY)    = 3
read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\00005\0\000"..., 512)
= 512
fstat64(3, {st_mode=S_IFREG|0777, st_size=134496, ...}) = 0
old_mmap(NULL, 136976, PROT_READ|PROT_EXEC, MAP_PRIVATE, 3, 0) = 0xb7eec000
old_mmap(0xb7f0d000, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED, 3,
0x20000) = 0xb7f0d000
close(3)                                = 0
access("/etc/ld.so.nohwcap", F_OK)      = -1 ENOENT (No such file or
directory)
open("/lib/tls/libresolv.so.2", O_RDONLY) = 3
read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0\220)\0"..., 512) =
512
fstat64(3, {st_mode=S_IFREG|0777, st_size=64924, ...}) = 0
old_mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0)
= 0xb7eeb000
old_mmap(NULL, 73640, PROT_READ|PROT_EXEC, MAP_PRIVATE, 3, 0) = 0xb7ed9000
old_mmap(0xb7ee8000, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED, 3,
0xf000) = 0xb7ee8000
old_mmap(0xb7ee9000, 8104, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0xb7ee9000
close(3)                                = 0
access("/etc/ld.so.nohwcap", F_OK)      = -1 ENOENT (No such file or
directory)
open("/lib/tls/libc.so.6", O_RDONLY)    = 3
read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0`Z\1\000"..., 512) =
512
fstat64(3, {st_mode=S_IFREG|0777, st_size=1254468, ...}) = 0
old_mmap(NULL, 1264780, PROT_READ|PROT_EXEC, MAP_PRIVATE, 3, 0) = 0xb7da4000
old_mmap(0xb7ece000, 36864, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED, 3,
0x129000) = 0xb7ece000
old_mmap(0xb7ed7000, 7308, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0xb7ed7000
close(3)                                = 0
set_thread_area({entry_number:-1 -> 6, base_addr:0xb7eebb80, limit:1048575,
seg_32bit:1, contents:0, read_exec_only:0, limit_in_pages:1,
seg_not_present:0, useable:1}) = 0
munmap(0xb7f0e000, 55830)               = 0
socket(PF_NETLINK, SOCK_RAW, 0)         = 3
setsockopt(3, SOL_SOCKET, SO_SNDBUF, [32768], 4) = 0
setsockopt(3, SOL_SOCKET, SO_RCVBUF, [32768], 4) = 0
bind(3, {sa_family=AF_NETLINK, pid=0, groups=00000000}, 12) = 0
getsockname(3, {sa_family=AF_NETLINK, pid=5298, groups=00000000}, [12]) = 0
time(NULL)                              = 1152646179
sendto(3, "\24\0\0\0\22\0\1\3$\374\263D\0\0\0\0\0\200\0\0", 20, 0,
{sa_family=AF_NETLINK, pid=0, groups=00000000}, 12) = 20
recvmsg(3, {msg_name(12)={sa_family=AF_NETLINK, pid=0, groups=00000000},
msg_iov(1)=[{"\344\0\0\0\20\0\2\0$\374\263D\262\24\0\0\0\0\4\3\1\0\0"...,
16384}], msg_controllen=0, msg_flags=0}, 0) = 896
brk(0)                                  = 0x8053000
brk(0x8074000)                          = 0x8074000
brk(0)                                  = 0x8074000
recvmsg(3, {msg_name(12)={sa_family=AF_NETLINK, pid=0, groups=00000000},
msg_iov(1)=[{"\24\0\0\0\3\0\2\0$\374\263D\262\24\0\0\0\0\0\0\1\0\0\0"...,
16384}], msg_controllen=0, msg_flags=0}, 0) = 20
sendmsg(3, {msg_name(12)={sa_family=AF_NETLINK, pid=0, groups=00000000},
msg_iov(1)=[{"\204\10\0\0\20\0\1\4%\374\263D\0\0\0\0\36\0\0\0\0\0\0\0"...,
2180}], msg_controllen=0, msg_flags=0}, 0) = 2180
recvmsg(3, {msg_name(12)={sa_family=AF_NETLINK, pid=0, groups=00000000},
msg_iov(1)=[{"$\0\0\0\2\0\0\0%\374\263D\262\24\0\0\352\377\377\377\204"...,
16384}], msg_controllen=0, msg_flags=0}, 0) = 36
dup(2)                                  = 4
fcntl64(4, F_GETFL)                     = 0x2 (flags O_RDWR)
fstat64(4, {st_mode=S_IFCHR|0620, st_rdev=makedev(136, 1), ...}) = 0
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0xb7f1b000
_llseek(4, 0, 0xbf92b508, SEEK_CUR)     = -1 ESPIPE (Illegal seek)
write(4, "RTNETLINK answers: Invalid argum"..., 36) = 36
close(4)                                = 0
munmap(0xb7f1b000, 4096)                = 0
exit_group(2)                           = ?

Re: [mpls-linux-devel] Need help, Thanks!

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

On Wed, Jun 28, 2006 at 08:43:11PM +0800, shaoshuchao wrote:
>=20
> Hi:
> =20
>     I have run the ldp-quagga on Linux well. Recently we=20
> want to add the multicast function into the ldp-portable, the most thing =
we need=20
> to do is adding a P2MP FEC into LDP and using it.

There is already code for the Martini FEC, full support for it is still in
development.

>     Can u give me some suggestions about where can we=20
> start from? And can we find the development document(e.g. the structure o=
f ldp=20
> design and implemention) somewhere? Thanks!

The code is your best guide.  I'm more then happy to answer specific questi=
ons.

> =20
>     Best Wishes!
> =20
>                                                 Shao=20
> Shu-chao   =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...

[mpls-linux-devel] (no subject)

[Bayo D. <od...@op...>]

--=20
_______________________________________________
Surf the Web in a faster, safer and easier way:
Download Opera 8 at http://www.opera.com

Powered by Outblaze

[mpls-linux-devel] Need help, Thanks!

[shaoshuchao <sha...@12...>]

Hi:
 
    I have run the ldp-quagga on Linux well. Recently we 
want to add the multicast function into the ldp-portable, the most thing we need 
to do is adding a P2MP FEC into LDP and using it.
 
    Can u give me some suggestions about where can we 
start from? And can we find the development document(e.g. the structure of ldp 
design and implemention) somewhere? Thanks!
 
    Best Wishes!
 
                                                Shao 
Shu-chao    

Re: [mpls-linux-devel] ok to apply mpls patch on recent kernel: 2.6.16.18?

[Bob B. <bob...@gm...>]

On 5/31/06, James R. Leu <jl...@mi...> wrote:
> I haven't tried teh recent 2.6.16.x kernels.  I'm assuming it should
> work fine (besides the conflict you mentioned).

Just curious ...
Any more progress on including mpls in vanilla kernel?

-Bob

Re: [mpls-linux-devel] ok to apply mpls patch on recent kernel: 2.6.16.18?

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

I haven't tried teh recent 2.6.16.x kernels.  I'm assuming it should
work fine (besides the conflict you mentioned).

On Tue, May 30, 2006 at 04:27:15PM -0400, Bob Beers wrote:
> Hello James,
>=20
> I noticed in linux 2.6.16.x, TIPC has taken your socket!
>=20
> see include/linux/socket.h:
>=20
> #define AF_WANPIPE	25	/* Wanpipe API Sockets */
> #define AF_LLC		26	/* Linux LLC			*/
> #define AF_TIPC		30	/* TIPC sockets			*/
> #define AF_BLUETOOTH	31	/* Bluetooth sockets 		*/
> #define AF_MAX		32	/* For now.. */
>=20
> I was able to use 29, and with 4 other small fix-ups in:
> net/ipv4/Makefile, net/ipv4/netfilter/Kconfig,
> net/ipv4/netfilter/Makefile, and net/ipv6/netfilter/Makefile
> I was able to apply kernel patch to 2.6.16.18, with only
> one fuzz, and about 12 offsets.
>=20
> I see netfilter has been modified a bit,
> (some of the targets have moved,
>  e.g.: now CONFIG_NETFILTER_XT_TARGET_CLASSIFY
>          was CONFIG_IP_NF_TARGET_CLASSIFY).
>=20
> Is mpls 1.950 still expected to work with 2.6.16.x?
>=20
>=20
>=20
>=20
> I get these warnings/errors when compiling kernel (gcc 3.4.4):
> (but can compile after making included, suggested fixes below)
> ...
>  CC [M]  net/ipv4/netfilter/ipt_mpls.o
> net/ipv4/netfilter/ipt_mpls.c:76: warning: initialization from
> incompatible pointer type
> +++++++++++
> maybe needs: ".checkentry     =3D &checkentry,"
> and change in checkentry function args:
> -	   const struct ipt_entry *e,
> +	  const void *e,
>=20
>=20
>  CC [M]  net/ipv6/netfilter/ip6t_mpls.o
> net/ipv6/netfilter/ip6t_mpls.c:74: warning: initialization from
> incompatible pointer type
> +++++++++++
> maybe needs: ".checkentry     =3D &checkentry,"
>=20
>=20
> CC [M]  net/mpls/mpls_input.o
> net/mpls/mpls_input.c: In function `mpls_skb_recv':
> net/mpls/mpls_input.c:255: error: `ARPHRD_ETHER' undeclared (first use
> in this function)
> net/mpls/mpls_input.c:255: error: (Each undeclared identifier is
> reported only once
> net/mpls/mpls_input.c:255: error: for each function it appears in.)
> net/mpls/mpls_input.c:256: error: `ARPHRD_FDDI' undeclared (first use
> in this function)
> net/mpls/mpls_input.c:257: error: `ARPHRD_IEEE802' undeclared (first
> use in this function)
> net/mpls/mpls_input.c:258: error: `ARPHRD_PPP' undeclared (first use
> in this function)
> net/mpls/mpls_input.c:259: error: `ARPHRD_LOOPBACK' undeclared (first
> use in this function)
> net/mpls/mpls_input.c:260: error: `ARPHRD_HDLC' undeclared (first use
> in this function)
> net/mpls/mpls_input.c:261: error: `ARPHRD_IPGRE' undeclared (first use
> in this function)
> +++++++++++
> maybe needs "#include <linux/if_arp.h>"
>=20
>  CC [M]  net/mpls/mpls_netlink.o
> net/mpls/mpls_netlink.c:39: error: unknown field `owner' specified in
> initializer
> net/mpls/mpls_netlink.c:39: warning: initialization from incompatible
> pointer type
> +++++++++++
> maybe needs to remove " .owner =3D THIS_MODULE,"
>=20
>=20
>=20
> -Bob
>=20
>=20
> -------------------------------------------------------
> All the advantages of Linux Managed Hosting--Without the Cost and Risk!
> Fully trained technicians. The highest number of Red Hat certifications in
> the hosting industry. Fanatical Support. Click to learn more
> http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D107521&bid=3D248729&dat=
=3D121642
> _______________________________________________
> mpls-linux-devel mailing list
> mpl...@li...
> https://lists.sourceforge.net/lists/listinfo/mpls-linux-devel

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

[mpls-linux-devel] ok to apply mpls patch on recent kernel: 2.6.16.18?

[Bob B. <bob...@gm...>]

Hello James,

I noticed in linux 2.6.16.x, TIPC has taken your socket!

see include/linux/socket.h:

#define AF_WANPIPE	25	/* Wanpipe API Sockets */
#define AF_LLC		26	/* Linux LLC			*/
#define AF_TIPC		30	/* TIPC sockets			*/
#define AF_BLUETOOTH	31	/* Bluetooth sockets 		*/
#define AF_MAX		32	/* For now.. */

I was able to use 29, and with 4 other small fix-ups in:
 net/ipv4/Makefile, net/ipv4/netfilter/Kconfig,
 net/ipv4/netfilter/Makefile, and net/ipv6/netfilter/Makefile
 I was able to apply kernel patch to 2.6.16.18, with only
 one fuzz, and about 12 offsets.

I see netfilter has been modified a bit,
 (some of the targets have moved,
  e.g.: now CONFIG_NETFILTER_XT_TARGET_CLASSIFY
          was CONFIG_IP_NF_TARGET_CLASSIFY).

Is mpls 1.950 still expected to work with 2.6.16.x?




I get these warnings/errors when compiling kernel (gcc 3.4.4):
 (but can compile after making included, suggested fixes below)
...
  CC [M]  net/ipv4/netfilter/ipt_mpls.o
net/ipv4/netfilter/ipt_mpls.c:76: warning: initialization from
incompatible pointer type
+++++++++++
maybe needs: ".checkentry     = &checkentry,"
and change in checkentry function args:
-	   const struct ipt_entry *e,
+	  const void *e,


  CC [M]  net/ipv6/netfilter/ip6t_mpls.o
net/ipv6/netfilter/ip6t_mpls.c:74: warning: initialization from
incompatible pointer type
+++++++++++
maybe needs: ".checkentry     = &checkentry,"


 CC [M]  net/mpls/mpls_input.o
net/mpls/mpls_input.c: In function `mpls_skb_recv':
net/mpls/mpls_input.c:255: error: `ARPHRD_ETHER' undeclared (first use
in this function)
net/mpls/mpls_input.c:255: error: (Each undeclared identifier is
reported only once
net/mpls/mpls_input.c:255: error: for each function it appears in.)
net/mpls/mpls_input.c:256: error: `ARPHRD_FDDI' undeclared (first use
in this function)
net/mpls/mpls_input.c:257: error: `ARPHRD_IEEE802' undeclared (first
use in this function)
net/mpls/mpls_input.c:258: error: `ARPHRD_PPP' undeclared (first use
in this function)
net/mpls/mpls_input.c:259: error: `ARPHRD_LOOPBACK' undeclared (first
use in this function)
net/mpls/mpls_input.c:260: error: `ARPHRD_HDLC' undeclared (first use
in this function)
net/mpls/mpls_input.c:261: error: `ARPHRD_IPGRE' undeclared (first use
in this function)
+++++++++++
maybe needs "#include <linux/if_arp.h>"

  CC [M]  net/mpls/mpls_netlink.o
net/mpls/mpls_netlink.c:39: error: unknown field `owner' specified in
initializer
net/mpls/mpls_netlink.c:39: warning: initialization from incompatible
pointer type
+++++++++++
maybe needs to remove " .owner = THIS_MODULE,"



-Bob

[mpls-linux-devel] mpls iptables.diff for 1.3.5 source

[Bob B. <bob...@gm...>]

Hi james,

I wanted to apply mpls patch from 1.950 tarball
 [17503 Dec 14 22:44 iptables.diff]
 to current iptables source (v1.3.5), since I
 don't use FC4.

But it didn't apply cleanly.  So here's a version
 that does. :)  It compiles too.  That's as far
 as I've gone with it.

--
-Bob

Re: [mpls-linux-devel] mpls patch vs. rt patch

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

I'm sure the RT patch doesn't like my locking technique.  Spinlocks are
a big no-no in the RT world ...  probably not going to work together at
this time.  At some point I will modify my locking scheme to not use spinlo=
cks
which will allow the RT patch and MPLS patch to play nicely with each other.

On Tue, Mar 14, 2006 at 07:50:17PM -0500, Bob Beers wrote:
> Hi,
>=20
> I tried applying the patch-2.6.15-rt21  (realtime linux)
>  over my 2.6.15.4 kernel, already patched with mpls
>  (from 1.946), but at compile time I got an error:
>=20
>  CC      net/core/shim.o
> net/core/shim.c:23: error: `SPIN_LOCK_UNLOCKED' undeclared here (not
> in a function)
> make[2]: *** [net/core/shim.o] Error 1
> make[1]: *** [net/core] Error 2
> make: *** [net] Error 2
>=20
>=20
> Do you know if these patches are incompatible, or should I just make
>  sure to apply the patches in the other order?
>=20
> Meanwhile, I'm going to try again with 2.6.15.6, then rt21, then mpls-1.9=
50.
>=20
>=20
> Thanks,
>=20
> -Bob
>=20
>=20
> -------------------------------------------------------
> This SF.Net email is sponsored by xPML, a groundbreaking scripting langua=
ge
> that extends applications into web and mobile media. Attend the live webc=
ast
> and join the prime developer group breaking into this new coding territor=
y!
> http://sel.as-us.falkag.net/sel?cmd______________________________________=
_________
> mpls-linux-devel mailing list
> mpl...@li...
> https://lists.sourceforge.net/lists/listinfo/mpls-linux-devel

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

[mpls-linux-devel] mpls patch vs. rt patch

[Bob B. <bob...@gm...>]

Hi,

I tried applying the patch-2.6.15-rt21  (realtime linux)
 over my 2.6.15.4 kernel, already patched with mpls
 (from 1.946), but at compile time I got an error:

 CC      net/core/shim.o
net/core/shim.c:23: error: `SPIN_LOCK_UNLOCKED' undeclared here (not
in a function)
make[2]: *** [net/core/shim.o] Error 1
make[1]: *** [net/core] Error 2
make: *** [net] Error 2


Do you know if these patches are incompatible, or should I just make
 sure to apply the patches in the other order?

Meanwhile, I'm going to try again with 2.6.15.6, then rt21, then mpls-1.950=
.


Thanks,

-Bob

Re: [mpls-linux-devel] Merging into the kernel?

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

Hello Steven,

On Sun, Feb 26, 2006 at 05:47:22PM +0000, Steven Whitehouse wrote:
> Hi,
>=20
> On Wed, Feb 15, 2006 at 09:40:57PM -0600, James R. Leu wrote:

<snip original XFRM discussion>

> Yes - I wonder though whether we could use a different selector mechanism
> but keeping some of the general framework. When I looked at it, the main
> thing which struck me was that the difficulty in changing the selector
> mechanism was mostly down to the interface (via netlink) to userland.
> Actually changing it on the kernel side is not impossible I think.

If this can be done in an efficient manor, I think it would be more readily
accepted by the powers that be.  Although, every time I look at the problem
it still comes down to something has to be attached to a node in the L3 rou=
ting
table.  I thought about adding a XFRM reference to the IPv4|6 nodes, but ca=
me
to the conclusion that a generic system (the shim layer) would be more
flexible for other protocols.  Also, I thought it would be easier to
implement a new 'shim' hook in other L3 protocols, as opposed to implementi=
ng
a XFRM interface for them.

Perhaps I've overlooked something.  Let me know if you have any ideas
about how to go about this.

<snip XC/radix discussion>

> And of it occured to me that in order to find this out we'd need some
> tools to test against. Please find attached a patch for pktgen (as
> current in davem's net-2.6.17 git tree at kernel.org) to generate
> MPLS packets.
>=20
> The extension allows you to add a stack of labels onto the packets its
> sending out. There is one extra hack which I included: since we know
> how many labels there are in the stack, I've used the bottom of stack
> bit to indicate whether the label should be randomly generated or not.
>=20
> You can thus push a stack of (up to 16 labels) where each label in the
> stack is either a fixed value or random.
>=20
> pgset "mpls 0001000a,0002000a,0000000a"
>=20
> for example pushes labels 16, 32 and 0 (ipv4 null) each with a ttl of 10.
> If you set the bottom of stack bit in one of the labels it will turn on
> the MPLS_RND flag. You can also set and/or reset that flag in the=20
> normal way as well.
>=20
> Patches to pktgen have become very popular of late it seems
> so I'm going to wait until the latest set which are pending at the
> moment have made it into Dave's tree before making a final diff to send
> to Robert Olsson, the maintainer of pktgen.
>=20
> Also if anyone has feedback about this feature, please let me know.

Excellent!  I will play around with this.

> > > I have been giving some thought as to the efficiency of the forwarding
> > > process itself recently, with the idea of "transcoding" the instructi=
ons
> > > as provided via netlink into an efficient byte code to allow faster
> > > execution. The would appear to be considerable scope for merging cert=
ain
> > > instructions (e.g. a pull followed by a push) into one internal instr=
uction
> > > (i.e. the interface would be the same and the effect the same so it
> > > wouldn't break the protocol at all).
> >=20
> > I like the idea.  This is much like what I'm used to in the hardware
> > forwarding world. What you're kind of hinting at it a packet translation
> > engine, this would make it easier to map the forwarding of packets onto=
 FPGA
> > or ASIC based hardware (isn't there a couple of projects doing this
> > for packet filtering? nf-HIPAC)
> >
> Its possible it might make it easier. I have to say that although I'm a
> hardware engineer by training I've never really got into details of
> network interfaces and what its possible to do on the cards. I wouldn't
> be at all surprised if it was the case though and it would be nice to
> do :-)

I think this is a great idea, but would like to worry about getting the base
MPLS code accepted first.  After that we can work on the optimizations.

> > > The various instructions to set/get tcindex and nfmark seem like a
> > > very good plan. I'm considering writing a patch to add setting nfmark
> > > through the ipv4/6/decnet routing tables which I think would be a
> > > generally useful plan. I wonder also if using one or the other or both
> > > of nfmark and/or tcindex as a key in looking up the nhlfe and/or ilm
> > > isn't a bad idea either.
> >=20
> > That might be against the RFCs.  I know I'm already overstepping the
> > RFCs by allowing the EXP bits to determine a NHLFE.
> >
> I wouldn't worry too much about overstepping what the RFCs say so long
> as the result makes sense and the stack can still comply with them on
> all the required points. The main worry with schemes like this is really
> just a question of forwarding speed and whether it will slow things down
> too much.
>=20
> > > If nfmark could be 1:1 with mpls fec, then it might be possible to use
> > > it together with xfrm as the interface for higher level protocols.
> >=20
> > Not sure I follow you here.  Currently with the shim setup there is no
> > NHLFE lookup in the forward path, the NHLFE is bound to the IPv4|6 rout=
e or
> > the eb|iptables rule.
> >
> Ok, let me explain a bit more then.... I'm assuming a scenario where the
> NHFLE is determined based upon nfmark and nfmark is set in the route
> (of whatever protocol). If nfmark were also a key for xfrm then it
> should be possible to "bundle" a set of dst_entry with the MPLS nhlfe
> as the last entry in the stack.

OK.  I understand now.  The existing nffwd instruction handles this but via
a second lookup.  Your idea would eliminate the second lookup.  My
technique allows the nfmark to be used at any node in a LSP, not just on
the ingress LER.

> I haven't got any further with the DECnet interface since I last posted
> but I may well make that my next project,

Let me know if I can be of assistance.

> Steve.

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