One clarification is that in the p4 depot the directory is called quagga-mp=
ls.
(there is a quagga-ldp directory, but that is the old non-mpls infrastructu=
re
implementation).
On Thu, Mar 17, 2005 at 11:26:45PM +0800, Timothy\(???x\) wrote:
> Hi James,
>=20
> I want to make sure the key problem of "quagga+ldp" is not ready for user=
s" is that quagga did not have any infrastructure for MPLS. And you finish =
this part, but still have some problem.
Correct quagga-mpls has the MPLS infrastructure. The ldpd daemon tries
to use that infrastructure. There are bugs in the implementation of ldpd
'porting layer'. The porting layer is all of the code that convert quagga
info into ldp-portable info and makes the calls to the ldp-portable library.
> Could you tell me more concepts about this part, I mean what we need to d=
o to let "quagga+ldp" can work on MPLS, what're the main functions we need=
to implement. And which code I can pay attention to dig in?
In your tree that you compile from, all of the code in the ldpd directory
which is not a symbolic link into the ldp-portable directory is what makes
up the porting layer. I think that the majority of the bugs can be found
there.
Were you able to sync your client?
>=20
> Thanks
>=20
> Best Regards
>=20
> Timothy
> 2005.03.17
--=20
James R. Leu
jl...@mi...
|
