Re: [mpls-linux-general] Zebra-port and Linux-port
Status: Beta
Brought to you by:
jleu
From: James R. L. <jl...@mi...> - 2001-11-27 17:31:15
|
On Tue, Nov 27, 2001 at 06:10:02PM +0100, Kauder Thorsten wrote: > Hi everyone, > I still didn't make it to compile the Zebra port. > While trying to figure out the problem I wondered what the difference > between the two ports might be anyway. > > So here comes the question: > What exactly are these Ports. The linux port uses linux system services to get info about routes/interfaces. It uses its own socket and timer managment functions, the cli is custom as well. The zebra port tries to take advantage of as much of the zebra achitecture as possible. > I tried to work with the Linux-port while distributing routes with zebra. > I don't understand how they could differ, because as far as I understand it > zebra works with the Kernel routing table as well and ldp shouldn't need > anything else. Right now route notification are not being proccessed correctly by the linux port. > > Here's what happens: > after I define global objects on two machines ( LSR-ID 1 and 2) and add the > interfaces on both mashines ( add interface eth0 ) they establish a session. > The machine I generated the routes on in the first place adds incomin labels in > /proc/net/mpls-in but removes the labelspacebinding to eth0. On the other machine > nothing happens in the /proc/net/* > > With ethereal I found out that they are exchanging mappings and wants. > What surprises me the most is, that in the mpls-in file every line starts with > a fec put there aren't any entries in mpls-fec. > > I think that I need to get the ldp_zebra compiled.... > If anyone did manage to do that. please let me know against wich version of zebra. > > Thanks for taking the time reading that. > I would really appreciate it if anyone could help me As soon as I get done releaseing mpls-linxu 1.106 I'll spend sometime on ldp-portable. Jim -- James R. Leu jl...@mi... |