# networking The discipline of interconnecting computer systems and devices to communicate and exchange data. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## CAPIF 5: Regional Interconnectivity in Central Asia DevFeed: [CAPIF 5: Regional Interconnectivity in Central Asia]() Original publisher: [Read original article]() Author: Anastasiya Pak Published: 2026-09-17T17:29:36Z Content type: article Language: en Sources: [RIPE Labs]() Topics: [Internet](), [Routing Security](), [networking](), [Networks]() Tags: [2026](), [adoption](), [aspa](), [atlas](), [central](), [connectivity](), [country](), [events](), [internet](), [ipv4](), [ipv6](), [ixps](), [measurements](), [progress](), [region](), [report](), [research](), [ripe](), [ris](), [routing](), [routing-security](), [rpki](), [traffic]() ### AI overview This report examines changes in Central Asia's Internet connectivity since CAPIF 1. It describes more direct regional routes, expanding IXPs, stronger routing security and new links toward Pakistan, China, Azerbaijan and Europe, while noting persistently low IPv6 adoption and continued, though reduced, reliance on routes through Russia. ### Source excerpt Central Asia's Internet looks very different than it did back at CAPIF 1. We trace the rise of direct regional routes, stronger routing security and new connectivity options - along with the gaps that remain. ## Dropbox Outlines How Focusing on Existing Infrastructure Efficiency Can Create Headroom for AI DevFeed: [Dropbox Outlines How Focusing on Existing Infrastructure Efficiency Can Create Headroom for AI]() Original publisher: [Read original article]() Author: Matt Foster Published: 2026-09-16T07:15:00Z Content type: news Language: en Sources: [InfoQ]() Topics: [Artificial Intelligence](), [cloud-infrastructure](), [Magic Pocket](), [data centers](), [networking]() Tags: [ai](), [ai-architecture](), [ai-ml-data-engineering](), [capacity](), [cloud](), [data-center](), [data-storage](), [devops](), [dropbox](), [dropbox-datacenter](), [efficiency](), [infrastructure](), [infrastructure-optimisation](), [magic-pocket](), [ml-data-engineering](), [networking](), [news](), [optimization](), [storage](), [sustainable-computing]() ### AI overview Dropbox describes how long-running infrastructure optimization helps it accommodate growing AI demand by improving forecasting, fleet utilization, storage density, hardware lifecycles, and rack-level power delivery. Its storage infrastructure has used more than 50% less power per petabyte since 2020. ### Source excerpt Dropbox has outlined how a decade of infrastructure optimization is helping it absorb growing demand from AI without treating new data-center capacity as the only answer. Its work spans forecasting, fleet utilization, storage density, hardware lifecycles, and rack-level power delivery, much of it predating the current AI boom. By Matt Foster ## OpenMANET - A higher-bandwidth Meshtastic alternative leveraging 802.11ah WiFi HaLow DevFeed: [OpenMANET - A higher-bandwidth Meshtastic alternative leveraging 802.11ah WiFi HaLow]() Original publisher: [Read original article]() Author: Jean-Luc Aufranc (CNXSoft) Published: 2026-09-16T07:00:04Z Content type: article Language: en Sources: [CNX Software - Embedded Systems News]() Topics: [Open Source](), [Networks](), [Wi-Fi](), [Raspberry Pi](), [lora](), [networking](), [meshtastic](), [Embedded Systems]() Tags: [802-11ah](), [broadcom-bcmxxxx](), [camera](), [embedded-systems](), [gps](), [halow](), [hardware](), [linux](), [low-power](), [mesh-networking](), [meshtastic](), [network](), [open-source](), [openmanet](), [openwrt](), [raspberry-pi](), [seeed-studio]() ### AI overview This article introduces OpenMANET, an open-source long-range wireless mesh networking project using Raspberry Pi hardware and Wi-Fi HaLow chips. It compares OpenMANET with LoRa-based Meshtastic, noting higher bandwidth and features such as push-to-talk, GPS sharing, video streaming, and ATAK integration, alongside higher hardware cost and power consumption. ### Source excerpt OpenMANET is an open-source project for building long-range wireless mesh Mobile Ad-hoc Networks (MANETs) using Raspberry Pi SBCs and Wi-Fi HaLow (802.11ah) chips from Morse Micro. This came up when we wrote about Morse Micro USB WiFi HaLow adapters, and an X user commented that "OpenMANET is going to explode with these available, no more adapter boards or M.2 cards". OpenMANET targets search and rescue, disaster response, airsoft events, and other off-grid or infrastructure-failed situations. So it looks like an alternative to LoRa-based Meshtastic and Meshcore, with higher bandwidth, at the cost of more expensive hardware and higher power consumption. OpenMANET supports field communications, including push-to-talk, sharing GPS positions, cameras/video streams, and ATAK (Android Team Awareness Kit) integration. The mesh network can access the Internet through a single "mesh gate" over Starlink or cellular connectivity. The project supports a range of hardware platforms including Gateworks Venice, Raspberry Pi Zero 2 W, [...] The post OpenMANET - A higher-bandwidth Meshtastic alternative leveraging 802.11ah WiFi HaLow appeared first on CNX Software - Embedded Systems News. ## Cornelis and Delos Data propose open alternatives to Nvidia's NVLink for AI scale-up networking DevFeed: [Cornelis and Delos Data propose open alternatives to Nvidia's NVLink for AI scale-up networking]() Original publisher: [Read original article]() Author: Tobias Mann Published: 2026-09-15T20:56:48Z Content type: news Language: en Sources: [www.theregister.com - Articles]() Topics: [NVLink](), [AI Networking](), [Nvidia](), [networking](), [Hardware](), [High-Performance Computing]() Tags: [ai](), [ai-networking](), [cornelis-networks](), [delos-data](), [hardware](), [high-performance-computing](), [network](), [networking](), [nvidia](), [nvlink](), [performance](), [software](), [systems]() ### AI overview The article reports that Cornelis Networks and Delos Data have entered the AI scale-up networking market with proposed alternatives to Nvidia's NVLink. Cornelis introduced its open Active Compute Fabric architecture, which combines programmable in-network compute with scale-up and scale-out networking, while the broader market is developing alternatives using protocols such as Ultra Ethernet and UALink. ### Source excerpt Intel spin-off Cornelis and newcomer Delos Data pitch open alternatives for scaling AI beyond the rack ## MPLS/VPN with SR-MPLS Core DevFeed: [MPLS/VPN with SR-MPLS Core]() Original publisher: [Read original article]() Published: 2026-09-15T05:45:00Z Content type: article Language: en Sources: [ipSpace.net blog]() Topics: [SR-MPLS](), [MPLS VPN](), [networking](), [BGP](), [IS-IS](), [Network](), [GitHub]() Tags: [bgp](), [devices](), [github](), [is-is](), [mpls](), [mpls-vpn](), [netlab](), [sr-mpls](), [vpn]() ### 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 ... ## Bringing QUIC to Seastar DevFeed: [Bringing QUIC to Seastar]() Original publisher: [Read original article]() Author: Cynthia Dunlop Published: 2026-09-14T13:02:07Z Content type: article Language: en Sources: [ScyllaDB]() Topics: [Seastar](), [networking](), [Remote Procedure Call (RPC)](), [C++](), [Latency](), [Protocol (disambiguation)]() Tags: [benchmarks](), [c-plus-plus](), [collaboration](), [engineering](), [latency](), [network](), [networking](), [rpc](), [scylladb](), [seastar](), [udp]() ### AI overview This article describes a University of Warsaw student project conducted with ScyllaDB to implement a QUIC transport for Seastar using the sans-I/O ngtcp2 library. It also adapts Seastar's RPC layer to operate over QUIC and reports benchmark results showing predictable overhead on a lossless loopback and benefits when packets are dropped. ### Source excerpt We built a QUIC transport for Seastar on top of ngtcp2's sans-I/O state machine, then adapted RPC to it twice: 1) as a one-to-one socket replacement, and 2) a QUIC-aware approach that opens a fresh stream per call. ## Building for the AI era: Inside Cisco IT's Wi-Fi 7 revolution DevFeed: [Building for the AI era: Inside Cisco IT's Wi-Fi 7 revolution]() Original publisher: [Read original article]() Author: Chris Tomazic Published: 2026-09-14T13:00:21Z Content type: article Language: en Sources: [Cisco Blogs]() Topics: [Wi-Fi 7](), [Cisco IT](), [cisco networking](), [networking](), [Deployment](), [Latency](), [Security](), [Authentication]() Tags: [authentication](), [cisco-catalyst-center](), [cisco-it](), [cisco-meraki](), [cisco-networking](), [cisco-on-cisco](), [deployment](), [enterprise-networking](), [infrastructure](), [latency](), [network-automation](), [networking](), [security](), [wi-fi-7]() ### AI overview Cisco IT describes a global Wi-Fi 7 rollout for 90,000 employees and hundreds of facilities. Its integrated Cisco networking portfolio, prior preparation with Wi-Fi 6 and 6E, certificate-based authentication, and Meraki Dashboard experience helped make the upgrade routine, seamless, and free of downtime. ### Source excerpt Cisco IT upgraded to Wi-Fi 7 for 90,000 employees with zero downtime and record speed. See how a fully integrated Cisco networking stack, built for the AI era, made a complex global rollout simple and seamless. ## I Added Break-Glass Accounts Before My Home Lab Locked Me Out DevFeed: [I Added Break-Glass Accounts Before My Home Lab Locked Me Out]() Original publisher: [Read original article]() Author: Brandon Lee Published: 2026-09-14T12:16:15Z Content type: article Language: en Sources: [Virtualization Howto]() Topics: [Homelab](), [Authentication](), [Single sign-on (SSO)](), [Docker](), [Database](), [networking](), [Server](), [Amazon Route 53]() Tags: [authentication](), [container](), [database](), [dns](), [docker](), [home-lab](), [home-server](), [infrastructure](), [networking](), [server](), [sso]() ### AI overview The article explains why a home lab that centralizes authentication through single sign-on can become inaccessible during an outage. It introduces "break glass" accounts as a recovery measure and emphasizes treating the authentication service as infrastructure with dependencies such as its application, database, certificates, networking, reverse proxy, and DNS. ### Source excerpt One of the coolest things that you can do is centralize your authentication in the home lab. So, instead of having all kinds of separate usernames and passwords that are... The post I Added Break-Glass Accounts Before My Home Lab Locked Me Out appeared first on Virtualization Howto. ## Solana: Building, Proving and Earning Trust in Public DevFeed: [Solana: Building, Proving and Earning Trust in Public]() Original publisher: [Read original article]() Author: Jacob Creech Published: 2026-09-14T11:00:00Z Content type: article Language: en Sources: [Solana News Feed]() Topics: [Network](), [Critical Infrastructure](), [incident](), [networking](), [Transactions](), [Amazon Web Services]() Tags: [2026](), [aws](), [blockchain](), [blockchain-technology](), [building](), [critical-infrastructure](), [crypto](), [crypto-news](), [cryptocurrency](), [defi](), [ecosystem](), [incident](), [infrastructure](), [network](), [nfts](), [outages](), [podcasts](), [routing](), [solana](), [solana-ecosystem](), [technology](), [transactions](), [uptime](), [web3]() ### AI overview Solana describes how repeated public testing, transparent incident reporting, and corrective engineering have strengthened trust in the network. It highlights a 2026 routing failure that took nearly 29% of network stake offline while blocks and transactions continued, followed by recovery of the infrastructure provider in just over 30 minutes. The article also cites validator capacity improvements, stake-weighted quality of service, and a redesigned transaction scheduler as examples of resilience work. ### Source excerpt Solana has maintained 100% uptime since February 2024, including when a routing failure took nearly 29% of network stake offline. ## Cilium 1.20: Gateway API ExternalAuth, TCPRoute/UDPRoute, ENI IPAM for IPv6, and more DevFeed: [Cilium 1.20: Gateway API ExternalAuth, TCPRoute/UDPRoute, ENI IPAM for IPv6, and more]() Original publisher: [Read original article]() Author: Nico Vibert and Donia Chaiehloudj, Cilium Published: 2026-09-14T10:45:49Z Content type: article Language: en Sources: [Cloud Native Computing Foundation]() Topics: [Cilium](), [Open Source](), [API](), [networking](), [Kubernetes](), [Amazon Web Services](), [eBPF](), [VPC](), [nginx]() Tags: [2026](), [api](), [authentication](), [authorization](), [aws](), [blog](), [cilium](), [cloud](), [cni](), [ebpf](), [google](), [ingress-nginx](), [ipv4](), [ipv6](), [kubernetes](), [microsoft](), [network](), [networking](), [nginx](), [open-source](), [release]() ### AI overview Cilium 1.20 expands Gateway API support with ExternalAuth, CORS filters, ListenerSets, TCPRoute, and UDPRoute. The release also introduces extensible datapath plugins, advances networking standardization with Kubernetes, and adds beta IPv6 support for AWS ENI IPAM. ### Source excerpt Cilium 1.20, the second major open source Cilium release of 2026 after Cilium 1.19, is finally here. Three themes stand out in this release: Thank you to every contributor, reviewer and maintainer who made Cilium 1.20... ## Airtel plans to begin RPKI Route Origin Validation rollout on 22 September 2026 DevFeed: [Airtel plans to begin RPKI Route Origin Validation rollout on 22 September 2026]() Original publisher: [Read original article]() Published: 2026-09-14T09:00:47Z Content type: opinion Language: en Sources: [Personal blog of Anurag Bhatia]() Topics: [networking](), [Routing Security](), [Security]() Tags: [airtel](), [apnic-62](), [as9498](), [india](), [ipv4](), [ipv6](), [routing-security](), [rov](), [rpki]() ### AI overview Airtel has told customers it plans to begin rolling out RPKI Route Origin Validation on 22 September 2026. The article examines 726 RPKI-invalid routes in Airtel's table, including 108 IPv4 and 618 IPv6 routes, and discusses their visibility outside India. ### Source excerpt Just back from Mumbai after APNIC 62 and Equinix's India Peering Forum. On excellent news: Airtel has started sending emails to its customers about RPKI RoV (Route Origin Validation). As per the mail, Airtel will start RPKI RoV soon and has mentioned 22 Sep 2026 as the timeline when they will start rolling out RoV. This is excellent news on the routing security front, and kudos to Airtel (AS9498) for taking the lead here among other large Indian backbones. This brings up the important question of how many routes exist in their table which are RPKI RoV invalids as of today? Looking at their announcements, I see the following: RPKI Valids: 33,735 RPKI Unknown: 4632 RPKI invalids: 726 This is for their table, including downstream routes. One can view the complete list of those 726 invalids, including prefix and AS_PATH here. One interesting thing here is that out of 726, 140 are from Airtel fixedline AS24560 and 122 are from Airtel Mobility. In terms of address family, there are 108 invalids from IPv4 and 618 from IPv6. How many of these invalids are single-homed vs multi-homed? This is important to check, as often the argument against RoV given by various operators in past was that they were losing traffic to their competitors. When I checked, I do not see any of these prefixes visible outside of India behind a transit-free / tier 1 network without AS9498 in the path. It could be because Tata Comm AS6453 drops RPKI invalid already & most of these are not dual-homed via Jio AS64049. So unless a less specific RPKI valid announcement is there, these are anyway largely blackholed for now by networks & IXPs doing RoV outside of India. Let's hope other Indian backbones also start doing RPKI RoV soon. Happy routing! 😀 ## Configuring Management IP Addresses to Virtual Network Devices DevFeed: [Configuring Management IP Addresses to Virtual Network Devices]() Original publisher: [Read original article]() Published: 2026-09-14T05:29:00Z Content type: article Language: en Sources: [ipSpace.net blog]() Topics: [networking](), [configuration](), [Orchestration](), [Vagrant](), [Cloud](), [ssh]() Tags: [cli](), [cloud](), [devices](), [dhcp](), [ip](), [ipv4](), [ipv6](), [management](), [netlab](), [network](), [networking](), [orchestration](), [server](), [ssh]() ### AI overview The article explains how to assign predictable management IP addresses to virtual network devices. It contrasts manual console-based setup with automated assignment through orchestration, containers, DHCPv4/DHCPv6, custom Vagrant boxes, and IPv6 mechanisms such as SLAAC. ### Source excerpt It goes without saying that if you want to configure (virtual) network devices with any semi-sane configuration mechanism1, the device must have a working IP address. Here's the time-honored method2 to assign an IP address to a virtual network device: Start the virtual machine (using a GUI)3 Open a new window: either a telnet session to the virtual console port or a full-blown virtual console (GUI) session. Manually configure the IP address, the SSH server, and the user credentials on the first interface. Read more ... ## JetKVM Mini - A low-cost, ESP32-P4X-based KVM with Ethernet or WiFi connectivity DevFeed: [JetKVM Mini - A low-cost, ESP32-P4X-based KVM with Ethernet or WiFi connectivity]() Original publisher: [Read original article]() Author: Jean-Luc Aufranc (CNXSoft) Published: 2026-09-14T02:03:40Z Content type: news Language: en Sources: [CNX Software - Embedded Systems News]() Topics: [Jetkvm](), [ESP32](), [Embedded Software Dev](), [Microcontroller](), [RISC-V](), [Web](), [WebRTC](), [networking](), [USB]() Tags: [4k](), [embedded-systems](), [esp-idf](), [esp32](), [esp32-p4](), [espressif](), [ethernet](), [firmware](), [freertos](), [github](), [hardware](), [hdmi](), [jetkvm](), [kvm](), [linux](), [macos](), [open-source](), [risc-v](), [soc](), [usb](), [video](), [webrtc](), [wifi](), [wifi-6]() ### AI overview JetKVM Mini is a smaller, lower-cost KVM over IP device based on the ESP32-P4X instead of Linux running on a Rockchip SoC. It provides Ethernet or WiFi connectivity, 1080p video capture, H.264 streaming over WebRTC, USB device emulation, and an information display. Its firmware uses FreeRTOS and ESP-IDF, while JetKVM OS Services add features such as 4K screen capture, shared clipboard, a guest terminal, and file transfer on compatible hosts. ### Source excerpt JetKVM Mini is a smaller, lower-cost version of the popular JetKVM KVM over IP solution. The new model features a small information display, offers Ethernet or WiFi connectivity, and supports 1080p video capture. The main under-the-hood change is that they ditched Linux on a Rockchip RV1106G3 SoC and now rely on an ESP32-P4X (ESP32-P4 version 3.x and greater) to handle video capture, H.264 encoding, USB, and other features. The largest cost saving is removing the RAM and eMMC flash required by Linux. JetKVM Mini specifications: SoC - Espressif Systems ESP32-P4X CPU Dual-core 32-bit RISC-V HP (High-performance) CPU @ up to 400 MHz with AI instruction extension and single-precision FPU Single-RISC-V LP (Low-power) MCU core @ up to 40 MHz Memory 768 KB HP L2MEM (for dual-core CPU), 32 KB LP SRAM, 8 KB TCM (for LP MCU core) 32 MB PSRAM Storage - 128 KB HP ROM, 16 KB LP ROM [...] The post JetKVM Mini - A low-cost, ESP32-P4X-based KVM with Ethernet or WiFi connectivity appeared first on CNX Software - Embedded Systems News. ## d-Matrix Joins the NVIDIA NVLink Fusion Platform DevFeed: [d-Matrix Joins the NVIDIA NVLink Fusion Platform]() Original publisher: [Read original article]() Author: Cliff Robinson Published: 2026-09-12T21:42:59Z Content type: news Language: en Sources: [ServeTheHome]() Topics: [d-matrix](), [NVLink](), [Nvidia](), [xpu](), [AI Inference](), [datacenter](), [networking](), [cpu](), [Spectrum-X]() Tags: [accelerators](), [ai](), [ai-accelerator](), [ai-inference](), [d-matrix](), [data-center](), [ethernet](), [networking](), [nvidia](), [nvidia-vera](), [nvlink](), [server](), [xpu]() ### AI overview d-Matrix and NVIDIA announced that d-Matrix will bring its next-generation XPUs to the NVLink Fusion platform. The integration is intended to support scaling from individual Raptor XPUs to larger rack-scale and clustered deployments for AI inference, alongside NVIDIA networking and CPU technologies. ### Source excerpt d-Matrix and NVIDIA announced that d-Matrix will use NVLink Fusion to scale up and out with its next-gen Raptor AI accelerators The post d-Matrix Joins the NVIDIA NVLink Fusion Platform appeared first on ServeTheHome. ## Scaling AI Agent Infrastructure with the MCP Stateless updates DevFeed: [Scaling AI Agent Infrastructure with the MCP Stateless updates]() Original publisher: [Read original article]() Author: Kurtis Van Gent; Alan Blount Published: 2026-09-12T11:04:33.891311Z Content type: release Language: en Sources: [Google Developers Blog]() Topics: [networking](), [SDKs]() Tags: [agentic](), [ai-agent](), [c-sharp](), [go](), [http](), [infrastructure](), [mcp](), [python](), [routing](), [sdks](), [serverless](), [typescript](), [updates]() ### AI overview The MCP release candidate replaces transport-level session management with a stateless core for HTTP load balancing, cloud-native scaling, and serverless deployments. It also introduces routing headers, caching controls, MRTR, and beta SDKs for Python, TypeScript, Go, and C#. ### Source excerpt The 2026-07-28 Model Context Protocol (MCP) specification replaces legacy stateful constraints with a fully stateless core, enabling cloud-native horizontal scaling, serverless deployments, and standard round-robin load balancing. This architectural shift introduces standardized HTTP headers for efficient routing without deep packet inspection, caching controls, and Multi Round-Trip Requests (MRTR) to handle interactive and long-running tasks without blocking connections. Developers can immediately begin migrating their agentic applications to this highly scalable infrastructure using the newly available beta SDKs for Python, TypeScript, Go, and C#. ## Your built-in router VPN might be more trouble than it's worth DevFeed: [Your built-in router VPN might be more trouble than it's worth]() Original publisher: [Read original article]() Author: Andrew Cunningham Published: 2026-09-11T16:00:00Z Content type: opinion Language: en Sources: [Blog on Tailscale]() Topics: [networking](), [Networks](), [Server](), [Hardware]() Tags: [nas](), [networks](), [performance](), [routing](), [security](), [server]() ### AI overview The article argues that built-in VPN servers on routers and NAS devices can be unreliable and difficult to use, especially on restrictive networks. It presents Tailscale as a better option for addressing those connection limitations. ### Source excerpt Built-in VPNs are easy to start--then harder to live with. ## Presentation: How To Run on Three Clouds at Once, and When Not To DevFeed: [Presentation: How To Run on Three Clouds at Once, and When Not To]() Original publisher: [Read original article]() Author: Ross McFarlane, Kevin Holditch Published: 2026-09-11T11:00:00Z Content type: article Language: en Sources: [InfoQ]() Topics: [networking](), [Databases](), [Kubernetes]() Tags: [amazon](), [architecture](), [architecture-design](), [availability](), [aws](), [cloud](), [cloud-architecture](), [cloud-computing](), [cloud-networking](), [cockroach-labs](), [cockroachdb](), [containers](), [databases](), [devops](), [disaster-recovery](), [engineering](), [europe](), [financial-applications](), [fintech](), [form3-multicloud-architecture](), [infoq](), [kubernetes](), [microservices](), [networking](), [presentation](), [qcon-london-2026](), [qcon-software-development-conference](), [resilience](), [transcripts](), [us]() ### AI overview A presentation on Form3's move from one cloud to a triple-active multi-cloud architecture, covering cross-cloud networking, distributed databases, Kubernetes operators, and regional disaster-recovery expectations. ### Source excerpt Ross McFarlane and Kevin Holditch discuss Form3's evolution from a single-cloud setup to a triple active multi-cloud architecture. They share key engineering strategies for cross-cloud networking, distributed databases with CockroachDB and NATS, custom Kubernetes operators, and navigating distinct regional disaster recovery expectations across the UK, Europe, and US financial markets. By Ross McFarlane, Kevin Holditch ## Advancing Embedded Go: Recoverable Panics, UEFI, Radio and Hardware Dev Kit DevFeed: [Advancing Embedded Go: Recoverable Panics, UEFI, Radio and Hardware Dev Kit]() Original publisher: [Read original article]() Author: Olimpiu Pop Published: 2026-09-11T05:05:00Z Content type: news Language: en Sources: [InfoQ]() Topics: [Go Language](), [Embedded Software Dev](), [networking]() Tags: [development](), [embedded](), [embedded-software-dev](), [errors](), [go](), [hardware](), [llvm](), [networking](), [news](), [release](), [tiny-go](), [tinygo-devkit](), [wasm](), [webassembly]() ### AI overview TinyGo 0.42 adds recoverable runtime panics, Go 1.27 and LLVM 22 support, and a UEFI target. The article also covers prior wireless and board support, WebAssembly and WASI compilation, and the TinyGo Starter Kit with Seeed Studio XIAO. ### Source excerpt TinyGo version 0.42 introduces significant updates, including recoverable panics and support for Go 1.27 and LLVM 22, improving error handling and enabling Go code to run as UEFI applications. The TinyGo Starter Kit with Seeed Studio XIAO facilitates hardware use for developers, featuring an ESP32-C3 board and modular sensors. These features enhance its functionality for embedded systems and Wasm. By Olimpiu Pop ## How Tailscale built a customer-facing model router on AI Gateway DevFeed: [How Tailscale built a customer-facing model router on AI Gateway]() Original publisher: [Read original article]() Author: Susan Aziz Published: 2026-09-11T04:00:00Z Content type: article Language: en Sources: [Vercel News]() Topics: [AI Platform](), [networking](), [API keys]() Tags: [ai-gateway](), [ai-models](), [api](), [model-routing](), [sandbox](), [security](), [vercel]() ### AI overview Tailscale describes using Vercel AI Gateway and Sandbox to deliver customer-facing access to hundreds of AI models through tailnet identity. The article explains that provider integration and secure agent execution were complex enough that Tailscale chose managed routing and sandboxing instead of building those layers in-house. ### Source excerpt Tailscale on Vercel Hundreds of AI models shipped to customers in-product Model access granted and revoked by tailnet network identity Went from model routing prototype to paying customers in months Tailscale connects a company's laptops, servers, cloud instances, and personal devices into one private network called a tailnet. Remy Guercio, who leads product for Aperture by Tailscale, describes it simply: "It's basically like a VPC that can span any cloud, on-prem, your house, and your phone." Aperture takes that same idea and applies it to AI. Instead of giving every employee, agent, or tool a separate provider API key, Aperture lets companies control model access through the tailnet itself. Add someone to the network, and they can immediately use approved models. Remove them, and access disappears. Under the hood, Aperture is built on Vercel AI Gateway and Vercel Sandbox. AI Gateway gives Tailscale one API for hundreds of models. Sandbox gives agents a safe place to run. Together, they let Tailscale offer model access and agent execution inside a customer's private network, without their team building every piece of AI infrastructure from scratch. Model routing is harder than it looks Tailscale is an infrastructure company, so building the routing and execution layers in-house was the obvious first option. But once they took a deeper look into the engineering effort required, they chose not to. The provider layer looked deceptively simple from the outside. "You would think all of the endpoints are the same," Remy says. "They are not." David Carney, Co-founder and Chief Strategy Officer, has the receipts, because Tailscale still maintains that plumbing for a few customers who haven't migrated to Aperture yet. "There are a lot of things the big providers don't do that blow my mind that the gateway does, like simply putting the cost in the response," he says. "We initially built those systems for customers ourselves, and the complexity is insane." Agents raised the s ## A Guide to Application Networking Basics DevFeed: [A Guide to Application Networking Basics]() Original publisher: [Read original article]() Author: ByteByteGo Published: 2026-09-10T15:31:28Z Content type: tutorial Language: en Sources: [ByteByteGo]() Topics: [networking]() Tags: [article](), [guide](), [networking]() ### AI overview The article introduces application networking basics and states that it will examine various aspects of networking in detail. The supplied text does not provide further technical findings. ### Source excerpt In this article, we will look at the various aspects of networking in detail. ## Thanks for participating in APNIC 62 DevFeed: [Thanks for participating in APNIC 62]() Original publisher: [Read original article]() Author: Timothy Hildred Published: 2026-09-10T13:16:58Z Content type: article Language: en Sources: [APNIC Blog]() Topics: [Internet](), [networking](), [NIXI]() Tags: [apnic-62](), [blog](), [community](), [conference](), [conferences](), [event](), [events](), [india](), [industry](), [internet](), [keynote](), [learn](), [linkedin](), [networking](), [nixi](), [september-2026](), [speakers](), [survey](), [transcripts](), [updates](), [videos](), [youtube]() ### AI overview APNIC 62 brought together 583 in-person and remote attendees from 54 economies in Mumbai from 4 to 10 September 2026. The article thanks participants, speakers, sponsors, and organizers, and points readers to the conference report, recordings, presentations, transcripts, and survey. ### Source excerpt Thank you to everyone who participated in person and remotely at APNIC 62, hosted by the National Internet Exchange of India (NIXI) and co-hosted by ISPAI, from 4 to 10 September 2026 in Mumbai, India. ## d-Matrix Adopts NVIDIA NVLink Fusion for Rack-Scale XPU Deployment DevFeed: [d-Matrix Adopts NVIDIA NVLink Fusion for Rack-Scale XPU Deployment]() Original publisher: [Read original article]() Author: Jesse Clayton Published: 2026-09-10T13:00:21Z Content type: news Language: en Sources: [NVIDIA Blog]() Topics: [NVLink](), [AI Platform](), [AI Inference](), [Deployment](), [networking](), [Latency](), [cpu](), [GPU]() Tags: [ai-inference](), [ai-infrastructure](), [ai-platform](), [corporate](), [d-matrix](), [deployment](), [gpu](), [latency](), [networking](), [nvidia](), [nvidia-vera](), [nvidia-vera-rubin](), [nvlink](), [spectrum-x](), [xpu]() ### AI overview d-Matrix announced plans to use NVIDIA NVLink Fusion to connect its next-generation Raptor XPUs with NVIDIA AI infrastructure. The article describes using NVLink, Spectrum-X networking and MGX rack designs to support rack-scale, low-latency inference deployments. ### Source excerpt AI inference chipmaker d-Matrix today announced it will use NVLink Fusion to connect its next-generation Raptor XPUs to NVIDIA's AI infrastructure platform -- joining a growing roster of ecosystem partners. By connecting Raptor to NVIDIA NVLink scale-up and Spectrum-X scale-out networking, the NVIDIA MGX rack architecture and the broader NVIDIA AI platform, NVLink Fusion gives [...] ## Unpacking My Bags: How I Found Belonging, Scale, and Real-Time Networking at Cisco DevFeed: [Unpacking My Bags: How I Found Belonging, Scale, and Real-Time Networking at Cisco]() Original publisher: [Read original article]() Author: Altanai Bisht Published: 2026-09-10T12:00:13Z Content type: article Language: en Sources: [Cisco Blogs]() Topics: [WebRTC](), [networking](), [real-time](), [Open Source](), [Software](), [Machine learning]() Tags: [be-you-with-us](), [career-growth](), [engineering](), [lovewhereyouwork](), [networking](), [open-source](), [real-time](), [software](), [streaming](), [voice](), [we-are-cisco](), [wearecisco](), [webrtc](), [women-in-tech](), [writing]() ### AI overview Software engineer Altanai B. describes a non-linear career spanning startups, research and development, product engineering, streaming, telecoms, and Cisco. She reflects on her long-standing curiosity about how real-time networked communications work, including writing a WebRTC guide and building an open-source robot using edge machine learning. ### Source excerpt Software Engineer Altanai B. shares her non-linear career journey and how she finally found a place to unpack her bags and belong at Cisco. ## The /3 Body Problem DevFeed: [The /3 Body Problem]() Original publisher: [Read original article]() Author: Remco van Mook Published: 2026-09-10T09:22:46Z Content type: article Language: en Sources: [RIPE Labs]() Topics: [networking](), [Internet](), [Internet Engineering Task Force (IETF)]() Tags: [article](), [ietf](), [internet](), [ipv6](), [networking](), [policy](), [space]() ### AI overview The article examines how IPv6 addressing and policy mechanisms may need to evolve for space networking. It argues that terrestrial assumptions break down beyond low Earth orbit and calls for addressing policy questions now, including through the proposed EXPANSE working group. ### Source excerpt A large chunk of IPv6 is heading for space, and every policy question about it is currently going to be deferred to the RIR communities. This article outlines what those questions look like, and argues why now is the time to start asking them. [Next page]()