Re: [mpls-linux-general] how much of LDP is actually working?

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

On Tue, Aug 09, 2005 at 03:02:22PM +0300, Razvan Deaconescu wrote:
> Hi James,
>=20
> i have managed to acces your P4 development tree, compile and install
> the latest quagga-mpls suite (ldp included);
>=20
> however i ran in the same problems that are mentioned here
> http://sourceforge.net/mailarchive/message.php?msg_id=3D11547051

The have been significant changes since then.  I wouldn't
trust anything with regards to LDP before 2005.

> you have that demand unsolicited is well tested (and that is what i
> used); did you mean to say that it doesn't crash, or it really works
> (i mean label distribution, LSP generation, MPLS forwarding)?

I should remove that statement.  The internals of LDP have been well
tested on other platforms.  The quagga-mpls infrastructure is immature
and is the source of most of the problems.  The other source of
problems that is I overhauled the FEC handling code to accommodate
non-IPv4 FECs (martini FECs are what I had in mind when making the
changes).

> what i want to know is how much of LDP is actually working? this way i
> can find out whether i haven't made a mistake in my
> install/configuration; is the entire protocol implemented (some parts
> may need adjusting of course) or are the parts of the communication
> protocol that are still missing (in which case i will probably head on
> to the development team :-) )? if the former is true, where should i
> start with "getting my hands dirty": the ldp-portable-0.800 source
> code, or the quagga-zebra interraction with ldp?

I would say 95% of the protocol is implemented.  The parts that are
missing are related to Notification messages.  In addition I haven't
looked over 3036bis yet to see what other changes are needed.

If you're serious about trying to help the first thing to understand
is that the quagga porting layer is modeled after juniper's use of LDP.
In other words don't expect label distribution for every route in the
routing table, only for those which are directly connected to a LDP speaker.
Also I think there is a bug in the MPLS infrastructure for FTN bindings.

Give me some output of show commands and an explanation of what you
would expect to see and we can decide where to focus a bug hunt.

> regards,
> Razvan
>=20
>=20
> -------------------------------------------------------
> SF.Net email is Sponsored by the Better Software Conference & EXPO
> September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practic=
es
> Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
> Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
> _______________________________________________
> mpls-linux-general mailing list
> mpl...@li...
> https://lists.sourceforge.net/lists/listinfo/mpls-linux-general

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