Thread: [mpls-linux-general] ldp-portable

SourceForge Headquarters 1320 Columbia Street Suite 310 San Diego, CA 92101 +1 (858) 422-6466

Dear all,

Is it possible to use ldp -portable with the "gated" routing code instead of
the "zebra"one.

Thank you for an answer,

Jacques

Hi lists,

I have installed Fedora Core 2 and I have applied the patch=20
of mpls 1.946 and everything is
ok. Afterwards, I installed quagga 0.96=20
and I have applied the ldp-portable 0.800 patch:
quagga-mpls.diff and=20
then i modified and execute 'create-links'. Then, I configure and=20
compile quagga and while compiling I have an error about "mpls-linux.
o", and it says that
it does not know how to build the file (I believe=20
it is because the file does not exist).
The file "README.quagga-mpls"=20
says that if you are not running on a mpls-linux enabled
kernel, modify=20
quagga/zebra/Makefile.am and change mpls-linux.o to mpl_null.o; but I=20
don't
think I have to do so because I have a Kernel 2.6.9 with mpls=20
1.946. Do you know what
I can do with mpls-linux.o?

Thanks in advance

Prueba el Nuevo Correo Terra; Seguro, R=C3=A1pido, Fiable.

Did you do anything with you're /usr/include/linux directory.  If
you want to compile quagga with mpls-linux suport you need to have
the file /usr/include/linux/mpls.h  You can get this file from your
mpls-linux kernel source (linux-kernel/include/linux/mpls.h)

As I tell anyone who is trying to using quagga-mpls, it is not ready for
users.  It is still very buggy and needs more development work.  If you
plan on helping with development, you're better off getting the latest
quagga-mpls code from my development tree (see http://mpls-linux.sf.net for
more info).

On Wed, Nov 23, 2005 at 10:20:36AM +0100, EMI...@te... wrote:
> Hi lists,
>=20
> I have installed Fedora Core 2 and I have applied the patch=20
> of mpls 1.946 and everything is
> ok. Afterwards, I installed quagga 0.96=20
> and I have applied the ldp-portable 0.800 patch:
> quagga-mpls.diff and=20
> then i modified and execute 'create-links'. Then, I configure and=20
> compile quagga and while compiling I have an error about "mpls-linux.
> o", and it says that
> it does not know how to build the file (I believe=20
> it is because the file does not exist).
> The file "README.quagga-mpls"=20
> says that if you are not running on a mpls-linux enabled
> kernel, modify=20
> quagga/zebra/Makefile.am and change mpls-linux.o to mpl_null.o; but I=20
> don't
> think I have to do so because I have a Kernel 2.6.9 with mpls=20
> 1.946. Do you know what
> I can do with mpls-linux.o?
>=20
> Thanks in advance
>=20
>=20
> Prueba el Nuevo Correo Terra; Seguro, R??pido, Fiable.
>=20
>=20
>=20
> -------------------------------------------------------
> This SF.Net email is sponsored by the JBoss Inc.  Get Certified Today
> Register for a JBoss Training Course.  Free Certification Exam
> for All Training Attendees Through End of 2005. For more info visit:
> http://ads.osdn.com/?ad_idv28&alloc_id=16845&op?k
> _______________________________________________
> mpls-linux-general mailing list
> mpl...@li...
> https://lists.sourceforge.net/lists/listinfo/mpls-linux-general

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

Hi,

 this is a raw (unlinted, unindented, it will eat your boot sector) diff of
my ldp-portable tree vs cvs (i hope).

lib:
 * be quiet, remove prints.
 * exit decode loop on error, it will endlessly loop otherwise. (i tested
    ldp-portable against the indian (bangalore) ldp stuff, it would endlessly
    loop (they are using some private definition of ldp, apparently).
 * assorted random patches I've forgotten what they were about (mostly to
    avoid asserts and NULLs for some particular states I've encountered and
    I couldnt explain)

zebra-port:
 * the start of 2 snmp implementations, one of my own, the other an ugly hacked
     version of smidumps version (now that they are cleaning the mpls mib
     mess and smidump can swallow all of them, btw the OIDS havent been
     assigned yet, I use transmission.188.646 for the start of the ldp mib).
     They dont quite work, but I think there were some ppl interested
     in doing snmp development, this might be helpful.
 * make depend
 * outdated README
 * GPL boiler plate & (c)s , jim is missing from some (C).
 * changed the memory allocation to use differentiated names, so leaks are
    easier to pinpoint. (mostly bgp names)(not that I'm debugging that yet)
 * zebra will send funny routes when it doesnt manage to instatiate the
     route in the kernel FIB, avoid dying.
 * it compiles with an april zebra cvs version
 * interface startup doesnt have a 3 second hold time anymore
 * "show ldp bindings" can filter by binding type (usually only map_(recv|sent)
    are of any interest (and present at all longer than 1 second, AFAIK))
 * configure per interface hello/keepalive hold/interval timers commands
 * configure per interface distribution mode (aka "make me core dump")
 * commands to configure resources, paths and tunnels. Nothing useful. I
    implemented the following: When the egress/32 for a tunnel (show mpls ldp
    egress) gets mapped and installed an interface is brought up and bound
    to that label. That interface follows the label should it ever change.
    If you want routes to follow that interface just add routes in zebra (ip
    route bgp-nexthop/32 tunnel_44t0). Handle with care. Do not loop
    your route recursion.

 The zebra port is still for the old kernel interface, I'm waiting for Jorge
Boncompte <jo...@dt...> to release his port to the new world order kernel
interface, I hope to integrate both making it a -D option (before september,
I hope).

 BTW, why do have mpls tunnel interface have an mtu of underlying interface
minus 4 bytes? We are sending oversized labeled packets over the hw interface,
why backoff now? IMHO label stacking is not a reason, as it applies to the
non-interface case, too. Jim?

regards
 yon