Re: [mpls-linux-general] ldp-portable updates
Status: Beta
Brought to you by:
jleu
Menu
▾
▴
Re: [mpls-linux-general] ldp-portable updates
|
From: Venisa C. <vca...@ho...> - 2001-06-26 14:28:17
|
Hi, Sorry for the late response, I have to go downstair and upstair just to copy the contents of /proc/net/mpls_*, (my lab and my office are not in the same room) but I have done as fast as I can ... :-) First, I have to inform you that since I use my computers as routers, I do certainly have at least three ethernet cards in my routers (that is, the topology that I gave you is far from complete, which will explain the important contents of file mpls_in) but I used only the commands that I have described in my last email. In router1: mpls_in: 40004000 gen 16 0 POP DLV 40004400 gen 17 0 POP DLV 40004800 gen 18 0 POP DLV 40004c00 gen 19 0 POP DLV 40005000 gen 20 0 POP DLV 40005400 gen 21 0 POP DLV 40005800 gen 22 0 POP DLV mpls_out: 40004003 PUSH(gen 16) SET (eth1) mpls_fec: 40004003 10.0.0.6/32 mpls_labelspace: lo 0 In router2: mpls_in: 40004000 gen 16 0 POP DLV 40004400 gen 17 0 POP DLV 40004800 gen 18 0 POP DLV 40004c00 gen 19 0 POP DLV 40005000 gen 20 0 POP DLV 40005400 gen 21 0 POP DLV 40005800 gen 22 0 POP DLV mpls_out: 40004004 PUSH(gen 16) SET (eth2) mpls_fec: 40004004 10.0.0.5/32 mpls_labelspace: lo 0 There is nothing in mpls_tunnel, which is normal. regards, ~Venisa Cabrilla >From: "James R. Leu" <jl...@mi...> >Reply-To: jl...@mi... >To: Venisa Cabrilla <vca...@ho...> >CC: mpl...@li... >Subject: Re: [mpls-linux-general] ldp-portable updates >Date: Tue, 26 Jun 2001 08:45:55 -0500 > >On Tue, Jun 26, 2001 at 01:31:11PM -0000, Venisa Cabrilla wrote: > > Hi James, > > > > Thanks for your ldp-portable updates, now I can see that mpls_in, >mpls_out, > > and mpls_fec are not empty. > >Hello, > >I think I know the problem. It has to do with the fact that LDP is setting >up >LSPs for too many entries in the route table. Send me the contents of >/proc/net/mpls_* and we can verify this. > >My default policy of "send labels for everything" may not be valid in all >cases. This will be simple enough to change I just need to figure out what >the >best default policy should be :-( > >I'll try to duplicate this setup here and see if I can figure it out as >well. > >Jim > > > > > I use the simple configuration in file README.sample : > > > > lo 10.0.0.6 lo 10.0.0.5 > > --------- --------- > > | Router2 |----------------| Router1 | > > --------- --------- > > |eth2 192.168.12.0/24 |eth1 > > --------------------------------------- > > > > In router1: > > bash# ifconfig lo 10.0.0.5 netmask 255.255.255.255 > > bash# route add 10.0.0.6 gw 192.168.12.2 > > > > >From inside ldp_linux: > > prompt> add global 10.0.0.5 > > prompt> add interface eth1 > > > > In router2: > > bash# ifconfig lo 10.0.0.6 netmask 255.255.255.255 > > bash# route add 10.0.0.5 gw 192.168.12.1 > > > > >From inside ldp_linux: > > prompt> add global 10.0.0.6 > > prompt> add interface eth2 > > > > After that I can see that mpls_in, mpls_out, and mpls_fec in each router >are > > not empty. > > > > Unfortunately, I cannot ping anymore router1 from router2 and router2 >from > > router1. Before I enter ldp_linux, I can ping 10.0.0.5 from router1 and >ping > > 10.0.0.6 from router2. However, I can see the MPLS encapsulation using > > ethereal for ping request messages but there is no ping reply message. > > > > Would you mind verify my configuration above and tell me what might be >my > > mistakes ? > > > > > > PS: I have to explicitly add the routes using route commands this time, > > because if I use zebra, I cannot use ethereal (ethereal hangs). > > I still do not know the reason, it might be due to TCP/UDP conflicts. > > > > > > regards, > > ~Venisa Cabrilla > > > > > > > > >From: "James R. Leu" <jl...@mi...> > > >Reply-To: jl...@mi... > > >To: mpl...@li... > > >Subject: [mpls-linux-general] ldp-portable updates > > >Date: Sun, 24 Jun 2001 20:23:13 -0500 > > > > > >Sorry to those who have been trying to use ldp-portable from CVS. > > >I finnally have gotten around to fixing and testing ldp-portable. > > >It's almost back to where it was before I started mucking around with >PDU > > >processing. (interoping with cisco pointed out the need to handle >multiple > > >PDUs per TCP segment and handle one PDU spread across multiple TCP > > >segments) > > > > > >If you tried ldp-portable in the last 3 weeks and it was broken, try > > >updating your CVS client and giving it another go. > > > > > >Sorry for the long delay. > > >Jim > > >-- > > >James R. Leu > > > > > >_______________________________________________ > > >mpls-linux-general mailing list > > >mpl...@li... > > >http://lists.sourceforge.net/lists/listinfo/mpls-linux-general > > > > >_________________________________________________________________________ > > Get Your Private, Free E-mail from MSN Hotmail at >http://www.hotmail.com. > > > > > > _______________________________________________ > > mpls-linux-general mailing list > > mpl...@li... > > http://lists.sourceforge.net/lists/listinfo/mpls-linux-general > >-- >James R. Leu > >_______________________________________________ >mpls-linux-general mailing list >mpl...@li... >http://lists.sourceforge.net/lists/listinfo/mpls-linux-general _________________________________________________________________________ Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com. |
