Description
Description
Details
Details
- Version
- -
- Is it a breaking change?
- Perfectly compatible
- Issue type
- Unspecified (please specify)
Status | Subtype | Assigned | Task | ||
---|---|---|---|---|---|
Resolved | FEATURE REQUEST | c-po | T591 Support SRv6 | ||
Resolved | FEATURE REQUEST | c-po | T5849 Add SRv6 route commands |
Event Timeline
Comment Actions
What is the benefit of simply enabling it in the Kernel configuration? I guess there is userspace support required, too? Or does it work out of the box?
Comment Actions
Yes, it's a first step. I think the next step will be wrapper set/show commands for iproute2.
Comment Actions
User space implementation in Zebra 2.0: https://github.com/coreswitch/zebra/blob/master/docs/srv6.md
Comment Actions
@higebu thanks for sharing the link. Looks like they also have some CLI examples. Does this apply to FRR, too? I remember the idea was to move to FRR for routing.
Comment Actions
Implement FRR features for SRv6
- https://docs.frrouting.org/en/stable-9.0/bgp.html?highlight=srv6#l3vpn-srv6
- https://docs.frrouting.org/en/stable-9.0/zebra.html?highlight=segment-routing#segment-routing-ipv6
PR https://github.com/vyos/vyos-1x/pull/2606
VyOS CLI:
set protocols bgp sid vpn per-vrf export '99' set protocols bgp srv6 locator 'foo' set protocols bgp system-as '100' set protocols segment-routing srv6 locator bar prefix '2001:b::/64' set protocols segment-routing srv6 locator foo behavior-usid set protocols segment-routing srv6 locator foo prefix '2001:a::/64'
Will generate in FRR:
router bgp 100 no bgp ebgp-requires-policy no bgp default ipv4-unicast no bgp network import-check ! segment-routing srv6 locator foo exit sid vpn per-vrf export 99 exit ! segment-routing srv6 locators locator bar prefix 2001:b::/64 block-len 40 node-len 24 func-bits 16 exit ! locator foo prefix 2001:a::/64 block-len 40 node-len 24 func-bits 16 behavior usid exit ! exit ! exit ! exit