# BGP

BGP is an inter-Autonomous System routing protocol that exchanges network reachability information between BGP systems.

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

## Test Real-Life Routing Scenario with netlab

DevFeed: [Test Real-Life Routing Scenario with netlab](<https://devfeed.tech/articles/test-real-life-routing-scenario-with-netlab-134810.md>)

Original publisher: [Read original article](<https://blog.ipspace.net/2026/11/worth-reading-netlab-routing-scenario/>)

Published: 2026-11-16T06:28:00Z

Content type: tutorial

Language: en

Sources: [ipSpace](<https://devfeed.tech/sources/ipspace-net-blog-2.md>)

Topics: [IP routing](<https://devfeed.tech/topics/ip-routing.md>), [BGP](<https://devfeed.tech/topics/bgp.md>)

Tags: [arista](<https://devfeed.tech/tags/arista.md>), [bfd](<https://devfeed.tech/tags/bfd.md>), [bgp](<https://devfeed.tech/tags/bgp.md>), [container](<https://devfeed.tech/tags/container.md>), [customer](<https://devfeed.tech/tags/customer.md>), [netlab](<https://devfeed.tech/tags/netlab.md>), [network](<https://devfeed.tech/tags/network.md>), [ospf](<https://devfeed.tech/tags/ospf.md>), [policies](<https://devfeed.tech/tags/policies.md>), [router](<https://devfeed.tech/tags/router.md>), [routing](<https://devfeed.tech/tags/routing.md>), [topology](<https://devfeed.tech/tags/topology.md>), [worth-reading](<https://devfeed.tech/tags/worth-reading.md>)

### AI overview

Tony Mattke's walkthrough recreates a customer routing scenario in netlab, starting by importing an Arista cEOS container and building a netlab file for an eight-router network. The resulting topology runs BGP, BFD, and OSPF with several routing policies. The supplied excerpt describes the setup but does not provide implementation details or comparisons.

### Source excerpt

In his Labs as Code, Part 2: Real Images, Real Topology article, Tony Mattke described how he used netlab to recreate a customer routing scenario. His article starts with the basics (importing an Arista cEOS container), and then slowly walks you through the process of building a netlab file that results in an 8-router network running BGP, BFD, OSPF, and a few routing policies. Absolutely marvelous reading if you're new to netlab or exploring its capabilities. Read more ...

## How DeepL keeps closest-exit routing during maintenance with AWS Cloud WAN

DevFeed: [How DeepL keeps closest-exit routing during maintenance with AWS Cloud WAN](<https://devfeed.tech/articles/how-deepl-keeps-closest-exit-routing-during-maintenance-with-aws-cloud-wan-124813.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/architecture/how-deepl-keeps-closest-exit-routing-during-maintenance-with-aws-cloud-wan/>)

Author: Guzman Freigedo

Published: 2026-11-09T20:15:09Z

Content type: article

Language: en

Sources: [AWS Architecture Blog](<https://devfeed.tech/sources/aws-architecture-blog.md>)

Topics: [Cloud Networking](<https://devfeed.tech/topics/cloud-networking.md>), [IP routing](<https://devfeed.tech/topics/ip-routing.md>), [BGP](<https://devfeed.tech/topics/bgp.md>), [Amazon Web Services](<https://devfeed.tech/topics/aws.md>), [Amazon VPC](<https://devfeed.tech/topics/amazon-vpc.md>), [MPLS VPN](<https://devfeed.tech/topics/mpls-vpn.md>)

Tags: [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-cloud-wan](<https://devfeed.tech/tags/aws-cloud-wan.md>), [aws-direct-connect](<https://devfeed.tech/tags/aws-direct-connect.md>), [customer-solutions](<https://devfeed.tech/tags/customer-solutions.md>), [deepl](<https://devfeed.tech/tags/deepl.md>), [hybrid](<https://devfeed.tech/tags/hybrid.md>), [maintenance](<https://devfeed.tech/tags/maintenance.md>), [multi-region](<https://devfeed.tech/tags/multi-region.md>), [network](<https://devfeed.tech/tags/network.md>), [routing](<https://devfeed.tech/tags/routing.md>)

### AI overview

DeepL drains a Direct Connect link by prepending its advertised AS_PATH, steering the affected AWS Cloud WAN core network edge to a peer edge while other Regions retain their local exits. At least two prepends are needed to beat the peer paths; DeepL uses five. BGP sessions stay up, avoiding the convergence gap associated with withdrawing routes. For a Dublin drain, DeepL also lowers local preference on its on-premises routers so traffic toward AWS leaves through Copenhagen or Stockholm, then restores both settings after maintenance. The displaced eu-west-1 traffic crosses Regions, creating inter-Region data transfer charges, and default routing does not let DeepL choose which peer location receives it. Since inbound and outbound paths are selected independently, stateful firewalls require symmetric routing. DeepL recommends validating the procedure in non-production and checking Regions without a local Direct Connect location. Its planned Cloud WAN routing policies would allow explicit fallback selection and route summarization.

### Source excerpt

DeepL runs a multi-Region hybrid network across multiple AWS Regions and AWS Direct Connect locations. See how DeepL drains a single Direct Connect link for planned maintenance without packet loss or cross-Region rerouting, using AWS Cloud WAN and an on-premises AS_PATH prepend so every other Region keeps its closest-exit routing.

## Worth Reading: BGP Multi-Homed with Two ISPs and Two Routers

DevFeed: [Worth Reading: BGP Multi-Homed with Two ISPs and Two Routers](<https://devfeed.tech/articles/worth-reading-bgp-multi-homed-with-two-isps-and-two-routers-123020.md>)

Original publisher: [Read original article](<https://blog.ipspace.net/2026/11/worth-reading-bgp-multihomed-two-isps/>)

Published: 2026-11-09T07:25:00Z

Content type: article

Language: en

Sources: [ipSpace](<https://devfeed.tech/sources/ipspace-net-blog-2.md>)

Topics: [BGP](<https://devfeed.tech/topics/bgp.md>), [Network](<https://devfeed.tech/topics/network.md>)

Tags: [bgp](<https://devfeed.tech/tags/bgp.md>), [reading](<https://devfeed.tech/tags/reading.md>), [worth-reading](<https://devfeed.tech/tags/worth-reading.md>)

### AI overview

Suresh Vinasiththamby's BGP multihoming scenario covers practical details for building a working setup with two ISPs and two routers. The recommendation notes that Suresh used netlab to build the lab, making it possible to reproduce the scenario with non-Cisco devices. The excerpt does not specify the configuration details or which BGP requirements the article covers.

### Source excerpt

I was reading the nice BGP Multi-Homed with Two ISPs and Two Routers scenario by Suresh Vinasiththamby - Packetswitch and thought wouldn't it be nice if he were using netlab to build the lab, as that would give you the opportunity to build the same lab with zero hassle using non-Cisco devices. Guess what - Suresh already did just that. I was so glad to see someone using netlab in just the way I imagined it to be used. Read more ...

## Help Me Make the BGP Labs Even Better

DevFeed: [Help Me Make the BGP Labs Even Better](<https://devfeed.tech/articles/help-me-make-the-bgp-labs-even-better-114308.md>)

Original publisher: [Read original article](<https://blog.ipspace.net/2026/11/bgp-labs-further-reading/>)

Published: 2026-11-03T07:24:00Z

Content type: opinion

Language: en

Sources: [ipSpace](<https://devfeed.tech/sources/ipspace-net-blog-2.md>)

Topics: [BGP](<https://devfeed.tech/topics/bgp.md>), [Documentation](<https://devfeed.tech/topics/documentation.md>), [Claude](<https://devfeed.tech/topics/claude.md>), [Open Source](<https://devfeed.tech/topics/open-source.md>)

Tags: [basics](<https://devfeed.tech/tags/basics.md>), [bgp](<https://devfeed.tech/tags/bgp.md>), [blog-posts](<https://devfeed.tech/tags/blog-posts.md>), [claude](<https://devfeed.tech/tags/claude.md>), [diversity](<https://devfeed.tech/tags/diversity.md>), [documentation](<https://devfeed.tech/tags/documentation.md>), [labs](<https://devfeed.tech/tags/labs.md>), [links](<https://devfeed.tech/tags/links.md>), [reading](<https://devfeed.tech/tags/reading.md>)

### AI overview

The author is adding "Further Reading" sections to BGP lab exercises and asks readers to contribute relevant vendor documentation and blog links through pull requests or issues. Claude found related blog posts readily, but precise vendor documentation links were harder to identify: many vendor docs use changeable auto-generated anchors and bury practical configuration details, such as BGP neighbor commands, in lengthy explanations. The author also wants more varied entry-level BGP resources. Readers can edit the relevant lab's Further Reading section via its GitHub page and submit a PR. The labs are free and open source, with contributor recognition but no budget for rewards.

### Source excerpt

I decided to add "Further Reading" sections to BGP lab exercises, containing links to vendor documentation and useful related blog posts. I naively expected to offload the job to Claude, commit the results, and move on. The "related blog posts" were a piece of cake; precise links to relevant vendor documentation turned out to be more of a challenge. TL&DR: I would love to get your suggestions for further reading as PRs in the BGP Labs repo. Apart from FRRouting, the vendor documentation is mostly generated from whatever internal system and uses auto-generated anchors that can change at any moment - somewhat "suboptimal" for what I wanted to do. Read more ...

## netlab: Testing Network Protocol Implementations

DevFeed: [netlab: Testing Network Protocol Implementations](<https://devfeed.tech/articles/netlab-testing-network-protocol-implementations-112470.md>)

Original publisher: [Read original article](<https://blog.ipspace.net/2026/11/netlab-device-test-harness/>)

Published: 2026-11-02T07:18:00Z

Content type: tutorial

Language: en

Sources: [ipSpace](<https://devfeed.tech/sources/ipspace-net-blog-2.md>)

Topics: [Protocol (disambiguation)](<https://devfeed.tech/topics/protocol.md>), [BGP](<https://devfeed.tech/topics/bgp.md>), [developer setup](<https://devfeed.tech/topics/developer-setup.md>)

Tags: [bgp](<https://devfeed.tech/tags/bgp.md>), [cisco](<https://devfeed.tech/tags/cisco.md>), [configuration](<https://devfeed.tech/tags/configuration.md>), [container](<https://devfeed.tech/tags/container.md>), [containers](<https://devfeed.tech/tags/containers.md>), [eigrp](<https://devfeed.tech/tags/eigrp.md>), [implementation](<https://devfeed.tech/tags/implementation.md>), [infrastructure](<https://devfeed.tech/tags/infrastructure.md>), [interoperability](<https://devfeed.tech/tags/interoperability.md>), [ios](<https://devfeed.tech/tags/ios.md>), [ios-xe](<https://devfeed.tech/tags/ios-xe.md>), [lab](<https://devfeed.tech/tags/lab.md>), [labs](<https://devfeed.tech/tags/labs.md>), [netlab](<https://devfeed.tech/tags/netlab.md>), [network-device](<https://devfeed.tech/tags/network-device.md>), [repository](<https://devfeed.tech/tags/repository.md>), [server](<https://devfeed.tech/tags/server.md>), [source-code](<https://devfeed.tech/tags/source-code.md>), [test](<https://devfeed.tech/tags/test.md>), [testing](<https://devfeed.tech/tags/testing.md>)

### AI overview

The excerpt reports that netlab worked for testing OpenEIGRP-Cisco IOS interoperability and gives setup guidance for similar protocol tests. It recommends container labs via the `clab` provider for faster startup than virtual machines; IOL is suggested for IOS/XE, with IOLL2 faster but not guaranteed to support all features. For Nexus OS, it suggests obtaining the latest registered download and using vrnetlab to make a container. Labs can use one topology per directory or multiple topology files, with filenames specified to `netlab create` or `netlab up` in the latter case; defaults can be project-wide. The author recommends putting FRR settings in defaults and using wildcard groups to assign device types. Netlab's EIGRP support is described as minimal and potentially insufficient, while it can handle other configuration such as addressing, OSPF, BGP, and static routes. Custom Jinja2 templates are suggested for EIGRP configuration, with possible later work toward generic support or OpenEIGRP integration.

### Source excerpt

Donnie Savage decided to use netlab to test OpenEIGRP-Cisco IOS interoperability (TL&DR: it works and the source code is in Donnie's EIGRP repository). He asked me for a few hints before setting up his test server. This is what I sent him; you might find it useful if you ever decide to use netlab to test a new network device/protocol implementation. Read more ...

## BGP Graceful Shutdown

DevFeed: [BGP Graceful Shutdown](<https://devfeed.tech/articles/bgp-graceful-shutdown-112642.md>)

Original publisher: [Read original article](<https://blog.j2sw.com/netops/bgp-graceful-shutdown/>)

Author: j2sw

Published: 2026-11-02T05:09:37Z

Content type: article

Language: en

Sources: [Justin Wilson (j2sw)](<https://devfeed.tech/sources/justin-wilson-j2sw.md>)

Topics: [BGP](<https://devfeed.tech/topics/bgp.md>)

Tags: [bgp](<https://devfeed.tech/tags/bgp.md>), [bgp-communities](<https://devfeed.tech/tags/bgp-communities.md>), [control](<https://devfeed.tech/tags/control.md>), [exchange](<https://devfeed.tech/tags/exchange.md>), [fd-ix](<https://devfeed.tech/tags/fd-ix.md>), [graceful-shutdown](<https://devfeed.tech/tags/graceful-shutdown.md>), [internet-peering](<https://devfeed.tech/tags/internet-peering.md>), [isp](<https://devfeed.tech/tags/isp.md>), [isp-routing](<https://devfeed.tech/tags/isp-routing.md>), [maintenance](<https://devfeed.tech/tags/maintenance.md>), [network](<https://devfeed.tech/tags/network.md>), [network-maintenance](<https://devfeed.tech/tags/network-maintenance.md>), [network-operations](<https://devfeed.tech/tags/network-operations.md>), [peering](<https://devfeed.tech/tags/peering.md>), [policies](<https://devfeed.tech/tags/policies.md>), [policy](<https://devfeed.tech/tags/policy.md>), [sessions](<https://devfeed.tech/tags/sessions.md>), [shutdown](<https://devfeed.tech/tags/shutdown.md>), [traffic](<https://devfeed.tech/tags/traffic.md>)

### AI overview

BGP graceful shutdown lets operators shift traffic before taking a session down by marking routes with the RFC 8326 GRACEFUL_SHUTDOWN community (65535:0). A neighbor that has policy to honor the community can lower those routes' local preference; RFC 8326 recommends 0. Routes remain available, so another usable path can take over, but reachability cannot be preserved if no alternative exists. Traffic direction matters: operators can control outbound path selection, while inbound shifts depend on neighboring networks' policies. At an Internet exchange, behavior also depends on whether route servers preserve and distribute the community and whether members honor it. Graceful shutdown prepares for a planned outage; graceful restart instead holds routes temporarily after an unexpected session loss, assuming the restarting router still forwards traffic.

### Source excerpt

BGP sessions can drop for many reasons. Dropping a session causes BGP to withdraw the routes learned through that neighbor. If it's unexpected, this can cause congestion or other issues. The graceful shutdown option in BGP can help mitigate this. BGP graceful shutdown lets you move traffic before taking the session down. Rather than waiting ... Read more The post BGP Graceful Shutdown appeared first on Justin Wilson (j2sw).

## Direct VM networking in AWS: Introducing BGP cloud connector on Red Hat OpenShift Service on AWS

DevFeed: [Direct VM networking in AWS: Introducing BGP cloud connector on Red Hat OpenShift Service on AWS](<https://devfeed.tech/articles/direct-vm-networking-in-aws-introducing-bgp-cloud-connector-on-red-hat-openshift-service-on-aws-109785.md>)

Original publisher: [Read original article](<https://www.redhat.com/en/blog/direct-vm-networking-aws-introducing-bgp-cloud-connector-red-hat-openshift-service-aws>)

Author: Daniel Axelrod

Published: 2026-10-30T00:00:00Z

Content type: release

Language: en

Sources: [Red Hat Blog](<https://devfeed.tech/sources/red-hat-blog.md>)

Topics: [BGP](<https://devfeed.tech/topics/bgp.md>), [Amazon VPC](<https://devfeed.tech/topics/amazon-vpc.md>), [Cloud Networking](<https://devfeed.tech/topics/cloud-networking.md>), [virtual machines](<https://devfeed.tech/topics/virtual-machines.md>), [Amazon EC2](<https://devfeed.tech/topics/amazon-ec2.md>), [NAT and SNAT](<https://devfeed.tech/topics/nat-and-snat.md>)

Tags: [2](<https://devfeed.tech/tags/2.md>), [3](<https://devfeed.tech/tags/3.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [aws](<https://devfeed.tech/tags/aws.md>), [bgp](<https://devfeed.tech/tags/bgp.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [cloud-environments](<https://devfeed.tech/tags/cloud-environments.md>), [cluster](<https://devfeed.tech/tags/cluster.md>), [customers](<https://devfeed.tech/tags/customers.md>), [environments](<https://devfeed.tech/tags/environments.md>), [hat](<https://devfeed.tech/tags/hat.md>), [hit](<https://devfeed.tech/tags/hit.md>), [ip](<https://devfeed.tech/tags/ip.md>), [networking](<https://devfeed.tech/tags/networking.md>), [openshift](<https://devfeed.tech/tags/openshift.md>), [red](<https://devfeed.tech/tags/red.md>), [red-hat](<https://devfeed.tech/tags/red-hat.md>), [red-hat-openshift](<https://devfeed.tech/tags/red-hat-openshift.md>), [service](<https://devfeed.tech/tags/service.md>), [vm](<https://devfeed.tech/tags/vm.md>)

### AI overview

BGP cloud connector enables direct routing between a ClusterUserDefinedNetwork (CUDN) and the AWS VPC for Red Hat OpenShift Service on AWS clusters running version 4.22 or later, so external systems can reach guest VMs at their own IP addresses without worker-node NAT. Worker nodes advertise CUDN routes to Amazon VPC Route Server using BGP; the server updates VPC route tables and selects one worker as the gateway for each IP prefix. If that gateway fails, BGP failure detection lets Route Server switch the route to a healthy worker. The text describes benefits for source-IP-based firewall rules, Active Directory Dynamic DNS, and clustered software that expects consistent member IPs. A demonstrated EC2 instance connects directly to a VM service in the same VPC. The excerpt points readers to product documentation for setup details.

### Source excerpt

When migrating virtual machines (VMs) to the cloud, virtualization engineers hit a familiar wall: how do you route traffic directly to a Red Hat OpenShift Virtualization guest VM using that VM's own IP address?OpenShift Virtualization has long offered a solution to this problem with localnets--as long as the cluster is using an on-premise Layer 2 network. Most cloud providers only expose Layer 3 on their networks, however, forcing OpenShift Virtualization customers in cloud environments to redesign their networking architecture. Without direct IP routing in the cloud, virtualization teams w

## VyOS Project October 2026 Update

DevFeed: [VyOS Project October 2026 Update](<https://devfeed.tech/articles/vyos-project-october-2026-update-103462.md>)

Original publisher: [Read original article](<https://blog.vyos.io/vyos-project-october-2026-update>)

Author: taras@vyos.io (Taras Pudiak)

Published: 2026-10-27T12:44:59Z

Content type: news

Language: en

Sources: [VyOS](<https://devfeed.tech/sources/vyos-blog.md>)

Topics: [IP routing](<https://devfeed.tech/topics/ip-routing.md>), [BGP](<https://devfeed.tech/topics/bgp.md>), [DHCP](<https://devfeed.tech/topics/dhcp.md>), [Access Control](<https://devfeed.tech/topics/access-control.md>), [MPLS VPN](<https://devfeed.tech/topics/mpls-vpn.md>), [VXLAN](<https://devfeed.tech/topics/vxlan.md>), [Segment Routing over IPv6 (SRv6)](<https://devfeed.tech/topics/segment-routing-over-ipv6-srv6.md>), [Segment Routing with MPLS Labels (SR-MPLS)](<https://devfeed.tech/topics/segment-routing-with-mpls-labels-sr-mpls.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [bgp](<https://devfeed.tech/tags/bgp.md>), [commit](<https://devfeed.tech/tags/commit.md>), [community](<https://devfeed.tech/tags/community.md>), [development-update](<https://devfeed.tech/tags/development-update.md>), [dhcp](<https://devfeed.tech/tags/dhcp.md>), [firewall](<https://devfeed.tech/tags/firewall.md>), [frr](<https://devfeed.tech/tags/frr.md>), [mpls](<https://devfeed.tech/tags/mpls.md>), [october](<https://devfeed.tech/tags/october.md>), [october-2026](<https://devfeed.tech/tags/october-2026.md>), [openvpn](<https://devfeed.tech/tags/openvpn.md>), [ospf](<https://devfeed.tech/tags/ospf.md>), [project](<https://devfeed.tech/tags/project.md>), [routing](<https://devfeed.tech/tags/routing.md>), [security](<https://devfeed.tech/tags/security.md>), [srv6](<https://devfeed.tech/tags/srv6.md>), [update](<https://devfeed.tech/tags/update.md>), [vpp](<https://devfeed.tech/tags/vpp.md>), [vxlan](<https://devfeed.tech/tags/vxlan.md>), [vyos](<https://devfeed.tech/tags/vyos.md>), [vyos-project](<https://devfeed.tech/tags/vyos-project.md>), [vyos-rolling](<https://devfeed.tech/tags/vyos-rolling.md>), [vyosnetwork](<https://devfeed.tech/tags/vyosnetwork.md>)

### AI overview

The September-October 2026 Rolling update fixes disruptive or misleading commits and adds routing, firewall, DHCP, VPP, and OpenVPN capabilities. FRR configuration is now rendered in forms that avoid repeated resets or route processing; commit and large prefix-list checks are faster, and commits reject deletion of interfaces still referenced elsewhere. Additions include MPLS Inter-AS label switching, BGP-LS distribution for SRv6, VXLAN firewall-mark transfer, DHCP client classes, and OpenVPN DCO support for ChaCha20-Poly1305. The update also fixes UTC and daylight-saving firewall time windows and reports a VPP test increase from 84 to 140 Mpps with 64-byte packets on 100G ConnectX-6 NICs. Read the upgrade notes: affected Rolling builds had an OIDC audience-check flaw, and OIDC configurations now require an audience; commands, defaults, and NAT load-balancing behavior also change.

### Source excerpt

Hello, Community! This update covers the changes that landed in Rolling in September and October, and looking back, the month has a theme that nobody planned. A commit is a promise: change what I asked for, and leave everything else alone. This month, we found several places where VyOS broke that promise. With certain routing options set, a commit that only touched a route-map description could reset BGP sessions or OSPF adjacencies. Elsewhere, configurations committed without complaint and then quietly did something else. Much of this post is about closing those gaps, and about the community members who found several of them on their own routers. There is new ground too: MPLS Inter-AS label switching, BGP-LS for SRv6, a VXLAN extension that carries firewall marks, and updates to DHCP, VPP, and OpenVPN. Please read the security section before you upgrade.

## APNIC 62 workshops help build network security, automation, and routing expertise across the region

DevFeed: [APNIC 62 workshops help build network security, automation, and routing expertise across the region](<https://devfeed.tech/articles/apnic-62-workshops-help-build-network-security-automation-and-routing-expertise-across-the-region-101319.md>)

Original publisher: [Read original article](<https://blog.apnic.net/2026/10/27/apnic-62-workshops-help-build-network-security-automation-and-routing-expertise-across-the-region/>)

Author: Sheryl Hermoso

Published: 2026-10-27T01:27:49Z

Content type: news

Language: en

Sources: [APNIC Blog](<https://devfeed.tech/sources/apnic-blog.md>)

Topics: [network security](<https://devfeed.tech/topics/network-security.md>), [Network Operations](<https://devfeed.tech/topics/network-operations.md>), [Automation](<https://devfeed.tech/topics/automation.md>), [IP routing](<https://devfeed.tech/topics/ip-routing.md>), [saltstack](<https://devfeed.tech/topics/saltstack.md>), [Routing Security](<https://devfeed.tech/topics/routing-security.md>), [Network Configuration](<https://devfeed.tech/topics/network-configuration.md>), [BGP](<https://devfeed.tech/topics/bgp.md>)

Tags: [apnic-62](<https://devfeed.tech/tags/apnic-62.md>), [apnic-academy](<https://devfeed.tech/tags/apnic-academy.md>), [apnic-training](<https://devfeed.tech/tags/apnic-training.md>), [automation](<https://devfeed.tech/tags/automation.md>), [bgp](<https://devfeed.tech/tags/bgp.md>), [cryptography](<https://devfeed.tech/tags/cryptography.md>), [ddos](<https://devfeed.tech/tags/ddos.md>), [development](<https://devfeed.tech/tags/development.md>), [distributed-denial-of-service](<https://devfeed.tech/tags/distributed-denial-of-service.md>), [dns](<https://devfeed.tech/tags/dns.md>), [dns-security](<https://devfeed.tech/tags/dns-security.md>), [ethernet](<https://devfeed.tech/tags/ethernet.md>), [event-driven](<https://devfeed.tech/tags/event-driven.md>), [events](<https://devfeed.tech/tags/events.md>), [evpn](<https://devfeed.tech/tags/evpn.md>), [flex](<https://devfeed.tech/tags/flex.md>), [network](<https://devfeed.tech/tags/network.md>), [network-operators](<https://devfeed.tech/tags/network-operators.md>), [network-security](<https://devfeed.tech/tags/network-security.md>), [region](<https://devfeed.tech/tags/region.md>), [routing](<https://devfeed.tech/tags/routing.md>), [security](<https://devfeed.tech/tags/security.md>), [skills](<https://devfeed.tech/tags/skills.md>), [workshops](<https://devfeed.tech/tags/workshops.md>)

### AI overview

APNIC 62's workshops gave network engineers practical training in security, automation, and advanced service provider routing. The APNIC Academy security and automation workshops drew 55 participants; a separately organized INNOG routing workshop drew 27. Security exercises covered topics including DDoS mitigation, BGP and DNS security, RPKI, and open-source tools. The automation workshop covered configuration management, SALT, YAML and Jinja, and event-driven workflows, using a train-the-trainer format so participants could share skills with their teams and communities. INNOG's three-day routing workshop was designed for experienced provider engineers and used hands-on labs for Segment Routing, EVPN, Flex-Algo, Containerlab, and telemetry-driven monitoring. Participant feedback described plans to apply the training to security practices, incident response automation, and safer network operations.

### Source excerpt

More than 80 network engineers and operators strengthened their skills at APNIC 62 through hands-on workshops in network security, automation, and next-generation service provider routing.

## Azure Firewall Security: How Routing Decisions Can Bypass Inspection

DevFeed: [Azure Firewall Security: How Routing Decisions Can Bypass Inspection](<https://devfeed.tech/articles/azure-firewall-security-how-routing-decisions-can-bypass-inspection-97406.md>)

Original publisher: [Read original article](<https://hackernoon.com/azure-firewall-security-how-routing-decisions-can-bypass-inspection?source=rss>)

Author: Ramesh Subramani

Published: 2026-10-23T07:03:01Z

Content type: article

Language: en

Sources: [HackerNoon](<https://devfeed.tech/sources/hackernoon.md>)

Topics: [Azure](<https://devfeed.tech/topics/azure.md>), [Firewall](<https://devfeed.tech/topics/firewall.md>), [IP routing](<https://devfeed.tech/topics/ip-routing.md>), [BGP](<https://devfeed.tech/topics/bgp.md>), [Network Segmentation](<https://devfeed.tech/topics/network-segmentation.md>), [Load Balancing](<https://devfeed.tech/topics/load-balancing.md>)

Tags: [2](<https://devfeed.tech/tags/2.md>), [3](<https://devfeed.tech/tags/3.md>), [about](<https://devfeed.tech/tags/about.md>), [actions](<https://devfeed.tech/tags/actions.md>), [admin](<https://devfeed.tech/tags/admin.md>), [all](<https://devfeed.tech/tags/all.md>), [allowed](<https://devfeed.tech/tags/allowed.md>), [azure](<https://devfeed.tech/tags/azure.md>), [bgp](<https://devfeed.tech/tags/bgp.md>), [bypass](<https://devfeed.tech/tags/bypass.md>), [can](<https://devfeed.tech/tags/can.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [cloud-migration-strategy](<https://devfeed.tech/tags/cloud-migration-strategy.md>), [cloud-security](<https://devfeed.tech/tags/cloud-security.md>), [cybersecurity](<https://devfeed.tech/tags/cybersecurity.md>), [firewall](<https://devfeed.tech/tags/firewall.md>), [guidance](<https://devfeed.tech/tags/guidance.md>), [inspection](<https://devfeed.tech/tags/inspection.md>), [network-security](<https://devfeed.tech/tags/network-security.md>), [practical](<https://devfeed.tech/tags/practical.md>), [routing](<https://devfeed.tech/tags/routing.md>), [security](<https://devfeed.tech/tags/security.md>), [security-architecture](<https://devfeed.tech/tags/security-architecture.md>), [traffic](<https://devfeed.tech/tags/traffic.md>), [validation](<https://devfeed.tech/tags/validation.md>), [with](<https://devfeed.tech/tags/with.md>), [zero-trust](<https://devfeed.tech/tags/zero-trust.md>)

### AI overview

Azure firewall rules cannot inspect traffic that routing sends around the firewall. Route selection uses longest-prefix match first, so a more specific BGP route can beat a broader UDR; effective routes and Network Watcher Next hop can reveal which path Azure selects. Correct the route design, then validate forwarding and the return path: stateful inspection can fail or be incomplete when replies bypass the firewall or reach a different instance without shared session state. The article also cautions that disabling BGP propagation is broader and may disrupt other connectivity, SNAT hides the original client address and consumes NAT resources, and Virtual WAN routing intent supports only specified security solutions and configurations. Restrict route-table permissions as security-sensitive access, and validate representative flows in both directions. For new flow logging, it points to VNet flow logs because NSG flow log creation is no longer supported.

### Source excerpt

Learn how Azure routing decisions can bypass firewall inspection, with practical guidance on UDRs, BGP, asymmetric routing, and traffic validation.

## Using External Tools in BGP Labs

DevFeed: [Using External Tools in BGP Labs](<https://devfeed.tech/articles/using-external-tools-in-bgp-labs-95139.md>)

Original publisher: [Read original article](<https://blog.ipspace.net/2026/10/bgp-labs-external-tools/>)

Published: 2026-10-22T07:51:00Z

Content type: article

Language: en

Sources: [ipSpace](<https://devfeed.tech/sources/ipspace-net-blog-2.md>)

Topics: [BGP](<https://devfeed.tech/topics/bgp.md>), [Tool](<https://devfeed.tech/topics/tool.md>)

Tags: [bgp](<https://devfeed.tech/tags/bgp.md>), [codespaces](<https://devfeed.tech/tags/codespaces.md>), [external](<https://devfeed.tech/tags/external.md>), [labs](<https://devfeed.tech/tags/labs.md>), [netlab](<https://devfeed.tech/tags/netlab.md>), [tools](<https://devfeed.tech/tags/tools.md>)

### AI overview

The document explains how to start external tools, including network-xray, in open-source BGP configuration labs without changing the lab topology. It also describes how this works in GitHub Codespaces and says lab instructions now point readers to an optional tool setup step.

### Source excerpt

After Kazuya Takahashi released his wonderful network-xray tool and added it as an external tool to the open-source BGP configuration labs, I wrote a short document explaining how to start external tools in your BGP labs without changing the lab topology, and how it works in GitHub Codespaces (hint: wonderfully). I also modified all lab instructions to include a pointer to the optional tool-setup step. Happy labbing ;)

## BGP-Free Network Core with SRv6

DevFeed: [BGP-Free Network Core with SRv6](<https://devfeed.tech/articles/bgp-free-network-core-with-srv6-66530.md>)

Original publisher: [Read original article](<https://blog.ipspace.net/2026/10/srv6-bgp-free-core/>)

Published: 2026-10-07T05:27:00Z

Content type: article

Language: en

Sources: [ipSpace](<https://devfeed.tech/sources/ipspace-net-blog-2.md>)

Topics: [BGP](<https://devfeed.tech/topics/bgp.md>), [Segment Routing over IPv6 (SRv6)](<https://devfeed.tech/topics/segment-routing-over-ipv6-srv6.md>), [IP routing](<https://devfeed.tech/topics/ip-routing.md>), [Network](<https://devfeed.tech/topics/network.md>)

Tags: [bgp](<https://devfeed.tech/tags/bgp.md>), [ipv6](<https://devfeed.tech/tags/ipv6.md>), [mpls](<https://devfeed.tech/tags/mpls.md>), [network](<https://devfeed.tech/tags/network.md>), [srv6](<https://devfeed.tech/tags/srv6.md>)

### AI overview

The article explains how SRv6 supports a BGP-free network core, where edge routers exchange BGP routes while core routers forward traffic without carrying customer routes. It describes IPv6 transport, extended next hops, and the SRv6 Prefix-SID information used to carry customer IPv4 or IPv6 packets through the core.

### Source excerpt

The concept of a BGP-free core is decades old: The network core routers (P routers in MPLS terminology) do not carry BGP routes; BGP routes are exchanged solely between network edge routers. The core routers thus cannot use the customer IP addresses in the packet forwarding process. The edge routers (PE routers in MPLS terminology) know how to reach BGP next hops using an encapsulation mechanism that makes IP packets opaque to the network core. Interestingly, the concept predates Cisco's Tag Switching (later MPLS) by at least a decade; that's how all ATM and Frame Relay networks worked (with ATM VPI/VCI or Frame Relay DLCI used as the in-network addresses). Read more ...

## EVPN-VXLAN with Internet DCI on VyOS

DevFeed: [EVPN-VXLAN with Internet DCI on VyOS](<https://devfeed.tech/articles/evpn-vxlan-with-internet-dci-on-vyos-65711.md>)

Original publisher: [Read original article](<https://blog.vyos.io/evpn-vxlan-internet-dci-vyos>)

Author: f.maidana@vyos.io (Fernando Maidana)

Published: 2026-10-06T11:44:59Z

Content type: article

Language: en

Sources: [VyOS](<https://devfeed.tech/sources/vyos-blog.md>)

Topics: [VXLAN](<https://devfeed.tech/topics/vxlan.md>), [BGP](<https://devfeed.tech/topics/bgp.md>), [evpn](<https://devfeed.tech/topics/evpn.md>), [Cloud Networking](<https://devfeed.tech/topics/cloud-networking.md>), [control-plane](<https://devfeed.tech/topics/control-plane.md>), [data centers](<https://devfeed.tech/topics/data-centers.md>), [Routing Security](<https://devfeed.tech/topics/routing-security.md>)

Tags: [anycast-gateway](<https://devfeed.tech/tags/anycast-gateway.md>), [bgp](<https://devfeed.tech/tags/bgp.md>), [bgp-evpn](<https://devfeed.tech/tags/bgp-evpn.md>), [centralized-routing](<https://devfeed.tech/tags/centralized-routing.md>), [data-center](<https://devfeed.tech/tags/data-center.md>), [data-center-interconnect](<https://devfeed.tech/tags/data-center-interconnect.md>), [data-centers](<https://devfeed.tech/tags/data-centers.md>), [dci](<https://devfeed.tech/tags/dci.md>), [distributed-routing](<https://devfeed.tech/tags/distributed-routing.md>), [evpn](<https://devfeed.tech/tags/evpn.md>), [internet](<https://devfeed.tech/tags/internet.md>), [layer-2-dci](<https://devfeed.tech/tags/layer-2-dci.md>), [network](<https://devfeed.tech/tags/network.md>), [routing](<https://devfeed.tech/tags/routing.md>), [vxlan](<https://devfeed.tech/tags/vxlan.md>)

### AI overview

This article outlines an Internet-based data center interconnect built with VyOS, using BGP EVPN as the control plane and VXLAN as the data plane. It compares centralized and distributed routing, discusses Layer 2 and Layer 3 interconnect choices, and covers resiliency considerations such as redundancy, convergence, gateway placement, and failure domains.

### Source excerpt

Modern data centers increasingly rely on IP fabrics that use BGP EVPN as the control plane and VXLAN as the data plane. This standards-based architecture extends Layer 2 and Layer 3 services across an IP underlay while keeping a clear separation between the physical network and tenant or service networks. This post summarizes the routing models, interconnect options, and resiliency considerations behind an Internet-based Data Center Interconnect (DCI) built on VyOS. For the complete configuration and validation steps, see the EVPN-VXLAN DCI Deployment Guide.

## Is RPKI becoming harmful to BGP stability?

DevFeed: [Is RPKI becoming harmful to BGP stability?](<https://devfeed.tech/articles/is-rpki-becoming-harmful-to-bgp-stability-63693.md>)

Original publisher: [Read original article](<https://blog.apnic.net/2026/10/02/is-rpki-becoming-harmful-to-bgp-stability/>)

Author: Samuele Quinzi

Published: 2026-10-01T23:18:58Z

Content type: article

Language: en

Sources: [APNIC Blog](<https://devfeed.tech/sources/apnic-blog.md>)

Topics: [BGP](<https://devfeed.tech/topics/bgp.md>), [Routing Security](<https://devfeed.tech/topics/routing-security.md>)

Tags: [bgp](<https://devfeed.tech/tags/bgp.md>), [distributed](<https://devfeed.tech/tags/distributed.md>), [guest-post](<https://devfeed.tech/tags/guest-post.md>), [routing](<https://devfeed.tech/tags/routing.md>), [rpki](<https://devfeed.tech/tags/rpki.md>), [tech-matters](<https://devfeed.tech/tags/tech-matters.md>)

### AI overview

An analysis of more than 11 years of RPKI and BGP data finds that RPKI-related updates are increasing but remain well below 1% of observed BGP update volume. The findings suggest that RPKI currently adds little routing noise, while continued monitoring remains important as deployment grows.

### Source excerpt

Guest Post: Could the growing deployment of RPKI become a threat to routing stability? This study analyses more than 11 years of RPKI and BGP data, measuring how much routing activity can be associated with RPKI-related changes.

## In the age of AI, teaching networking principles remains more important than learning protocols

DevFeed: [In the age of AI, teaching networking principles remains more important than learning protocols](<https://devfeed.tech/articles/in-the-age-of-ai-teaching-networking-principles-remains-more-important-than-learning-protocols-58412.md>)

Original publisher: [Read original article](<https://www.theregister.com/networks/2026/09/23/in-the-age-of-ai-teaching-networking-principles-remains-more-important-than-learning-protocols/5298478>)

Author: Bruce Davie

Published: 2026-09-23T06:25:26Z

Content type: article

Language: en

Sources: [theregister](<https://devfeed.tech/sources/www-theregister-com-articles.md>)

Topics: [Learning](<https://devfeed.tech/topics/learning.md>), [protocols](<https://devfeed.tech/topics/protocols.md>), [systems](<https://devfeed.tech/topics/systems.md>), [Programming](<https://devfeed.tech/topics/programming.md>), [BGP](<https://devfeed.tech/topics/bgp.md>), [Artificial Intelligence](<https://devfeed.tech/topics/ai.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [education](<https://devfeed.tech/tags/education.md>), [learning](<https://devfeed.tech/tags/learning.md>), [networking](<https://devfeed.tech/tags/networking.md>), [networks](<https://devfeed.tech/tags/networks.md>), [principles](<https://devfeed.tech/tags/principles.md>), [programming](<https://devfeed.tech/tags/programming.md>), [protocols](<https://devfeed.tech/tags/protocols.md>), [systems-approach](<https://devfeed.tech/tags/systems-approach.md>), [teaching](<https://devfeed.tech/tags/teaching.md>)

### AI overview

An educator reflects on a SIGCOMM workshop about networking education in the age of AI. The discussion emphasizes teaching networking principles, classroom labs, programming exercises, and other methods for engaging students.

### Source excerpt

Kids can learn why BGP matters in a semester, but that won't leave them ready to implement it

## Understanding ASPA: The next step in routing security

DevFeed: [Understanding ASPA: The next step in routing security](<https://devfeed.tech/articles/understanding-aspa-the-next-step-in-routing-security-58378.md>)

Original publisher: [Read original article](<https://blog.apnic.net/2026/09/23/understanding-aspa-the-next-step-in-routing-security/>)

Author: Dale Roberts

Published: 2026-09-23T04:55:18Z

Content type: news

Language: en

Sources: [APNIC Blog](<https://devfeed.tech/sources/apnic-blog.md>)

Topics: [Routing Security](<https://devfeed.tech/topics/routing-security.md>), [Security](<https://devfeed.tech/topics/security.md>), [BGP](<https://devfeed.tech/topics/bgp.md>), [Network Operations](<https://devfeed.tech/topics/network-operations.md>), [Monitoring](<https://devfeed.tech/topics/monitoring.md>), [Internet](<https://devfeed.tech/topics/internet.md>)

Tags: [apnic-academy](<https://devfeed.tech/tags/apnic-academy.md>), [aspa](<https://devfeed.tech/tags/aspa.md>), [bgp](<https://devfeed.tech/tags/bgp.md>), [development](<https://devfeed.tech/tags/development.md>), [monitoring](<https://devfeed.tech/tags/monitoring.md>), [network](<https://devfeed.tech/tags/network.md>), [network-operations](<https://devfeed.tech/tags/network-operations.md>), [routing](<https://devfeed.tech/tags/routing.md>), [routing-security](<https://devfeed.tech/tags/routing-security.md>), [rov](<https://devfeed.tech/tags/rov.md>), [rpki](<https://devfeed.tech/tags/rpki.md>), [security](<https://devfeed.tech/tags/security.md>), [tech-matters](<https://devfeed.tech/tags/tech-matters.md>), [webinar](<https://devfeed.tech/tags/webinar.md>)

### AI overview

APNIC Academy announces a webinar on Autonomous System Provider Authorizations (ASPAs), an RPKI object for validating BGP AS paths and identifying route leaks. The session will cover ASPA deployment, monitoring, validation, and its relationship to ROAs and ROV.

### Source excerpt

Join this APNIC Academy webinar to understand how ASPAs work, how they complement ROAs, and how you can begin monitoring and deploying them in your network.

## EVPN with SR-MPLS Core

DevFeed: [EVPN with SR-MPLS Core](<https://devfeed.tech/articles/evpn-with-sr-mpls-core-57778.md>)

Original publisher: [Read original article](<https://blog.ipspace.net/2026/09/sr-mpls-evpn/>)

Published: 2026-09-22T05:25:00Z

Content type: tutorial

Language: en

Sources: [ipSpace](<https://devfeed.tech/sources/ipspace-net-blog-2.md>)

Topics: [evpn](<https://devfeed.tech/topics/evpn.md>), [BGP](<https://devfeed.tech/topics/bgp.md>), [Wails](<https://devfeed.tech/topics/wails.md>), [GitHub](<https://devfeed.tech/topics/github.md>), [Repository](<https://devfeed.tech/topics/repository.md>), [FIRST](<https://devfeed.tech/topics/first.md>)

Tags: [bgp](<https://devfeed.tech/tags/bgp.md>), [evpn](<https://devfeed.tech/tags/evpn.md>), [github](<https://devfeed.tech/tags/github.md>), [github-repository](<https://devfeed.tech/tags/github-repository.md>), [netlab](<https://devfeed.tech/tags/netlab.md>), [routers](<https://devfeed.tech/tags/routers.md>), [segment-routing](<https://devfeed.tech/tags/segment-routing.md>), [sr-mpls](<https://devfeed.tech/tags/sr-mpls.md>)

### AI overview

A workshop tutorial demonstrates EVPN services over an SR-MPLS core using an Arista EOS lab topology. It covers BGP EVPN routes, MPLS label stacks, VLAN configuration, and running the lab through a GitHub repository and Codespace.

### Source excerpt

After a long journey, we finally we got to the final scenario in my ITNOG10 Segment Routing workshop: EVPN services over an SR-MPLS core. I used the same lab topology as in the previous services-focused scenarios blog post, replacing two PE-to-host subnets with a stretched VLAN. EVPN over SR-MPLS core Read more ...

## Latest BGP hijack targets hosting software vendor

DevFeed: [Latest BGP hijack targets hosting software vendor](<https://devfeed.tech/articles/latest-bgp-hijack-targets-hosting-software-vendor-57743.md>)

Original publisher: [Read original article](<https://blog.apnic.net/2026/09/22/latest-bgp-hijack-targets-hosting-software-vendor/>)

Author: Doug Madory

Published: 2026-09-22T04:04:24Z

Content type: article

Language: en

Sources: [APNIC Blog](<https://devfeed.tech/sources/apnic-blog.md>)

Topics: [BGP](<https://devfeed.tech/topics/bgp.md>), [incident](<https://devfeed.tech/topics/incident.md>), [Security](<https://devfeed.tech/topics/security.md>), [Routing (disambiguation)](<https://devfeed.tech/topics/routing.md>), [TLS (Transport Layer Security)](<https://devfeed.tech/topics/tls.md>), [hosting](<https://devfeed.tech/topics/hosting.md>), [Software](<https://devfeed.tech/topics/software.md>), [Risk](<https://devfeed.tech/topics/risk.md>)

Tags: [analysis](<https://devfeed.tech/tags/analysis.md>), [attack](<https://devfeed.tech/tags/attack.md>), [bgp](<https://devfeed.tech/tags/bgp.md>), [certificate](<https://devfeed.tech/tags/certificate.md>), [guest-post](<https://devfeed.tech/tags/guest-post.md>), [hijack](<https://devfeed.tech/tags/hijack.md>), [hosting](<https://devfeed.tech/tags/hosting.md>), [incident](<https://devfeed.tech/tags/incident.md>), [platform](<https://devfeed.tech/tags/platform.md>), [protocol](<https://devfeed.tech/tags/protocol.md>), [route](<https://devfeed.tech/tags/route.md>), [routing](<https://devfeed.tech/tags/routing.md>), [routing-table](<https://devfeed.tech/tags/routing-table.md>), [rpki](<https://devfeed.tech/tags/rpki.md>), [security](<https://devfeed.tech/tags/security.md>), [software](<https://devfeed.tech/tags/software.md>), [tech-matters](<https://devfeed.tech/tags/tech-matters.md>), [tls](<https://devfeed.tech/tags/tls.md>)

### AI overview

An analysis of a BGP hijack targeting Softaculous, a hosting software vendor. The incident enabled an attacker to obtain a technically valid TLS certificate and distribute a malicious Virtualizor update to a small number of installations.

### Source excerpt

Guest Post: An analysis of the BGP hijack against Softaculous that enabled an attacker to obtain a fraudulent TLS certificate and distribute a malicious Virtualizor update.

## BGP MED: Controlling Which Entry Point Another Network Uses

DevFeed: [BGP MED: Controlling Which Entry Point Another Network Uses](<https://devfeed.tech/articles/bgp-med-controlling-which-entry-point-another-network-uses-57548.md>)

Original publisher: [Read original article](<https://blog.j2sw.com/resources/bgp-med-control-inbound-entry-points/>)

Author: j2sw

Published: 2026-09-21T17:28:53Z

Content type: tutorial

Language: en

Sources: [Justin Wilson (j2sw)](<https://devfeed.tech/sources/justin-wilson-j2sw.md>)

Topics: [BGP](<https://devfeed.tech/topics/bgp.md>), [Network](<https://devfeed.tech/topics/network.md>)

Tags: [bgp](<https://devfeed.tech/tags/bgp.md>), [capacity](<https://devfeed.tech/tags/capacity.md>), [internet-architecture](<https://devfeed.tech/tags/internet-architecture.md>), [med](<https://devfeed.tech/tags/med.md>), [network](<https://devfeed.tech/tags/network.md>), [network-engineering-resources](<https://devfeed.tech/tags/network-engineering-resources.md>), [platform](<https://devfeed.tech/tags/platform.md>), [policy](<https://devfeed.tech/tags/policy.md>), [route](<https://devfeed.tech/tags/route.md>), [router](<https://devfeed.tech/tags/router.md>), [routing](<https://devfeed.tech/tags/routing.md>), [selection](<https://devfeed.tech/tags/selection.md>), [sessions](<https://devfeed.tech/tags/sessions.md>), [traffic](<https://devfeed.tech/tags/traffic.md>), [transit](<https://devfeed.tech/tags/transit.md>), [upstream](<https://devfeed.tech/tags/upstream.md>)

### AI overview

A practical explanation of how the BGP Multi-Exit Discriminator (MED) influences which entry point a neighboring network uses when multiple interconnections exist. It covers lower-MED path preference, MED's dependence on the neighbor's policy, and its interaction with local preference and AS-path selection.

### Source excerpt

Let's look at another BGP attribute, the Multi-Exit Discriminator, or MED. Two networks may interconnect in more than one location, and MED lets you attach a preference to the routes you advertise. An ISP might connect to the same upstream in Indianapolis and Chicago while advertising the same prefixes at both locations. The upstream now ... Read more The post BGP MED: Controlling Which Entry Point Another Network Uses appeared first on Justin Wilson (j2sw).

## Why Multi-Cloud Routing Creates VPN Gaps: Here's How to Fix Them

DevFeed: [Why Multi-Cloud Routing Creates VPN Gaps: Here's How to Fix Them](<https://devfeed.tech/articles/why-multi-cloud-routing-creates-vpn-gaps-here-s-how-to-fix-them-53626.md>)

Original publisher: [Read original article](<https://blog.vyos.io/why-multi-cloud-routing-creates-vpn-gaps>)

Author: g.yigit@vyos.io (Gizem Yigit)

Published: 2026-09-15T12:00:04Z

Content type: opinion

Language: en

Sources: [VyOS](<https://devfeed.tech/sources/vyos-blog.md>)

Topics: [Cloud](<https://devfeed.tech/topics/cloud.md>), [Network](<https://devfeed.tech/topics/network.md>), [Virtual Private Network](<https://devfeed.tech/topics/vpn.md>), [Amazon Web Services](<https://devfeed.tech/topics/aws.md>), [Azure](<https://devfeed.tech/topics/azure.md>), [data centers](<https://devfeed.tech/topics/data-centers.md>), [Routing (disambiguation)](<https://devfeed.tech/topics/routing.md>), [BGP](<https://devfeed.tech/topics/bgp.md>), [Resilience](<https://devfeed.tech/topics/resilience.md>), [Scalability](<https://devfeed.tech/topics/scalability.md>), [Monitoring](<https://devfeed.tech/topics/monitoring.md>)

Tags: [architecture](<https://devfeed.tech/tags/architecture.md>), [aws](<https://devfeed.tech/tags/aws.md>), [azure](<https://devfeed.tech/tags/azure.md>), [bgp](<https://devfeed.tech/tags/bgp.md>), [bgp-routing](<https://devfeed.tech/tags/bgp-routing.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [cloud-routing](<https://devfeed.tech/tags/cloud-routing.md>), [connectivity](<https://devfeed.tech/tags/connectivity.md>), [datacenter](<https://devfeed.tech/tags/datacenter.md>), [deployment](<https://devfeed.tech/tags/deployment.md>), [edge-networking](<https://devfeed.tech/tags/edge-networking.md>), [failover](<https://devfeed.tech/tags/failover.md>), [firewall](<https://devfeed.tech/tags/firewall.md>), [hybrid-cloud](<https://devfeed.tech/tags/hybrid-cloud.md>), [hybrid-cloud-connectivity](<https://devfeed.tech/tags/hybrid-cloud-connectivity.md>), [monitoring](<https://devfeed.tech/tags/monitoring.md>), [multi-cloud](<https://devfeed.tech/tags/multi-cloud.md>), [multi-cloud-routing](<https://devfeed.tech/tags/multi-cloud-routing.md>), [multicloud-networking](<https://devfeed.tech/tags/multicloud-networking.md>), [multicloud-vpn](<https://devfeed.tech/tags/multicloud-vpn.md>), [network](<https://devfeed.tech/tags/network.md>), [networking](<https://devfeed.tech/tags/networking.md>), [outages](<https://devfeed.tech/tags/outages.md>), [resilience](<https://devfeed.tech/tags/resilience.md>), [routing](<https://devfeed.tech/tags/routing.md>), [site-to-site-vpn](<https://devfeed.tech/tags/site-to-site-vpn.md>), [vpn](<https://devfeed.tech/tags/vpn.md>), [vyos](<https://devfeed.tech/tags/vyos.md>)

### AI overview

This article explains why multi-cloud routing becomes difficult to manage across AWS, Azure, Google Cloud, and datacenter environments. It identifies inconsistent routing behavior, VPN tunnel proliferation, policy drift, and monitoring blind spots as recurring architectural problems.

### Source excerpt

Organizations go multi-cloud for good reasons, resilience and pricing leverage among them. What rarely gets budgeted is what happens to the network team once those workloads are actually live in AWS, Azure, and a datacenter at the same time. Routing tables drift out of sync. VPN tunnels accumulate faster than anyone documents them. And the failover design that looked airtight in the diagram takes three times as long as planned the first time someone actually pulls the plug. I want to be precise about why this happens, because it is not a monitoring problem, and another dashboard will not fix it. It is a routing architecture problem.

## MPLS/VPN with SR-MPLS Core

DevFeed: [MPLS/VPN with SR-MPLS Core](<https://devfeed.tech/articles/mpls-vpn-with-sr-mpls-core-26234.md>)

Original publisher: [Read original article](<https://blog.ipspace.net/2026/09/sr-mpls-vpn/>)

Published: 2026-09-15T05:45:00Z

Content type: article

Language: en

Sources: [ipSpace](<https://devfeed.tech/sources/ipspace-net-blog-2.md>)

Topics: [Segment Routing with MPLS Labels (SR-MPLS)](<https://devfeed.tech/topics/segment-routing-with-mpls-labels-sr-mpls.md>), [MPLS VPN](<https://devfeed.tech/topics/mpls-vpn.md>), [Network](<https://devfeed.tech/topics/network.md>), [BGP](<https://devfeed.tech/topics/bgp.md>), [IS-IS](<https://devfeed.tech/topics/is-is.md>), [GitHub](<https://devfeed.tech/topics/github.md>)

Tags: [bgp](<https://devfeed.tech/tags/bgp.md>), [devices](<https://devfeed.tech/tags/devices.md>), [github](<https://devfeed.tech/tags/github.md>), [is-is](<https://devfeed.tech/tags/is-is.md>), [mpls](<https://devfeed.tech/tags/mpls.md>), [mpls-vpn](<https://devfeed.tech/tags/mpls-vpn.md>), [netlab](<https://devfeed.tech/tags/netlab.md>), [sr-mpls](<https://devfeed.tech/tags/sr-mpls.md>), [vpn](<https://devfeed.tech/tags/vpn.md>)

### AI overview

This article explains how to build and test an MPLS/VPN service over an SR-MPLS core. It describes the required lab topology changes, including enabling MPLS/VPN, disabling LDP, configuring PE routers with IS-IS, SR-MPLS, BGP, MPLS, and VRF modules, and moving PE-to-host links into tenant VRFs. It also outlines how to run the lab using GitHub Codespaces, an Arista cEOS container, and netlab.

### Source excerpt

As we discussed in the BGP-Free Core with SR-MPLS blog post, SR-MPLS works as a drop-in replacement for the traditional MPLS control plane. No wonder it works well (when properly implemented) with MPLS/VPN services - the second "fun" scenario in my ITNOG10 Segment Routing workshop. It uses the same topology as the BGP-Free Core scenario: Simplest possible MPLS/VPN network with SR-MPLS core Read more ...

## Indian backbones need AS\_PATH filters

DevFeed: [Indian backbones need AS\_PATH filters](<https://devfeed.tech/articles/indian-backbones-need-as-path-filters-39786.md>)

Original publisher: [Read original article](<https://anuragbhatia.com/post/2026/09/india-routing-security/>)

Published: 2026-09-07T20:11:07Z

Content type: opinion

Language: en

Sources: [Personal blog of Anurag Bhatia](<https://devfeed.tech/sources/personal-blog-of-anurag-bhatia.md>)

Topics: [BGP](<https://devfeed.tech/topics/bgp.md>), [Routing (disambiguation)](<https://devfeed.tech/topics/routing.md>), [Network](<https://devfeed.tech/topics/network.md>), [Security](<https://devfeed.tech/topics/security.md>)

Tags: [airtel](<https://devfeed.tech/tags/airtel.md>), [as4755](<https://devfeed.tech/tags/as4755.md>), [as55836](<https://devfeed.tech/tags/as55836.md>), [as9498](<https://devfeed.tech/tags/as9498.md>), [bgp](<https://devfeed.tech/tags/bgp.md>), [india](<https://devfeed.tech/tags/india.md>), [jio](<https://devfeed.tech/tags/jio.md>), [network](<https://devfeed.tech/tags/network.md>), [rcom](<https://devfeed.tech/tags/rcom.md>), [routing](<https://devfeed.tech/tags/routing.md>), [tata-comm](<https://devfeed.tech/tags/tata-comm.md>)

### AI overview

The article argues that route leaks are a longstanding security problem for India's routing infrastructure. It explains limitations of IRR AS-SETs, discusses ASPA and AS_PATH filters or peer lock, and questions whether major Indian backbones can consistently apply those filters because of indirect routing and smaller downstream networks.

### Source excerpt

The security of India's routing infrastructure is something that isn't discussed as much as cybersecurity, software vulnerabilities, etc. Part of the blame for that has to go to our industry, which is relatively closed when it comes to sharing incidents and also lacks good documentation on the deployment side of things. Some of these things came to light after the RCom (AS18101) BGP hijack of Telegram prefixes in June 2026. One silent problem for a long time has been route leaks. BGP route leak Route leaks happen when a network ends up announcing a route to a BGP adjacency where it is not supposed to announce that route. Take, for example, a network "leaking" routes learnt from a peer to transit, or vice versa. One can filter downstreams which are small, but it's very hard to filter large downstream networks which have further downstreams, or if one is far removed from that ASN. IRR AS-SETs exist for this reason, but they have not worked well due to tooling challenges. Furthermore, IRR (Internet Routing Registry) by design is a public register where one "publishes intent" before actually doing that in BGP, and then anyone can match the intent with the state in BGP. New tech ASPA will help address this issue, but it's new, vendor support is still in the development phase and it will take its own adoption time. AS_PATH filters / Peer lock This is older tech which can play a very effective role in controlling leaks. If network A decides to peer with network B, they both can agree to announce all routes to each other over the peering & agree to reject each other's ASN from all other BGP sessions. It's a common practice between large transit-free Tier-1 networks as well as major backbones and is often referred to by the fancy name of "peer lock". In India, I doubt backbones like Airtel, Jio, and Tata Comm can have AS_PATH filters rejecting each other from everywhere except direct sessions because there is some indirect routing visible all the time. It could be because of

## BGP-Free Core with SR-MPLS

DevFeed: [BGP-Free Core with SR-MPLS](<https://devfeed.tech/articles/bgp-free-core-with-sr-mpls-11437.md>)

Original publisher: [Read original article](<https://blog.ipspace.net/2026/09/sr-mpls-bgp-free/>)

Published: 2026-09-03T05:30:00Z

Content type: article

Language: en

Sources: [ipSpace](<https://devfeed.tech/sources/ipspace-net-blog-2.md>)

Topics: [Segment Routing with MPLS Labels (SR-MPLS)](<https://devfeed.tech/topics/segment-routing-with-mpls-labels-sr-mpls.md>), [BGP](<https://devfeed.tech/topics/bgp.md>), [Network](<https://devfeed.tech/topics/network.md>), [Routing (disambiguation)](<https://devfeed.tech/topics/routing.md>), [container](<https://devfeed.tech/topics/container.md>), [Linux](<https://devfeed.tech/topics/linux.md>), [GitHub](<https://devfeed.tech/topics/github.md>)

Tags: [bgp](<https://devfeed.tech/tags/bgp.md>), [containers](<https://devfeed.tech/tags/containers.md>), [edge](<https://devfeed.tech/tags/edge.md>), [examples](<https://devfeed.tech/tags/examples.md>), [github](<https://devfeed.tech/tags/github.md>), [is-is](<https://devfeed.tech/tags/is-is.md>), [linux](<https://devfeed.tech/tags/linux.md>), [mpls](<https://devfeed.tech/tags/mpls.md>), [netlab](<https://devfeed.tech/tags/netlab.md>), [network](<https://devfeed.tech/tags/network.md>), [router](<https://devfeed.tech/tags/router.md>), [routing](<https://devfeed.tech/tags/routing.md>), [sr-mpls](<https://devfeed.tech/tags/sr-mpls.md>)

### AI overview

This article demonstrates how to build a BGP-free transport core with SR-MPLS using netlab. It describes a lab topology with IS-IS, BGP, Linux container hosts, and PE routers, then shows how SR-MPLS labels provide end-to-end connectivity without BGP routes on the core router.

### Source excerpt

The beauty of SR-MPLS is that it's a drop-in replacement for the traditional (LDP- or RSVP-based) MPLS control plane. For example, you could replace LDP with SR-MPLS in a network using MPLS to implement a BGP-free transport core, and it just keeps working. This scenario was the first "fun" scenario in the ITNOG10 Segment Routing workshop. The core network uses the same topology as in the previous examples; I added two hosts and BGP routing. Simplest possible network using a BGP-free core Read more ...

## The IRR Landscape: What RPKI Can Replace

DevFeed: [The IRR Landscape: What RPKI Can Replace](<https://devfeed.tech/articles/the-irr-landscape-what-rpki-can-replace-11449.md>)

Original publisher: [Read original article](<https://labs.ripe.net/author/mw/the-irr-landscape-what-rpki-can-replace/>)

Author: Matthias Wichtlhuber

Published: 2026-09-01T12:20:33Z

Content type: article

Language: en

Sources: [RIPE Labs](<https://devfeed.tech/sources/ripe-labs.md>)

Topics: [BGP](<https://devfeed.tech/topics/bgp.md>), [Routing Security](<https://devfeed.tech/topics/routing-security.md>), [Routing (disambiguation)](<https://devfeed.tech/topics/routing.md>), [Database](<https://devfeed.tech/topics/database.md>), [Internet](<https://devfeed.tech/topics/internet.md>)

Tags: [analysis](<https://devfeed.tech/tags/analysis.md>), [bgp](<https://devfeed.tech/tags/bgp.md>), [competition](<https://devfeed.tech/tags/competition.md>), [data](<https://devfeed.tech/tags/data.md>), [database](<https://devfeed.tech/tags/database.md>), [ixp](<https://devfeed.tech/tags/ixp.md>), [ixps](<https://devfeed.tech/tags/ixps.md>), [measurements](<https://devfeed.tech/tags/measurements.md>), [overview](<https://devfeed.tech/tags/overview.md>), [research](<https://devfeed.tech/tags/research.md>), [routing](<https://devfeed.tech/tags/routing.md>), [routing-security](<https://devfeed.tech/tags/routing-security.md>), [rpki](<https://devfeed.tech/tags/rpki.md>), [series](<https://devfeed.tech/tags/series.md>)

### AI overview

This article analyzes which parts of the Internet Route Registry landscape can safely be replaced by RPKI using traffic and route-server data from AMS-IX and DE-CIX. It concludes that third-party ROUTE(6) objects can largely be phased out, while third-party AS-SETs remain important for BGP filter generation.

### Source excerpt

In the third part of our IRR landscape series, we use traffic measurements from AMS-IX and DE-CIX to assess which parts of the IRR landscape can safely be replaced with RPKI. Third-party ROUTE(6) objects can largely be phased out, while third-party AS-SETs remain essential for BGP filter generation.

[Next page](<https://devfeed.tech/topics/bgp.md?cursor=WyIyMDI2LTA5LTAxVDEyOjIwOjMzKzAwOjAwIiwgIjI5ZTM0YmZmLTkxNWMtNGI2OS1hMWVmLTg2NjQ3NjViZmI1MiJd>)