MPLS invisible neighbors

RouterOS Forwarding Protocols
1

Hi everyone,

I’m having some problems enabling MPLS LDP sessions. We connect 5 mikrotik as you can see in the diagram (two RB433 and three RB333, all of them with 6.27 version of RouterOS), we add the addresses, the configuration of OSPF (which we were advised to do through Winbox graphical interface) works propperly, it finds the neighbors perfectly.
Diagrama.jpg
When setting MPLS, we used these lines, adapting the addresses to each system:

/mpls
set propagate-ttl=no
/mpls ldp
set enabled=yes lsr-id=0.0.1.2 transport-address=0.0.1.2
/mpls ldp interface
add interface=wlan1
add interface=wlan2

Not only it does not recognize the neighbors (just 0.0.1.1 can see both of its neighbors), but also when trying to do a traceroute from 172.17.3.2 to the other side, we can still see each of the hops (in spite of having set propagate-ttl=no).

PLEEEAAAASEEE HEEELP!!

Thank you!

2

I’m suspicious of the loopback addresses.
0.0.0.0/8 is technically a bogon prefix and not a valid network, right?
Those are fine as ospf router IDs because an OSPF ID is not really an IP, but I’m thinking this might be part of the issue with something that really needs to traverse real links like LSR-IDs and so forth.

Can you ping all loopback addresses from all loopback addresses?

3

The only problem I haved (for me fixed on 6.27) with the machine (and also with it’s VRRP mirror) is the SFP driver not auto-sensing rightly.
Too much often BGP peer freeze not for the BGP itself, but for the poor quality of SFP link with S-85DLC05D 850nm