How to configure MP-BGP ipv6 over ipv4 through vrf on v1.4?

hackedbaked · December 12, 2023, 6:35pm

Hello, I am looking for instructions on how to configure MP-BGP ipv6 over ipv4 through a vrf on VyOS 1.4. Can someone point me to the documentation to configure this? or a guide?
I found this guide. However I am not able to use all of the following command:

set protocols bgp 100 address-family ipv6-unicast network 2001:db8::/64

The syntax fails at network as it does not exist on my system.

I know there is a protocol called 6PE referenced in RFC4798 that can be used to accomplish what I need. Is there a way to enable this in VyOS? Note I am connecting to a Cisco IOS XR system on the other end, and we have been able to connect Cisco IOS XR to Juniper in our core using 6PE.

I cant seem to find where else to configure this. Note I am using route-maps. Here is my current configuration, I know its misconfigured. I just need guidance on how to set this up.

set interfaces ethernet eth2 vif 3677 address '10.36.77.1/31'
set interfaces ethernet eth2 vif 3677 address 'fdd1:10:36:77::2/64'
set interfaces ethernet eth2 vif 3677 vrf 'cust77'
set policy prefix-list cust77-network rule 1 action 'permit'
set policy prefix-list cust77-network rule 1 prefix '10.35.77.0/24'
set policy route-map cust77-import-bgp-routes rule 1 action 'permit'
set policy route-map cust77-import-bgp-routes rule 1 match ip route-source prefix-list '10.36.77.0/31'
set vrf name cust77 protocols bgp address-family ipv4-unicast network 10.35.77.0/24
set vrf name cust77 protocols bgp address-family ipv6-unicast network fdd1:10:35:77::0/64
set vrf name cust77 protocols bgp neighbor 10.36.77.0 address-family ipv4-unicast prefix-list export 'cust77-network'
set vrf name cust77 protocols bgp neighbor 10.36.77.0 remote-as '65250'
set vrf name cust77 protocols bgp neighbor fdd1:10:36:77::1 address-family ipv6-unicast
set vrf name cust77 protocols bgp neighbor fdd1:10:36:77::1 remote-as '65250'
set vrf name cust77 protocols bgp route-map 'cust77-import-bgp-routes'
set vrf name cust77 protocols bgp system-as '65077'
set vrf name cust77 table '3677'

Anyone hopefully someone can help, looking forward to replies.

fernando · December 12, 2023, 7:30pm

6PE is not supported by FRR , So this is the reason why is not supported on VyOS :

github.com/FRRouting/frr

FRR as RR into 6PE architecture

opened 03:39PM - 18 Feb 20 UTC

mshuttle76

Hello, I'm testing FRR 7.2 as RR for a IPv4 MPLS backbone. I'm using ISIS+LDP…+BGP. In IPv4 environment all is working correctly. I'm trying to set up 6PE using ipv6 labeled-unicast address-family but I have some problems. The BGP session comes up but BGP does not interpretate correctly the 6PE next-hop. This is the BGP configuration: _address-family ipv6 unicast network 2a02:c7c0:1::9/128 route-map LOCALv6-ORIGINATED maximum-paths ibgp 1 exit-address-family ! address-family ipv6 labeled-unicast neighbor 172.31.255.3 activate neighbor 172.31.255.3 route-map PERMIT-ALL in neighbor 172.31.255.3 route-map PERMIT-ALL out_ From 172.31.255.3 i receive the 6PE routes in this format: #sh ip bgp ipv6 unicast 3269:1::/48 BGP routing table entry for 3269:1::/48 Paths: (1 available, no best path) Not advertised to any peer 6272 3269 ::ffff:ac1f:ff03 (inaccessible) from 172.31.255.3 (185.4.155.3) Origin IGP, localpref 130, invalid, internal Community: 59699:130 59699:200 59699:300 59699:301 59699:399 59699:400 Remote label: 2 Last update: Tue Feb 18 13:11:26 2020 As you can see I get correctly the route with the remote-label because of 6PE but the nexthop remain **"inaccessible"**. The ::ffff:ac1f:ff03 address should be 172.31.255.3 IPv6 translated If it remains inaccessible the prefixes do not going to be advertised to RR clients. In Cisco IOS I see in this way: #sh ip bgp ipv6 unicast 3269:1::/48 BGP routing table entry for 3269:1::/48, version 49 Paths: (1 available, best #1, table default) Advertised to update-groups: 4 Refresh Epoch 1 6272 3269 ::FFFF:172.31.255.3 (metric 5150) from 172.31.255.3 (185.4.155.3) Origin IGP, localpref 130, valid, internal, best Community: 59699:130 59699:200 59699:300 59699:301 59699:399 59699:400 mpls labels in/out nolabel/2 rx pathid: 0, tx pathid: 0x0 What am I missing ? Davide

when FRR work on this feature and will be introduce , we can add it in our system.

hackedbaked · December 12, 2023, 7:59pm

I figured it out.
Its not as complicated as I thought. Just configured the neighbors as ipv4, and added the ipv6 network as a advertised network.

set interfaces ethernet eth2 vif 3677 address '10.36.77.1/31'
set interfaces ethernet eth2 vif 3677 address 'fdd1:10:36:77::2/64'
set interfaces ethernet eth2 vif 3677 vrf 'cust77'
set policy prefix-list cust77-network rule 1 action 'permit'
set policy prefix-list cust77-network rule 1 prefix '10.35.77.0/24'
set policy route-map cust77-import-bgp-routes rule 1 action 'permit'
set policy route-map cust77-import-bgp-routes rule 1 match ip route-source prefix-list '10.36.77.0/31'
set vrf name cust77 protocols bgp address-family ipv4-unicast network 10.35.77.0/24
set vrf name cust77 protocols bgp address-family ipv6-unicast network fdd1:10:35:77::0/64
set vrf name cust77 protocols bgp neighbor 10.36.77.0 address-family ipv4-unicast
set vrf name cust77 protocols bgp neighbor 10.36.77.0 remote-as '65250'
set vrf name cust77 protocols bgp route-map 'cust77-import-bgp-routes'
set vrf name cust77 protocols bgp system-as '65077'
set vrf name cust77 table '3677'

That way bgp established over ipv4 and advertised the networks.

hackedbaked · December 12, 2023, 8:00pm

Right, I did not need 6PE actually. I am good, I found the answer, posted below.

system · January 11, 2024, 8:00pm

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.