Cannot ping to loopback

Hello guys,
I have a question for connectivity between cisco and vyos
2 router are in BGP peering and I made a loopback interface in vyos.
Cisco could get this route but can’t reach to it

This is a configuration and each routing table

set interfaces ethernet eth0 address ‘100.64.52.10/24’
set interfaces ethernet eth0 hw-id ‘00:50:56:aa:2b:e3’
set interfaces ethernet eth1 hw-id ‘00:50:56:aa:c8:9b’
set interfaces ethernet eth2 hw-id ‘00:50:56:aa:ad:24’
set interfaces loopback lo address ‘6.6.6.6/32’
set protocols bgp address-family ipv4-unicast network 6.6.6.6/32
set protocols bgp neighbor 192.168.2.107 address-family ipv4-unicast
set protocols bgp neighbor 192.168.2.107 ebgp-multihop ‘5’
set protocols bgp neighbor 192.168.2.107 remote-as ‘50812’
set protocols bgp neighbor 192.168.2.107 update-source ‘100.64.52.10’
set protocols bgp parameters log-neighbor-changes
set protocols bgp parameters router-id ‘100.64.52.10’
set protocols bgp system-as ‘64666’
set protocols static route 0.0.0.0/0 next-hop 100.64.52.1
set protocols static route 192.168.2.0/24 next-hop 100.64.52.1

routing table of Vyos

vyos@vyos:~$ show ip route

S>* 0.0.0.0/0 [1/0] via 100.64.52.1, eth0, weight 1, 01w6d21h
C>* 6.6.6.6/32 is directly connected, lo, 00:16:58
C>* 100.64.52.0/24 is directly connected, eth0, 01w6d21h
S>* 192.168.2.0/24 [1/0] via 100.64.52.1, eth0, weight 1, 6d20h34m

routing table of cisco

NR-IB-VEN-B2-01#show bgp vrf vrf-mngmt neighbors 100.64.52.10 routes

 Network          Next Hop            Metric LocPrf Weight Path

Route Distinguisher: 1:1 (default for vrf vrf-mngmt)
*> 6.6.6.6/32 100.64.52.10 0 0 64666 i

S* 0.0.0.0/0 [1/0] via 192.168.2.254
192.168.2.0/24 is variably subnetted, 2 subnets, 2 masks
C 192.168.2.0/24 is directly connected, Port-channel1.4000
L 192.168.2.107/32 is directly connected, Port-channel1.4000

This is weird, even if cisco get a bgp route, but I cann’t see any route in routing table.

I captured the packet in vyos but couldn’t see any ping packet

Devices are not connected directly… Router in the middle knows the route for 6.6.6.6 address?