Re: [mpls-linux-devel] MPLS-Linux-1.955 FC5

[<gsr...@al...>]

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.