Skip to content

SRv6 next hops for global BGP routes on FRR#3369

Merged
ipspace merged 1 commit into
devfrom
FRR-SRv6-BGP
May 11, 2026
Merged

SRv6 next hops for global BGP routes on FRR#3369
ipspace merged 1 commit into
devfrom
FRR-SRv6-BGP

Conversation

@ipspace
Copy link
Copy Markdown
Owner

@ipspace ipspace commented May 10, 2026

Based on work done by @jbemmel in #3263

Also includes: cleaned-up integration tests

Based on work done by @jbemmel in #3263

Also includes: cleaned-up integration tests
Copy link
Copy Markdown

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR adds FRR support for SRv6 next-hops on global (non-VPN) BGP routes and updates SRv6 integration tests/docs accordingly.

Changes:

  • Enable features.srv6.bgp for FRR devices and extend the FRR SRv6 templates to configure BGP SRv6 encapsulation/behavior for global unicast routes.
  • Add FRR-specific SRv6 bootstrapping (VRF device creation) when SRv6+BGP is used.
  • Clean up SRv6 integration tests (standardized waits, shared warnings defaults) and refresh SRv6 module documentation to reflect global BGP SRv6 transport support.

Reviewed changes

Copilot reviewed 6 out of 6 changed files in this pull request and generated 1 comment.

Show a summary per file
File Description
tests/integration/srv6/11-isis-ipv6-bgp.yml Standardizes validation waits and pulls in shared warnings defaults; adjusts SRv6 loopback allocation behavior.
tests/integration/srv6/01-isis-ipv4-bgp.yml Same integration test cleanup (wait constants, warnings defaults) plus minor SRv6/BGP-related tweaks.
netsim/devices/frr.yml Marks FRR as supporting srv6.bgp.
netsim/ansible/templates/srv6/frr.j2 Adds SRv6-related VRF device creation and includes SRv6 BGP template when srv6.bgp is enabled.
netsim/ansible/templates/srv6/frr.bgp.j2 Adds global BGP SRv6 neighbor/address-family configuration (including encapsulation-srv6).
docs/module/srv6.md Updates documented supported features/platform support and clarifies srv6.bgp semantics for global routes.

Comment thread netsim/ansible/templates/srv6/frr.bgp.j2
@ipspace ipspace linked an issue May 10, 2026 that may be closed by this pull request
prefix: 32

srv6.allocate_loopback: True # Override the ipv6 loopback address and allocate one from the per-node locator range
srv6.allocate_loopback: False # Keep loopback interface outside of SRv6 SID
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We may want to remove this knob altogether, I initially thought this was a good idea but it does not solve the chicken-and-egg routing problem and mainly causes confusion

{% if srv6.vpn is defined %}
{% for n in bgp.neighbors|default([]) if n.ipv6 is defined %}
{% if srv6.vpn|default(False) or srv6.bgp|default(False) %}
{% for n in bgp.neighbors|default([]) if n.ipv6 is defined and n.type == 'ibgp' %}
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If this is limited to IBGP neighbors, we should probably document that more explicitly

Copy link
Copy Markdown
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Will do. Thank you.

Copy link
Copy Markdown
Collaborator

@jbemmel jbemmel left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Documentation suggestion, deprecating srv6.allocate_loopback could also be a separate PR

@ipspace ipspace merged commit 44d41e9 into dev May 11, 2026
15 checks passed
@ipspace ipspace deleted the FRR-SRv6-BGP branch May 11, 2026 08:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

EVPN/VXLAN-over-IPv6 and global SRv6 on FRR

3 participants