Re: [mpls-linux-devel] LDP problems

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

Hi:

For you, Marco this is the config I made for the following simple =
scenario:      =20

                  eth0   eth1             eth1   eth0
       12.0.0.1-------PE1---------------------PE2-------13.0.0.1
                         .1  10.0.0.0/24    .2

I keep the config files for zebra, ospfd and ldpd empty (only log file =
and hostname) and I configure everything via vtysh:

PE1
-------------------------------------------------------------------------=
-

router ospf
	network 10.0.0.0/24 area 0
	network 12.0.0.0/24 area 0

mpls ldp

int eth1
	mpls labelspace 0
	mpls ip

PE2
-------------------------------------------------------------------------=
-

router ospf
	network 10.0.0.0/24 area 0
	network 13.0.0.0/24 area 0

mpls ldp

int eth1
	mpls labelspace 0
	mpls ip=09

At first I only type in the ospf commands and wait until new routes are =
learned to configure LDP. The label 10000 is distributed properly, the =
NHLFE and ILM entries are created but the problem is that it's not =
possible to associate the label with the route learned via ospf.

I tried your configuration files in my scenario, adding a dummy =
interface in each PE.

                  eth0   eth1             eth1   eth0
       12.0.0.1-------PE1---------------------PE2-------13.0.0.1
                       | .1   10.0.0.0/24   .2 |
                       |                       |
                       |dummy0                 |dummy0
                 192.168.0.1/32          192.168.0.2/32

Now I include at zebra.conf the directions of each interface and at =
ospf.conf, the whole config with eth0 and dummy0 as passive-interfaces =
and the dummy0 as the ID of the OSPF router.

After this I configure via vtysh the LDP commands for eth1.

The labels are distributed and I'm even able to send labeled packets =
from each PE to the dummy interface of the other.

But for the eth0 interfaces, the problem is the same as before, the =
label isn't bound to the corresponding route.

Regards,
Gonzalo.