Thread: Re: [mpls-linux-devel] New MPLS-Linux code
Status: Beta
Brought to you by:
jleu
Menu
▾
▴
mpls-linux-devel
|
From: <gsr...@al...> - 2007-02-19 11:00:01
|
Hi James:
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
Thanks in advance.
P.D.: These are the outputs I get.
[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
[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
[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
|
|
From: <gsr...@al...> - 2007-02-26 22:41:02
|
Hi James! 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. Thanks, Gonzalo. I updated the FC4 kernel RPMs. Can you please try them? 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 James R. Leu jl...@mi... |
|
From: James R. L. <jl...@mi...> - 2007-02-26 14:11:58
|
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 rebooti= ng 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 i= t works right. I'm able to create MPLS static configurations. In this versi= on 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 we= ll but I can't put most of the ldpd commands, in fact, the only one that ap= pears with "show running-config" is "mpls labelspace 0" in the correspondin= g 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 problem= s. > > When I try to install the kernel-2.6.18 from Source Forge for FC4 it ma= kes 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 an= ywhere for FC4. I search for them and people talks about 64 architecture an= d I'm working with Intel(R) Pentium(R) D CPU 3.00GHz. Could you provide the= m 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.9= 55.i686.rpm > > error: Failed dependencies: > > mkinitrd >=3D 4.2.21-1 is needed by kernel-2.6.18-1.2257.fc4.mp= ls.1.955.i686 > > isdn4k-utils < 3.2-32 conflicts with kernel-2.6.18-1.2257.fc4.m= pls.1.955.i686 > > kudzu < 1.2.5 conflicts with kernel-2.6.18-1.2257.fc4.mpls.1.95= 5.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... |
|
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: 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: <gsr...@al...> - 2007-03-16 13:23:57
|
Hi James: This is the log file for PE2 debugging zebra kernel, packet and rib. 2007/03/16 13:59:31 OSPF: interface 10.0.0.2 [4] join AllSPFRouters = Multicast group. 2007/03/16 13:59:31 ZEBRA: zebra message received [ZEBRA_IPV4_ROUTE_ADD] = 17 2007/03/16 13:59:31 ZEBRA: rib_link: rn 0x97e2fb8, rib 0x97e8bf0 2007/03/16 13:59:31 ZEBRA: rib_link: new head, rn_status copied over 2007/03/16 13:59:31 ZEBRA: rib_process: Updating existing route, select = 0x97e2ff8, fib 0x97e2ff8 2007/03/16 13:59:35 OSPF: interface 13.0.0.1 [3] join AllSPFRouters = Multicast group. 2007/03/16 13:59:36 ZEBRA: zebra message received [ZEBRA_IPV4_ROUTE_ADD] = 17 2007/03/16 13:59:36 ZEBRA: rib_link: rn 0x97e2db0, rib 0x97e8d18 2007/03/16 13:59:36 ZEBRA: rib_link: new head, rn_status copied over 2007/03/16 13:59:36 ZEBRA: rib_process: Updating existing route, select = 0x97e2df0, fib 0x97e2df0 2007/03/16 13:59:59 OSPF: ospfTrapNbrStateChange trap sent: 10.0.0.1 now = Init/DROther 2007/03/16 14:00:11 OSPF: DR-Election[1st]: Backup 10.0.0.1 2007/03/16 14:00:11 OSPF: DR-Election[1st]: DR 10.0.0.1 2007/03/16 14:00:11 OSPF: ospfTrapIfStateChange trap sent: 10.0.0.2 now = DROther 2007/03/16 14:00:15 OSPF: DR-Election[1st]: Backup 13.0.0.1 2007/03/16 14:00:15 OSPF: DR-Election[1st]: DR 13.0.0.1 2007/03/16 14:00:15 OSPF: DR-Election[2nd]: Backup 0.0.0.0 2007/03/16 14:00:15 OSPF: DR-Election[2nd]: DR 13.0.0.1 2007/03/16 14:00:15 OSPF: ospfTrapIfStateChange trap sent: 13.0.0.1 now = DR 2007/03/16 14:00:15 OSPF: interface 13.0.0.1 [3] join AllDRouters = Multicast group. 2007/03/16 14:00:39 OSPF: Packet[DD]: Neighbor 12.0.0.1 Negotiation done = (Slave). 2007/03/16 14:00:39 OSPF: nsm_change_state(12.0.0.1, Loading -> Full): = scheduling new router-LSA origination 2007/03/16 14:00:39 OSPF: DR-Election[1st]: Backup 10.0.0.2 2007/03/16 14:00:39 OSPF: DR-Election[1st]: DR 10.0.0.1 2007/03/16 14:00:39 OSPF: DR-Election[2nd]: Backup 10.0.0.2 2007/03/16 14:00:39 OSPF: DR-Election[2nd]: DR 10.0.0.1 2007/03/16 14:00:39 OSPF: ospfTrapIfStateChange trap sent: 10.0.0.2 now = Backup 2007/03/16 14:00:39 OSPF: interface 10.0.0.2 [4] join AllDRouters = Multicast group. 2007/03/16 14:00:44 ZEBRA: zebra message received [ZEBRA_IPV4_ROUTE_ADD] = 17 2007/03/16 14:00:44 ZEBRA: rib_link: rn 0x97e9200, rib 0x97e9138 2007/03/16 14:00:44 ZEBRA: rib_process: Adding route, select 0x97e9138 2007/03/16 14:00:44 ZEBRA: netlink_route_multipath() (single hop): = RTM_NEWROUTE 12.0.0.0/24, type IPv4=20 2007/03/16 14:00:44 ZEBRA: netlink_route_multipath() (single hop): = nexthop via 10.0.0.1 if 4 2007/03/16 14:00:44 ZEBRA: netlink_talk: netlink-cmd type = RTM_NEWROUTE(24), seq=3D6 2007/03/16 14:00:44 ZEBRA: netlink_parse_info: netlink-cmd ACK: = type=3DRTM_NEWROUTE(24), seq=3D6, pid=3D0 2007/03/16 14:00:44 ZEBRA: netlink_parse_info: netlink-listen type = RTM_NEWROUTE(24), seq=3D6, pid=3D4294963195 2007/03/16 14:00:44 ZEBRA: netlink_parse_info: netlink-cmd packet comes = from netlink-listen 2007/03/16 14:00:54 ZEBRA: zebra message received = [ZEBRA_REDISTRIBUTE_ADD] 1 2007/03/16 14:00:54 ZEBRA: zebra message received = [ZEBRA_REDISTRIBUTE_ADD] 1 2007/03/16 14:00:54 ZEBRA: zebra message received = [ZEBRA_REDISTRIBUTE_ADD] 1 2007/03/16 14:00:54 ZEBRA: zebra message received = [ZEBRA_REDISTRIBUTE_ADD] 1 2007/03/16 14:00:54 ZEBRA: zebra message received = [ZEBRA_REDISTRIBUTE_ADD] 1 2007/03/16 14:00:54 ZEBRA: zebra message received = [ZEBRA_REDISTRIBUTE_ADD] 1 2007/03/16 14:00:54 ZEBRA: zebra message received = [ZEBRA_REDISTRIBUTE_ADD] 1 2007/03/16 14:00:54 ZEBRA: zebra message received = [ZEBRA_REDISTRIBUTE_ADD] 1 2007/03/16 14:00:54 ZEBRA: zebra message received = [ZEBRA_REDISTRIBUTE_ADD] 1 2007/03/16 14:00:54 ZEBRA: zebra message received = [ZEBRA_REDISTRIBUTE_ADD] 1 2007/03/16 14:00:54 ZEBRA: zebra message received = [ZEBRA_REDISTRIBUTE_ADD] 1 2007/03/16 14:00:54 LDP: route 169.254.0.0/16 2007/03/16 14:00:54 LDP: num ifindex 0 2007/03/16 14:00:54 LDP: ifindex 4 2007/03/16 14:00:54 LDP: add 2007/03/16 14:00:54 LDP: route 10.0.0.0/24 2007/03/16 14:00:54 LDP: num ifindex 0 2007/03/16 14:00:54 LDP: attached 2007/03/16 14:00:54 LDP: ifindex 4 2007/03/16 14:00:54 LDP: add 2007/03/16 14:00:54 LDP: route 13.0.0.0/24 2007/03/16 14:00:54 LDP: num ifindex 0 2007/03/16 14:00:54 LDP: attached 2007/03/16 14:00:54 LDP: ifindex 3 2007/03/16 14:00:54 LDP: add 2007/03/16 14:00:54 LDP: route 12.0.0.0/24 2007/03/16 14:00:54 LDP: num nexthop 0 2007/03/16 14:00:54 LDP: nexthop 10.0.0.1 2007/03/16 14:00:54 LDP: add 2007/03/16 14:01:02 ZEBRA: netlink_talk: mpls-netlink-cmd type (29), = seq=3D1 2007/03/16 14:01:02 ZEBRA: netlink_parse_info: mpls-netlink-cmd ACK: = type=3D(29), seq=3D1, pid=3D0 2007/03/16 14:01:36 LDP: OUT: ldp_session_attempt_setup: = MPLS_NON_BLOCKING 2007/03/16 14:01:36 LDP: OUT: LDP_NOTIF_SESSION_REJECTED_NO_HELLO: 2007/03/16 14:01:41 LDP: OUT: ldp_session_attempt_setup: = MPLS_NON_BLOCKING 2007/03/16 14:01:43 ZEBRA: zebra message received = [ZEBRA_MPLS_IN_SEGMENT_ADD] 10 2007/03/16 14:01:43 ZEBRA: netlink_talk: mpls-netlink-cmd type (29), = seq=3D2 2007/03/16 14:01:43 ZEBRA: netlink_parse_info: mpls-netlink-cmd ACK: = type=3D(29), seq=3D2, pid=3D0 2007/03/16 14:01:43 ZEBRA: netlink_parse_info: mpls-netlink-listen type = (29), seq=3D0, pid=3D0 2007/03/16 14:01:43 ZEBRA: zebra message received = [ZEBRA_MPLS_OUT_SEGMENT_ADD] 39 2007/03/16 14:01:43 ZEBRA: netlink_talk: mpls-netlink-nhlfe type (29), = seq=3D1 2007/03/16 14:01:43 ZEBRA: netlink_parse_info: mpls-netlink-nhlfe type = (29), seq=3D1, pid=3D4294963193 2007/03/16 14:01:43 ZEBRA: netlink_talk: ignoring message type 0x001d 2007/03/16 14:01:43 ZEBRA: mpls_ctrl_nhlfe_register(): NHLFE 0x00000002 2007/03/16 14:01:43 ZEBRA: netlink_parse_info: mpls-netlink-listen type = (29), seq=3D1, pid=3D4294963193 2007/03/16 14:01:43 LDP: found pending NHLFE: 0x9d347e8 2007/03/16 14:01:43 ZEBRA: netlink_parse_info: mpls-netlink-nhlfe packet = comes from mpls-netlink-listen 2007/03/16 14:01:43 ZEBRA: zebra message received [ZEBRA_MPLS_FTN_ADD] = 11 2007/03/16 14:04:38 LDP: Terminating on signal 2007/03/16 14:04:38 ZEBRA: Terminating on signal 2007/03/16 14:04:38 ZEBRA: netlink_route_multipath() (single hop): = RTM_DELROUTE 12.0.0.0/24, type IPv4=20 2007/03/16 14:04:38 ZEBRA: netlink_route_multipath() (single hop): = nexthop via 10.0.0.1 if 4 2007/03/16 14:04:38 ZEBRA: netlink_talk: netlink-cmd type = RTM_DELROUTE(25), seq=3D7 2007/03/16 14:04:38 ZEBRA: netlink_parse_info: netlink-cmd ACK: = type=3DRTM_DELROUTE(25), seq=3D7, pid=3D0 2007/03/16 14:04:38 ZEBRA: netlink_talk: mpls-netlink-cmd type (29), = seq=3D3 2007/03/16 14:04:38 ZEBRA: netlink_parse_info: mpls-netlink-cmd ACK: = type=3D(29), seq=3D3, pid=3D0 2007/03/16 14:04:38 ZEBRA: netlink_talk: mpls-netlink-cmd type (29), = seq=3D4 2007/03/16 14:04:38 ZEBRA: netlink_parse_info: mpls-netlink-cmd ACK: = type=3D(29), seq=3D4, pid=3D0 2007/03/16 14:04:38 ZEBRA: IRDP: Received shutdown notification. Thanks in advance, Gonzalo. -----Mensaje original----- De: James R. Leu [mailto:jl...@mi...] Enviado el: vie 16/03/2007 6:55 Para: Sienes Rodr=EDguez Gonzalo CC: mpl...@li... Asunto: Re: [mpls-linux-devel] MPLS-Linux-1.955 FC5 =20 This doesn't seem to be enough debugging. Try adding: debug zebra rib debug zebra packet |
|
From: James R. L. <jl...@mi...> - 2007-02-19 13:54:21
|
My main development plateform is FC5 on i386. The FC4 RPMs I've released are just FC5 RPMs compiled in a FC4 environment. You're best bet is to use FC5 for testing/development of mpls-linux. With that being said, I will still try to fix the FC4 RPMs. 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 make= s me install lots of RPMs, most of them can be installed by "yum update" bu= t I can't find the libraries libc.so.6(GLIBC_2.4) and libpcap.so.0.9.3 anyw= here 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.mpl= s.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 > ------------------------------------------------------------------------- > 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-02-22 03:50:11
|
I updated the FC4 kernel RPMs. Can you please try them? 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 make= s me install lots of RPMs, most of them can be installed by "yum update" bu= t I can't find the libraries libc.so.6(GLIBC_2.4) and libpcap.so.0.9.3 anyw= here 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.mpl= s.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 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 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-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: 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... |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X