Thread: [mpls-linux-general] ldpd doesn't start properly
Status: Beta
Brought to you by:
jleu
Menu
▾
▴
mpls-linux-general
|
From: Adrian P. <adr...@gm...> - 2006-03-13 13:40:53
|
I'm trying to get ldpd to work and I'm having difficulties. I'm connecting to ldpd using telnet and this is how I configured my LER: e1:/home/irina.dumitrascu# cat /usr/etc/ldpd.conf ! ! Zebra configuration saved from vty ! 2006/03/13 16:01:36 ! hostname uml-1 password root enable password root ! interface eth0 ! interface eth1 mpls ip ! interface eth2 ! interface eth3 ! interface gre0 ! interface ip6tnl0 ! interface lo ! interface mpls0 ! interface sit0 ! interface teql0 ! ! mpls ldp egress connected ! line vty ! On the LSR I set up both interfaces with mpls ip (eth0 and eth1), but when I try to start ldpd on the lsr, it says: e2:/home/irina.dumitrascu# ldpd -u root -P 6222 ldpd: ldp_interface.c:59: ldp_interface_create2: Assertion `li->iff.index' failed. Aborted. I can start it if I comment out the 'mpls ip' lines from interface eth0 and eth1. After I manage to start LDP on the LSR, and try to run show ldp I get an error message: 'There isn't an active LDP instance.' This happens after I have have configured manually the interfaces (mpls ip). When I have the lsr manually configured (172.16.0.3) and the next ler running (172.16.0.2), and on the lsr I issue the command 'mpls ldp' this is what happens: * the ler is constantly sending out LDP Hello packets * when I issue mpls ldp on the lsr, the lsr sends a LDP Hello, and then freezes (actually only ldpd freezes) This is the output of tcpdump 16:18:56.453269 IP 172.16.0.2.646 > 224.0.0.2.646: LDP, Label-Space-ID: 192.168.0.2:0, length: 34 16:19:01.453496 IP 172.16.0.2.646 > 224.0.0.2.646: LDP, Label-Space-ID: 192.168.0.2:0, length: 34 16:19:02.924352 IP 172.16.0.3.646 > 224.0.0.2.646: LDP, Label-Space-ID: 141.85.43.122:0, length: 34 16:19:06.453724 IP 172.16.0.2.646 > 224.0.0.2.646: LDP, Label-Space-ID: 192.168.0.2:0, length: 34 16:19:11.453952 IP 172.16.0.2.646 > 224.0.0.2.646: LDP, Label-Space-ID: 192.168.0.2:0, length: 34 Do you have any idea why this doesn't work? |
|
From: Adrian P. <adr...@gm...> - 2006-03-13 14:01:27
Attachments:
ethereal_output
|
I have some extra information on this. Attached is a packet capture when the two LDP neighbours connect (just before one of them dies) The file is in libpcap format (viewable with tcpdump or with ethereal) On 3/13/06, Adrian Popa <adr...@gm...> wrote: > I'm trying to get ldpd to work and I'm having difficulties. > > I'm connecting to ldpd using telnet and this is how I configured my LER: > > e1:/home/irina.dumitrascu# cat /usr/etc/ldpd.conf > ! > ! Zebra configuration saved from vty > ! 2006/03/13 16:01:36 > ! > hostname uml-1 > password root > enable password root > ! > interface eth0 > ! > interface eth1 > mpls ip > ! > interface eth2 > ! > interface eth3 > ! > interface gre0 > ! > interface ip6tnl0 > ! > interface lo > ! > interface mpls0 > ! > interface sit0 > ! > interface teql0 > ! > ! > mpls ldp > egress connected > ! > line vty > ! > > On the LSR I set up both interfaces with mpls ip (eth0 and eth1), but > when I try to start ldpd on the lsr, it says: > > e2:/home/irina.dumitrascu# ldpd -u root -P 6222 > ldpd: ldp_interface.c:59: ldp_interface_create2: Assertion > `li->iff.index' failed. > Aborted. > > I can start it if I comment out the 'mpls ip' lines from interface > eth0 and eth1. > > After I manage to start LDP on the LSR, and try to run show ldp I get > an error message: 'There isn't an active LDP instance.' This happens > after I have have configured manually the interfaces (mpls ip). > > When I have the lsr manually configured (172.16.0.3) and the next ler > running (172.16.0.2), and on the lsr I issue the command 'mpls ldp' > this is what happens: > > * the ler is constantly sending out LDP Hello packets > * when I issue mpls ldp on the lsr, the lsr sends a LDP Hello, and > then freezes (actually only ldpd freezes) > > This is the output of tcpdump > > 16:18:56.453269 IP 172.16.0.2.646 > 224.0.0.2.646: LDP, > Label-Space-ID: 192.168.0.2:0, length: 34 > 16:19:01.453496 IP 172.16.0.2.646 > 224.0.0.2.646: LDP, > Label-Space-ID: 192.168.0.2:0, length: 34 > 16:19:02.924352 IP 172.16.0.3.646 > 224.0.0.2.646: LDP, > Label-Space-ID: 141.85.43.122:0, length: 34 > 16:19:06.453724 IP 172.16.0.2.646 > 224.0.0.2.646: LDP, > Label-Space-ID: 192.168.0.2:0, length: 34 > 16:19:11.453952 IP 172.16.0.2.646 > 224.0.0.2.646: LDP, > Label-Space-ID: 192.168.0.2:0, length: 34 > > > Do you have any idea why this doesn't work? > |
|
From: James R. L. <jl...@mi...> - 2006-03-13 16:38:11
|
Not unexpected. If you look back in the archives you'll see that I do not consider ldpd ready for users. If you are a developer, and want to help fix it, I'll be more then happy to provide pointers. Otherwise wait until I've had a chance to work on it some more before using it. On Mon, Mar 13, 2006 at 03:34:05PM +0200, Adrian Popa wrote: > I'm trying to get ldpd to work and I'm having difficulties. >=20 > I'm connecting to ldpd using telnet and this is how I configured my LER: >=20 > e1:/home/irina.dumitrascu# cat /usr/etc/ldpd.conf > ! > ! Zebra configuration saved from vty > ! 2006/03/13 16:01:36 > ! > hostname uml-1 > password root > enable password root > ! > interface eth0 > ! > interface eth1 > mpls ip > ! > interface eth2 > ! > interface eth3 > ! > interface gre0 > ! > interface ip6tnl0 > ! > interface lo > ! > interface mpls0 > ! > interface sit0 > ! > interface teql0 > ! > ! > mpls ldp > egress connected > ! > line vty > ! >=20 > On the LSR I set up both interfaces with mpls ip (eth0 and eth1), but > when I try to start ldpd on the lsr, it says: >=20 > e2:/home/irina.dumitrascu# ldpd -u root -P 6222 > ldpd: ldp_interface.c:59: ldp_interface_create2: Assertion > `li->iff.index' failed. > Aborted. >=20 > I can start it if I comment out the 'mpls ip' lines from interface > eth0 and eth1. >=20 > After I manage to start LDP on the LSR, and try to run show ldp I get > an error message: 'There isn't an active LDP instance.' This happens > after I have have configured manually the interfaces (mpls ip). >=20 > When I have the lsr manually configured (172.16.0.3) and the next ler > running (172.16.0.2), and on the lsr I issue the command 'mpls ldp' > this is what happens: >=20 > * the ler is constantly sending out LDP Hello packets > * when I issue mpls ldp on the lsr, the lsr sends a LDP Hello, and > then freezes (actually only ldpd freezes) >=20 > This is the output of tcpdump >=20 > 16:18:56.453269 IP 172.16.0.2.646 > 224.0.0.2.646: LDP, > Label-Space-ID: 192.168.0.2:0, length: 34 > 16:19:01.453496 IP 172.16.0.2.646 > 224.0.0.2.646: LDP, > Label-Space-ID: 192.168.0.2:0, length: 34 > 16:19:02.924352 IP 172.16.0.3.646 > 224.0.0.2.646: LDP, > Label-Space-ID: 141.85.43.122:0, length: 34 > 16:19:06.453724 IP 172.16.0.2.646 > 224.0.0.2.646: LDP, > Label-Space-ID: 192.168.0.2:0, length: 34 > 16:19:11.453952 IP 172.16.0.2.646 > 224.0.0.2.646: LDP, > Label-Space-ID: 192.168.0.2:0, length: 34 >=20 >=20 > Do you have any idea why this doesn't work? >=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-general mailing list > mpl...@li... > https://lists.sourceforge.net/lists/listinfo/mpls-linux-general --=20 James R. Leu jl...@mi... |
|
From: Adrian P. <adr...@gm...> - 2006-03-13 18:38:35
|
Ok. Thank you for message. I hadn't realized that ldpd wasn't ready for users. I'd like to help out, but I don't have a lot of experience in C, or the linux network architecture. If there is a way I can help, please let me know. For now, I'll keep sending bug reports :) The thing is that I kind of relied on ldpd working so I can set up experiments for my graduation diploma. I'd like to ask you at what stage has the development of ldp arrived? Is it mostly done, with bugs to clear? Or is it somewhere in the middle of development? If it's the first case, I'd like to help you (as best I can) to isolate and correct any bugs. If there's a lot of work to be done, I'm sorry, I'd like to help, but I'm afraid I'm pressed by the lack of time. Are you close to releasing a new version of ldp? (Could it be done in less than 1.5 months?) If yes, I'm eager to help. If not, then the result could arrive to late to help me. I hope my reply hasn't brought you down. I'll keep trying to use ldpd (I'm not out of ideas yet), but I'd like to ask you two more questions: 1. Has this version of ldpd worked on a given test-bed? (Has it done what it was supposed to do?) 2. Do you have some more elaborate configuration files for ldpd for the test-bed it worked on? (So that at least, I have somewhere to start from). Thank you kindly for your time On 3/13/06, James R. Leu <jl...@mi...> wrote: > Not unexpected. If you look back in the archives you'll see that I do no= t > consider ldpd ready for users. If you are a developer, and want to help = fix > it, I'll be more then happy to provide pointers. > > Otherwise wait until I've had a chance to work on it some more > before using it. > > On Mon, Mar 13, 2006 at 03:34:05PM +0200, Adrian Popa wrote: > > I'm trying to get ldpd to work and I'm having difficulties. > > > > I'm connecting to ldpd using telnet and this is how I configured my LER= : > > > > e1:/home/irina.dumitrascu# cat /usr/etc/ldpd.conf > > ! > > ! Zebra configuration saved from vty > > ! 2006/03/13 16:01:36 > > ! > > hostname uml-1 > > password root > > enable password root > > ! > > interface eth0 > > ! > > interface eth1 > > mpls ip > > ! > > interface eth2 > > ! > > interface eth3 > > ! > > interface gre0 > > ! > > interface ip6tnl0 > > ! > > interface lo > > ! > > interface mpls0 > > ! > > interface sit0 > > ! > > interface teql0 > > ! > > ! > > mpls ldp > > egress connected > > ! > > line vty > > ! > > > > On the LSR I set up both interfaces with mpls ip (eth0 and eth1), but > > when I try to start ldpd on the lsr, it says: > > > > e2:/home/irina.dumitrascu# ldpd -u root -P 6222 > > ldpd: ldp_interface.c:59: ldp_interface_create2: Assertion > > `li->iff.index' failed. > > Aborted. > > > > I can start it if I comment out the 'mpls ip' lines from interface > > eth0 and eth1. > > > > After I manage to start LDP on the LSR, and try to run show ldp I get > > an error message: 'There isn't an active LDP instance.' This happens > > after I have have configured manually the interfaces (mpls ip). > > > > When I have the lsr manually configured (172.16.0.3) and the next ler > > running (172.16.0.2), and on the lsr I issue the command 'mpls ldp' > > this is what happens: > > > > * the ler is constantly sending out LDP Hello packets > > * when I issue mpls ldp on the lsr, the lsr sends a LDP Hello, and > > then freezes (actually only ldpd freezes) > > > > This is the output of tcpdump > > > > 16:18:56.453269 IP 172.16.0.2.646 > 224.0.0.2.646: LDP, > > Label-Space-ID: 192.168.0.2:0, length: 34 > > 16:19:01.453496 IP 172.16.0.2.646 > 224.0.0.2.646: LDP, > > Label-Space-ID: 192.168.0.2:0, length: 34 > > 16:19:02.924352 IP 172.16.0.3.646 > 224.0.0.2.646: LDP, > > Label-Space-ID: 141.85.43.122:0, length: 34 > > 16:19:06.453724 IP 172.16.0.2.646 > 224.0.0.2.646: LDP, > > Label-Space-ID: 192.168.0.2:0, length: 34 > > 16:19:11.453952 IP 172.16.0.2.646 > 224.0.0.2.646: LDP, > > Label-Space-ID: 192.168.0.2:0, length: 34 > > > > > > Do you have any idea why this doesn't work? > > > > > > ------------------------------------------------------- > > This SF.Net email is sponsored by xPML, a groundbreaking scripting lang= uage > > that extends applications into web and mobile media. Attend the live we= bcast > > and join the prime developer group breaking into this new coding territ= ory! > > http://sel.as-us.falkag.net/sel?cmd____________________________________= ___________ > > mpls-linux-general mailing list > > mpl...@li... > > https://lists.sourceforge.net/lists/listinfo/mpls-linux-general > > -- > James R. Leu > jl...@mi... > > > |
|
From: James R. L. <jl...@mi...> - 2006-03-13 21:47:19
|
It is mostly implemented, which just bugs to fix. I'm sure there are plenty of though. Last week I started working on it again, so additional testing, bug reports are exactly what I'm looking for. Although I need the bug reports to contain more debugging info. If you are interesting in helping me hunt bugs/do testing, then you should get the latest quagga-mpls and ld-portable from the perforce server. This way you will be able to update your tree and rebuild RPMs for more testing. I think the instuctions for the accesing the perforce server at http://mpls-linux.sf.net are still update date. Give them a try and let me know if you hit any snags. On Mon, Mar 13, 2006 at 08:32:02PM +0200, Adrian Popa wrote: > Ok. Thank you for message. >=20 > I hadn't realized that ldpd wasn't ready for users. >=20 > I'd like to help out, but I don't have a lot of experience in C, or > the linux network architecture. >=20 > If there is a way I can help, please let me know. For now, I'll keep > sending bug reports :) >=20 > The thing is that I kind of relied on ldpd working so I can set up > experiments for my graduation diploma. >=20 > I'd like to ask you at what stage has the development of ldp arrived? > Is it mostly done, with bugs to clear? Or is it somewhere in the > middle of development? If it's the first case, I'd like to help you > (as best I can) to isolate and correct any bugs. If there's a lot of > work to be done, I'm sorry, I'd like to help, but I'm afraid I'm > pressed by the lack of time. >=20 > Are you close to releasing a new version of ldp? (Could it be done in > less than 1.5 months?) If yes, I'm eager to help. If not, then the > result could arrive to late to help me. >=20 > I hope my reply hasn't brought you down. I'll keep trying to use ldpd > (I'm not out of ideas yet), but I'd like to ask you two more > questions: >=20 > 1. Has this version of ldpd worked on a given test-bed? (Has it done > what it was supposed to do?) > 2. Do you have some more elaborate configuration files for ldpd for > the test-bed it worked on? (So that at least, I have somewhere to > start from). >=20 > Thank you kindly for your time >=20 >=20 > On 3/13/06, James R. Leu <jl...@mi...> wrote: > > Not unexpected. If you look back in the archives you'll see that I do = not > > consider ldpd ready for users. If you are a developer, and want to hel= p fix > > it, I'll be more then happy to provide pointers. > > > > Otherwise wait until I've had a chance to work on it some more > > before using it. > > > > On Mon, Mar 13, 2006 at 03:34:05PM +0200, Adrian Popa wrote: > > > I'm trying to get ldpd to work and I'm having difficulties. > > > > > > I'm connecting to ldpd using telnet and this is how I configured my L= ER: > > > > > > e1:/home/irina.dumitrascu# cat /usr/etc/ldpd.conf > > > ! > > > ! Zebra configuration saved from vty > > > ! 2006/03/13 16:01:36 > > > ! > > > hostname uml-1 > > > password root > > > enable password root > > > ! > > > interface eth0 > > > ! > > > interface eth1 > > > mpls ip > > > ! > > > interface eth2 > > > ! > > > interface eth3 > > > ! > > > interface gre0 > > > ! > > > interface ip6tnl0 > > > ! > > > interface lo > > > ! > > > interface mpls0 > > > ! > > > interface sit0 > > > ! > > > interface teql0 > > > ! > > > ! > > > mpls ldp > > > egress connected > > > ! > > > line vty > > > ! > > > > > > On the LSR I set up both interfaces with mpls ip (eth0 and eth1), but > > > when I try to start ldpd on the lsr, it says: > > > > > > e2:/home/irina.dumitrascu# ldpd -u root -P 6222 > > > ldpd: ldp_interface.c:59: ldp_interface_create2: Assertion > > > `li->iff.index' failed. > > > Aborted. > > > > > > I can start it if I comment out the 'mpls ip' lines from interface > > > eth0 and eth1. > > > > > > After I manage to start LDP on the LSR, and try to run show ldp I get > > > an error message: 'There isn't an active LDP instance.' This happens > > > after I have have configured manually the interfaces (mpls ip). > > > > > > When I have the lsr manually configured (172.16.0.3) and the next ler > > > running (172.16.0.2), and on the lsr I issue the command 'mpls ldp' > > > this is what happens: > > > > > > * the ler is constantly sending out LDP Hello packets > > > * when I issue mpls ldp on the lsr, the lsr sends a LDP Hello, and > > > then freezes (actually only ldpd freezes) > > > > > > This is the output of tcpdump > > > > > > 16:18:56.453269 IP 172.16.0.2.646 > 224.0.0.2.646: LDP, > > > Label-Space-ID: 192.168.0.2:0, length: 34 > > > 16:19:01.453496 IP 172.16.0.2.646 > 224.0.0.2.646: LDP, > > > Label-Space-ID: 192.168.0.2:0, length: 34 > > > 16:19:02.924352 IP 172.16.0.3.646 > 224.0.0.2.646: LDP, > > > Label-Space-ID: 141.85.43.122:0, length: 34 > > > 16:19:06.453724 IP 172.16.0.2.646 > 224.0.0.2.646: LDP, > > > Label-Space-ID: 192.168.0.2:0, length: 34 > > > 16:19:11.453952 IP 172.16.0.2.646 > 224.0.0.2.646: LDP, > > > Label-Space-ID: 192.168.0.2:0, length: 34 > > > > > > > > > Do you have any idea why this doesn't work? > > > > > > > > > ------------------------------------------------------- > > > This SF.Net email is sponsored by xPML, a groundbreaking scripting la= nguage > > > that extends applications into web and mobile media. Attend the live = webcast > > > and join the prime developer group breaking into this new coding terr= itory! > > > http://sel.as-us.falkag.net/sel?cmd__________________________________= _____________ > > > mpls-linux-general mailing list > > > mpl...@li... > > > https://lists.sourceforge.net/lists/listinfo/mpls-linux-general > > > > -- > > James R. Leu > > jl...@mi... > > > > > > --=20 James R. Leu jl...@mi... |
|
From: Adrian P. <adr...@gm...> - 2006-03-14 19:21:15
|
Hello Thank you for your help. It looks like I might have a chance to get ldp working in a small network using your implementation... I'd like to try out some things tomorrow with the old version of quagga (I have the suspicion that I issued some conflicting commands), but I think I'll switch to your development version soon, and help you track down and maybe fix some bugs. When I switch to the development version, it's possible that I'll ask some questions on how to install it. But I'll ask then. Now, I'd like to ask a few questions, about the current ldpd: 1) can it be controlled by vtysh, or is it only controllable by telnetting to its port? (I noticed that some options weren't available when telnetting (for example mpls-te commands)) 2) Should LDP be activated only on the desired interfaces (with the interface eth0; mpls ip; commands) or globally (with mpls ldp)? I tried setting both of them (and one of the machines froze). Does it matter in which order I configure them? (I configured the interfaces first, then the global operation mode - and only then it started sending out LDP Hello packets) - I will try both ways with the current LDP. 3) Is labelspace 0 set by default as a 'per platform' labelspace? If I want to use per interface labelspaces do I have to set the number to something else different from 0? And is this true for static labels as well as LDP? Thank you kindly and I look forward to help you as best I can On 3/13/06, James R. Leu <jl...@mi...> wrote: > It is mostly implemented, which just bugs to fix. I'm sure there are > plenty of though. Last week I started working on it again, so additional > testing, bug reports are exactly what I'm looking for. Although I need t= he > bug reports to contain more debugging info. > > If you are interesting in helping me hunt bugs/do testing, then you shoul= d > get the latest quagga-mpls and ld-portable from the perforce server. > This way you will be able to update your tree and rebuild RPMs for > more testing. > > I think the instuctions for the accesing the perforce server at > http://mpls-linux.sf.net are still update date. Give them a try > and let me know if you hit any snags. > > On Mon, Mar 13, 2006 at 08:32:02PM +0200, Adrian Popa wrote: > > Ok. Thank you for message. > > > > I hadn't realized that ldpd wasn't ready for users. > > > > I'd like to help out, but I don't have a lot of experience in C, or > > the linux network architecture. > > > > If there is a way I can help, please let me know. For now, I'll keep > > sending bug reports :) > > > > The thing is that I kind of relied on ldpd working so I can set up > > experiments for my graduation diploma. > > > > I'd like to ask you at what stage has the development of ldp arrived? > > Is it mostly done, with bugs to clear? Or is it somewhere in the > > middle of development? If it's the first case, I'd like to help you > > (as best I can) to isolate and correct any bugs. If there's a lot of > > work to be done, I'm sorry, I'd like to help, but I'm afraid I'm > > pressed by the lack of time. > > > > Are you close to releasing a new version of ldp? (Could it be done in > > less than 1.5 months?) If yes, I'm eager to help. If not, then the > > result could arrive to late to help me. > > > > I hope my reply hasn't brought you down. I'll keep trying to use ldpd > > (I'm not out of ideas yet), but I'd like to ask you two more > > questions: > > > > 1. Has this version of ldpd worked on a given test-bed? (Has it done > > what it was supposed to do?) > > 2. Do you have some more elaborate configuration files for ldpd for > > the test-bed it worked on? (So that at least, I have somewhere to > > start from). > > > > Thank you kindly for your time > > > > > > On 3/13/06, James R. Leu <jl...@mi...> wrote: > > > Not unexpected. If you look back in the archives you'll see that I d= o not > > > consider ldpd ready for users. If you are a developer, and want to h= elp fix > > > it, I'll be more then happy to provide pointers. > > > > > > Otherwise wait until I've had a chance to work on it some more > > > before using it. > > > > > > On Mon, Mar 13, 2006 at 03:34:05PM +0200, Adrian Popa wrote: > > > > I'm trying to get ldpd to work and I'm having difficulties. > > > > > > > > I'm connecting to ldpd using telnet and this is how I configured my= LER: > > > > > > > > e1:/home/irina.dumitrascu# cat /usr/etc/ldpd.conf > > > > ! > > > > ! Zebra configuration saved from vty > > > > ! 2006/03/13 16:01:36 > > > > ! > > > > hostname uml-1 > > > > password root > > > > enable password root > > > > ! > > > > interface eth0 > > > > ! > > > > interface eth1 > > > > mpls ip > > > > ! > > > > interface eth2 > > > > ! > > > > interface eth3 > > > > ! > > > > interface gre0 > > > > ! > > > > interface ip6tnl0 > > > > ! > > > > interface lo > > > > ! > > > > interface mpls0 > > > > ! > > > > interface sit0 > > > > ! > > > > interface teql0 > > > > ! > > > > ! > > > > mpls ldp > > > > egress connected > > > > ! > > > > line vty > > > > ! > > > > > > > > On the LSR I set up both interfaces with mpls ip (eth0 and eth1), b= ut > > > > when I try to start ldpd on the lsr, it says: > > > > > > > > e2:/home/irina.dumitrascu# ldpd -u root -P 6222 > > > > ldpd: ldp_interface.c:59: ldp_interface_create2: Assertion > > > > `li->iff.index' failed. > > > > Aborted. > > > > > > > > I can start it if I comment out the 'mpls ip' lines from interface > > > > eth0 and eth1. > > > > > > > > After I manage to start LDP on the LSR, and try to run show ldp I = get > > > > an error message: 'There isn't an active LDP instance.' This happen= s > > > > after I have have configured manually the interfaces (mpls ip). > > > > > > > > When I have the lsr manually configured (172.16.0.3) and the next l= er > > > > running (172.16.0.2), and on the lsr I issue the command 'mpls ldp' > > > > this is what happens: > > > > > > > > * the ler is constantly sending out LDP Hello packets > > > > * when I issue mpls ldp on the lsr, the lsr sends a LDP Hello, and > > > > then freezes (actually only ldpd freezes) > > > > > > > > This is the output of tcpdump > > > > > > > > 16:18:56.453269 IP 172.16.0.2.646 > 224.0.0.2.646: LDP, > > > > Label-Space-ID: 192.168.0.2:0, length: 34 > > > > 16:19:01.453496 IP 172.16.0.2.646 > 224.0.0.2.646: LDP, > > > > Label-Space-ID: 192.168.0.2:0, length: 34 > > > > 16:19:02.924352 IP 172.16.0.3.646 > 224.0.0.2.646: LDP, > > > > Label-Space-ID: 141.85.43.122:0, length: 34 > > > > 16:19:06.453724 IP 172.16.0.2.646 > 224.0.0.2.646: LDP, > > > > Label-Space-ID: 192.168.0.2:0, length: 34 > > > > 16:19:11.453952 IP 172.16.0.2.646 > 224.0.0.2.646: LDP, > > > > Label-Space-ID: 192.168.0.2:0, length: 34 > > > > > > > > > > > > Do you have any idea why this doesn't work? > > > > > > > > > > > > ------------------------------------------------------- > > > > This SF.Net email is sponsored by xPML, a groundbreaking scripting = language > > > > that extends applications into web and mobile media. Attend the liv= e webcast > > > > and join the prime developer group breaking into this new coding te= rritory! > > > > http://sel.as-us.falkag.net/sel?cmd________________________________= _______________ > > > > mpls-linux-general mailing list > > > > mpl...@li... > > > > https://lists.sourceforge.net/lists/listinfo/mpls-linux-general > > > > > > -- > > > James R. Leu > > > jl...@mi... > > > > > > > > > > > -- > James R. Leu > jl...@mi... > > > |
Thanks for helping keep SourceForge clean.
X