mpls-linux-devel Mailing List for MPLS for Linux (Page 18)
Status: Beta
Brought to you by:
jleu
Menu
▾
▴
mpls-linux-devel — Mailig list for discussing the development of MPLS on Linux
You can subscribe to this list here.
| 2003 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(7) |
Dec
(8) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2004 |
Jan
(5) |
Feb
(73) |
Mar
(22) |
Apr
(21) |
May
|
Jun
|
Jul
(3) |
Aug
(5) |
Sep
(4) |
Oct
(4) |
Nov
(2) |
Dec
(6) |
| 2005 |
Jan
(5) |
Feb
|
Mar
(6) |
Apr
(11) |
May
(6) |
Jun
(5) |
Jul
(4) |
Aug
(1) |
Sep
(1) |
Oct
|
Nov
(9) |
Dec
(15) |
| 2006 |
Jan
(11) |
Feb
(7) |
Mar
(4) |
Apr
(1) |
May
(2) |
Jun
(2) |
Jul
(7) |
Aug
|
Sep
(8) |
Oct
(9) |
Nov
(10) |
Dec
(14) |
| 2007 |
Jan
(11) |
Feb
(9) |
Mar
(39) |
Apr
(7) |
May
(4) |
Jun
(2) |
Jul
(5) |
Aug
(6) |
Sep
(6) |
Oct
(1) |
Nov
(1) |
Dec
(8) |
| 2008 |
Jan
|
Feb
(13) |
Mar
(19) |
Apr
(11) |
May
(16) |
Jun
(6) |
Jul
(2) |
Aug
(4) |
Sep
|
Oct
(5) |
Nov
|
Dec
(16) |
| 2009 |
Jan
(13) |
Feb
(5) |
Mar
|
Apr
|
May
(11) |
Jun
(7) |
Jul
(3) |
Aug
|
Sep
(2) |
Oct
(8) |
Nov
(16) |
Dec
(15) |
| 2010 |
Jan
(6) |
Feb
(5) |
Mar
(1) |
Apr
(14) |
May
(42) |
Jun
(4) |
Jul
(1) |
Aug
(1) |
Sep
|
Oct
|
Nov
(4) |
Dec
(1) |
| 2011 |
Jan
(3) |
Feb
|
Mar
|
Apr
(7) |
May
(1) |
Jun
(2) |
Jul
(4) |
Aug
(19) |
Sep
(9) |
Oct
(13) |
Nov
(4) |
Dec
(3) |
| 2012 |
Jan
(2) |
Feb
(3) |
Mar
|
Apr
|
May
|
Jun
(11) |
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
(3) |
Dec
(2) |
| 2013 |
Jan
(4) |
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2014 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
(7) |
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
|
| 2015 |
Jan
(1) |
Feb
|
Mar
|
Apr
(2) |
May
|
Jun
(2) |
Jul
(2) |
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
(2) |
| 2016 |
Jan
(6) |
Feb
(2) |
Mar
(1) |
Apr
|
May
|
Jun
(2) |
Jul
|
Aug
(1) |
Sep
(1) |
Oct
|
Nov
|
Dec
|
| 2017 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(4) |
Dec
|
| 2021 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: James R. L. <jl...@mi...> - 2007-03-16 05:56:07
|
This doesn't seem to be enough debugging. Try adding: debug zebra rib debug zebra packet On Wed, Mar 14, 2007 at 12:46:57PM +0100, Sienes Rodr?guez Gonzalo wrote: > Hi James: >=20 > This is what I get in the log file at PE2, maybe these could be helpful t= o understand what's happening: >=20 > As always the NHLFE and ILM entries are created and IP routes learned by = OSPF. >=20 > 2007/03/14 12:04:37 LDP: Terminating on signal > 2007/03/14 12:04:37 ZEBRA: Terminating on signal > 2007/03/14 12:04:37 ZEBRA: netlink_route_multipath() (single hop): RTM_DE= LROUTE 12.0.0.0/24, type IPv4=20 > 2007/03/14 12:04:37 ZEBRA: netlink_route_multipath() (single hop): nextho= p via 10.0.0.1 if 4 > 2007/03/14 12:04:37 ZEBRA: netlink_talk: netlink-cmd type RTM_DELROUTE(25= ), seq=3D7 > 2007/03/14 12:04:37 ZEBRA: netlink_parse_info: netlink-cmd ACK: type=3DRT= M_DELROUTE(25), seq=3D7, pid=3D0 > 2007/03/14 12:04:37 ZEBRA: netlink_talk: mpls-netlink-cmd type (29), seq= =3D3 > 2007/03/14 12:04:37 ZEBRA: netlink_parse_info: mpls-netlink-cmd ACK: type= =3D(29), seq=3D3, pid=3D0 > 2007/03/14 12:04:37 ZEBRA: netlink_talk: mpls-netlink-cmd type (29), seq= =3D4 > 2007/03/14 12:04:37 ZEBRA: netlink_parse_info: mpls-netlink-cmd ACK: type= =3D(29), seq=3D4, pid=3D0 > 2007/03/14 12:04:37 ZEBRA: IRDP: Received shutdown notification. > 2007/03/14 12:06:02 OSPF: interface 13.0.0.1 [3] join AllSPFRouters Multi= cast group. > 2007/03/14 12:06:22 OSPF: interface 10.0.0.2 [4] join AllSPFRouters Multi= cast group. > 2007/03/14 12:06:40 OSPF: ospfTrapNbrStateChange trap sent: 10.0.0.1 now = Init/DROther > 2007/03/14 12:06:42 OSPF: DR-Election[1st]: Backup 13.0.0.1 > 2007/03/14 12:06:42 OSPF: DR-Election[1st]: DR 13.0.0.1 > 2007/03/14 12:06:42 OSPF: DR-Election[2nd]: Backup 0.0.0.0 > 2007/03/14 12:06:42 OSPF: DR-Election[2nd]: DR 13.0.0.1 > 2007/03/14 12:06:42 OSPF: ospfTrapIfStateChange trap sent: 13.0.0.1 now DR > 2007/03/14 12:06:42 OSPF: interface 13.0.0.1 [3] join AllDRouters Multica= st group. > 2007/03/14 12:07:02 OSPF: DR-Election[1st]: Backup 10.0.0.1 > 2007/03/14 12:07:02 OSPF: DR-Election[1st]: DR 10.0.0.1 > 2007/03/14 12:07:02 OSPF: ospfTrapIfStateChange trap sent: 10.0.0.2 now D= ROther > 2007/03/14 12:07:20 OSPF: Packet[DD]: Neighbor 12.0.0.1 Negotiation done = (Slave). > 2007/03/14 12:07:20 OSPF: nsm_change_state(12.0.0.1, Loading -> Full): sc= heduling new router-LSA origination > 2007/03/14 12:07:20 OSPF: DR-Election[1st]: Backup 10.0.0.2 > 2007/03/14 12:07:20 OSPF: DR-Election[1st]: DR 10.0.0.1 > 2007/03/14 12:07:20 OSPF: DR-Election[2nd]: Backup 10.0.0.2 > 2007/03/14 12:07:20 OSPF: DR-Election[2nd]: DR 10.0.0.1 > 2007/03/14 12:07:20 OSPF: ospfTrapIfStateChange trap sent: 10.0.0.2 now B= ackup > 2007/03/14 12:07:20 OSPF: interface 10.0.0.2 [4] join AllDRouters Multica= st group. > 2007/03/14 12:07:25 ZEBRA: netlink_route_multipath() (single hop): RTM_NE= WROUTE 12.0.0.0/24, type IPv4=20 > 2007/03/14 12:07:25 ZEBRA: netlink_route_multipath() (single hop): nextho= p via 10.0.0.1 if 4 > 2007/03/14 12:07:25 ZEBRA: netlink_talk: netlink-cmd type RTM_NEWROUTE(24= ), seq=3D6 > 2007/03/14 12:07:25 ZEBRA: netlink_parse_info: netlink-cmd ACK: type=3DRT= M_NEWROUTE(24), seq=3D6, pid=3D0 > 2007/03/14 12:07:25 ZEBRA: netlink_parse_info: netlink-listen type RTM_NE= WROUTE(24), seq=3D6, pid=3D4294963184 > 2007/03/14 12:07:25 ZEBRA: netlink_parse_info: netlink-cmd packet comes f= rom netlink-listen > 2007/03/14 12:07:34 LDP: route 169.254.0.0/16 > 2007/03/14 12:07:34 LDP: num ifindex 0 > 2007/03/14 12:07:34 LDP: ifindex 4 > 2007/03/14 12:07:34 LDP: add > 2007/03/14 12:07:34 LDP: route 10.0.0.0/24 > 2007/03/14 12:07:34 LDP: num ifindex 0 > 2007/03/14 12:07:34 LDP: attached > 2007/03/14 12:07:34 LDP: ifindex 4 > 2007/03/14 12:07:34 LDP: add > 2007/03/14 12:07:34 LDP: route 13.0.0.0/24 > 2007/03/14 12:07:34 LDP: num ifindex 0 > 2007/03/14 12:07:34 LDP: attached > 2007/03/14 12:07:34 LDP: ifindex 3 > 2007/03/14 12:07:34 LDP: add > 2007/03/14 12:07:34 LDP: route 12.0.0.0/24 > 2007/03/14 12:07:34 LDP: num nexthop 0 > 2007/03/14 12:07:34 LDP: nexthop 10.0.0.1 > 2007/03/14 12:07:34 LDP: add > 2007/03/14 12:07:44 ZEBRA: netlink_talk: mpls-netlink-cmd type (29), seq= =3D1 > 2007/03/14 12:07:44 ZEBRA: netlink_parse_info: mpls-netlink-cmd ACK: type= =3D(29), seq=3D1, pid=3D0 > 2007/03/14 12:07:59 LDP: OUT: ldp_session_attempt_setup: MPLS_NON_BLOCKING > 2007/03/14 12:07:59 LDP: OUT: LDP_NOTIF_SESSION_REJECTED_NO_HELLO: > 2007/03/14 12:08:03 LDP: OUT: ldp_session_attempt_setup: MPLS_NON_BLOCKING > 2007/03/14 12:08:03 LDP: OUT: LDP_NOTIF_SESSION_REJECTED_NO_HELLO: > 2007/03/14 12:08:08 LDP: OUT: ldp_session_attempt_setup: MPLS_NON_BLOCKING > 2007/03/14 12:08:10 ZEBRA: netlink_talk: mpls-netlink-cmd type (29), seq= =3D2 > 2007/03/14 12:08:10 ZEBRA: netlink_parse_info: mpls-netlink-cmd ACK: type= =3D(29), seq=3D2, pid=3D0 > 2007/03/14 12:08:10 ZEBRA: netlink_parse_info: mpls-netlink-listen type (= 29), seq=3D0, pid=3D0 > 2007/03/14 12:08:10 ZEBRA: netlink_talk: mpls-netlink-nhlfe type (29), se= q=3D1 > 2007/03/14 12:08:10 ZEBRA: netlink_parse_info: mpls-netlink-nhlfe type (2= 9), seq=3D1, pid=3D4294963182 > 2007/03/14 12:08:10 ZEBRA: netlink_talk: ignoring message type 0x001d > 2007/03/14 12:08:10 ZEBRA: mpls_ctrl_nhlfe_register(): NHLFE 0x00000003 > 2007/03/14 12:08:10 ZEBRA: netlink_parse_info: mpls-netlink-listen type (= 29), seq=3D1, pid=3D4294963182 > 2007/03/14 12:08:10 ZEBRA: netlink_parse_info: mpls-netlink-nhlfe packet = comes from mpls-netlink-listen > 2007/03/14 12:08:10 LDP: found pending NHLFE: 0x916d858 >=20 > Thanks in advance, > Gonzalo. >=20 >=20 >=20 > -----Mensaje original----- > De: James R. Leu [mailto:jl...@mi...] > Enviado el: mar 13/03/2007 14:11 > Para: Sienes Rodr?guez Gonzalo > CC: mpl...@li... > Asunto: Re: [mpls-linux-devel] MPLS-Linux-1.955 FC5 > =20 > I see some difference with my testing setup. First, I create all > my routes via vtysh with LDP running at that time, in otherwords: >=20 > I start zebra, ospfd, and ldpd, then start my configuration via vtysh. > I configure EVERYTHING via vtysh. The only interface on the box that is > not configure via vtysh is the managment interface which does not > participate in routing. >=20 > Is there a reason you do not use the system scripts to start zebra ospfd > and ldpd? (ie service zebra start; service ospfd start; service ldpd sta= rt) >=20 > Have you tried turning on zebra debugging? (in vtysh: debug zebra kernel) > You will need to have logging configured for this to produce anything > useful. >=20 > I've run your exact configuration on my network at home at it works just = fine. > There must be something with the order of events that is causing an issue. > Obviously I'd like to fix this issue, but I need to know what "mis-orderi= ng" > is causing it and be able to reproduce it before I can fix it. >=20 > At this point I do not believe you have ever gotten LDP to work for you > so forgive me for being sceptical. >=20 > On Tue, Mar 13, 2007 at 09:27:53AM +0100, Sienes Rodr?guez Gonzalo wrote: > > Hi James: > > =20 > > I?m trying two different experiments with the following scenario and th= ese are the results. > > =20 > > eth0 eth1 eth1 eth0 > > 12.0.0.1-------PE1---------------------PE2-------13.0.0.1 > > .1 10.0.0.0/24 .2 > > =20 > >=20 > > 1? - I create static routes from PE1 to 13..0/24 and PE3 to 12..0/24= .=20 > > =20 > > - Then I launch zebra and ldpd typing zebra -d and ldpd -d by th= e command line.=20 > > (I load the mpls4 module since system boots). > > =20 > > - I configure PE1 and PE3 as LSRs by vtysh: > > =20 > > > "mpls ldp" > > > int eth1 (in each LSR): "mpls ip" and "mpls labelspace 0" > > =20 > > - Then I hang a host at 12..0/24 to send packets to 13.1 through= 10..0/24. > > =20 > > - RESULTS: > > =20 > > > Those packets can't even arrive to their destination, cause the sta= tic routes that > > I configured DISAPEAR. From vtysh (sh ip route) I see the new route= s with their LABEL,=20 > > but from the command line (ip route) I just see the default routes = at PE1 and PE3. > > =20 > > > The NHLFE and ILM entries for that routes are created properly: > > =20 > > NHLFE entry key 0x00000002 mtu 1496 propagate_ttl > > push gen 10000 set eth1 ipv4 10.0.0.2 (0 bytes, 0 pkts) > > =20 > > ILM entry label gen 10000 labelspace 0 proto ipv4 > > pop peek (0 bytes, 0 pkts) > > =20 > > > So the problem is that with those entries the control component isn= 't able to change=20 > > the kernel routes. > > =20 > > 2? - I launch zebra and ospfd.=20 > > =20 > > - Then I configure ospf by vtysh: "router ospf" -> "network 10.0= .0.0/24 area 0" (PE1 and PE3) > > -> "network 12.0.0.0/24 area 0" (PE3) > > -> "network 13.0.0.0/24 area 0" (PE1) > > =20 > > - After new routes are learned I close vtysh, launch ldpd and con= figure PE1 and PE3 as LSRs by vtysh: > > =20 > > > "mpls ldp" > > > int eth1 (in each LSR): "mpls ip" and "mpls labelspace 0" > > =20 > > - Then I hang a host at 12..0/24 to send packets to 13.1 through = 10..0/24. > > =20 > > - RESULTS: > > =20 > > > Those packets arrive to their destination, but without a label.= >From vtysh (sh ip route) I see the new ospf=20 > > routes with their hop count (not any label) and from the comma= nd line (ip route) I see the same routes learned by ospf. > > =20 > > > The NHLFE and ILM entries for that routes are created properly: > > =20 > > NHLFE entry key 0x00000002 mtu 1496 propagate_ttl > > push gen 10000 set eth1 ipv4 10.0.0.2 (0 bytes, 0 pkts) > > =20 > > ILM entry label gen 10000 labelspace 0 proto ipv4 > > pop peek (0 bytes, 0 pkts) > > =20 > > > So the problem, again, is that with those entries the control co= mponent isn't able to change=20 > > the kernel routes. > > =20 > > Any idea of what's happening? As I told you, if you could provide me so= me documentation for understanding how the code is organized, maybe I could= help. > > =20 > > Thanks for your time, > > Gonzalo. > >=20 >=20 >=20 >=20 > --=20 > James R. Leu > jl...@mi... >=20 --=20 James R. Leu jl...@mi... |
|
From: James R. L. <jl...@mi...> - 2007-03-16 05:49:51
|
On Thu, Mar 15, 2007 at 07:49:03PM +0100, Marco Schmidt wrote: <snip> >=20 > This happens, if I try to compile the patched quagga-sources from sf > on my FC6 machine. I've got no other MPLS Packages installed on this > machine (it is used for other work), perhaps you forgot to install the > glibc-kernheaders from sf? > > I'm also trying to compile Quagga, because the zebra-daemon is not as > stable as I wished... Which snapshot has been used for the RPM at sf? > I encounter the following errors on my FC5 MPLS machines: I'm using http://quagga.net/download/quagga-0.99.6.tar.gz as the base, with my nexthop and MPLS framework changes which are significant. Can you elaborate on "zebra-daemon is not as stable"? What configure command line are you using before building quagga that resul= ts in the errors below? >=20 > In file included from /usr/include/sys/uio.h:24, > from /usr/include/sys/socket.h:27, > from /usr/include/linux/mpls.h:32, > from mpls_netlink.c:1: > /usr/include/sys/types.h:62: error: conflicting types for 'dev_t' > /usr/include/linux/types.h:10: error: previous declaration of 'dev_t'= was here > /usr/include/sys/types.h:67: error: conflicting types for 'gid_t' > /usr/include/linux/types.h:21: error: previous declaration of 'gid_t'= was here > /usr/include/sys/types.h:72: error: conflicting types for 'mode_t' > /usr/include/linux/types.h:12: error: previous declaration of 'mode_t= ' was here > /usr/include/sys/types.h:77: error: conflicting types for 'nlink_t' > /usr/include/linux/types.h:13: error: previous declaration of 'nlink_= t' was here > /usr/include/sys/types.h:82: error: conflicting types for 'uid_t' > /usr/include/linux/types.h:20: error: previous declaration of 'uid_t'= was here > In file included from /usr/include/sys/types.h:220, > from /usr/include/sys/uio.h:24, > from /usr/include/sys/socket.h:27, > from /usr/include/linux/mpls.h:32, > from mpls_netlink.c:1: > /usr/include/sys/select.h:78: error: conflicting types for 'fd_set' > /usr/include/linux/types.h:9: error: previous declaration of 'fd_set'= was here > make[2]: *** [mpls_netlink.o] Error 1 > make[2]: Leaving directory `/usr/src/redhat/BUILD/quagga-0.99.6/zebra' > make[1]: *** [all-recursive] Error 1 > make[1]: Leaving directory `/usr/src/redhat/BUILD/quagga-0.99.6' > make: *** [all] Error 2 >=20 > Does anyone know, how to solve these declaration-problems? >=20 > Regards, > Marco >=20 >=20 >=20 > > =20 > > Hi, I'm trying to install mpls on Linux machines and I've problems > > when I compile the quagga-mpls source from your repository > > ? > > I'm using Fedora Core 5, kernels ?rpms from sourceforge and > > quagga-mpls and ldp-portable from your repository > > I use your update-tools script to update autoconf and automake. > > First of all I modify?create-links to point to?ldp-portable > > directory. Then, ?I create?Makefile and when I'm going to compile > > and install quagga I find this error: > > ? > > #./configure --enable-vtysh --enable-mpls --enable-netlink > > #make > > ? > > // after some compiling time > > =20 > > zebra_vty.c:148: aviso: no hay un prototipo previo para ?zebra_static_i= pv4? > > =20 > > zebra_vty.c: En la funci?n ?vty_show_ipv6_route?: > > =20 > > zebra_vty.c:2668: error: clase de almacenamiento inv?lida para la funci= ?n ?show_ipv6_route? > > =20 > > zebra_vty.c:2668: error: ?show_ipv6_route? no se declar? aqu? (primer u= so en esta funci?n) > > =20 > > zebra_vty.c:2668: error: (Cada identificador no declarado solamente se = reporta una vez > > =20 > > zebra_vty.c:2668: error: ara cada funcion en la que aparece.) > > =20 > > zebra_vty.c:2674: error: clase de almacenamiento inv?lida para la funci= ?n ?show_ipv6_route? > > =20 > > zebra_vty.c:2674: aviso: no hay un prototipo previo para ?show_ipv6_rou= te? > > =20 > > zebra_vty.c:2698: error: clase de almacenamiento inv?lida para la > > funci?n ?show_ipv6_route_prefix_longer? > > =20 > > zebra_vty.c:2698: error: ?show_ipv6_route_prefix_longer? no se > > declar? aqu? (primer uso en esta funci?n) > > =20 > > zebra_vty.c:2706: error: clase de almacenamiento inv?lida para la > > funci?n ?show_ipv6_route_prefix_longer? > > =20 > > zebra_vty.c:2706: aviso: no hay un prototipo previo para ?show_ipv6_rou= te_prefix_longer? > > =20 > > zebra_vty.c:2740: error: clase de almacenamiento inv?lida para la > > funci?n ?show_ipv6_route_protocol? > > =20 > > zebra_vty.c:2740: error: ?show_ipv6_route_protocol? no se declar? aqu? = (primer uso en esta funci?n) > > =20 > > zebra_vty.c:2753: error: clase de almacenamiento inv?lida para la > > funci?n ?show_ipv6_route_protocol? > > =20 > > zebra_vty.c:2753: aviso: no hay un prototipo previo para ?show_ipv6_rou= te_protocol? > > =20 > > zebra_vty.c:2801: error: clase de almacenamiento inv?lida para la funci= ?n ?show_ipv6_route_addr? > > =20 > > zebra_vty.c:2801: error: ?show_ipv6_route_addr? no se declar? aqu? (pri= mer uso en esta funci?n) > > =20 > > zebra_vty.c:2808: error: clase de almacenamiento inv?lida para la funci= ?n ?show_ipv6_route_addr? > > =20 > > zebra_vty.c:2808: aviso: no hay un prototipo previo para ?show_ipv6_rou= te_addr? > > =20 > > zebra_vty.c:2839: error: clase de almacenamiento inv?lida para la funci= ?n ?show_ipv6_route_prefix? > > =20 > > zebra_vty.c:2839: error: ?show_ipv6_route_prefix? no se declar? aqu? (p= rimer uso en esta funci?n) > > =20 > > zebra_vty.c:2846: error: clase de almacenamiento inv?lida para la funci= ?n ?show_ipv6_route_prefix? > > =20 > > zebra_vty.c:2846: aviso: no hay un prototipo previo para ?show_ipv6_rou= te_prefix? > > =20 > > zebra_vty.c:2881: error: clase de almacenamiento inv?lida para la funci= ?n ?static_config_ipv6? > > =20 > > zebra_vty.c:2881: aviso: no hay un prototipo previo para ?static_config= _ipv6? > > =20 > > zebra_vty.c:2943: error: clase de almacenamiento inv?lida para la funci= ?n ?zebra_ip_config? > > =20 > > zebra_vty.c:2943: aviso: no hay un prototipo previo para ?zebra_ip_conf= ig? > > =20 > > zebra_vty.c:2960: aviso: no hay un prototipo previo para ?zebra_vty_ini= t? > > =20 > > zebra_vty.c:3087: error: expected declaration or statement at end of in= put > > =20 > > make[2]: *** [zebra_vty.o] Error 1 > > =20 > > make[2]: Leaving directory > > `/root/Desktop/anteriores/quagga-mpls/zebra' > > =20 > > make[1]: *** [all-recursive] Error 1 > > =20 > > make[1]: Leaving directory `/root/Desktop/anteriores/quagga-mpls' > > =20 > > make: *** [all] Error 2 > > ? > > Do you know the reason of this kind of errors? Has this situation happ= ened to someone? > > ? > > Thanks in advance for your time > > ? > > Regards,=20 > > Miguel Andr?s > > ? > > ? >=20 >=20 >=20 >=20 >=20 > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share y= our > opinions on IT & business topics through brief surveys-and earn cash > http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3D= DEVDEV > _______________________________________________ > mpls-linux-devel mailing list > mpl...@li... > https://lists.sourceforge.net/lists/listinfo/mpls-linux-devel --=20 James R. Leu jl...@mi... |
|
From: James R. L. <jl...@mi...> - 2007-03-16 05:40:13
|
I think the ipt_mpls module is broken. I'm working on a fix. When I figure it out. I'll post a new kernel. On Wed, Mar 14, 2007 at 01:50:27PM +0100, Julien Bisconti wrote: > Hi James, >=20 >=20 > You updated the repository according to my previous email. Now iptables > compiles like a charm :-) > But I still have the problem of the usability. >=20 > Simple example: >=20 > LSR1:~# iptables -A OUTPUT -d 128.104.17.130/32 -j mpls --nhlfe 0x2 > iptables v1.3.5: Couldn't load target `mpls' >=20 > Try `iptables -h' or 'iptables --help' for more information. > LSR1:~# lsmod > Module Size Used by > ipt_mpls 2816 0 > ip6t_mpls 2688 0 > x_tables 15876 2 ipt_mpls,ip6t_mpls > mpls_tunnel 9092 0 > ebt_mpls 3328 0 > ebtables 20096 1 ebt_mpls > mplsbr 3840 0 > mpls6 4224 0 > ipv6 260768 11 mpls6 > mpls4 6528 0 > mpls 83244 7 > ipt_mpls,ip6t_mpls,mpls_tunnel,ebt_mpls,mplsbr,mpls6,mpls4 >=20 >=20 > Could you help make this work? Because the module is loaded and iptables > doesn't seem to find it. >=20 > Thank you for your help. >=20 >=20 > Julien >=20 >=20 > --=20 > -------------------------------------------- > Julien BISCONTI <julien.bisconti(at)student.fundp.ac.be> > M.Sc. student in Computer Science, University of Namur > FUNDP, Belgium > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share y= our > opinions on IT & business topics through brief surveys-and earn cash > http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3D= DEVDEV > _______________________________________________ > mpls-linux-devel mailing list > mpl...@li... > https://lists.sourceforge.net/lists/listinfo/mpls-linux-devel --=20 James R. Leu jl...@mi... |
|
From: Marco S. <mar...@s2...> - 2007-03-15 18:51:11
|
Hello,
here's a short outline of the same error:
> zebra_vty.c:2943: Fehler: ung=FCltige Speicherklasse f=FCr Funktion =BBze=
bra_ip_config=AB
> zebra_vty.c:2943: Warnung: kein vorheriger Prototyp f=FCr =BBzebra_ip_con=
fig=AB
> zebra_vty.c:2960: Warnung: kein vorheriger Prototyp f=FCr =BBzebra_vty_in=
it=AB
> zebra_vty.c:3087: Fehler: expected declaration or statement at end of inp=
ut
> make[2]: *** [zebra_vty.o] Fehler 1
> make[2]: Leaving directory `/usr/src/redhat/SOURCES/quagga-0.99.6/zebra'
> make[1]: *** [all-recursive] Fehler 1
> make[1]: Leaving directory `/usr/src/redhat/SOURCES/quagga-0.99.6'
> make: *** [all] Fehler 2
This happens, if I try to compile the patched quagga-sources from sf
on my FC6 machine. I've got no other MPLS Packages installed on this
machine (it is used for other work), perhaps you forgot to install the
glibc-kernheaders from sf?
I'm also trying to compile Quagga, because the zebra-daemon is not as
stable as I wished... Which snapshot has been used for the RPM at sf?
I encounter the following errors on my FC5 MPLS machines:
In file included from /usr/include/sys/uio.h:24,
from /usr/include/sys/socket.h:27,
from /usr/include/linux/mpls.h:32,
from mpls_netlink.c:1:
/usr/include/sys/types.h:62: error: conflicting types for 'dev_t'
/usr/include/linux/types.h:10: error: previous declaration of 'dev_t' w=
as here
/usr/include/sys/types.h:67: error: conflicting types for 'gid_t'
/usr/include/linux/types.h:21: error: previous declaration of 'gid_t' w=
as here
/usr/include/sys/types.h:72: error: conflicting types for 'mode_t'
/usr/include/linux/types.h:12: error: previous declaration of 'mode_t' =
was here
/usr/include/sys/types.h:77: error: conflicting types for 'nlink_t'
/usr/include/linux/types.h:13: error: previous declaration of 'nlink_t'=
was here
/usr/include/sys/types.h:82: error: conflicting types for 'uid_t'
/usr/include/linux/types.h:20: error: previous declaration of 'uid_t' w=
as here
In file included from /usr/include/sys/types.h:220,
from /usr/include/sys/uio.h:24,
from /usr/include/sys/socket.h:27,
from /usr/include/linux/mpls.h:32,
from mpls_netlink.c:1:
/usr/include/sys/select.h:78: error: conflicting types for 'fd_set'
/usr/include/linux/types.h:9: error: previous declaration of 'fd_set' w=
as here
make[2]: *** [mpls_netlink.o] Error 1
make[2]: Leaving directory `/usr/src/redhat/BUILD/quagga-0.99.6/zebra'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/usr/src/redhat/BUILD/quagga-0.99.6'
make: *** [all] Error 2
Does anyone know, how to solve these declaration-problems?
Regards,
Marco
> =20
> Hi, I'm trying to install mpls on Linux machines and I've problems
> when I compile the quagga-mpls source from your repository
> =A0
> I'm using Fedora Core 5, kernels =A0rpms from sourceforge and
> quagga-mpls and ldp-portable from your repository
> I use your update-tools script to update autoconf and automake.
> First of all I modify=A0create-links to point to=A0ldp-portable
> directory. Then, =A0I create=A0Makefile and when I'm going to compile
> and install quagga I find this error:
> =A0
> #./configure --enable-vtysh --enable-mpls --enable-netlink
> #make
> =A0
> // after some compiling time
> =20
> zebra_vty.c:148: aviso: no hay un prototipo previo para =91zebra_static_i=
pv4=92
> =20
> zebra_vty.c: En la funci=F3n =91vty_show_ipv6_route=92:
> =20
> zebra_vty.c:2668: error: clase de almacenamiento inv=E1lida para la funci=
=F3n =91show_ipv6_route=92
> =20
> zebra_vty.c:2668: error: =91show_ipv6_route=92 no se declar=F3 aqu=ED (pr=
imer uso en esta funci=F3n)
> =20
> zebra_vty.c:2668: error: (Cada identificador no declarado solamente se re=
porta una vez
> =20
> zebra_vty.c:2668: error: ara cada funcion en la que aparece.)
> =20
> zebra_vty.c:2674: error: clase de almacenamiento inv=E1lida para la funci=
=F3n =91show_ipv6_route=92
> =20
> zebra_vty.c:2674: aviso: no hay un prototipo previo para =91show_ipv6_rou=
te=92
> =20
> zebra_vty.c:2698: error: clase de almacenamiento inv=E1lida para la
> funci=F3n =91show_ipv6_route_prefix_longer=92
> =20
> zebra_vty.c:2698: error: =91show_ipv6_route_prefix_longer=92 no se
> declar=F3 aqu=ED (primer uso en esta funci=F3n)
> =20
> zebra_vty.c:2706: error: clase de almacenamiento inv=E1lida para la
> funci=F3n =91show_ipv6_route_prefix_longer=92
> =20
> zebra_vty.c:2706: aviso: no hay un prototipo previo para =91show_ipv6_rou=
te_prefix_longer=92
> =20
> zebra_vty.c:2740: error: clase de almacenamiento inv=E1lida para la
> funci=F3n =91show_ipv6_route_protocol=92
> =20
> zebra_vty.c:2740: error: =91show_ipv6_route_protocol=92 no se declar=F3 a=
qu=ED (primer uso en esta funci=F3n)
> =20
> zebra_vty.c:2753: error: clase de almacenamiento inv=E1lida para la
> funci=F3n =91show_ipv6_route_protocol=92
> =20
> zebra_vty.c:2753: aviso: no hay un prototipo previo para =91show_ipv6_rou=
te_protocol=92
> =20
> zebra_vty.c:2801: error: clase de almacenamiento inv=E1lida para la funci=
=F3n =91show_ipv6_route_addr=92
> =20
> zebra_vty.c:2801: error: =91show_ipv6_route_addr=92 no se declar=F3 aqu=
=ED (primer uso en esta funci=F3n)
> =20
> zebra_vty.c:2808: error: clase de almacenamiento inv=E1lida para la funci=
=F3n =91show_ipv6_route_addr=92
> =20
> zebra_vty.c:2808: aviso: no hay un prototipo previo para =91show_ipv6_rou=
te_addr=92
> =20
> zebra_vty.c:2839: error: clase de almacenamiento inv=E1lida para la funci=
=F3n =91show_ipv6_route_prefix=92
> =20
> zebra_vty.c:2839: error: =91show_ipv6_route_prefix=92 no se declar=F3 aqu=
=ED (primer uso en esta funci=F3n)
> =20
> zebra_vty.c:2846: error: clase de almacenamiento inv=E1lida para la funci=
=F3n =91show_ipv6_route_prefix=92
> =20
> zebra_vty.c:2846: aviso: no hay un prototipo previo para =91show_ipv6_rou=
te_prefix=92
> =20
> zebra_vty.c:2881: error: clase de almacenamiento inv=E1lida para la funci=
=F3n =91static_config_ipv6=92
> =20
> zebra_vty.c:2881: aviso: no hay un prototipo previo para =91static_config=
_ipv6=92
> =20
> zebra_vty.c:2943: error: clase de almacenamiento inv=E1lida para la funci=
=F3n =91zebra_ip_config=92
> =20
> zebra_vty.c:2943: aviso: no hay un prototipo previo para =91zebra_ip_conf=
ig=92
> =20
> zebra_vty.c:2960: aviso: no hay un prototipo previo para =91zebra_vty_ini=
t=92
> =20
> zebra_vty.c:3087: error: expected declaration or statement at end of input
> =20
> make[2]: *** [zebra_vty.o] Error 1
> =20
> make[2]: Leaving directory
> `/root/Desktop/anteriores/quagga-mpls/zebra'
> =20
> make[1]: *** [all-recursive] Error 1
> =20
> make[1]: Leaving directory `/root/Desktop/anteriores/quagga-mpls'
> =20
> make: *** [all] Error 2
> =A0
> Do you know the reason of this kind of errors? Has this situation happen=
ed to someone?
> =A0
> Thanks in advance for your time
> =A0
> Regards,=20
> Miguel Andr=E9s
> =A0
> =A0
|
|
From: Julien B. <jul...@gm...> - 2007-03-14 12:50:34
|
Hi James, You updated the repository according to my previous email. Now iptables compiles like a charm :-) But I still have the problem of the usability. Simple example: LSR1:~# iptables -A OUTPUT -d 128.104.17.130/32 -j mpls --nhlfe 0x2 iptables v1.3.5: Couldn't load target `mpls' Try `iptables -h' or 'iptables --help' for more information. LSR1:~# lsmod Module Size Used by ipt_mpls 2816 0 ip6t_mpls 2688 0 x_tables 15876 2 ipt_mpls,ip6t_mpls mpls_tunnel 9092 0 ebt_mpls 3328 0 ebtables 20096 1 ebt_mpls mplsbr 3840 0 mpls6 4224 0 ipv6 260768 11 mpls6 mpls4 6528 0 mpls 83244 7 ipt_mpls,ip6t_mpls,mpls_tunnel,ebt_mpls,mplsbr,mpls6,mpls4 Could you help make this work? Because the module is loaded and iptables doesn't seem to find it. Thank you for your help. Julien -- -------------------------------------------- Julien BISCONTI <julien.bisconti(at)student.fundp.ac.be> M.Sc. student in Computer Science, University of Namur FUNDP, Belgium |
|
From: James R. L. <jl...@mi...> - 2007-03-14 12:34:19
|
You need to enable IPv6 support. Why are your trying to compile quagga-mpls? There is a binary FC5 RPM for quagga-mpls already. On Wed, Mar 14, 2007 at 10:28:24AM +0000, Miguel Andr?s wrote: > Hi, I'm trying to install mpls on Linux machines and I've problems when I= compile the quagga-mpls source from your repository > =20 > I'm using Fedora Core 5, kernels rpms from sourceforge and quagga-mpls a= nd ldp-portable from your repository > I use your update-tools script to update autoconf and automake. First of = all I modify create-links to point to ldp-portable directory. Then, I crea= te Makefile and when I'm going to compile and install quagga I find this er= ror: > =20 > #./configure --enable-vtysh --enable-mpls --enable-netlink > #make > =20 > // after some compiling time > zebra_vty.c:148: aviso: no hay un prototipo previo para ?zebra_static_ipv= 4? > zebra_vty.c: En la funci?n ?vty_show_ipv6_route?: > zebra_vty.c:2668: error: clase de almacenamiento inv?lida para la funci?n= ?show_ipv6_route? > zebra_vty.c:2668: error: ?show_ipv6_route? no se declar? aqu? (primer uso= en esta funci?n) > zebra_vty.c:2668: error: (Cada identificador no declarado solamente se re= porta una vez > zebra_vty.c:2668: error: ara cada funcion en la que aparece.) > zebra_vty.c:2674: error: clase de almacenamiento inv?lida para la funci?n= ?show_ipv6_route? > zebra_vty.c:2674: aviso: no hay un prototipo previo para ?show_ipv6_route? > zebra_vty.c:2698: error: clase de almacenamiento inv?lida para la funci?n= ?show_ipv6_route_prefix_longer? > zebra_vty.c:2698: error: ?show_ipv6_route_prefix_longer? no se declar? aq= u? (primer uso en esta funci?n) > zebra_vty.c:2706: error: clase de almacenamiento inv?lida para la funci?n= ?show_ipv6_route_prefix_longer? > zebra_vty.c:2706: aviso: no hay un prototipo previo para ?show_ipv6_route= _prefix_longer? > zebra_vty.c:2740: error: clase de almacenamiento inv?lida para la funci?n= ?show_ipv6_route_protocol? > zebra_vty.c:2740: error: ?show_ipv6_route_protocol? no se declar? aqu? (p= rimer uso en esta funci?n) > zebra_vty.c:2753: error: clase de almacenamiento inv?lida para la funci?n= ?show_ipv6_route_protocol? > zebra_vty.c:2753: aviso: no hay un prototipo previo para ?show_ipv6_route= _protocol? > zebra_vty.c:2801: error: clase de almacenamiento inv?lida para la funci?n= ?show_ipv6_route_addr? > zebra_vty.c:2801: error: ?show_ipv6_route_addr? no se declar? aqu? (prime= r uso en esta funci?n) > zebra_vty.c:2808: error: clase de almacenamiento inv?lida para la funci?n= ?show_ipv6_route_addr? > zebra_vty.c:2808: aviso: no hay un prototipo previo para ?show_ipv6_route= _addr? > zebra_vty.c:2839: error: clase de almacenamiento inv?lida para la funci?n= ?show_ipv6_route_prefix? > zebra_vty.c:2839: error: ?show_ipv6_route_prefix? no se declar? aqu? (pri= mer uso en esta funci?n) > zebra_vty.c:2846: error: clase de almacenamiento inv?lida para la funci?n= ?show_ipv6_route_prefix? > zebra_vty.c:2846: aviso: no hay un prototipo previo para ?show_ipv6_route= _prefix? > zebra_vty.c:2881: error: clase de almacenamiento inv?lida para la funci?n= ?static_config_ipv6? > zebra_vty.c:2881: aviso: no hay un prototipo previo para ?static_config_i= pv6? > zebra_vty.c:2943: error: clase de almacenamiento inv?lida para la funci?n= ?zebra_ip_config? > zebra_vty.c:2943: aviso: no hay un prototipo previo para ?zebra_ip_config? > zebra_vty.c:2960: aviso: no hay un prototipo previo para ?zebra_vty_init? > zebra_vty.c:3087: error: expected declaration or statement at end of input > make[2]: *** [zebra_vty.o] Error 1 > make[2]: Leaving directory `/root/Desktop/anteriores/quagga-mpls/zebra' > make[1]: *** [all-recursive] Error 1 > make[1]: Leaving directory `/root/Desktop/anteriores/quagga-mpls' > make: *** [all] Error 2 > =20 > Do you know the reason of this kind of errors? Has this situation happene= d to someone? > =20 > Thanks in advance for your time > =20 > Regards,=20 > Miguel Andr?s > =20 > =20 > _________________________________________________________________ > Busca desde cualquier p?gina Web con una protecci?n excepcional. Consigue= la Barra de herramientas de Windows Live hoy mismo y GRATUITAMENTE. > http://www.toolbar.live.com > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share y= our > opinions on IT & business topics through brief surveys-and earn cash > http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3D= DEVDEV > _______________________________________________ > mpls-linux-devel mailing list > mpl...@li... > https://lists.sourceforge.net/lists/listinfo/mpls-linux-devel --=20 James R. Leu jl...@mi... |
|
From: <gsr...@al...> - 2007-03-14 11:49:41
|
Hi James: This is what I get in the log file at PE2, maybe these could be helpful = to understand what's happening: As always the NHLFE and ILM entries are created and IP routes learned by = OSPF. 2007/03/14 12:04:37 LDP: Terminating on signal 2007/03/14 12:04:37 ZEBRA: Terminating on signal 2007/03/14 12:04:37 ZEBRA: netlink_route_multipath() (single hop): = RTM_DELROUTE 12.0.0.0/24, type IPv4=20 2007/03/14 12:04:37 ZEBRA: netlink_route_multipath() (single hop): = nexthop via 10.0.0.1 if 4 2007/03/14 12:04:37 ZEBRA: netlink_talk: netlink-cmd type = RTM_DELROUTE(25), seq=3D7 2007/03/14 12:04:37 ZEBRA: netlink_parse_info: netlink-cmd ACK: = type=3DRTM_DELROUTE(25), seq=3D7, pid=3D0 2007/03/14 12:04:37 ZEBRA: netlink_talk: mpls-netlink-cmd type (29), = seq=3D3 2007/03/14 12:04:37 ZEBRA: netlink_parse_info: mpls-netlink-cmd ACK: = type=3D(29), seq=3D3, pid=3D0 2007/03/14 12:04:37 ZEBRA: netlink_talk: mpls-netlink-cmd type (29), = seq=3D4 2007/03/14 12:04:37 ZEBRA: netlink_parse_info: mpls-netlink-cmd ACK: = type=3D(29), seq=3D4, pid=3D0 2007/03/14 12:04:37 ZEBRA: IRDP: Received shutdown notification. 2007/03/14 12:06:02 OSPF: interface 13.0.0.1 [3] join AllSPFRouters = Multicast group. 2007/03/14 12:06:22 OSPF: interface 10.0.0.2 [4] join AllSPFRouters = Multicast group. 2007/03/14 12:06:40 OSPF: ospfTrapNbrStateChange trap sent: 10.0.0.1 now = Init/DROther 2007/03/14 12:06:42 OSPF: DR-Election[1st]: Backup 13.0.0.1 2007/03/14 12:06:42 OSPF: DR-Election[1st]: DR 13.0.0.1 2007/03/14 12:06:42 OSPF: DR-Election[2nd]: Backup 0.0.0.0 2007/03/14 12:06:42 OSPF: DR-Election[2nd]: DR 13.0.0.1 2007/03/14 12:06:42 OSPF: ospfTrapIfStateChange trap sent: 13.0.0.1 now = DR 2007/03/14 12:06:42 OSPF: interface 13.0.0.1 [3] join AllDRouters = Multicast group. 2007/03/14 12:07:02 OSPF: DR-Election[1st]: Backup 10.0.0.1 2007/03/14 12:07:02 OSPF: DR-Election[1st]: DR 10.0.0.1 2007/03/14 12:07:02 OSPF: ospfTrapIfStateChange trap sent: 10.0.0.2 now = DROther 2007/03/14 12:07:20 OSPF: Packet[DD]: Neighbor 12.0.0.1 Negotiation done = (Slave). 2007/03/14 12:07:20 OSPF: nsm_change_state(12.0.0.1, Loading -> Full): = scheduling new router-LSA origination 2007/03/14 12:07:20 OSPF: DR-Election[1st]: Backup 10.0.0.2 2007/03/14 12:07:20 OSPF: DR-Election[1st]: DR 10.0.0.1 2007/03/14 12:07:20 OSPF: DR-Election[2nd]: Backup 10.0.0.2 2007/03/14 12:07:20 OSPF: DR-Election[2nd]: DR 10.0.0.1 2007/03/14 12:07:20 OSPF: ospfTrapIfStateChange trap sent: 10.0.0.2 now = Backup 2007/03/14 12:07:20 OSPF: interface 10.0.0.2 [4] join AllDRouters = Multicast group. 2007/03/14 12:07:25 ZEBRA: netlink_route_multipath() (single hop): = RTM_NEWROUTE 12.0.0.0/24, type IPv4=20 2007/03/14 12:07:25 ZEBRA: netlink_route_multipath() (single hop): = nexthop via 10.0.0.1 if 4 2007/03/14 12:07:25 ZEBRA: netlink_talk: netlink-cmd type = RTM_NEWROUTE(24), seq=3D6 2007/03/14 12:07:25 ZEBRA: netlink_parse_info: netlink-cmd ACK: = type=3DRTM_NEWROUTE(24), seq=3D6, pid=3D0 2007/03/14 12:07:25 ZEBRA: netlink_parse_info: netlink-listen type = RTM_NEWROUTE(24), seq=3D6, pid=3D4294963184 2007/03/14 12:07:25 ZEBRA: netlink_parse_info: netlink-cmd packet comes = from netlink-listen 2007/03/14 12:07:34 LDP: route 169.254.0.0/16 2007/03/14 12:07:34 LDP: num ifindex 0 2007/03/14 12:07:34 LDP: ifindex 4 2007/03/14 12:07:34 LDP: add 2007/03/14 12:07:34 LDP: route 10.0.0.0/24 2007/03/14 12:07:34 LDP: num ifindex 0 2007/03/14 12:07:34 LDP: attached 2007/03/14 12:07:34 LDP: ifindex 4 2007/03/14 12:07:34 LDP: add 2007/03/14 12:07:34 LDP: route 13.0.0.0/24 2007/03/14 12:07:34 LDP: num ifindex 0 2007/03/14 12:07:34 LDP: attached 2007/03/14 12:07:34 LDP: ifindex 3 2007/03/14 12:07:34 LDP: add 2007/03/14 12:07:34 LDP: route 12.0.0.0/24 2007/03/14 12:07:34 LDP: num nexthop 0 2007/03/14 12:07:34 LDP: nexthop 10.0.0.1 2007/03/14 12:07:34 LDP: add 2007/03/14 12:07:44 ZEBRA: netlink_talk: mpls-netlink-cmd type (29), = seq=3D1 2007/03/14 12:07:44 ZEBRA: netlink_parse_info: mpls-netlink-cmd ACK: = type=3D(29), seq=3D1, pid=3D0 2007/03/14 12:07:59 LDP: OUT: ldp_session_attempt_setup: = MPLS_NON_BLOCKING 2007/03/14 12:07:59 LDP: OUT: LDP_NOTIF_SESSION_REJECTED_NO_HELLO: 2007/03/14 12:08:03 LDP: OUT: ldp_session_attempt_setup: = MPLS_NON_BLOCKING 2007/03/14 12:08:03 LDP: OUT: LDP_NOTIF_SESSION_REJECTED_NO_HELLO: 2007/03/14 12:08:08 LDP: OUT: ldp_session_attempt_setup: = MPLS_NON_BLOCKING 2007/03/14 12:08:10 ZEBRA: netlink_talk: mpls-netlink-cmd type (29), = seq=3D2 2007/03/14 12:08:10 ZEBRA: netlink_parse_info: mpls-netlink-cmd ACK: = type=3D(29), seq=3D2, pid=3D0 2007/03/14 12:08:10 ZEBRA: netlink_parse_info: mpls-netlink-listen type = (29), seq=3D0, pid=3D0 2007/03/14 12:08:10 ZEBRA: netlink_talk: mpls-netlink-nhlfe type (29), = seq=3D1 2007/03/14 12:08:10 ZEBRA: netlink_parse_info: mpls-netlink-nhlfe type = (29), seq=3D1, pid=3D4294963182 2007/03/14 12:08:10 ZEBRA: netlink_talk: ignoring message type 0x001d 2007/03/14 12:08:10 ZEBRA: mpls_ctrl_nhlfe_register(): NHLFE 0x00000003 2007/03/14 12:08:10 ZEBRA: netlink_parse_info: mpls-netlink-listen type = (29), seq=3D1, pid=3D4294963182 2007/03/14 12:08:10 ZEBRA: netlink_parse_info: mpls-netlink-nhlfe packet = comes from mpls-netlink-listen 2007/03/14 12:08:10 LDP: found pending NHLFE: 0x916d858 Thanks in advance, Gonzalo. -----Mensaje original----- De: James R. Leu [mailto:jl...@mi...] Enviado el: mar 13/03/2007 14:11 Para: Sienes Rodr=EDguez Gonzalo CC: mpl...@li... Asunto: Re: [mpls-linux-devel] MPLS-Linux-1.955 FC5 =20 I see some difference with my testing setup. First, I create all my routes via vtysh with LDP running at that time, in otherwords: I start zebra, ospfd, and ldpd, then start my configuration via vtysh. I configure EVERYTHING via vtysh. The only interface on the box that is not configure via vtysh is the managment interface which does not participate in routing. Is there a reason you do not use the system scripts to start zebra ospfd and ldpd? (ie service zebra start; service ospfd start; service ldpd = start) Have you tried turning on zebra debugging? (in vtysh: debug zebra = kernel) You will need to have logging configured for this to produce anything useful. I've run your exact configuration on my network at home at it works just = fine. There must be something with the order of events that is causing an = issue. Obviously I'd like to fix this issue, but I need to know what = "mis-ordering" is causing it and be able to reproduce it before I can fix it. At this point I do not believe you have ever gotten LDP to work for you so forgive me for being sceptical. On Tue, Mar 13, 2007 at 09:27:53AM +0100, Sienes Rodr?guez Gonzalo = wrote: > Hi James: > =20 > I?m trying two different experiments with the following scenario and = these are the results. > =20 > eth0 eth1 eth1 eth0 > 12.0.0.1-------PE1---------------------PE2-------13.0.0.1 > .1 10.0.0.0/24 .2 > =20 >=20 > 1? - I create static routes from PE1 to 13..0/24 and PE3 to = 12..0/24.=20 > =20 > - Then I launch zebra and ldpd typing zebra -d and ldpd -d by = the command line.=20 > (I load the mpls4 module since system boots). > =20 > - I configure PE1 and PE3 as LSRs by vtysh: > =20 > > "mpls ldp" > > int eth1 (in each LSR): "mpls ip" and "mpls labelspace 0" > =20 > - Then I hang a host at 12..0/24 to send packets to 13.1 = through 10..0/24. > =20 > - RESULTS: > =20 > > Those packets can't even arrive to their destination, cause the = static routes that > I configured DISAPEAR. From vtysh (sh ip route) I see the new = routes with their LABEL,=20 > but from the command line (ip route) I just see the default routes = at PE1 and PE3. > =20 > > The NHLFE and ILM entries for that routes are created properly: > =20 > NHLFE entry key 0x00000002 mtu 1496 propagate_ttl > push gen 10000 set eth1 ipv4 10.0.0.2 (0 bytes, 0 pkts) > =20 > ILM entry label gen 10000 labelspace 0 proto ipv4 > pop peek (0 bytes, 0 pkts) > =20 > > So the problem is that with those entries the control component = isn't able to change=20 > the kernel routes. > =20 > 2? - I launch zebra and ospfd.=20 > =20 > - Then I configure ospf by vtysh: "router ospf" -> "network = 10.0.0.0/24 area 0" (PE1 and PE3) > -> "network 12.0.0.0/24 area 0" (PE3) > -> "network 13.0.0.0/24 area 0" (PE1) > =20 > - After new routes are learned I close vtysh, launch ldpd and = configure PE1 and PE3 as LSRs by vtysh: > =20 > > "mpls ldp" > > int eth1 (in each LSR): "mpls ip" and "mpls labelspace 0" > =20 > - Then I hang a host at 12..0/24 to send packets to 13.1 through = 10..0/24. > =20 > - RESULTS: > =20 > > Those packets arrive to their destination, but without a = label. >From vtysh (sh ip route) I see the new ospf=20 > routes with their hop count (not any label) and from the = command line (ip route) I see the same routes learned by ospf. > =20 > > The NHLFE and ILM entries for that routes are created = properly: > =20 > NHLFE entry key 0x00000002 mtu 1496 propagate_ttl > push gen 10000 set eth1 ipv4 10.0.0.2 (0 bytes, 0 pkts) > =20 > ILM entry label gen 10000 labelspace 0 proto ipv4 > pop peek (0 bytes, 0 pkts) > =20 > > So the problem, again, is that with those entries the control = component isn't able to change=20 > the kernel routes. > =20 > Any idea of what's happening? As I told you, if you could provide me = some documentation for understanding how the code is organized, maybe I = could help. > =20 > Thanks for your time, > Gonzalo. >=20 --=20 James R. Leu jl...@mi... |
|
From: <ni...@ho...> - 2007-03-14 10:28:34
|
Hi, I'm trying to install mpls on Linux machines and I've problems when I c= ompile the quagga-mpls source from your repository =20 I'm using Fedora Core 5, kernels rpms from sourceforge and quagga-mpls and= ldp-portable from your repository I use your update-tools script to update autoconf and automake. First of al= l I modify create-links to point to ldp-portable directory. Then, I create= Makefile and when I'm going to compile and install quagga I find this erro= r: =20 #./configure --enable-vtysh --enable-mpls --enable-netlink #make =20 // after some compiling time zebra_vty.c:148: aviso: no hay un prototipo previo para =91zebra_static_ipv= 4=92 zebra_vty.c: En la funci=F3n =91vty_show_ipv6_route=92: zebra_vty.c:2668: error: clase de almacenamiento inv=E1lida para la funci= =F3n =91show_ipv6_route=92 zebra_vty.c:2668: error: =91show_ipv6_route=92 no se declar=F3 aqu=ED (prim= er uso en esta funci=F3n) zebra_vty.c:2668: error: (Cada identificador no declarado solamente se repo= rta una vez zebra_vty.c:2668: error: ara cada funcion en la que aparece.) zebra_vty.c:2674: error: clase de almacenamiento inv=E1lida para la funci= =F3n =91show_ipv6_route=92 zebra_vty.c:2674: aviso: no hay un prototipo previo para =91show_ipv6_route= =92 zebra_vty.c:2698: error: clase de almacenamiento inv=E1lida para la funci= =F3n =91show_ipv6_route_prefix_longer=92 zebra_vty.c:2698: error: =91show_ipv6_route_prefix_longer=92 no se declar= =F3 aqu=ED (primer uso en esta funci=F3n) zebra_vty.c:2706: error: clase de almacenamiento inv=E1lida para la funci= =F3n =91show_ipv6_route_prefix_longer=92 zebra_vty.c:2706: aviso: no hay un prototipo previo para =91show_ipv6_route= _prefix_longer=92 zebra_vty.c:2740: error: clase de almacenamiento inv=E1lida para la funci= =F3n =91show_ipv6_route_protocol=92 zebra_vty.c:2740: error: =91show_ipv6_route_protocol=92 no se declar=F3 aqu= =ED (primer uso en esta funci=F3n) zebra_vty.c:2753: error: clase de almacenamiento inv=E1lida para la funci= =F3n =91show_ipv6_route_protocol=92 zebra_vty.c:2753: aviso: no hay un prototipo previo para =91show_ipv6_route= _protocol=92 zebra_vty.c:2801: error: clase de almacenamiento inv=E1lida para la funci= =F3n =91show_ipv6_route_addr=92 zebra_vty.c:2801: error: =91show_ipv6_route_addr=92 no se declar=F3 aqu=ED = (primer uso en esta funci=F3n) zebra_vty.c:2808: error: clase de almacenamiento inv=E1lida para la funci= =F3n =91show_ipv6_route_addr=92 zebra_vty.c:2808: aviso: no hay un prototipo previo para =91show_ipv6_route= _addr=92 zebra_vty.c:2839: error: clase de almacenamiento inv=E1lida para la funci= =F3n =91show_ipv6_route_prefix=92 zebra_vty.c:2839: error: =91show_ipv6_route_prefix=92 no se declar=F3 aqu= =ED (primer uso en esta funci=F3n) zebra_vty.c:2846: error: clase de almacenamiento inv=E1lida para la funci= =F3n =91show_ipv6_route_prefix=92 zebra_vty.c:2846: aviso: no hay un prototipo previo para =91show_ipv6_route= _prefix=92 zebra_vty.c:2881: error: clase de almacenamiento inv=E1lida para la funci= =F3n =91static_config_ipv6=92 zebra_vty.c:2881: aviso: no hay un prototipo previo para =91static_config_i= pv6=92 zebra_vty.c:2943: error: clase de almacenamiento inv=E1lida para la funci= =F3n =91zebra_ip_config=92 zebra_vty.c:2943: aviso: no hay un prototipo previo para =91zebra_ip_config= =92 zebra_vty.c:2960: aviso: no hay un prototipo previo para =91zebra_vty_init= =92 zebra_vty.c:3087: error: expected declaration or statement at end of input make[2]: *** [zebra_vty.o] Error 1 make[2]: Leaving directory `/root/Desktop/anteriores/quagga-mpls/zebra' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/root/Desktop/anteriores/quagga-mpls' make: *** [all] Error 2 =20 Do you know the reason of this kind of errors? Has this situation happened = to someone? =20 Thanks in advance for your time =20 Regards,=20 Miguel Andr=E9s =20 =20 _________________________________________________________________ Busca desde cualquier p=E1gina Web con una protecci=F3n excepcional. Consig= ue la Barra de herramientas de Windows Live hoy mismo y GRATUITAMENTE. http://www.toolbar.live.com= |
|
From: James R. L. <jl...@mi...> - 2007-03-13 13:12:07
|
I see some difference with my testing setup. First, I create all my routes via vtysh with LDP running at that time, in otherwords: I start zebra, ospfd, and ldpd, then start my configuration via vtysh. I configure EVERYTHING via vtysh. The only interface on the box that is not configure via vtysh is the managment interface which does not participate in routing. Is there a reason you do not use the system scripts to start zebra ospfd and ldpd? (ie service zebra start; service ospfd start; service ldpd start) Have you tried turning on zebra debugging? (in vtysh: debug zebra kernel) You will need to have logging configured for this to produce anything useful. I've run your exact configuration on my network at home at it works just fi= ne. There must be something with the order of events that is causing an issue. Obviously I'd like to fix this issue, but I need to know what "mis-ordering" is causing it and be able to reproduce it before I can fix it. At this point I do not believe you have ever gotten LDP to work for you so forgive me for being sceptical. On Tue, Mar 13, 2007 at 09:27:53AM +0100, Sienes Rodr?guez Gonzalo wrote: > Hi James: > =20 > I?m trying two different experiments with the following scenario and thes= e are the results. > =20 > eth0 eth1 eth1 eth0 > 12.0.0.1-------PE1---------------------PE2-------13.0.0.1 > .1 10.0.0.0/24 .2 > =20 >=20 > 1? - I create static routes from PE1 to 13..0/24 and PE3 to 12..0/24.= =20 > =20 > - Then I launch zebra and ldpd typing zebra -d and ldpd -d by the = command line.=20 > (I load the mpls4 module since system boots). > =20 > - I configure PE1 and PE3 as LSRs by vtysh: > =20 > > "mpls ldp" > > int eth1 (in each LSR): "mpls ip" and "mpls labelspace 0" > =20 > - Then I hang a host at 12..0/24 to send packets to 13.1 through 1= 0..0/24. > =20 > - RESULTS: > =20 > > Those packets can't even arrive to their destination, cause the stati= c routes that > I configured DISAPEAR. From vtysh (sh ip route) I see the new routes = with their LABEL,=20 > but from the command line (ip route) I just see the default routes at= PE1 and PE3. > =20 > > The NHLFE and ILM entries for that routes are created properly: > =20 > NHLFE entry key 0x00000002 mtu 1496 propagate_ttl > push gen 10000 set eth1 ipv4 10.0.0.2 (0 bytes, 0 pkts) > =20 > ILM entry label gen 10000 labelspace 0 proto ipv4 > pop peek (0 bytes, 0 pkts) > =20 > > So the problem is that with those entries the control component isn't= able to change=20 > the kernel routes. > =20 > 2? - I launch zebra and ospfd.=20 > =20 > - Then I configure ospf by vtysh: "router ospf" -> "network 10.0.0= .0/24 area 0" (PE1 and PE3) > -> "network 12.0.0.0/24 area 0" (PE3) > -> "network 13.0.0.0/24 area 0" (PE1) > =20 > - After new routes are learned I close vtysh, launch ldpd and confi= gure PE1 and PE3 as LSRs by vtysh: > =20 > > "mpls ldp" > > int eth1 (in each LSR): "mpls ip" and "mpls labelspace 0" > =20 > - Then I hang a host at 12..0/24 to send packets to 13.1 through 10= ..0/24. > =20 > - RESULTS: > =20 > > Those packets arrive to their destination, but without a label. >= =46rom vtysh (sh ip route) I see the new ospf=20 > routes with their hop count (not any label) and from the command= line (ip route) I see the same routes learned by ospf. > =20 > > The NHLFE and ILM entries for that routes are created properly: > =20 > NHLFE entry key 0x00000002 mtu 1496 propagate_ttl > push gen 10000 set eth1 ipv4 10.0.0.2 (0 bytes, 0 pkts) > =20 > ILM entry label gen 10000 labelspace 0 proto ipv4 > pop peek (0 bytes, 0 pkts) > =20 > > So the problem, again, is that with those entries the control comp= onent isn't able to change=20 > the kernel routes. > =20 > Any idea of what's happening? As I told you, if you could provide me some= documentation for understanding how the code is organized, maybe I could h= elp. > =20 > Thanks for your time, > Gonzalo. >=20 --=20 James R. Leu jl...@mi... |
|
From: <gsr...@al...> - 2007-03-13 08:34:31
|
Hi James:
=20
I=B4m trying two different experiments with the following scenario and =
these are the results.
=20
eth0 eth1 eth1 eth0
12.0.0.1-------PE1---------------------PE2-------13.0.0.1
.1 10.0.0.0/24 .2
=20
1=BA - I create static routes from PE1 to 13..0/24 and PE3 to =
12..0/24.=20
=20
- Then I launch zebra and ldpd typing zebra -d and ldpd -d by the =
command line.=20
(I load the mpls4 module since system boots).
=20
- I configure PE1 and PE3 as LSRs by vtysh:
=20
> "mpls ldp"
> int eth1 (in each LSR): "mpls ip" and "mpls labelspace 0"
=20
- Then I hang a host at 12..0/24 to send packets to 13.1 through =
10..0/24.
=20
- RESULTS:
=20
> Those packets can't even arrive to their destination, cause the =
static routes that
I configured DISAPEAR. From vtysh (sh ip route) I see the new routes =
with their LABEL,=20
but from the command line (ip route) I just see the default routes =
at PE1 and PE3.
=20
> The NHLFE and ILM entries for that routes are created properly:
=20
NHLFE entry key 0x00000002 mtu 1496 propagate_ttl
push gen 10000 set eth1 ipv4 10.0.0.2 (0 bytes, 0 pkts)
=20
ILM entry label gen 10000 labelspace 0 proto ipv4
pop peek (0 bytes, 0 pkts)
=20
> So the problem is that with those entries the control component =
isn't able to change=20
the kernel routes.
=20
2=BA - I launch zebra and ospfd.=20
=20
- Then I configure ospf by vtysh: "router ospf" -> "network =
10.0.0.0/24 area 0" (PE1 and PE3)
-> "network 12.0.0.0/24 area 0" (PE3)
-> "network 13.0.0.0/24 area 0" (PE1)
=20
- After new routes are learned I close vtysh, launch ldpd and =
configure PE1 and PE3 as LSRs by vtysh:
=20
> "mpls ldp"
> int eth1 (in each LSR): "mpls ip" and "mpls labelspace 0"
=20
- Then I hang a host at 12..0/24 to send packets to 13.1 through =
10..0/24.
=20
- RESULTS:
=20
> Those packets arrive to their destination, but without a label. =
>From vtysh (sh ip route) I see the new ospf=20
routes with their hop count (not any label) and from the =
command line (ip route) I see the same routes learned by ospf.
=20
> The NHLFE and ILM entries for that routes are created properly:
=20
NHLFE entry key 0x00000002 mtu 1496 propagate_ttl
push gen 10000 set eth1 ipv4 10.0.0.2 (0 bytes, 0 pkts)
=20
ILM entry label gen 10000 labelspace 0 proto ipv4
pop peek (0 bytes, 0 pkts)
=20
> So the problem, again, is that with those entries the control =
component isn't able to change=20
the kernel routes.
=20
Any idea of what's happening? As I told you, if you could provide me =
some documentation for understanding how the code is organized, maybe I =
could help.
=20
Thanks for your time,
Gonzalo.
|
|
From: Julien B. <jul...@gm...> - 2007-03-12 20:09:36
|
Hi James, The latest version of iptables with mpls is impossible to compile or when I changed the code to compile it, "-j mpls" doesn't work anymore. The first problem is well-known from the iptables community because it's an incompatibility between the header of kernel 2.6.19. cc -O2 -Wall -Wunused -I/usr/src/kernel-mpls//include -Iinclude/ -DIPTABLES_VERSION=\"1.3.5\" -fPIC -o extensions/libipt_iprange_sh.o -c extensions/libipt_iprange.c In file included from extensions/libipt_iprange.c:9: /usr/src/kernel-mpls//include/linux/netfilter_ipv4/ipt_iprange.h:11: error: expected specifier-qualifier-list before '__be32' extensions/libipt_iprange.c: In function 'parse_iprange': extensions/libipt_iprange.c:43: error: 'struct ipt_iprange' has no member named 'min_ip' extensions/libipt_iprange.c:50: error: 'struct ipt_iprange' has no member named 'max_ip' extensions/libipt_iprange.c:52: error: 'struct ipt_iprange' has no member named 'max_ip' extensions/libipt_iprange.c:52: error: 'struct ipt_iprange' has no member named 'min_ip' extensions/libipt_iprange.c: In function 'print_iprange': extensions/libipt_iprange.c:117: error: 'const struct ipt_iprange' has no member named 'min_ip' extensions/libipt_iprange.c:118: error: 'const struct ipt_iprange' has no member named 'max_ip' make: *** [extensions/libipt_iprange_sh.o] Error 1 The previous error can be fixed : see here<http://lists.netfilter.org/pipermail/netfilter/2006-October/066947.html> The second error is more difficult to solve: I tried to compile it on two different computers and the error is the same : 1) cc -O2 -Wall -Wunused -I/usr/src/kernel-mpls//include -Iinclude/ -DIPTABLES_VERSION=\"1.3.5\" -fPIC -o extensions/libipt_mpls_sh.o -c extensions/libipt_mpls.c cc -shared -o extensions/libipt_mpls.so extensions/libipt_mpls_sh.o extensions/libipt_mpls_sh.o: In function `_init': libipt_mpls.c:(.text+0x10): multiple definition of `_init' /usr/lib/gcc/i686-pc-linux-gnu/4.1.1/../../../crti.o:/var/tmp/portage/glibc- 2.3.6-r5/work/build-default-i686-pc-linux-gnu-linuxthreads/csu/crti.S:12: first defined here collect2: ld returned 1 exit status make: *** [extensions/libipt_mpls.so] Error 1 2) cc -O2 -Wall -Wunused -I/sys/usr/src/kernel-mpls//include -Iinclude/ -DIPTABLES_VERSION=\"1.3.5\" -fPIC -o extensions/libipt_mpls_sh.o -c extensions/libipt_mpls.c cc -shared -o extensions/libipt_mpls.so extensions/libipt_mpls_sh.o extensions/libipt_mpls_sh.o: In function `_init': libipt_mpls.c:(.text+0x10): multiple definition of `_init' /usr/lib/gcc/i486-linux-gnu/4.1.2/../../../../lib/crti.o:/build/buildd/glibc- 2.3.6.ds1/build-tree/i386-libc/csu/crti.S:36: first defined here The problem comes from the declaration of the _init function! If I change the function _init to my_init the argument "-j mpls" doesn't work anymore. Could you please tell me how to fix this issue please? Thank you in advance, Julien -- -------------------------------------------- Julien BISCONTI <julien.bisconti(at)student.fundp.ac.be> M.Sc. student in Computer Science, University of Namur FUNDP, Belgium |
|
From: James R. L. <jl...@mi...> - 2007-03-09 13:59:20
|
You will need to run OSPF (or create static routes) before LDP will operate correctly. On Fri, Mar 09, 2007 at 12:41:37PM +0100, Sienes Rodr?guez Gonzalo wrote: > Hi: >=20 > This is what I tried. I launch only zebra and ldpd on both LSRs and I spe= cify the routes for PE1 to reach 13.1 and for PE2 to 12.1: >=20 > eth0 eth1 eth1 eth0 > 12.0.0.1-------PE1---------------------PE2-------13.0.0.1 > .1 10.0.0.0/24 .2 >=20 > As you could see the label 10000 is distributed correctly, but the routes= are created only in vtysh with that label. Although nhlfe and ilm are upda= ted, the mpls route doesn't appear. >=20 > Thanks in advance, >=20 > Gonzalo. >=20 > PE1 configuration: > ----------------------------------------------------------------------- >=20 > [root@PE1 ~]# ip route add 13.0.0.0/24 via 10.0.0.2 > [root@PE1 ~]# ip route > 10.0.0.0/24 dev eth1 proto kernel scope link src 10.0.0.1 > 12.0.0.0/24 dev eth0 proto kernel scope link src 12.0.0.1 > 13.0.0.0/24 via 10.0.0.2 dev eth1 > [root@PE1 ~]# zebra -d > [root@PE1 ~]# ldpd -d > [root@PE1 ~]# lsmod | grep mpls > mpls4 10240 0 > [root@PE1 ~]# ps -e | grep ze > 2724 ? 00:00:00 zebra > [root@PE1 ~]# ps -e | grep ldp > 2726 ? 00:00:00 ldpd > [root@PE1 ~]# vtysh >=20 > Hello, this is Quagga (version 0.99.6). > Copyright 1996-2005 Kunihiro Ishiguro, et al. >=20 > PE1# con t > PE1(config)# mpls ldp > PE1(config-ldp)# ex > PE1(config)# int eth1 > PE1(config-if)# mpls ip > PE1(config-if-ldp)# ex > PE1(config-if)# mpls labelsp 0 > Labelspace: 0 > PE1(config-if)# end > PE1# sh run > Building configuration... >=20 > Current configuration: > ! > hostname PE1 > hostname uml-1 > ! > password root > enable password root > ! > interface eth0 > ipv6 nd suppress-ra > ! > interface eth1 > ipv6 nd suppress-ra > mpls ip > mpls labelspace 0 > ! > interface lo > ! > interface sit0 > ipv6 nd suppress-ra > ! > mpls ldp > egress connected > ! > ip forwarding > ! > line vty > ! >=20 > PE1# sh ldp disc >=20 > Local LSR Identifier: 12.0.0.1 >=20 > Interface Discovery Sources: > eth1: xmit/recv > LDP Id: 10.0.0.2:0 >=20 > Targeted Discovery Sources: > No configured peers >=20 > PE1# sh ldp neig > Peer LDP Ident: 10.0.0.2:0; Local LDP Ident: 12.0.0.1:0 > TCP connection: 10.0.0.1.34306 - 10.0.0.2.39775 > State: OPERATIONAL; Msgs sent/recv: 12/35; UNSOLICITED > Up time: 00:01:53 > LDP discovery sources: > eth1 > Addresses bound to peer: > 10.0.0.2 13.0.0.1 >=20 >=20 > PE1# sh ldp ses > 4 10.0.0.2 45 OPERATIONAL > 10.0.0.2 > 13.0.0.1 >=20 > PE1# sh ip route > Codes: K - kernel route, C - connected, S - static, R - RIP, O - OSPF, > I - ISIS, B - BGP, > - selected route, * - FIB route >=20 > C>* 10.0.0.0/24 is directly connected, eth1 > C>* 12.0.0.0/24 is directly connected, eth0 > K> 13.0.0.0/24 via 10.0.0.2, eth1 (label 10000) > C>* 127.0.0.0/8 is directly connected, lo >=20 > PE1# ping 13.1 > connect: Network is unreachable >=20 > PE1# sh lpd ses > % Unknown command. > PE1# sh lpd ses > % Unknown command. > PE1# sh ldp dis >=20 > Local LSR Identifier: 10.0.0.1 >=20 > Interface Discovery Sources: > eth1: xmit/recv > LDP Id: 10.0.0.2:0 >=20 > Targeted Discovery Sources: > No configured peers >=20 > PE1# sh ldp neigh > Peer LDP Ident: 10.0.0.2:0; Local LDP Ident: 10.0.0.1:0 > TCP connection: 10.0.0.1.34306 - 10.0.0.2.34166 > State: OPERATIONAL; Msgs sent/recv: 26/77; UNSOLICITED > Up time: 00:05:28 > LDP discovery sources: > eth1 > Addresses bound to peer: > 10.0.0.2 13.0.0.1 >=20 >=20 > [root@PE1 ~]# mpls nhlfe > NHLFE entry key 0x00000002 mtu 1496 propagate_ttl > push gen 10000 set eth1 ipv4 10.0.0.2 (0 bytes, 0 pkts) > [root@PE1 ~]# mpls ilm > ILM entry label gen 10000 labelspace 0 proto ipv4 > pop peek (0 bytes, 0 pkts) >=20 > [root@PE1 ~]# ip route > 10.0.0.0/24 dev eth1 proto kernel scope link src 10.0.0.1 > 12.0.0.0/24 dev eth0 proto kernel scope link src 12.0.0.1 >=20 > [root@PE1 ~]# > [root@PE1 ~]# mpls nhlfe > NHLFE entry key 0x00000002 mtu 1496 propagate_ttl > push gen 10000 set eth1 ipv4 10.0.0.2 (0 bytes, 0 pkts) > [root@PE1 ~]# mpls ilm > ILM entry label gen 10000 labelspace 0 proto ipv4 > pop peek (0 bytes, 0 pkts) > [root@PE1 ~]# ip route > 10.0.0.0/24 dev eth1 proto kernel scope link src 10.0.0.1 > 12.0.0.0/24 dev eth0 proto kernel scope link src 12.0.0.1 > [root@PE1 ~]# >=20 > PE3 configuration: > ----------------------------------------------------------------------- >=20 > [root@PE3 ~]# ip route add 12.0.0.0/24 via 10.0.0.1 >=20 > [root@PE3 ~]# ip route > 10.0.0.0/24 dev eth1 proto kernel scope link src 10.0.0.2 > 12.0.0.0/24 via 10.0.0.1 dev eth1 > 13.0.0.0/24 dev eth0 proto kernel scope link src 13.0.0.1 >=20 > [root@PE3 ~]# zebra -d > [root@PE3 ~]# ldpd -d > [root@PE3 ~]# vtysh >=20 > Hello, this is Quagga (version 0.99.6). > Copyright 1996-2005 Kunihiro Ishiguro, et al. >=20 > PE3# con t > PE3(config)# mpls ldp > PE3(config-ldp)# ex > PE3(config)# int eth1 > PE3(config-if)# mpls ip > PE3(config-if-ldp)# ex > PE3(config-if)# mpls labelsp 0 > Labelspace: 0 > PE3(config-if)# end > PE3# sh run > Building configuration... >=20 > Current configuration: > ! > hostname PE3 > hostname uml-1 > ! > password root > enable password root > ! > interface eth0 > ipv6 nd suppress-ra > ! > interface eth1 > ipv6 nd suppress-ra > mpls ip > mpls labelspace 0 > ! > interface eth2 > ipv6 nd suppress-ra > ! > interface lo > ! > interface sit0 > ipv6 nd suppress-ra > ! > mpls ldp > egress connected > ! > ip forwarding > ! > line vty >=20 > PE3# sh ip route > Codes: K - kernel route, C - connected, S - static, R - RIP, O - OSPF, > I - ISIS, B - BGP, > - selected route, * - FIB route >=20 > C>* 10.0.0.0/24 is directly connected, eth1 > K> 12.0.0.0/24 via 10.0.0.1, eth1 (label 10000) > C>* 13.0.0.0/24 is directly connected, eth0 > C>* 127.0.0.0/8 is directly connected, lo > K>* 169.254.0.0/16 is directly connected, eth1 > PE3# ping 12.1 > connect: Network is unreachable >=20 > PE3# sh ldp ses > 3 8.162.7.240 45 OPERATIONAL > 10.0.0.1 > 12.0.0.1 > PE3# sh ldp disc >=20 > Local LSR Identifier: 10.0.0.2 >=20 > Interface Discovery Sources: > eth1: xmit/recv > LDP Id: 10.0.0.1:0 >=20 > Targeted Discovery Sources: > No configured peers >=20 > PE3# sh ldp neigh > Peer LDP Ident: 10.0.0.1:0; Local LDP Ident: 10.0.0.2:0 > TCP connection: 10.0.0.2.30341 - 10.0.0.1.646 > State: OPERATIONAL; Msgs sent/recv: 21/62; UNSOLICITED > Up time: 00:04:06 > LDP discovery sources: > eth1 > Addresses bound to peer: > 10.0.0.1 12.0.0.1 >=20 >=20 > [root@PE3 ~]# ip route > 10.0.0.0/24 dev eth1 proto kernel scope link src 10.0.0.2 > 13.0.0.0/24 dev eth0 proto kernel scope link src 13.0.0.1 >=20 > [root@PE3 ~]# mpls nhlfe > NHLFE entry key 0x00000002 mtu 1496 propagate_ttl > push gen 10000 set eth1 ipv4 10.0.0.1 (0 bytes, 0 pkts) > [root@PE3 ~]# mpls ilm > ILM entry label gen 10000 labelspace 0 proto ipv4 > pop peek (0 bytes, 0 pkts) >=20 >=20 --=20 James R. Leu jl...@mi... |
|
From: <gsr...@al...> - 2007-03-09 11:44:46
|
Hi:
This is what I tried. I launch only zebra and ldpd on both LSRs and I =
specify the routes for PE1 to reach 13.1 and for PE2 to 12.1:
eth0 eth1 eth1 eth0
12.0.0.1-------PE1---------------------PE2-------13.0.0.1
.1 10.0.0.0/24 .2
As you could see the label 10000 is distributed correctly, but the =
routes are created only in vtysh with that label. Although nhlfe and ilm =
are updated, the mpls route doesn't appear.
Thanks in advance,
Gonzalo.
PE1 configuration:
-----------------------------------------------------------------------
[root@PE1 ~]# ip route add 13.0.0.0/24 via 10.0.0.2
[root@PE1 ~]# ip route
10.0.0.0/24 dev eth1 proto kernel scope link src 10.0.0.1
12.0.0.0/24 dev eth0 proto kernel scope link src 12.0.0.1
13.0.0.0/24 via 10.0.0.2 dev eth1
[root@PE1 ~]# zebra -d
[root@PE1 ~]# ldpd -d
[root@PE1 ~]# lsmod | grep mpls
mpls4 10240 0
[root@PE1 ~]# ps -e | grep ze
2724 ? 00:00:00 zebra
[root@PE1 ~]# ps -e | grep ldp
2726 ? 00:00:00 ldpd
[root@PE1 ~]# vtysh
Hello, this is Quagga (version 0.99.6).
Copyright 1996-2005 Kunihiro Ishiguro, et al.
PE1# con t
PE1(config)# mpls ldp
PE1(config-ldp)# ex
PE1(config)# int eth1
PE1(config-if)# mpls ip
PE1(config-if-ldp)# ex
PE1(config-if)# mpls labelsp 0
Labelspace: 0
PE1(config-if)# end
PE1# sh run
Building configuration...
Current configuration:
!
hostname PE1
hostname uml-1
!
password root
enable password root
!
interface eth0
ipv6 nd suppress-ra
!
interface eth1
ipv6 nd suppress-ra
mpls ip
mpls labelspace 0
!
interface lo
!
interface sit0
ipv6 nd suppress-ra
!
mpls ldp
egress connected
!
ip forwarding
!
line vty
!
PE1# sh ldp disc
Local LSR Identifier: 12.0.0.1
Interface Discovery Sources:
eth1: xmit/recv
LDP Id: 10.0.0.2:0
Targeted Discovery Sources:
No configured peers
PE1# sh ldp neig
Peer LDP Ident: 10.0.0.2:0; Local LDP Ident: 12.0.0.1:0
TCP connection: 10.0.0.1.34306 - 10.0.0.2.39775
State: OPERATIONAL; Msgs sent/recv: 12/35; UNSOLICITED
Up time: 00:01:53
LDP discovery sources:
eth1
Addresses bound to peer:
10.0.0.2 13.0.0.1
PE1# sh ldp ses
4 10.0.0.2 45 OPERATIONAL
10.0.0.2
13.0.0.1
PE1# sh ip route
Codes: K - kernel route, C - connected, S - static, R - RIP, O - OSPF,
I - ISIS, B - BGP, > - selected route, * - FIB route
C>* 10.0.0.0/24 is directly connected, eth1
C>* 12.0.0.0/24 is directly connected, eth0
K> 13.0.0.0/24 via 10.0.0.2, eth1 (label 10000)
C>* 127.0.0.0/8 is directly connected, lo
PE1# ping 13.1
connect: Network is unreachable
PE1# sh lpd ses
% Unknown command.
PE1# sh lpd ses
% Unknown command.
PE1# sh ldp dis
Local LSR Identifier: 10.0.0.1
Interface Discovery Sources:
eth1: xmit/recv
LDP Id: 10.0.0.2:0
Targeted Discovery Sources:
No configured peers
PE1# sh ldp neigh
Peer LDP Ident: 10.0.0.2:0; Local LDP Ident: 10.0.0.1:0
TCP connection: 10.0.0.1.34306 - 10.0.0.2.34166
State: OPERATIONAL; Msgs sent/recv: 26/77; UNSOLICITED
Up time: 00:05:28
LDP discovery sources:
eth1
Addresses bound to peer:
10.0.0.2 13.0.0.1
[root@PE1 ~]# mpls nhlfe
NHLFE entry key 0x00000002 mtu 1496 propagate_ttl
push gen 10000 set eth1 ipv4 10.0.0.2 (0 bytes, 0 pkts)
[root@PE1 ~]# mpls ilm
ILM entry label gen 10000 labelspace 0 proto ipv4
pop peek (0 bytes, 0 pkts)
[root@PE1 ~]# ip route
10.0.0.0/24 dev eth1 proto kernel scope link src 10.0.0.1
12.0.0.0/24 dev eth0 proto kernel scope link src 12.0.0.1
[root@PE1 ~]#
[root@PE1 ~]# mpls nhlfe
NHLFE entry key 0x00000002 mtu 1496 propagate_ttl
push gen 10000 set eth1 ipv4 10.0.0.2 (0 bytes, 0 pkts)
[root@PE1 ~]# mpls ilm
ILM entry label gen 10000 labelspace 0 proto ipv4
pop peek (0 bytes, 0 pkts)
[root@PE1 ~]# ip route
10.0.0.0/24 dev eth1 proto kernel scope link src 10.0.0.1
12.0.0.0/24 dev eth0 proto kernel scope link src 12.0.0.1
[root@PE1 ~]#
PE3 configuration:
-----------------------------------------------------------------------
[root@PE3 ~]# ip route add 12.0.0.0/24 via 10.0.0.1
[root@PE3 ~]# ip route
10.0.0.0/24 dev eth1 proto kernel scope link src 10.0.0.2
12.0.0.0/24 via 10.0.0.1 dev eth1
13.0.0.0/24 dev eth0 proto kernel scope link src 13.0.0.1
[root@PE3 ~]# zebra -d
[root@PE3 ~]# ldpd -d
[root@PE3 ~]# vtysh
Hello, this is Quagga (version 0.99.6).
Copyright 1996-2005 Kunihiro Ishiguro, et al.
PE3# con t
PE3(config)# mpls ldp
PE3(config-ldp)# ex
PE3(config)# int eth1
PE3(config-if)# mpls ip
PE3(config-if-ldp)# ex
PE3(config-if)# mpls labelsp 0
Labelspace: 0
PE3(config-if)# end
PE3# sh run
Building configuration...
Current configuration:
!
hostname PE3
hostname uml-1
!
password root
enable password root
!
interface eth0
ipv6 nd suppress-ra
!
interface eth1
ipv6 nd suppress-ra
mpls ip
mpls labelspace 0
!
interface eth2
ipv6 nd suppress-ra
!
interface lo
!
interface sit0
ipv6 nd suppress-ra
!
mpls ldp
egress connected
!
ip forwarding
!
line vty
PE3# sh ip route
Codes: K - kernel route, C - connected, S - static, R - RIP, O - OSPF,
I - ISIS, B - BGP, > - selected route, * - FIB route
C>* 10.0.0.0/24 is directly connected, eth1
K> 12.0.0.0/24 via 10.0.0.1, eth1 (label 10000)
C>* 13.0.0.0/24 is directly connected, eth0
C>* 127.0.0.0/8 is directly connected, lo
K>* 169.254.0.0/16 is directly connected, eth1
PE3# ping 12.1
connect: Network is unreachable
PE3# sh ldp ses
3 8.162.7.240 45 OPERATIONAL
10.0.0.1
12.0.0.1
PE3# sh ldp disc
Local LSR Identifier: 10.0.0.2
Interface Discovery Sources:
eth1: xmit/recv
LDP Id: 10.0.0.1:0
Targeted Discovery Sources:
No configured peers
PE3# sh ldp neigh
Peer LDP Ident: 10.0.0.1:0; Local LDP Ident: 10.0.0.2:0
TCP connection: 10.0.0.2.30341 - 10.0.0.1.646
State: OPERATIONAL; Msgs sent/recv: 21/62; UNSOLICITED
Up time: 00:04:06
LDP discovery sources:
eth1
Addresses bound to peer:
10.0.0.1 12.0.0.1
[root@PE3 ~]# ip route
10.0.0.0/24 dev eth1 proto kernel scope link src 10.0.0.2
13.0.0.0/24 dev eth0 proto kernel scope link src 13.0.0.1
[root@PE3 ~]# mpls nhlfe
NHLFE entry key 0x00000002 mtu 1496 propagate_ttl
push gen 10000 set eth1 ipv4 10.0.0.1 (0 bytes, 0 pkts)
[root@PE3 ~]# mpls ilm
ILM entry label gen 10000 labelspace 0 proto ipv4
pop peek (0 bytes, 0 pkts)
|
|
From: James R. L. <jl...@mi...> - 2007-03-09 05:08:06
|
Please include the output of: sho ip route from vtysh and: ip route show from the command line. On Thu, Mar 08, 2007 at 12:20:43PM +0100, Sienes Rodr?guez Gonzalo wrote: > Hi James! >=20 > I've just installed FC5 and all the MPLS-Linux-1.955 RPMs for this OS: >=20 > [root@PE1 ~]# rpm -qa | grep mpls | sort > ebtables-2.0.8-0.6.rc2.fc5.mpls.1.955 > glibc-kernheaders-3.0-5.2.fc5.mpls.1.955 > iproute-2.6.16-1.fc5.mpls.1.955 > iptables-1.3.5-1.2.fc5.mpls.1.955 > kernel-devel-2.6.18-1.2257.fc5.mpls.1.955 > kernel-smp-2.6.18-1.2257.fc5.mpls.1.955 > kernel-smp-devel-2.6.18-1.2257.fc5.mpls.1.955 > quagga-0.99.6-01.fc5.mpls.1.955 >=20 > [root@PE1 ~]# lsmod | grep mpls > mpls4 10240 0 >=20 > I try a simple environment with 2 LSRs: > =20 > eth0 eth1 eth1 eth0 > 12.0.0.1-------PE1---------------------PE2-------172.29.17.60 > .1 10.0.0.0/24 .2 >=20 > This is the configuration I made on PE1 by vtysh: >=20 > PE1# sh run > Building configuration... >=20 > Current configuration: > ! > hostname PE1 > ! > password root > enable password root > ! > interface eth0 > ipv6 nd suppress-ra > ! > interface eth1 > ipv6 nd suppress-ra > mpls ip > mpls labelspace 0 > ! > interface lo > ! > interface sit0 > ipv6 nd suppress-ra > ! > mpls ldp > egress connected > ! > ip forwarding > ! > line vty > ! >=20 > And the outputs of the commands relative to LDP: >=20 > PE1# sh ldp > LSR-ID: 12.0.0.1 Admin State: ENABLED > Transport Address: 0.0.0.0 > Control Mode: ORDERED Repair Mode: GLOBAL > Propogate Release: TRUE Label Merge: TRUE > Retention Mode: LIBERAL Loop Detection Mode: NONE > TTL-less-domain: FALSE > Local TCP Port: 646 Local UDP Port: 646 > Keep-alive Time: 45 Keep-alive Interval: 15 > Hello Time: 15 Hello Interval: 5 >=20 > PE1# sh ldp data > 10.0.0.0/24 local binding: label: gen 10002 > 10.0.0.0/24 remote binding: no outlabel lsr: 10.0.0.2:0 > 172.29.16.0/22 remote binding: no outlabel lsr: 10.0.0.2:0 > PE1# sh ldp dis >=20 > Local LSR Identifier: 12.0.0.1 >=20 > Interface Discovery Sources: > eth1: xmit/recv > LDP Id: 10.0.0.2:0 >=20 > Targeted Discovery Sources: > No configured peers >=20 > PE1# sh ldp fec > FEC: 1 10.0.0.0/24 > 1 0.0.0.0 1 > FEC: 4 172.29.16.0/22 >=20 > PE1# sh ldp neigh > Peer LDP Ident: 10.0.0.2:0; Local LDP Ident: 12.0.0.1:0 > TCP connection: 10.0.0.1.34306 - 10.0.0.2.36479 > State: OPERATIONAL; Msgs sent/recv: 63/191; UNSOLICITED > Up time: 00:14:38 > LDP discovery sources: > eth1 > Addresses bound to peer: > 172.29.17.60 10.0.0.2 >=20 > PE1# sh ldp ses > 4 10.0.0.2 45 OPERATIONAL > 172.29.17.60 > 10.0.0.2 >=20 > PE1# sh mpls har > MPLS-Linux: 1.955 netlink control >=20 > [root@PE1 ~]# mpls nhlfe > [root@PE1 ~]# mpls ilm > ILM entry label gen 10002 labelspace 0 proto ipv4 > pop peek (0 bytes, 0 pkts) >=20 > What I want to do is to send labelled packets while they are crossing 10.= 0.0.0/24. The problem is that LDP doesn't associate the labels that are dis= covered to the routes. >=20 > Where could I look at? >=20 > Thanks, >=20 > Gonzalo. >=20 > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share y= our > opinions on IT & business topics through brief surveys-and earn cash > http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3D= DEVDEV > _______________________________________________ > mpls-linux-devel mailing list > mpl...@li... > https://lists.sourceforge.net/lists/listinfo/mpls-linux-devel --=20 James R. Leu jl...@mi... |
|
From: <gsr...@al...> - 2007-03-08 11:24:16
|
Hi James!
I've just installed FC5 and all the MPLS-Linux-1.955 RPMs for this OS:
[root@PE1 ~]# rpm -qa | grep mpls | sort
ebtables-2.0.8-0.6.rc2.fc5.mpls.1.955
glibc-kernheaders-3.0-5.2.fc5.mpls.1.955
iproute-2.6.16-1.fc5.mpls.1.955
iptables-1.3.5-1.2.fc5.mpls.1.955
kernel-devel-2.6.18-1.2257.fc5.mpls.1.955
kernel-smp-2.6.18-1.2257.fc5.mpls.1.955
kernel-smp-devel-2.6.18-1.2257.fc5.mpls.1.955
quagga-0.99.6-01.fc5.mpls.1.955
[root@PE1 ~]# lsmod | grep mpls
mpls4 10240 0
I try a simple environment with 2 LSRs:
=20
eth0 eth1 eth1 eth0
12.0.0.1-------PE1---------------------PE2-------172.29.17.60
.1 10.0.0.0/24 .2
This is the configuration I made on PE1 by vtysh:
PE1# sh run
Building configuration...
Current configuration:
!
hostname PE1
!
password root
enable password root
!
interface eth0
ipv6 nd suppress-ra
!
interface eth1
ipv6 nd suppress-ra
mpls ip
mpls labelspace 0
!
interface lo
!
interface sit0
ipv6 nd suppress-ra
!
mpls ldp
egress connected
!
ip forwarding
!
line vty
!
And the outputs of the commands relative to LDP:
PE1# sh ldp
LSR-ID: 12.0.0.1 Admin State: ENABLED
Transport Address: 0.0.0.0
Control Mode: ORDERED Repair Mode: GLOBAL
Propogate Release: TRUE Label Merge: TRUE
Retention Mode: LIBERAL Loop Detection Mode: NONE
TTL-less-domain: FALSE
Local TCP Port: 646 Local UDP Port: 646
Keep-alive Time: 45 Keep-alive Interval: 15
Hello Time: 15 Hello Interval: 5
PE1# sh ldp data
10.0.0.0/24 local binding: label: gen 10002
10.0.0.0/24 remote binding: no outlabel lsr: 10.0.0.2:0
172.29.16.0/22 remote binding: no outlabel lsr: 10.0.0.2:0
PE1# sh ldp dis
Local LSR Identifier: 12.0.0.1
Interface Discovery Sources:
eth1: xmit/recv
LDP Id: 10.0.0.2:0
Targeted Discovery Sources:
No configured peers
PE1# sh ldp fec
FEC: 1 10.0.0.0/24
1 0.0.0.0 1
FEC: 4 172.29.16.0/22
PE1# sh ldp neigh
Peer LDP Ident: 10.0.0.2:0; Local LDP Ident: 12.0.0.1:0
TCP connection: 10.0.0.1.34306 - 10.0.0.2.36479
State: OPERATIONAL; Msgs sent/recv: 63/191; UNSOLICITED
Up time: 00:14:38
LDP discovery sources:
eth1
Addresses bound to peer:
172.29.17.60 10.0.0.2
PE1# sh ldp ses
4 10.0.0.2 45 OPERATIONAL
172.29.17.60
10.0.0.2
PE1# sh mpls har
MPLS-Linux: 1.955 netlink control
[root@PE1 ~]# mpls nhlfe
[root@PE1 ~]# mpls ilm
ILM entry label gen 10002 labelspace 0 proto ipv4
pop peek (0 bytes, 0 pkts)
What I want to do is to send labelled packets while they are crossing =
10.0.0.0/24. The problem is that LDP doesn't associate the labels that =
are discovered to the routes.
Where could I look at?
Thanks,
Gonzalo.
|
|
From: prachi g. <pra...@gm...> - 2007-03-05 14:58:02
|
We have to provide point to multipoint multicast as an extension to existing LDP http://tools.ietf.org/wg/mpls/draft-ietf-mpls-ldp-p2mp/draft-ietf-mpls-ldp-p2mp-01.txt --Label Distribution Protocol Extensions for Point-to-Multipoint and Multipoint-to-Multipoint Label Switched Paths. . since we are using zMPLS(zMPLS supports LDP) we would like to know how to debug the existing code...can we insert ' printf ()' statements in code...??? also where will the output of such statements be logged... since most of the code is based on zebra routing software....... we would also like to know how we can understand the exact flow of code as in which functions get called when..we have studied the code for zMPLS but some suggestions on this would be of great help.. thank you, regards, Prachi |
|
From: James R. L. <jl...@mi...> - 2007-03-04 04:15:46
|
I'm glad to hear you got ldpd up and running. On Sat, Mar 03, 2007 at 12:28:37PM +0100, Marco Schmidt wrote: > Hello, >=20 > the problem was solved by deleting the "mpls ip"-commands in ldpd.conf. > Ldpd neither started without specifying a conf file, nor by just > typing ldpd. Notwithstanding, ldpd.conf seems to be accessed. I think this behavior is inline with the rest of the quagga daemons. If you think there is something that needs to change, please let me know and I'll look into it. > Thanks to your advice, ldpd is running. Now, I've got to spend some time > on vtysh ;-) Please let me know if you find any unexpected behaviors. I'm determined to get ldpd working reliably. >=20 > Marco >=20 >=20 > > Hello, >=20 > > I had the same problem months ago. Just try to start the ldpd daemon=20 > > *without* specifying any config file. >=20 > > [root@localhost ~]# ldpd -d -A 127.0.0.1 >=20 > > I configured everything with the vtysh interface. > > Just enter the command "vtysh" and then configure the ldpd daemon. > > Eventually, you can save the current configuration to a file. (I think > > it's the "write" command, I'm not sure.) >=20 > > The error makes sense, maybe the interface configuration wasn't=20 > > correctly made or maybe the syntax of the ldpd.conf isn't respected. > > I don't really know where this come from. > > But I'm pretty sure you will solve this problem by configuring=20 > > everything by vtysh. >=20 > > Regards, >=20 > > Julien >=20 >=20 >=20 > > Marco Schmidt wrote: > >> Hello everybody, > >> > >> i recently upgraded my PCs from from FC4 (with MPLS 1.950) to > >> FC5 with all needed RPMs for v1.955 from Sourceforge including > >> quagga-0.99.6-01.fc5.mpls.1.955.i386.rpm-package. A few PCs were upgra= ded > >> through yum, others through fresh installations as well. > >> > >> My problem in short: Following the instructions in README.quagga-mpls > >> of LDP-Portable 0.900 leads to the point where to start the ldpd > >> daemon - the following error message appears: > >> > >> [root@localhost ~]# ldpd -d -A 127.0.0.1 -f /etc/quagga/ldpd.conf > >> ldpd: ldp_interface.c:59: ldp_interface_create2: Assertion `li->iff.in= dex' failed. > >> > >> Did I forget something? I didn't compile anything or am I supposed to > >> do so? The same message appears if I only type ldpd... > >> Zebra and OSPF daemons work fine, I've also entered the "often forgott= en" > >> modprobe mpls4 - otherwise zebra won't start. All 3 .conf files for th= e daemons > >> in etc/quagga/ are present and customized. > >> > >> -- > >> Best Regards > >> Marco Schmidt > >> mailto:sm...@hr... > >> > >> > >> ----------------------------------------------------------------------= --- > >> Take Surveys. Earn Cash. Influence the Future of IT > >> Join SourceForge.net's Techsay panel and you'll get the chance to shar= e your > >> opinions on IT & business topics through brief surveys-and earn cash > >> http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID= =3DDEVDEV > >> _______________________________________________ > >> mpls-linux-devel mailing list > >> mpl...@li... > >> https://lists.sourceforge.net/lists/listinfo/mpls-linux-devel > >> > >> >=20 >=20 >=20 > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share y= our > opinions on IT & business topics through brief surveys-and earn cash > http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3D= DEVDEV > _______________________________________________ > mpls-linux-devel mailing list > mpl...@li... > https://lists.sourceforge.net/lists/listinfo/mpls-linux-devel --=20 James R. Leu jl...@mi... |
|
From: Marco S. <mar...@s2...> - 2007-03-03 11:29:13
|
Hello, the problem was solved by deleting the "mpls ip"-commands in ldpd.conf. Ldpd neither started without specifying a conf file, nor by just typing ldpd. Notwithstanding, ldpd.conf seems to be accessed. Thanks to your advice, ldpd is running. Now, I've got to spend some time on vtysh ;-) Marco > Hello, > I had the same problem months ago. Just try to start the ldpd daemon > *without* specifying any config file. > [root@localhost ~]# ldpd -d -A 127.0.0.1 > I configured everything with the vtysh interface. > Just enter the command "vtysh" and then configure the ldpd daemon. > Eventually, you can save the current configuration to a file. (I think > it's the "write" command, I'm not sure.) > The error makes sense, maybe the interface configuration wasn't > correctly made or maybe the syntax of the ldpd.conf isn't respected. > I don't really know where this come from. > But I'm pretty sure you will solve this problem by configuring > everything by vtysh. > Regards, > Julien > Marco Schmidt wrote: >> Hello everybody, >> >> i recently upgraded my PCs from from FC4 (with MPLS 1.950) to >> FC5 with all needed RPMs for v1.955 from Sourceforge including >> quagga-0.99.6-01.fc5.mpls.1.955.i386.rpm-package. A few PCs were upgraded >> through yum, others through fresh installations as well. >> >> My problem in short: Following the instructions in README.quagga-mpls >> of LDP-Portable 0.900 leads to the point where to start the ldpd >> daemon - the following error message appears: >> >> [root@localhost ~]# ldpd -d -A 127.0.0.1 -f /etc/quagga/ldpd.conf >> ldpd: ldp_interface.c:59: ldp_interface_create2: Assertion `li->iff.index' failed. >> >> Did I forget something? I didn't compile anything or am I supposed to >> do so? The same message appears if I only type ldpd... >> Zebra and OSPF daemons work fine, I've also entered the "often forgotten" >> modprobe mpls4 - otherwise zebra won't start. All 3 .conf files for the daemons >> in etc/quagga/ are present and customized. >> >> -- >> Best Regards >> Marco Schmidt >> mailto:sm...@hr... >> >> >> ------------------------------------------------------------------------- >> Take Surveys. Earn Cash. Influence the Future of IT >> Join SourceForge.net's Techsay panel and you'll get the chance to share your >> opinions on IT & business topics through brief surveys-and earn cash >> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV >> _______________________________________________ >> mpls-linux-devel mailing list >> mpl...@li... >> https://lists.sourceforge.net/lists/listinfo/mpls-linux-devel >> >> |
|
From: Julien B. <jul...@gm...> - 2007-03-02 19:09:52
|
Hello, I had the same problem months ago. Just try to start the ldpd daemon *without* specifying any config file. [root@localhost ~]# ldpd -d -A 127.0.0.1 I configured everything with the vtysh interface. Just enter the command "vtysh" and then configure the ldpd daemon. Eventually, you can save the current configuration to a file. (I think it's the "write" command, I'm not sure.) The error makes sense, maybe the interface configuration wasn't correctly made or maybe the syntax of the ldpd.conf isn't respected. I don't really know where this come from. But I'm pretty sure you will solve this problem by configuring everything by vtysh. Regards, Julien Marco Schmidt wrote: > Hello everybody, > > i recently upgraded my PCs from from FC4 (with MPLS 1.950) to > FC5 with all needed RPMs for v1.955 from Sourceforge including > quagga-0.99.6-01.fc5.mpls.1.955.i386.rpm-package. A few PCs were upgraded > through yum, others through fresh installations as well. > > My problem in short: Following the instructions in README.quagga-mpls > of LDP-Portable 0.900 leads to the point where to start the ldpd > daemon - the following error message appears: > > [root@localhost ~]# ldpd -d -A 127.0.0.1 -f /etc/quagga/ldpd.conf > ldpd: ldp_interface.c:59: ldp_interface_create2: Assertion `li->iff.index' failed. > > Did I forget something? I didn't compile anything or am I supposed to > do so? The same message appears if I only type ldpd... > Zebra and OSPF daemons work fine, I've also entered the "often forgotten" > modprobe mpls4 - otherwise zebra won't start. All 3 .conf files for the daemons > in etc/quagga/ are present and customized. > > -- > Best Regards > Marco Schmidt > mailto:sm...@hr... > > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share your > opinions on IT & business topics through brief surveys-and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > mpls-linux-devel mailing list > mpl...@li... > https://lists.sourceforge.net/lists/listinfo/mpls-linux-devel > > -- -------------------------------------------- Julien BISCONTI <jul...@st...> M.Sc. student in Computer Science, University of Namur FUNDP, Belgium |
|
From: Marco S. <mar...@s2...> - 2007-03-02 18:45:14
|
Hello everybody, i recently upgraded my PCs from from FC4 (with MPLS 1.950) to FC5 with all needed RPMs for v1.955 from Sourceforge including quagga-0.99.6-01.fc5.mpls.1.955.i386.rpm-package. A few PCs were upgraded through yum, others through fresh installations as well. My problem in short: Following the instructions in README.quagga-mpls of LDP-Portable 0.900 leads to the point where to start the ldpd daemon - the following error message appears: [root@localhost ~]# ldpd -d -A 127.0.0.1 -f /etc/quagga/ldpd.conf ldpd: ldp_interface.c:59: ldp_interface_create2: Assertion `li->iff.index' failed. Did I forget something? I didn't compile anything or am I supposed to do so? The same message appears if I only type ldpd... Zebra and OSPF daemons work fine, I've also entered the "often forgotten" modprobe mpls4 - otherwise zebra won't start. All 3 .conf files for the daemons in etc/quagga/ are present and customized. -- Best Regards Marco Schmidt mailto:sm...@hr... |
|
From: James R. L. <jl...@mi...> - 2007-03-02 14:50:03
|
I usually see this behavior if I've forgotten to load the mpls4 module. Did you do a 'modprobe mpls4' before starting ldpd? On Fri, Mar 02, 2007 at 11:03:38AM +0100, Sienes Rodr?guez Gonzalo wrote: > Hi James: >=20 > As you could see the enviroment is the same as yours: >=20 > [root@PE3 mpls-linux-1.955-FC4]# md5sum quagga-0.99.6-01.fc4.mpls.1.955.i= 386.rpm2187b703d908784b2c03d836086fc607 quagga-0.99.6-01.fc4.mpls.1.955.i3= 86.rpm > [root@PE3 mpls-linux-1.955-FC4]# rpm -qa | grep quagga > quagga-0.99.6-01.fc4.mpls.1.955 > [root@PE3 mpls-linux-1.955-FC4]# more /etc/fedora-release > Fedora Core release 4 (Stentz) > [root@PE3 mpls-linux-1.955-FC4]# zebra -d > [root@PE3 mpls-linux-1.955-FC4]# ospfd -d > [root@PE3 mpls-linux-1.955-FC4]# ldpd -d > [root@PE3 mpls-linux-1.955-FC4]# vtysh >=20 > Hello, this is Quagga (version 0.99.6). > Copyright 1996-2005 Kunihiro Ishiguro, et al. >=20 > PE3# con t > PE3(config)# mpls ldp > PE3(config-ldp)# exit > PE3(config)# int eth1 > PE3(config-if)# mpls ip > PE3(config-if-ldp)# end >=20 > PE3# sh ldp disc >=20 > Local LSR Identifier: 10.0.0.2 >=20 > Interface Discovery Sources: > eth1: xmit >=20 > Targeted Discovery Sources: > No configured peers >=20 > PE3# con t > PE3(config)# int eth1 > PE3(config-if)# mpls labelsp 0 > Labelspace: 0 > PE3(config-if)# end >=20 > The problem is that I'm not able to create an LDP session between to LSRs= , while I'm trying to configure the second of them I always get an I/O erro= r, then the ldpd daemon is closed. >=20 > I'm going to try it in FC5, with last RPMs from Source Forge. >=20 > Thanks for your time, > Gonzalo. >=20 > -----Mensaje original----- > De: James R. Leu [mailto:jl...@mi...] > Enviado el: jue 01/03/2007 4:24 > Para: Sienes Rodr?guez Gonzalo > CC: mpl...@li... > Asunto: Re: [mpls-linux-devel] New MPLS-Linux code > =20 > On Wed, Feb 28, 2007 at 10:56:10AM +0100, Sienes Rodr?guez Gonzalo wrote: > > Hi again: > >=20 > > I have configured a simple scenario. And the result, is that I'm able t= o create mpls segments from vtysh. In the sender I type: ip route 12.0.0.1 = gen 222 nexthop eth1 10.0.0.1, and in the receiver: mpls static 0 -> label-= map gen 222 pop. With ping from sender to 12.1 I can see that the ICMP pack= ets are labelled. Also I can see the new mpls segment created by mpls nhlfe= show and mpls ilm show. > > So the problem must be at configuring LDP, as I told you in the "runnin= g config" doesn't appear mpls ip (at the required interface) or the general= command mpls ldp. >=20 > I built a FC4 chroot environment and installed the quagga-mpls FC4 rpms > inside of it and launched zebra/ldpd/ospfd. Using vtysh I can able to > configure: >=20 > -bash-3.00# md5sum quagga-0.99.6-01.fc4.mpls.1.955.i386.rpm=20 > 2187b703d908784b2c03d836086fc607 quagga-0.99.6-01.fc4.mpls.1.955.i386.rpm > -bash-3.00# rpm -qa | grep quagga > quagga-0.99.6-01.fc4.mpls.1.955 > -bash-3.00# more /etc/fedora-release=20 > Fedora Core release 4 (Stentz) > -bash-3.00# vtysh >=20 > Hello, this is Quagga (version 0.99.6). > Copyright 1996-2005 Kunihiro Ishiguro, et al. >=20 > koko# conf t > koko(config)# mpls ldp=20 > koko(config-ldp)# exit > koko(config-ldp)# exit > koko(config-if)# mpls ip > koko(config-if-ldp)# end > koko# sho ldp discovery=20 >=20 > Local LSR Identifier: 192.168.1.16 >=20 > Interface Discovery Sources: > eth0: xmit >=20 > Targeted Discovery Sources: > No configured peers >=20 > koko#=20 >=20 > Please verify which version of the RPM you have installed, which=20 > vtysh your running and include the commands your using for starting > the processes. >=20 > Here is what I did to get it up and running after installing the RPM: >=20 > echo "hostname "`hostname -s` > /etc/quagga/zebra.conf > echo "hostname "`hostname -s` > /etc/quagga/ospfd.conf > echo "hostname "`hostname -s` > /etc/quagga/ldpd.conf > chown quagga.quagga /etc/quagga/zebra.conf /etc/quagga/ospfd.conf /etc/qu= agga/ldpd.conf > service zebra start > service ospfd start > service ldpd start > vtysh >=20 > > Thanks, > > Gonzalo > >=20 > >=20 > > -----Mensaje original----- > > De: James R. Leu [mailto:jl...@mi...] > > Enviado el: lun 26/02/2007 15:08 > > Para: Sienes Rodr?guez Gonzalo > > CC: mpl...@li... > > Asunto: Re: [mpls-linux-devel] New MPLS-Linux code > > =20 > > On Mon, Feb 26, 2007 at 11:32:15AM +0100, Sienes Rodr?guez Gonzalo wrot= e: > > > Hi James! > > >=20 > > > I've installed the revised RPMs for FC4. I got kernel panic after reb= ooting the system that I solved by typing "enforcing=3D0" at grub.conf. I h= ave some problems with the wheel of the mouse or the USB ports but in gener= al it works right. I'm able to create MPLS static configurations. In this v= ersion the "mpls" module has disappeared so I only load "mpls4". I launch z= ebra, ospfd and ldpd but I make the whole configuration by vtysh. OSPF work= s well but I can't put most of the ldpd commands, in fact, the only one tha= t appears with "show running-config" is "mpls labelspace 0" in the correspo= nding interface, Neither "mpls ldp" nor "mpls ip". Are these problems solve= d in FC5? If that's it I would like to work with FC5. > >=20 > > Can you manually create MPLS segments with the 'mpls' command? > > I'll look into the issue with no ldp command in vtysh. > >=20 > > > Thanks, > > >=20 > > > Gonzalo. > > >=20 > > > I updated the FC4 kernel RPMs. Can you please try them? > > >=20 > > > On Mon, Feb 19, 2007 at 11:47:24AM +0100, Sienes Rodr?guez Gonzalo wr= ote: > > > > Hi James: > > > >=20 > > > > I'm trying to install your new software for FC4 but I have some pro= blems. > > > > When I try to install the kernel-2.6.18 from Source Forge for FC4 i= t makes me install lots of RPMs, most of them can be installed by "yum upda= te" but I can't find the libraries libc.so.6(GLIBC_2.4) and libpcap.so.0.9.= 3 anywhere for FC4. I search for them and people talks about 64 architectur= e and I'm working with Intel(R) Pentium(R) D CPU 3.00GHz. Could you provide= them to me? Witch OS are you using? Should I install FC5? =20 > > > >=20 > > > > Thanks in advance. > > > >=20 > > > > P.D.: These are the outputs I get. > > > >=20 > > > > [root@PE3 mpls-linux-1.955]# rpm -ivh kernel-2.6.18-1.2257.fc4.mpls= .1.955.i686.rpm > > > > error: Failed dependencies: > > > > mkinitrd >=3D 4.2.21-1 is needed by kernel-2.6.18-1.2257.fc= 4.mpls.1.955.i686 > > > > isdn4k-utils < 3.2-32 conflicts with kernel-2.6.18-1.2257.f= c4.mpls.1.955.i686 > > > > kudzu < 1.2.5 conflicts with kernel-2.6.18-1.2257.fc4.mpls.= 1.955.i686 > > > >=20 > > > > [root@PE3 Requeridos]# rpm -ivh mkinitrd-4.2.21-1.i386.rpm > > > > error: Failed dependencies: > > > > libc.so.6(GLIBC_2.4) is needed by mkinitrd-4.2.21-1.i386 > > > >=20 > > > > [root@PE3 Requeridos]# rpm -ivh isdn4k-utils-3.2-32.i386.rpm > > > > error: Failed dependencies: > > > > libc.so.6(GLIBC_2.4) is needed by isdn4k-utils-3.2-32.i386 > > > > libpcap.so.0.9.3 is needed by isdn4k-utils-3.2-32.i386 > > > >=20 > > >=20 > > >=20 > > >=20 > > > --=20 > > > James R. Leu > > > jl...@mi... > > >=20 > > >=20 > > >=20 > >=20 > >=20 > >=20 > > --=20 > > James R. Leu > > jl...@mi... > >=20 > >=20 > > -----------------------------------------------------------------------= -- > > Take Surveys. Earn Cash. Influence the Future of IT > > Join SourceForge.net's Techsay panel and you'll get the chance to share= your > > opinions on IT & business topics through brief surveys-and earn cash > > http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID= =3DDEVDEV > > _______________________________________________ > > mpls-linux-devel mailing list > > mpl...@li... > > https://lists.sourceforge.net/lists/listinfo/mpls-linux-devel >=20 > --=20 > James R. Leu > jl...@mi... >=20 >=20 > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share y= our > opinions on IT & business topics through brief surveys-and earn cash > http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3D= DEVDEV > _______________________________________________ > mpls-linux-devel mailing list > mpl...@li... > https://lists.sourceforge.net/lists/listinfo/mpls-linux-devel --=20 James R. Leu jl...@mi... |
|
From: <gsr...@al...> - 2007-03-02 10:05:31
|
Hi James:
As you could see the enviroment is the same as yours:
[root@PE3 mpls-linux-1.955-FC4]# md5sum =
quagga-0.99.6-01.fc4.mpls.1.955.i386.rpm2187b703d908784b2c03d836086fc607 =
quagga-0.99.6-01.fc4.mpls.1.955.i386.rpm
[root@PE3 mpls-linux-1.955-FC4]# rpm -qa | grep quagga
quagga-0.99.6-01.fc4.mpls.1.955
[root@PE3 mpls-linux-1.955-FC4]# more /etc/fedora-release
Fedora Core release 4 (Stentz)
[root@PE3 mpls-linux-1.955-FC4]# zebra -d
[root@PE3 mpls-linux-1.955-FC4]# ospfd -d
[root@PE3 mpls-linux-1.955-FC4]# ldpd -d
[root@PE3 mpls-linux-1.955-FC4]# vtysh
Hello, this is Quagga (version 0.99.6).
Copyright 1996-2005 Kunihiro Ishiguro, et al.
PE3# con t
PE3(config)# mpls ldp
PE3(config-ldp)# exit
PE3(config)# int eth1
PE3(config-if)# mpls ip
PE3(config-if-ldp)# end
PE3# sh ldp disc
Local LSR Identifier: 10.0.0.2
Interface Discovery Sources:
eth1: xmit
Targeted Discovery Sources:
No configured peers
PE3# con t
PE3(config)# int eth1
PE3(config-if)# mpls labelsp 0
Labelspace: 0
PE3(config-if)# end
The problem is that I'm not able to create an LDP session between to =
LSRs, while I'm trying to configure the second of them I always get an =
I/O error, then the ldpd daemon is closed.
I'm going to try it in FC5, with last RPMs from Source Forge.
Thanks for your time,
Gonzalo.
-----Mensaje original-----
De: James R. Leu [mailto:jl...@mi...]
Enviado el: jue 01/03/2007 4:24
Para: Sienes Rodr=EDguez Gonzalo
CC: mpl...@li...
Asunto: Re: [mpls-linux-devel] New MPLS-Linux code
=20
On Wed, Feb 28, 2007 at 10:56:10AM +0100, Sienes Rodr?guez Gonzalo =
wrote:
> Hi again:
>=20
> I have configured a simple scenario. And the result, is that I'm able =
to create mpls segments from vtysh. In the sender I type: ip route =
12.0.0.1 gen 222 nexthop eth1 10.0.0.1, and in the receiver: mpls static =
0 -> label-map gen 222 pop. With ping from sender to 12.1 I can see that =
the ICMP packets are labelled. Also I can see the new mpls segment =
created by mpls nhlfe show and mpls ilm show.
> So the problem must be at configuring LDP, as I told you in the =
"running config" doesn't appear mpls ip (at the required interface) or =
the general command mpls ldp.
I built a FC4 chroot environment and installed the quagga-mpls FC4 rpms
inside of it and launched zebra/ldpd/ospfd. Using vtysh I can able to
configure:
-bash-3.00# md5sum quagga-0.99.6-01.fc4.mpls.1.955.i386.rpm=20
2187b703d908784b2c03d836086fc607 =
quagga-0.99.6-01.fc4.mpls.1.955.i386.rpm
-bash-3.00# rpm -qa | grep quagga
quagga-0.99.6-01.fc4.mpls.1.955
-bash-3.00# more /etc/fedora-release=20
Fedora Core release 4 (Stentz)
-bash-3.00# vtysh
Hello, this is Quagga (version 0.99.6).
Copyright 1996-2005 Kunihiro Ishiguro, et al.
koko# conf t
koko(config)# mpls ldp=20
koko(config-ldp)# exit
koko(config-ldp)# exit
koko(config-if)# mpls ip
koko(config-if-ldp)# end
koko# sho ldp discovery=20
Local LSR Identifier: 192.168.1.16
Interface Discovery Sources:
eth0: xmit
Targeted Discovery Sources:
No configured peers
koko#=20
Please verify which version of the RPM you have installed, which=20
vtysh your running and include the commands your using for starting
the processes.
Here is what I did to get it up and running after installing the RPM:
echo "hostname "`hostname -s` > /etc/quagga/zebra.conf
echo "hostname "`hostname -s` > /etc/quagga/ospfd.conf
echo "hostname "`hostname -s` > /etc/quagga/ldpd.conf
chown quagga.quagga /etc/quagga/zebra.conf /etc/quagga/ospfd.conf =
/etc/quagga/ldpd.conf
service zebra start
service ospfd start
service ldpd start
vtysh
> Thanks,
> Gonzalo
>=20
>=20
> -----Mensaje original-----
> De: James R. Leu [mailto:jl...@mi...]
> Enviado el: lun 26/02/2007 15:08
> Para: Sienes Rodr?guez Gonzalo
> CC: mpl...@li...
> Asunto: Re: [mpls-linux-devel] New MPLS-Linux code
> =20
> On Mon, Feb 26, 2007 at 11:32:15AM +0100, Sienes Rodr?guez Gonzalo =
wrote:
> > Hi James!
> >=20
> > I've installed the revised RPMs for FC4. I got kernel panic after =
rebooting the system that I solved by typing "enforcing=3D0" at =
grub.conf. I have some problems with the wheel of the mouse or the USB =
ports but in general it works right. I'm able to create MPLS static =
configurations. In this version the "mpls" module has disappeared so I =
only load "mpls4". I launch zebra, ospfd and ldpd but I make the whole =
configuration by vtysh. OSPF works well but I can't put most of the ldpd =
commands, in fact, the only one that appears with "show running-config" =
is "mpls labelspace 0" in the corresponding interface, Neither "mpls =
ldp" nor "mpls ip". Are these problems solved in FC5? If that's it I =
would like to work with FC5.
>=20
> Can you manually create MPLS segments with the 'mpls' command?
> I'll look into the issue with no ldp command in vtysh.
>=20
> > Thanks,
> >=20
> > Gonzalo.
> >=20
> > I updated the FC4 kernel RPMs. Can you please try them?
> >=20
> > On Mon, Feb 19, 2007 at 11:47:24AM +0100, Sienes Rodr?guez Gonzalo =
wrote:
> > > Hi James:
> > >=20
> > > I'm trying to install your new software for FC4 but I have some =
problems.
> > > When I try to install the kernel-2.6.18 from Source Forge for FC4 =
it makes me install lots of RPMs, most of them can be installed by "yum =
update" but I can't find the libraries libc.so.6(GLIBC_2.4) and =
libpcap.so.0.9.3 anywhere for FC4. I search for them and people talks =
about 64 architecture and I'm working with Intel(R) Pentium(R) D CPU =
3.00GHz. Could you provide them to me? Witch OS are you using? Should I =
install FC5? =20
> > >=20
> > > Thanks in advance.
> > >=20
> > > P.D.: These are the outputs I get.
> > >=20
> > > [root@PE3 mpls-linux-1.955]# rpm -ivh =
kernel-2.6.18-1.2257.fc4.mpls.1.955.i686.rpm
> > > error: Failed dependencies:
> > > mkinitrd >=3D 4.2.21-1 is needed by =
kernel-2.6.18-1.2257.fc4.mpls.1.955.i686
> > > isdn4k-utils < 3.2-32 conflicts with =
kernel-2.6.18-1.2257.fc4.mpls.1.955.i686
> > > kudzu < 1.2.5 conflicts with =
kernel-2.6.18-1.2257.fc4.mpls.1.955.i686
> > >=20
> > > [root@PE3 Requeridos]# rpm -ivh mkinitrd-4.2.21-1.i386.rpm
> > > error: Failed dependencies:
> > > libc.so.6(GLIBC_2.4) is needed by mkinitrd-4.2.21-1.i386
> > >=20
> > > [root@PE3 Requeridos]# rpm -ivh isdn4k-utils-3.2-32.i386.rpm
> > > error: Failed dependencies:
> > > libc.so.6(GLIBC_2.4) is needed by isdn4k-utils-3.2-32.i386
> > > libpcap.so.0.9.3 is needed by isdn4k-utils-3.2-32.i386
> > >=20
> >=20
> >=20
> >=20
> > --=20
> > James R. Leu
> > jl...@mi...
> >=20
> >=20
> >=20
>=20
>=20
>=20
> --=20
> James R. Leu
> jl...@mi...
>=20
>=20
> =
-------------------------------------------------------------------------=
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to =
share your
> opinions on IT & business topics through brief surveys-and earn cash
> =
http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3D=
DEVDEV
> _______________________________________________
> mpls-linux-devel mailing list
> mpl...@li...
> https://lists.sourceforge.net/lists/listinfo/mpls-linux-devel
--=20
James R. Leu
jl...@mi...
|
|
From: James R. L. <jl...@mi...> - 2007-03-01 03:24:43
|
On Wed, Feb 28, 2007 at 10:56:10AM +0100, Sienes Rodr?guez Gonzalo wrote:
> Hi again:
>=20
> I have configured a simple scenario. And the result, is that I'm able to =
create mpls segments from vtysh. In the sender I type: ip route 12.0.0.1 ge=
n 222 nexthop eth1 10.0.0.1, and in the receiver: mpls static 0 -> label-ma=
p gen 222 pop. With ping from sender to 12.1 I can see that the ICMP packet=
s are labelled. Also I can see the new mpls segment created by mpls nhlfe s=
how and mpls ilm show.
> So the problem must be at configuring LDP, as I told you in the "running =
config" doesn't appear mpls ip (at the required interface) or the general c=
ommand mpls ldp.
I built a FC4 chroot environment and installed the quagga-mpls FC4 rpms
inside of it and launched zebra/ldpd/ospfd. Using vtysh I can able to
configure:
-bash-3.00# md5sum quagga-0.99.6-01.fc4.mpls.1.955.i386.rpm=20
2187b703d908784b2c03d836086fc607 quagga-0.99.6-01.fc4.mpls.1.955.i386.rpm
-bash-3.00# rpm -qa | grep quagga
quagga-0.99.6-01.fc4.mpls.1.955
-bash-3.00# more /etc/fedora-release=20
Fedora Core release 4 (Stentz)
-bash-3.00# vtysh
Hello, this is Quagga (version 0.99.6).
Copyright 1996-2005 Kunihiro Ishiguro, et al.
koko# conf t
koko(config)# mpls ldp=20
koko(config-ldp)# exit
koko(config-ldp)# exit
koko(config-if)# mpls ip
koko(config-if-ldp)# end
koko# sho ldp discovery=20
Local LSR Identifier: 192.168.1.16
Interface Discovery Sources:
eth0: xmit
Targeted Discovery Sources:
No configured peers
koko#=20
Please verify which version of the RPM you have installed, which=20
vtysh your running and include the commands your using for starting
the processes.
Here is what I did to get it up and running after installing the RPM:
echo "hostname "`hostname -s` > /etc/quagga/zebra.conf
echo "hostname "`hostname -s` > /etc/quagga/ospfd.conf
echo "hostname "`hostname -s` > /etc/quagga/ldpd.conf
chown quagga.quagga /etc/quagga/zebra.conf /etc/quagga/ospfd.conf /etc/quag=
ga/ldpd.conf
service zebra start
service ospfd start
service ldpd start
vtysh
> Thanks,
> Gonzalo
>=20
>=20
> -----Mensaje original-----
> De: James R. Leu [mailto:jl...@mi...]
> Enviado el: lun 26/02/2007 15:08
> Para: Sienes Rodr?guez Gonzalo
> CC: mpl...@li...
> Asunto: Re: [mpls-linux-devel] New MPLS-Linux code
> =20
> On Mon, Feb 26, 2007 at 11:32:15AM +0100, Sienes Rodr?guez Gonzalo wrote:
> > Hi James!
> >=20
> > I've installed the revised RPMs for FC4. I got kernel panic after reboo=
ting the system that I solved by typing "enforcing=3D0" at grub.conf. I hav=
e some problems with the wheel of the mouse or the USB ports but in general=
it works right. I'm able to create MPLS static configurations. In this ver=
sion the "mpls" module has disappeared so I only load "mpls4". I launch zeb=
ra, ospfd and ldpd but I make the whole configuration by vtysh. OSPF works =
well but I can't put most of the ldpd commands, in fact, the only one that =
appears with "show running-config" is "mpls labelspace 0" in the correspond=
ing interface, Neither "mpls ldp" nor "mpls ip". Are these problems solved =
in FC5? If that's it I would like to work with FC5.
>=20
> Can you manually create MPLS segments with the 'mpls' command?
> I'll look into the issue with no ldp command in vtysh.
>=20
> > Thanks,
> >=20
> > Gonzalo.
> >=20
> > I updated the FC4 kernel RPMs. Can you please try them?
> >=20
> > On Mon, Feb 19, 2007 at 11:47:24AM +0100, Sienes Rodr?guez Gonzalo wrot=
e:
> > > Hi James:
> > >=20
> > > I'm trying to install your new software for FC4 but I have some probl=
ems.
> > > When I try to install the kernel-2.6.18 from Source Forge for FC4 it =
makes me install lots of RPMs, most of them can be installed by "yum update=
" but I can't find the libraries libc.so.6(GLIBC_2.4) and libpcap.so.0.9.3 =
anywhere for FC4. I search for them and people talks about 64 architecture =
and I'm working with Intel(R) Pentium(R) D CPU 3.00GHz. Could you provide t=
hem to me? Witch OS are you using? Should I install FC5? =20
> > >=20
> > > Thanks in advance.
> > >=20
> > > P.D.: These are the outputs I get.
> > >=20
> > > [root@PE3 mpls-linux-1.955]# rpm -ivh kernel-2.6.18-1.2257.fc4.mpls.1=
.955.i686.rpm
> > > error: Failed dependencies:
> > > mkinitrd >=3D 4.2.21-1 is needed by kernel-2.6.18-1.2257.fc4.=
mpls.1.955.i686
> > > isdn4k-utils < 3.2-32 conflicts with kernel-2.6.18-1.2257.fc4=
.mpls.1.955.i686
> > > kudzu < 1.2.5 conflicts with kernel-2.6.18-1.2257.fc4.mpls.1.=
955.i686
> > >=20
> > > [root@PE3 Requeridos]# rpm -ivh mkinitrd-4.2.21-1.i386.rpm
> > > error: Failed dependencies:
> > > libc.so.6(GLIBC_2.4) is needed by mkinitrd-4.2.21-1.i386
> > >=20
> > > [root@PE3 Requeridos]# rpm -ivh isdn4k-utils-3.2-32.i386.rpm
> > > error: Failed dependencies:
> > > libc.so.6(GLIBC_2.4) is needed by isdn4k-utils-3.2-32.i386
> > > libpcap.so.0.9.3 is needed by isdn4k-utils-3.2-32.i386
> > >=20
> >=20
> >=20
> >=20
> > --=20
> > James R. Leu
> > jl...@mi...
> >=20
> >=20
> >=20
>=20
>=20
>=20
> --=20
> James R. Leu
> jl...@mi...
>=20
>=20
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share y=
our
> opinions on IT & business topics through brief surveys-and earn cash
> http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3D=
DEVDEV
> _______________________________________________
> mpls-linux-devel mailing list
> mpl...@li...
> https://lists.sourceforge.net/lists/listinfo/mpls-linux-devel
--=20
James R. Leu
jl...@mi...
|
|
From: James R. L. <jl...@mi...> - 2007-03-01 03:05:39
|
On Wed, Feb 28, 2007 at 10:56:10AM +0100, Sienes Rodr?guez Gonzalo wrote: > Hi again: >=20 > I have configured a simple scenario. And the result, is that I'm able to = create mpls segments from vtysh. In the sender I type: ip route 12.0.0.1 ge= n 222 nexthop eth1 10.0.0.1, and in the receiver: mpls static 0 -> label-ma= p gen 222 pop. With ping from sender to 12.1 I can see that the ICMP packet= s are labelled. Also I can see the new mpls segment created by mpls nhlfe s= how and mpls ilm show. > So the problem must be at configuring LDP, as I told you in the "running = config" doesn't appear mpls ip (at the required interface) or the general c= ommand mpls ldp. OK. Thanks for the feedback. I'll look into it. > Thanks, > Gonzalo >=20 >=20 > -----Mensaje original----- > De: James R. Leu [mailto:jl...@mi...] > Enviado el: lun 26/02/2007 15:08 > Para: Sienes Rodr?guez Gonzalo > CC: mpl...@li... > Asunto: Re: [mpls-linux-devel] New MPLS-Linux code > =20 > On Mon, Feb 26, 2007 at 11:32:15AM +0100, Sienes Rodr?guez Gonzalo wrote: > > Hi James! > >=20 > > I've installed the revised RPMs for FC4. I got kernel panic after reboo= ting the system that I solved by typing "enforcing=3D0" at grub.conf. I hav= e some problems with the wheel of the mouse or the USB ports but in general= it works right. I'm able to create MPLS static configurations. In this ver= sion the "mpls" module has disappeared so I only load "mpls4". I launch zeb= ra, ospfd and ldpd but I make the whole configuration by vtysh. OSPF works = well but I can't put most of the ldpd commands, in fact, the only one that = appears with "show running-config" is "mpls labelspace 0" in the correspond= ing interface, Neither "mpls ldp" nor "mpls ip". Are these problems solved = in FC5? If that's it I would like to work with FC5. >=20 > Can you manually create MPLS segments with the 'mpls' command? > I'll look into the issue with no ldp command in vtysh. >=20 > > Thanks, > >=20 > > Gonzalo. > >=20 > > I updated the FC4 kernel RPMs. Can you please try them? > >=20 > > On Mon, Feb 19, 2007 at 11:47:24AM +0100, Sienes Rodr?guez Gonzalo wrot= e: > > > Hi James: > > >=20 > > > I'm trying to install your new software for FC4 but I have some probl= ems. > > > When I try to install the kernel-2.6.18 from Source Forge for FC4 it = makes me install lots of RPMs, most of them can be installed by "yum update= " but I can't find the libraries libc.so.6(GLIBC_2.4) and libpcap.so.0.9.3 = anywhere for FC4. I search for them and people talks about 64 architecture = and I'm working with Intel(R) Pentium(R) D CPU 3.00GHz. Could you provide t= hem to me? Witch OS are you using? Should I install FC5? =20 > > >=20 > > > Thanks in advance. > > >=20 > > > P.D.: These are the outputs I get. > > >=20 > > > [root@PE3 mpls-linux-1.955]# rpm -ivh kernel-2.6.18-1.2257.fc4.mpls.1= .955.i686.rpm > > > error: Failed dependencies: > > > mkinitrd >=3D 4.2.21-1 is needed by kernel-2.6.18-1.2257.fc4.= mpls.1.955.i686 > > > isdn4k-utils < 3.2-32 conflicts with kernel-2.6.18-1.2257.fc4= .mpls.1.955.i686 > > > kudzu < 1.2.5 conflicts with kernel-2.6.18-1.2257.fc4.mpls.1.= 955.i686 > > >=20 > > > [root@PE3 Requeridos]# rpm -ivh mkinitrd-4.2.21-1.i386.rpm > > > error: Failed dependencies: > > > libc.so.6(GLIBC_2.4) is needed by mkinitrd-4.2.21-1.i386 > > >=20 > > > [root@PE3 Requeridos]# rpm -ivh isdn4k-utils-3.2-32.i386.rpm > > > error: Failed dependencies: > > > libc.so.6(GLIBC_2.4) is needed by isdn4k-utils-3.2-32.i386 > > > libpcap.so.0.9.3 is needed by isdn4k-utils-3.2-32.i386 > > >=20 > >=20 > >=20 > >=20 > > --=20 > > James R. Leu > > jl...@mi... > >=20 > >=20 > >=20 >=20 >=20 >=20 > --=20 > James R. Leu > jl...@mi... >=20 >=20 > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share y= our > opinions on IT & business topics through brief surveys-and earn cash > http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3D= DEVDEV > _______________________________________________ > mpls-linux-devel mailing list > mpl...@li... > https://lists.sourceforge.net/lists/listinfo/mpls-linux-devel --=20 James R. Leu jl...@mi... |
|
From: <gsr...@al...> - 2007-02-28 09:58:09
|
Hi again: I have configured a simple scenario. And the result, is that I'm able to = create mpls segments from vtysh. In the sender I type: ip route 12.0.0.1 = gen 222 nexthop eth1 10.0.0.1, and in the receiver: mpls static 0 -> = label-map gen 222 pop. With ping from sender to 12.1 I can see that the = ICMP packets are labelled. Also I can see the new mpls segment created = by mpls nhlfe show and mpls ilm show. So the problem must be at configuring LDP, as I told you in the "running = config" doesn't appear mpls ip (at the required interface) or the = general command mpls ldp. Thanks, Gonzalo -----Mensaje original----- De: James R. Leu [mailto:jl...@mi...] Enviado el: lun 26/02/2007 15:08 Para: Sienes Rodr=EDguez Gonzalo CC: mpl...@li... Asunto: Re: [mpls-linux-devel] New MPLS-Linux code =20 On Mon, Feb 26, 2007 at 11:32:15AM +0100, Sienes Rodr?guez Gonzalo = wrote: > Hi James! >=20 > I've installed the revised RPMs for FC4. I got kernel panic after = rebooting the system that I solved by typing "enforcing=3D0" at = grub.conf. I have some problems with the wheel of the mouse or the USB = ports but in general it works right. I'm able to create MPLS static = configurations. In this version the "mpls" module has disappeared so I = only load "mpls4". I launch zebra, ospfd and ldpd but I make the whole = configuration by vtysh. OSPF works well but I can't put most of the ldpd = commands, in fact, the only one that appears with "show running-config" = is "mpls labelspace 0" in the corresponding interface, Neither "mpls = ldp" nor "mpls ip". Are these problems solved in FC5? If that's it I = would like to work with FC5. Can you manually create MPLS segments with the 'mpls' command? I'll look into the issue with no ldp command in vtysh. > Thanks, >=20 > Gonzalo. >=20 > I updated the FC4 kernel RPMs. Can you please try them? >=20 > On Mon, Feb 19, 2007 at 11:47:24AM +0100, Sienes Rodr?guez Gonzalo = wrote: > > Hi James: > >=20 > > I'm trying to install your new software for FC4 but I have some = problems. > > When I try to install the kernel-2.6.18 from Source Forge for FC4 it = makes me install lots of RPMs, most of them can be installed by "yum = update" but I can't find the libraries libc.so.6(GLIBC_2.4) and = libpcap.so.0.9.3 anywhere for FC4. I search for them and people talks = about 64 architecture and I'm working with Intel(R) Pentium(R) D CPU = 3.00GHz. Could you provide them to me? Witch OS are you using? Should I = install FC5? =20 > >=20 > > Thanks in advance. > >=20 > > P.D.: These are the outputs I get. > >=20 > > [root@PE3 mpls-linux-1.955]# rpm -ivh = kernel-2.6.18-1.2257.fc4.mpls.1.955.i686.rpm > > error: Failed dependencies: > > mkinitrd >=3D 4.2.21-1 is needed by = kernel-2.6.18-1.2257.fc4.mpls.1.955.i686 > > isdn4k-utils < 3.2-32 conflicts with = kernel-2.6.18-1.2257.fc4.mpls.1.955.i686 > > kudzu < 1.2.5 conflicts with = kernel-2.6.18-1.2257.fc4.mpls.1.955.i686 > >=20 > > [root@PE3 Requeridos]# rpm -ivh mkinitrd-4.2.21-1.i386.rpm > > error: Failed dependencies: > > libc.so.6(GLIBC_2.4) is needed by mkinitrd-4.2.21-1.i386 > >=20 > > [root@PE3 Requeridos]# rpm -ivh isdn4k-utils-3.2-32.i386.rpm > > error: Failed dependencies: > > libc.so.6(GLIBC_2.4) is needed by isdn4k-utils-3.2-32.i386 > > libpcap.so.0.9.3 is needed by isdn4k-utils-3.2-32.i386 > >=20 >=20 >=20 >=20 > --=20 > James R. Leu > jl...@mi... >=20 >=20 >=20 --=20 James R. Leu jl...@mi... |
14 messages has been excluded from this view by a project administrator.
