Thread: [mpls-linux-general] Dubts
Status: Beta
Brought to you by:
jleu
Menu
▾
▴
mpls-linux-general
|
From: Miquel C. P. <u10...@co...> - 2005-05-17 16:25:52
|
Hello, I have any dubts in protocol LDP, the first is: LDP_2# show ldp data 192.168.0.0/24 local binding: label: gen 10000 192.168.3.0/24 local binding: label: gen 10001 192.168.0.0/24 remote binding: no outlabel lsr: 192.168.0.1:0 192.168.1.0/24 remote binding: no outlabel lsr: 192.168.0.1:0 192.168.2.0/24 remote binding: no outlabel lsr: 192.168.3.3:0 192.168.0.0/24 local binding: label: gen 10002 192.168.3.0/24 local binding: label: gen 10003 192.168.3.0/24 remote binding: no outlabel lsr: 192.168.3.3:0 192.168.4.0/24 remote binding: no outlabel lsr: 192.168.3.3:0 But, I assign the remote binding manually?? The second is , when run the ldpd: [root@uni ldp-portable]# ldpd -P 1026 2005/05/09 18:38:46 LDP: old umask 23 127 2005/05/09 18:38:46 LDP: interface add eth0 index 2 flags 4098 metric 1 mtu 1500 2005/05/09 18:38:46 LDP: interface add eth1 index 3 flags 4098 metric 1 mtu 1500 2005/05/09 18:38:46 LDP: interface add eth2 index 4 flags 4098 metric 1 mtu 1500 2005/05/09 18:38:46 LDP: interface add eth3 index 5 flags 4163 metric 1 mtu 1500 2005/05/09 18:38:46 LDP: address add 192.168.3.2 to interface eth3 2005/05/09 18:38:46 LDP: interface add eth4 index 6 flags 4163 metric 1 mtu 1500 2005/05/09 18:38:46 LDP: address add 192.168.0.2 to interface eth4 2005/05/09 18:38:46 LDP: interface add lo index 1 flags 73 metric 1 mtu 16436 2005/05/09 18:38:46 LDP: address add 127.0.0.1 to interface lo 2005/05/09 18:38:46 LDP: interface add sit0 index 7 flags 128 metric 1 mtu 1480 2005/05/09 18:38:46 LDP: router-id change 192.168.0.2 2005/05/09 18:38:46 LDP: route 192.168.0.0/24 2005/05/09 18:38:46 LDP: attached 2005/05/09 18:38:46 LDP: num nexthop 1 2005/05/09 18:38:46 LDP: nexthop 1.0.0.0 2005/05/09 18:38:46 LDP: add 2005/05/09 18:38:46 LDP: route 192.168.3.0/24 2005/05/09 18:38:46 LDP: attached 2005/05/09 18:38:46 LDP: num nexthop 1 2005/05/09 18:38:46 LDP: nexthop 1.0.0.0 2005/05/09 18:38:46 LDP: add 2005/05/09 18:38:46 LDP: route 192.168.1.0/24 2005/05/09 18:38:46 LDP: num nexthop 1 2005/05/09 18:38:46 LDP: nexthop 5.192.168.0 2005/05/09 18:38:46 LDP: add 2005/05/09 18:38:46 LDP: route 192.168.2.0/24 2005/05/09 18:38:46 LDP: num nexthop 1 2005/05/09 18:38:46 LDP: nexthop 5.192.168.3 2005/05/09 18:38:46 LDP: add 2005/05/09 18:38:46 LDP: route 192.168.4.0/24 2005/05/09 18:38:46 LDP: num nexthop 1 2005/05/09 18:38:46 LDP: nexthop 5.192.168.3 2005/05/09 18:38:46 LDP: add OUT: ldp_session_attempt_setup: MPLS_NON_BLOCKING What is nexthop ??? t'he 1.0.0.0 isn't ip of my LAN, 5.192.168.3 isn't too. What is?? And the last, when execute the ripd deamon, I see the follow line: [root@uni quagga]# ripd -d 2005/05/09 18:24:51 RIP: can't setsockopt SO_RCVBUF The deamon run correctly, but I know the why? thank you!!! |
|
From: James R. L. <jl...@mi...> - 2005-05-17 17:22:16
|
Hello Miquel, A quick search of the mpls-linux-general mailing list will point out that ldpd is not ready for users. If you are willing to dig into the code and help fix bugs then get the most recent version of quagga-mpls and ldp-portable from my development tree. See http://mpls-linux.sf.net/ for more details. Otherwise I would suggest holding of on trying to use ldpd. Static LSPs configure via the zebra CLI should work. On Tue, May 17, 2005 at 06:38:12PM +0200, Miquel Casanovas Puigvi wrote: > Hello, I have any dubts in protocol LDP, the first is: >=20 > LDP_2# show ldp data > 192.168.0.0/24 local binding: label: gen 10000 > 192.168.3.0/24 local binding: label: gen 10001 > 192.168.0.0/24 remote binding: no outlabel lsr: 192.168.0.1:0 > 192.168.1.0/24 remote binding: no outlabel lsr: 192.168.0.1:0 > 192.168.2.0/24 remote binding: no outlabel lsr: 192.168.3.3:0 > 192.168.0.0/24 local binding: label: gen 10002 > 192.168.3.0/24 local binding: label: gen 10003 > 192.168.3.0/24 remote binding: no outlabel lsr: 192.168.3.3:0 > 192.168.4.0/24 remote binding: no outlabel lsr: 192.168.3.3:0 >=20 > But, I assign the remote binding manually?? >=20 > The second is , when run the ldpd: >=20 > [root@uni ldp-portable]# ldpd -P 1026 > 2005/05/09 18:38:46 LDP: old umask 23 127 > 2005/05/09 18:38:46 LDP: interface add eth0 index 2 flags 4098 metric 1 > mtu 1500 > 2005/05/09 18:38:46 LDP: interface add eth1 index 3 flags 4098 metric 1 > mtu 1500 > 2005/05/09 18:38:46 LDP: interface add eth2 index 4 flags 4098 metric 1 > mtu 1500 > 2005/05/09 18:38:46 LDP: interface add eth3 index 5 flags 4163 metric 1 > mtu 1500 > 2005/05/09 18:38:46 LDP: address add 192.168.3.2 to interface eth3 > 2005/05/09 18:38:46 LDP: interface add eth4 index 6 flags 4163 metric 1 > mtu 1500 > 2005/05/09 18:38:46 LDP: address add 192.168.0.2 to interface eth4 > 2005/05/09 18:38:46 LDP: interface add lo index 1 flags 73 metric 1 mtu 1= 6436 > 2005/05/09 18:38:46 LDP: address add 127.0.0.1 to interface lo > 2005/05/09 18:38:46 LDP: interface add sit0 index 7 flags 128 metric 1 mtu > 1480 > 2005/05/09 18:38:46 LDP: router-id change 192.168.0.2 > 2005/05/09 18:38:46 LDP: route 192.168.0.0/24 > 2005/05/09 18:38:46 LDP: attached > 2005/05/09 18:38:46 LDP: num nexthop 1 > 2005/05/09 18:38:46 LDP: nexthop 1.0.0.0 > 2005/05/09 18:38:46 LDP: add > 2005/05/09 18:38:46 LDP: route 192.168.3.0/24 > 2005/05/09 18:38:46 LDP: attached > 2005/05/09 18:38:46 LDP: num nexthop 1 > 2005/05/09 18:38:46 LDP: nexthop 1.0.0.0 > 2005/05/09 18:38:46 LDP: add > 2005/05/09 18:38:46 LDP: route 192.168.1.0/24 > 2005/05/09 18:38:46 LDP: num nexthop 1 > 2005/05/09 18:38:46 LDP: nexthop 5.192.168.0 > 2005/05/09 18:38:46 LDP: add > 2005/05/09 18:38:46 LDP: route 192.168.2.0/24 > 2005/05/09 18:38:46 LDP: num nexthop 1 > 2005/05/09 18:38:46 LDP: nexthop 5.192.168.3 > 2005/05/09 18:38:46 LDP: add > 2005/05/09 18:38:46 LDP: route 192.168.4.0/24 > 2005/05/09 18:38:46 LDP: num nexthop 1 > 2005/05/09 18:38:46 LDP: nexthop 5.192.168.3 > 2005/05/09 18:38:46 LDP: add > OUT: ldp_session_attempt_setup: MPLS_NON_BLOCKING >=20 >=20 > What is nexthop ??? t'he 1.0.0.0 isn't ip of my LAN, 5.192.168.3 isn't to= o. > What is?? >=20 > And the last, when execute the ripd deamon, I see the follow line: >=20 > [root@uni quagga]# ripd -d > 2005/05/09 18:24:51 RIP: can't setsockopt SO_RCVBUF >=20 > The deamon run correctly, but I know the why? >=20 > thank you!!! >=20 >=20 >=20 > ------------------------------------------------------- > This SF.Net email is sponsored by Oracle Space Sweepstakes > Want to be the first software developer in space? > Enter now for the Oracle Space Sweepstakes! > http://ads.osdn.com/?ad_id=3D7412&alloc_id=3D16344&op=3Dclick > _______________________________________________ > mpls-linux-general mailing list > mpl...@li... > https://lists.sourceforge.net/lists/listinfo/mpls-linux-general --=20 James R. Leu jl...@mi... |
Thanks for helping keep SourceForge clean.
X