WG: [mpls-linux-general] LDP (linux-port)
Status: Beta
Brought to you by:
jleu
From: Kauder T. <Tho...@ic...> - 2001-12-11 13:38:49
|
-----Urspr=FCngliche Nachricht----- Von: Kauder Thorsten=20 Gesendet: Dienstag, 11. Dezember 2001 13:53 An: 'nc...@si...' Betreff: AW: [mpls-linux-general] LDP (linux-port) Hi Paul, The ldp-linux port does not act as you might expect. I'll try helping you to find the problem. I found out that first of all you have to create the routes before starting ldp. If you add routes after having started the ldp_linux they are not exchanged or used to create LSPs. In the Readme they just add a route to the other Host. I didn't try that and have no idea if that works. I allways use a dummy device on each computer and create routes pointing out that dummydevice. e.g. on A ifconfig dummy0 1.2.3.4 route add -net 20.1.1.1/24 gw 1.2.3.4 on B route add -net 20.1.1.1/24 gw A (not shure if the commands are correct bwcause I use Zebra and ospf to = create the routing-tables) I think this is a more realistic scenario. What surprised me most is that I had a problem with only one route to = be propagated. With two or more it worked. try adding the routes prior to starting ldp. (by the way mpls_fec only holds the routes and FECs for outgoing LSPs) hope this helps tell me if it doesn't Thorsten PS: Be careful stopping your ldp_session. allways first delete the = interface before exiting. Otherwise the labelmappings stay in /proc/net/ and it's a quite = annoying procedure getting rid of them again. |