hi team
bases on report from forum
https://forum.vyos.io/t/vyos-1-4-l3vpn-bgp-import-export-nexthop-incorrect/9876/4
it seems that FRR doesn't install direct connected prefixes ,using the command 'network x.x.x./x' over address-family ipv4 unicast:
example :
set vrf bind-to-all
set vrf name customer protocols bgp address-family ipv4-unicast export vpn
set vrf name customer protocols bgp address-family ipv4-unicast import vpn
set vrf name customer protocols bgp address-family ipv4-unicast label vpn export 'auto'
set vrf name customer protocols bgp address-family ipv4-unicast network 10.180.2.0/24
set vrf name customer protocols bgp address-family ipv4-unicast rd vpn export '1:2'
set vrf name customer protocols bgp address-family ipv4-unicast route-target vpn export '1:2'
set vrf name customer protocols bgp address-family ipv4-unicast route-target vpn import '1:2'
set vrf name customer protocols bgp neighbor 2.1.1.10 address-family ipv4-unicast nexthop-self
set vrf name customer protocols bgp neighbor 2.1.1.10 address-family ipv4-unicast soft-reconfiguration inbound
set vrf name customer protocols bgp neighbor 2.1.1.10 ebgp-multihop '3'
set vrf name customer protocols bgp neighbor 2.1.1.10 remote-as '64530'
set vrf name customer protocols bgp neighbor 2.1.1.10 update-source 'eth1'
set vrf name customer protocols bgp neighbor 2.1.1.11 address-family ipv4-unicast soft-reconfiguration inbound
set vrf name customer protocols bgp neighbor 2.1.1.11 ebgp-multihop '3'
set vrf name customer protocols bgp neighbor 2.1.1.11 remote-as '64530'
set vrf name customer protocols bgp neighbor 2.1.1.11 update-source 'eth1'
set vrf name customer protocols bgp parameters log-neighbor-changes
set vrf name customer protocols bgp parameters router-id '10.180.2.2'
set vrf name customer protocols bgp system-as '64531'
set vrf name customer table '120'
we see it as `**inaccessible**`
vyos@vyos-99:~$ **show bgp ipv4 vpn 10.180.2.0/24**
BGP routing table entry for 1:2:10.180.2.0/24, version 0
not allocated
Paths: (1 available, no best path)
Not advertised to any peer
Local
0.0.0.0 (**inaccessible**) from 0.0.0.0 (10.255.254.2) **vrf customer**(6) announce-nh-self
Origin IGP, metric 0, weight 32768, invalid, sourced, local
Extended Community: RT:2:1
Originator: 10.255.254.2
Remote label: 80
Last update: Thu Nov 24 17:10:15 2022I found a workaround , redistributing connected route, it allows to install prefix:
vyos@cust-pe1:~$ show bgp ipv4 vpn 10.180.2.0/24
BGP routing table entry for 1:2:10.180.2.0/24, version 2
not allocated
Paths: (2 available, best #1)
Advertised to non peer-group peers:
1.1.1.1
Local
0.0.0.0 from 0.0.0.0 (10.255.254.2) vrf customer(7) announce-nh-self
Origin incomplete, metric 0, weight 32768, valid, sourced, local, best (First path received)
Extended Community: RT:1:2
Originator: 10.255.254.2
Remote label: 144
Last update: Mon Nov 28 17:22:10 2022