# SRv6 SRv6 is Segment Routing instantiated on the IPv6 data plane, using Segment Identifiers in IPv6 packet headers for routing and services. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## netlab 26.05: BGP-free SRv6 Core, Junos Features DevFeed: [netlab 26.05: BGP-free SRv6 Core, Junos Features]() Original publisher: [Read original article]() Published: 2026-05-19T06:02:00Z Content type: release Language: en Sources: [ipSpace.net blog]() Topics: [BGP](), [SRv6](), [releases](), [IS-IS](), [configuration]() Tags: [bgp](), [configuration](), [devices](), [is-is](), [netlab](), [release](), [release-notes](), [srv6]() ### AI overview The netlab 26.05 release adds support for global BGP routes with SRv6 next hops on FRR and IOS XR, several Junos OSPF and IS-IS capabilities, FortiOS configuration improvements, and Juniper cSRX container support. It also updates scripting, restart, configuration collection, reload testing, topology graph definitions, and multilab operation handling. ### Source excerpt netlab release 26.05 is out. Here are the highlights: Support for global BGP routes with SRv6 next hops (inspired by proof-of-concept by @jvbemmel) on FRR and IOS XR Junos OSPF/IS-IS route redistribution, VRF IS-IS instances, and OSPF interface parameters Streamline and speed up the FortiOS initial device configuration by @a-v-popov Support for Juniper cSRX container by @leec-666 Read more ... ## netlab 25.11: SRv6 on IOS/XE, Streamlined Graphs and Reports DevFeed: [netlab 25.11: SRv6 on IOS/XE, Streamlined Graphs and Reports]() Original publisher: [Read original article]() Published: 2025-11-13T09:02:00Z Content type: release Language: en Sources: [ipSpace.net blog]() Topics: [SRv6](), [releases](), [iOS](), [Graphs](), [Release notes](), [SVG]() Tags: [bugs](), [graph](), [improvements](), [ios](), [jpeg](), [netlab](), [pdf](), [release](), [release-notes](), [reports](), [srv6](), [svg]() ### AI overview The netlab 25.11 release adds SRv6 support on IOS/XE for selected Catalyst 8000v and IOL images, RIPv2/RIPng on OpenBSD, streamlined report and graph creation, and direct SVG, PNG, JPEG, or PDF graph output when D2 or Graphviz is installed. It also includes potentially breaking changes, bug fixes, and other improvements. ### Source excerpt I managed to push out netlab release 25.11 yesterday. Here are the highlights: SRv6 on IOS/XE. It works with Catalyst 8000v, IOL, and IOL layer-2 image, and can be used to build L3VPNs (the IOS/XE image I have supports no other service on top of SRv6) RIPv2/RIPng on OpenBSD A more streamlined way to create reports and graphs The netlab graph command creates the SVG/PNG/JPEG/PDF graph instead of a graph description file if you've installed D2/Graphviz on your system. We also had to make a few potentially-breaking changes, fixed a bunch of bugs, and added over a dozen small improvements. You'll find all the details in the release notes. Read more ... ## SwiNOG 40: Application-Based Source Routing with SRv6 DevFeed: [SwiNOG 40: Application-Based Source Routing with SRv6]() Original publisher: [Read original article]() Published: 2025-08-27T06:28:00Z Content type: opinion Language: en Sources: [ipSpace.net blog]() Topics: [SRv6](), [networking](), [eBPF](), [Routing (disambiguation)]() Tags: [ebpf](), [network](), [networking](), [routing](), [sdn](), [srv6]() ### AI overview This commentary examines an application-based traffic-steering design that uses SRv6, an intent-based system, and eBPF on client hosts to add per-application SRv6 headers. It highlights potentially better scalability than RSVP-based traffic engineering because the design avoids host-to-network signaling, periodic path refreshes, and extra network state, while noting unresolved path-liveness and failure-recovery concerns. ### Source excerpt The we should give different applications different paths across the network idea never dies (even though in many places the residential Internet gives you enough bandwidth to watch 4K videos), and the Leveraging Intent-Based Networking and SRv6 for Dynamic End-to-End Traffic Steering (video) by Severin Dellsperger was an interesting new riff on that ancient grail hunt. Their solution uses SRv6 for traffic steering1, an Intent-Based System2 that figures out paths across the network, and eBPF on client hosts3 to add per-application SRv6 headers to outgoing traffic. Read more ... ## netlab 2.0.0: Hosts, Bridges, and SRv6 DevFeed: [netlab 2.0.0: Hosts, Bridges, and SRv6]() Original publisher: [Read original article]() Published: 2025-05-12T07:05:00Z Content type: release Language: en Sources: [ipSpace.net blog]() Topics: [Release notes](), [releases](), [networking](), [SRv6](), [BGP](), [evpn](), [Firewall](), [Command-line interface](), [Routing (disambiguation)](), [Vagrant]() Tags: [2-0-0](), [bgp](), [cli](), [evpn](), [firewall](), [netlab](), [new-features](), [release](), [release-notes](), [routing](), [srv6](), [vagrant]() ### AI overview The article announces netlab 2.0.0 and summarizes new node roles, bridge support, a rudimentary firewall plugin, SRv6 BGP L3VPN support, a command-line defaults interface, routing and EVPN changes, graph styling, validation improvements, and platform or version changes. ### Source excerpt netlab release 2.0.0 is out. I spent the whole week fixing bugs and running integration tests, so I'm too brain-dead to go into the details. These are the major features we added (more about them in a few days; the details are in the release notes): Well-defined node roles (host, router, bridge) are now available on multiple platforms The firewall.zonebased plugin allows you to configure a rudimentary firewall SRv6: BGP L3VPN support is now available for FRRouting, so you can go out and kick its (free) tires. bridge nodes can be used as simple bridges or to implement multi-access links netlab defaults command provides sysctl-like CLI interface to user/system defaults. Other changes include: Read more ... ## Repost: The Benefits of SRv6 DevFeed: [Repost: The Benefits of SRv6]() Original publisher: [Read original article]() Published: 2024-08-26T05:44:00Z Content type: article Language: en Sources: [ipSpace.net blog]() Topics: [SRv6](), [networking](), [Scalability](), [Routing (disambiguation)](), [SR-MPLS]() Tags: [mpls](), [scalability](), [srv6](), [technical](), [technology]() ### AI overview This technical counterview discusses several claimed benefits of SRv6, including a unified address-and-label space, network programmability, interoperability with non-SRv6 IPv6 routers, and summarizable locators. It argues that locator summarization is especially valuable for scaling routing across very large networks and contrasts this with limitations in summarizing SR-MPLS labels. ### Source excerpt I love bashing SRv6, so it's only fair to post a (technical) counterview, this time coming as a comment from Henk Smit. There are several benefits of SRv6 that I've heard of. Read more ... ## BGP, EVPN, VXLAN, or SRv6? DevFeed: [BGP, EVPN, VXLAN, or SRv6?]() Original publisher: [Read original article]() Published: 2024-07-25T05:55:00Z Content type: article Language: en Sources: [ipSpace.net blog]() Topics: [networking](), [Routing (disambiguation)](), [BGP](), [evpn](), [SRv6](), [MPLS VPN](), [SR-MPLS](), [Virtual Private Network](), [VXLAN]() Tags: [bgp](), [evpn](), [mpls-vpn](), [protocol](), [routing](), [sr-mpls](), [srv6](), [vpn](), [vxlan]() ### AI overview This article explains how to choose among BGP, EVPN, VXLAN, MPLS VPN, SR-MPLS, and SRv6 based on network requirements. It distinguishes ordinary hop-by-hop IP forwarding from traffic engineering and from multiple forwarding domains such as L2VPNs and L3VPNs. ### Source excerpt Daniel Dib asked an interesting question on LinkedIn when considering an RT5-only EVPN design: I'm curious what EVPN provides if all you need is L3. For example, you could run pure L3 BGP fabric if you don't need VRFs or a limited amount of them. If many VRFs are needed, there is MPLS/VPN, SR-MPLS, and SRv6. I received a similar question numerous times in my previous life as a consultant. It's usually caused by vendor marketing polluting PowerPoint slide decks with acronyms without explaining the fundamentals1. Let's fix that. Read more ...