# Network architectures

The organization of network devices and services to meet the connectivity needs of client devices.

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

## Meet Liam Merritt: Making Complex Customer Challenges Simpler

DevFeed: [Meet Liam Merritt: Making Complex Customer Challenges Simpler](<https://devfeed.tech/articles/meet-liam-merritt-making-complex-customer-challenges-simpler-146904.md>)

Original publisher: [Read original article](<https://netboxlabs.com/blog/meet-liam-merritt/>)

Author: Meghna Khurana

Published: 2026-11-20T21:21:15Z

Content type: article

Language: en

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

Topics: [Network architectures](<https://devfeed.tech/topics/network-architectures.md>), [NetBox](<https://devfeed.tech/topics/netbox.md>)

Tags: [account](<https://devfeed.tech/tags/account.md>), [accountability](<https://devfeed.tech/tags/accountability.md>), [automation](<https://devfeed.tech/tags/automation.md>), [autonomy](<https://devfeed.tech/tags/autonomy.md>), [balance](<https://devfeed.tech/tags/balance.md>), [based](<https://devfeed.tech/tags/based.md>), [blog](<https://devfeed.tech/tags/blog.md>), [build](<https://devfeed.tech/tags/build.md>), [building](<https://devfeed.tech/tags/building.md>), [business](<https://devfeed.tech/tags/business.md>), [careers](<https://devfeed.tech/tags/careers.md>), [challenges](<https://devfeed.tech/tags/challenges.md>), [community](<https://devfeed.tech/tags/community.md>), [company](<https://devfeed.tech/tags/company.md>), [complex](<https://devfeed.tech/tags/complex.md>), [complexity](<https://devfeed.tech/tags/complexity.md>), [connect](<https://devfeed.tech/tags/connect.md>), [customer](<https://devfeed.tech/tags/customer.md>), [labs](<https://devfeed.tech/tags/labs.md>), [making](<https://devfeed.tech/tags/making.md>), [netbox](<https://devfeed.tech/tags/netbox.md>)

### AI overview

Liam Merritt, a Strategic Account Executive at NetBox Labs, helps strategic customers and prospective organizations clarify priorities, connect with technical resources and partners, and move infrastructure projects from initial discussions through evaluation and purchase. He says his work often means turning complex requirements and competing priorities into a clear recommendation and achievable next step. He is particularly energized by infrastructure refreshes and automation initiatives, and values the autonomy in his role alongside access to leadership support.

### Source excerpt

The post Meet Liam Merritt: Making Complex Customer Challenges Simpler appeared first on NetBox Labs.

## Capability Internet: A Network Architecture for Autonomous Agents

DevFeed: [Capability Internet: A Network Architecture for Autonomous Agents](<https://devfeed.tech/articles/capability-internet-a-network-architecture-for-autonomous-agents-142995.md>)

Original publisher: [Read original article](<https://arxiv.org/abs/2611.23841>)

Author: Zhuoming Wen, Hongwei Li, You Wu

Published: 2026-11-19T05:00:00Z

Content type: article

Language: en

Sources: [arXiv: Networking](<https://devfeed.tech/sources/arxiv-networking.md>)

Topics: [Multi Agent Systems](<https://devfeed.tech/topics/multi-agent-systems.md>), [agentic workflows](<https://devfeed.tech/topics/agentic-workflows.md>), [agent to agent communication](<https://devfeed.tech/topics/agent-to-agent-communication.md>), [Network architectures](<https://devfeed.tech/topics/network-architectures.md>)

Tags: [actions](<https://devfeed.tech/tags/actions.md>), [agent](<https://devfeed.tech/tags/agent.md>), [agents](<https://devfeed.tech/tags/agents.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [autonomous](<https://devfeed.tech/tags/autonomous.md>), [autonomous-agents](<https://devfeed.tech/tags/autonomous-agents.md>), [behavior](<https://devfeed.tech/tags/behavior.md>), [capabilities](<https://devfeed.tech/tags/capabilities.md>), [capability](<https://devfeed.tech/tags/capability.md>), [compute](<https://devfeed.tech/tags/compute.md>), [computing](<https://devfeed.tech/tags/computing.md>), [cs-ni](<https://devfeed.tech/tags/cs-ni.md>), [deployment](<https://devfeed.tech/tags/deployment.md>), [discovery](<https://devfeed.tech/tags/discovery.md>), [evaluation](<https://devfeed.tech/tags/evaluation.md>), [exchange](<https://devfeed.tech/tags/exchange.md>), [federated](<https://devfeed.tech/tags/federated.md>), [functions](<https://devfeed.tech/tags/functions.md>), [internet](<https://devfeed.tech/tags/internet.md>), [network](<https://devfeed.tech/tags/network.md>), [network-architecture](<https://devfeed.tech/tags/network-architecture.md>)

### AI overview

Capability Internet (CI) proposes coordinating autonomous agents through persistent tasks that record what has been completed, which actions are authorized, and which provider and terms apply to each invocation. Versioned capability descriptions specify behavior, while live instances identify providers and resources. If a provider changes, a task can reuse completed results that still satisfy its requirements. CI defines five functions: capability discovery, task coordination, federated compute, intelligence reuse, and governance of capability use and settlement. Reviewed task results can become versioned intelligence for later tasks. The abstract illustrates four deployment profiles--computing and intelligence services, manufacturing, vehicles and embodied robots, and space-ground operations--and proposes an evaluation plan.

### Source excerpt

arXiv:2611.23841v1 Announce Type: new Abstract: Autonomous agents increasingly provide and consume network services. An agent coordinating a long-running task across organizations must track what has been done, which actions are authorized, and which provider can perform the next step. We propose Capability Internet (CI), an architecture in which agents exchange capabilities and coordinate their use through persistent tasks. Versioned descriptions specify behavior, and live instances identify the providers and resources that can supply it. Task records link each invocation to its selected instance, authority, and terms of use. When providers change, the task can reuse completed results that still meet its requirements. Five functions support capability discovery, task coordination, federated compute, intelligence reuse, and governance of capability use and settlement. Reviewed task results can supply versioned intelligence for subsequent tasks. We illustrate CI through four deployment profiles covering computing and intelligence services, manufacturing, vehicles and embodied robots, and space-ground operations, and propose an evaluation plan.

## TE Connectivity at OCP Summit 2026 The Interview

DevFeed: [TE Connectivity at OCP Summit 2026 The Interview](<https://devfeed.tech/articles/te-connectivity-at-ocp-summit-2026-the-interview-134872.md>)

Original publisher: [Read original article](<https://www.servethehome.com/te-connectivity-at-ocp-summit-2026-the-interview/>)

Author: Patrick Kennedy

Published: 2026-11-16T07:00:21Z

Content type: news

Language: en

Sources: [ServeTheHome](<https://devfeed.tech/sources/servethehome.md>)

Topics: [communications](<https://devfeed.tech/topics/communications.md>), [Network architectures](<https://devfeed.tech/topics/network-architectures.md>), [CVE-2026-86060](<https://devfeed.tech/topics/cve-2026-86060.md>)

Tags: [2017](<https://devfeed.tech/tags/2017.md>), [2026](<https://devfeed.tech/tags/2026.md>), [3d](<https://devfeed.tech/tags/3d.md>), [3d-printed](<https://devfeed.tech/tags/3d-printed.md>), [448g](<https://devfeed.tech/tags/448g.md>), [800v](<https://devfeed.tech/tags/800v.md>), [about](<https://devfeed.tech/tags/about.md>), [ai](<https://devfeed.tech/tags/ai.md>), [connectivity](<https://devfeed.tech/tags/connectivity.md>), [copper](<https://devfeed.tech/tags/copper.md>), [first](<https://devfeed.tech/tags/first.md>), [interview](<https://devfeed.tech/tags/interview.md>), [more](<https://devfeed.tech/tags/more.md>), [news](<https://devfeed.tech/tags/news.md>), [ocp](<https://devfeed.tech/tags/ocp.md>), [ocp-summit](<https://devfeed.tech/tags/ocp-summit.md>), [optical](<https://devfeed.tech/tags/optical.md>), [power](<https://devfeed.tech/tags/power.md>), [serdes](<https://devfeed.tech/tags/serdes.md>), [summit](<https://devfeed.tech/tags/summit.md>), [te-connectivity](<https://devfeed.tech/tags/te-connectivity.md>)

### AI overview

At OCP Summit 2026, TE Connectivity described a system-level approach to AI infrastructure that combines high-speed data links, power delivery, cooling, serviceability and manufacturing. Payne outlined a newly announced 448G-per-lane front-panel concept developed with NVIDIA and Cisco, designed to balance signal integrity, power and form factor, with provision for liquid cooling as transceiver power rises. TE is advancing copper backplanes and midplanes while investing in co-packaged optics; Payne said copper remains important as routing limits make an eventual shift to optics more pressing. For power, the booth showed a sidecar power rack, liquid-cooled horizontal busbar and prototype rack-to-rack 800V cables, with 800V pathfinding aimed at future megawatt-class racks. Payne tied these developments to customer feedback, iterative design and production at scale, citing 10 DDN manufacturing facilities worldwide.

### Source excerpt

Brian Payne joins us for an interview on 800V DC power, 488G SerDes, copper and optical connectivity and more from OCP Summit 2026 The post TE Connectivity at OCP Summit 2026 The Interview appeared first on ServeTheHome.

## NeuralSat raises $3.2M to bring high-speed data connectivity and compute to space

DevFeed: [NeuralSat raises $3.2M to bring high-speed data connectivity and compute to space](<https://devfeed.tech/articles/neuralsat-raises-3-2m-to-bring-high-speed-data-connectivity-and-compute-to-space-132511.md>)

Original publisher: [Read original article](<https://siliconangle.com/2026/11/13/neuralsat-raises-3-2m-to-bring-high-speed-data-connectivity-and-compute-to-space/>)

Author: Kyt Dotson

Published: 2026-11-13T16:45:11Z

Content type: news

Language: en

Sources: [SiliconANGLE](<https://devfeed.tech/sources/siliconangle.md>)

Topics: [Network architectures](<https://devfeed.tech/topics/network-architectures.md>), [High-Performance Computing](<https://devfeed.tech/topics/high-performance-computing.md>), [mesh networking](<https://devfeed.tech/topics/mesh-networking.md>)

Tags: [communications](<https://devfeed.tech/tags/communications.md>), [compute](<https://devfeed.tech/tags/compute.md>), [computing](<https://devfeed.tech/tags/computing.md>), [connectivity](<https://devfeed.tech/tags/connectivity.md>), [emerging-tech](<https://devfeed.tech/tags/emerging-tech.md>), [low-earth-orbit](<https://devfeed.tech/tags/low-earth-orbit.md>), [mohd-bilal](<https://devfeed.tech/tags/mohd-bilal.md>), [nasdaq-nvda](<https://devfeed.tech/tags/nasdaq-nvda.md>), [network](<https://devfeed.tech/tags/network.md>), [neuralsat](<https://devfeed.tech/tags/neuralsat.md>), [news](<https://devfeed.tech/tags/news.md>), [optical-inter-satellite-links](<https://devfeed.tech/tags/optical-inter-satellite-links.md>), [pre-seed](<https://devfeed.tech/tags/pre-seed.md>), [processing](<https://devfeed.tech/tags/processing.md>), [raises](<https://devfeed.tech/tags/raises.md>), [relay](<https://devfeed.tech/tags/relay.md>), [satellite](<https://devfeed.tech/tags/satellite.md>), [satellite-data](<https://devfeed.tech/tags/satellite-data.md>), [satellites](<https://devfeed.tech/tags/satellites.md>), [space](<https://devfeed.tech/tags/space.md>), [startup](<https://devfeed.tech/tags/startup.md>), [startup-funding](<https://devfeed.tech/tags/startup-funding.md>), [the-latest](<https://devfeed.tech/tags/the-latest.md>)

### AI overview

NeuralSat raised EUR 2.9 million (about $3.2 million) in pre-seed funding, co-led by Capnamic and Bayern Kapital, to develop a planned 72-satellite data-relay and processing network. The company says optical and high-frequency radio links will deliver up to 50 gigabytes per second, supporting real-time edge processing, hosted commercial and defense workloads, and time-critical missions. Funding is intended to advance a first in-orbit demonstration node planned for October 2027, followed by commercial satellite deployment. The article describes the proposed benefit as processing near where data is produced or relaying it between satellites, which may reduce delays compared with routing data to Earth-based data centers; it says inter-satellite links can be 30% to 50% faster over long distances. The excerpt also notes that orbital computing faces heat-dissipation and payload-weight constraints and is framed as complementing, rather than replacing, terrestrial data centers.

### Source excerpt

German startup NeuralSat GmbH announced Thursday that it raised EUR 2.9 million, about $3.2 million, in pre-seed funding to develop a 72-satellite data-relay processing network aimed at speeding up the flow of data from space. Capnamic and Bayern Kapital co-led the round. Other investors participating in the round included ZOHO.VC, Robin Capital, BAB - Die Förderbank für Bremen [...] The post NeuralSat raises $3.2M to bring high-speed data connectivity and compute to space appeared first on SiliconANGLE.

## The Digital Networks Act: Building the connectivity infrastructure Europe needs for AI

DevFeed: [The Digital Networks Act: Building the connectivity infrastructure Europe needs for AI](<https://devfeed.tech/articles/the-digital-networks-act-building-the-connectivity-infrastructure-europe-needs-for-ai-131421.md>)

Original publisher: [Read original article](<https://blogs.cisco.com/gov/digital-networks-act-connectivity-infrastructure-europe-ai>)

Author: Diane Mievis

Published: 2026-11-13T08:00:12Z

Content type: opinion

Language: en

Sources: [Cisco Blogs](<https://devfeed.tech/sources/cisco-blogs.md>)

Topics: [AI Infrastructure](<https://devfeed.tech/topics/ai-infrastructure.md>), [Network architectures](<https://devfeed.tech/topics/network-architectures.md>), [Artificial Intelligence](<https://devfeed.tech/topics/ai.md>), [it modernization](<https://devfeed.tech/topics/it-modernization.md>)

Tags: [6g](<https://devfeed.tech/tags/6g.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-ready-networks](<https://devfeed.tech/tags/ai-ready-networks.md>), [connectivity](<https://devfeed.tech/tags/connectivity.md>), [digital](<https://devfeed.tech/tags/digital.md>), [digital-infrastructure](<https://devfeed.tech/tags/digital-infrastructure.md>), [eu-policy](<https://devfeed.tech/tags/eu-policy.md>), [eu-regulation](<https://devfeed.tech/tags/eu-regulation.md>), [europe](<https://devfeed.tech/tags/europe.md>), [high-tech-policy](<https://devfeed.tech/tags/high-tech-policy.md>), [infrastructure](<https://devfeed.tech/tags/infrastructure.md>), [networks](<https://devfeed.tech/tags/networks.md>), [regulatory](<https://devfeed.tech/tags/regulatory.md>), [scaling](<https://devfeed.tech/tags/scaling.md>), [scaling-ai](<https://devfeed.tech/tags/scaling-ai.md>)

### AI overview

The Digital Networks Act could support Europe's AI ambitions by reducing deployment barriers and directing investment toward high-performance, secure connectivity. The article recommends clearly limiting telecom obligations to the infrastructure providers they fit, while simplifying outdated rules; it cautions that extending them automatically to enterprise applications could add compliance costs without user benefit. It argues that resilience funding alone is insufficient: investment incentives should support fibre, optical transport, data-centre links and edge compute for high throughput and low latency. It also calls for licensed and unlicensed spectrum, including Wi-Fi, to complement 6G and satellite development, and for security to be built into infrastructure's lifecycle, with consistent enforcement and incentives to replace legacy technology. These are policy recommendations; the text does not establish that the proposed incentives or outcomes are already in place.

### Source excerpt

Three priorities for the Digital Networks Act to support Europe's AI ambitions: reducing regulatory burdens, scaling AI-ready infrastructure and modernising connectivity.

## This is the Meta MetaRoCE Network Adapter

DevFeed: [This is the Meta MetaRoCE Network Adapter](<https://devfeed.tech/articles/this-is-the-meta-metaroce-network-adapter-130994.md>)

Original publisher: [Read original article](<https://www.servethehome.com/this-is-the-meta-metaroce-network-adapter/>)

Author: Rohit Kumar

Published: 2026-11-12T04:51:39Z

Content type: news

Language: en

Sources: [ServeTheHome](<https://devfeed.tech/sources/servethehome.md>)

Topics: [Protocol (disambiguation)](<https://devfeed.tech/topics/protocol.md>), [Network architectures](<https://devfeed.tech/topics/network-architectures.md>), [AI Infrastructure](<https://devfeed.tech/topics/ai-infrastructure.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [adapter](<https://devfeed.tech/tags/adapter.md>), [clusters](<https://devfeed.tech/tags/clusters.md>), [congestion-control](<https://devfeed.tech/tags/congestion-control.md>), [convergence](<https://devfeed.tech/tags/convergence.md>), [ethernet](<https://devfeed.tech/tags/ethernet.md>), [fast](<https://devfeed.tech/tags/fast.md>), [features](<https://devfeed.tech/tags/features.md>), [gpu](<https://devfeed.tech/tags/gpu.md>), [hardware](<https://devfeed.tech/tags/hardware.md>), [hints](<https://devfeed.tech/tags/hints.md>), [implement](<https://devfeed.tech/tags/implement.md>), [layer](<https://devfeed.tech/tags/layer.md>), [meta](<https://devfeed.tech/tags/meta.md>), [metaroce](<https://devfeed.tech/tags/metaroce.md>), [network](<https://devfeed.tech/tags/network.md>), [networking](<https://devfeed.tech/tags/networking.md>), [ocp](<https://devfeed.tech/tags/ocp.md>), [ocp-summit](<https://devfeed.tech/tags/ocp-summit.md>), [scale](<https://devfeed.tech/tags/scale.md>), [training](<https://devfeed.tech/tags/training.md>)

### AI overview

MetaRoCE is Meta's open RDMA transport proposal for scaling training networks to million-GPU clusters. Its listed features include per-path reliability and congestion control, receiver rate hints for faster incast convergence, tolerance of packet loss and reordering, and multiple streams across network paths on a single queue pair. It is designed for commodity Ethernet using ECN and ECMP without switch changes. Meta previously demonstrated the protocol on programmable AMD Pensando NICs, which the excerpt says could let Meta source hardware from multiple vendors; an OCP NIC 3.0 adapter was displayed at OCP Summit 2026.

### Source excerpt

At OCP Summit 2026, Meta showed off its MetaRoCE adapter designed to scale to million-GPU training clusters The post This is the Meta MetaRoCE Network Adapter appeared first on ServeTheHome.

## Hacking the Sidekick in 2026

DevFeed: [Hacking the Sidekick in 2026](<https://devfeed.tech/articles/hacking-the-sidekick-in-2026-125076.md>)

Original publisher: [Read original article](<https://hackaday.com/2026/11/10/hacking-the-sidekick-in-2026/>)

Author: Navarre Bartz

Published: 2026-11-10T09:00:48Z

Content type: news

Language: en

Sources: [Hackaday](<https://devfeed.tech/sources/hackaday.md>)

Topics: [Hacking](<https://devfeed.tech/topics/hacking.md>), [Cryptography](<https://devfeed.tech/topics/cryptography.md>), [mobile-app-development](<https://devfeed.tech/topics/mobile-app-development.md>), [Embedded Software Dev](<https://devfeed.tech/topics/embedded-software-dev.md>), [Network architectures](<https://devfeed.tech/topics/network-architectures.md>)

Tags: [apps](<https://devfeed.tech/tags/apps.md>), [cado-nfs](<https://devfeed.tech/tags/cado-nfs.md>), [cellphone-hacks](<https://devfeed.tech/tags/cellphone-hacks.md>), [crack](<https://devfeed.tech/tags/crack.md>), [danger](<https://devfeed.tech/tags/danger.md>), [danger-hiptop](<https://devfeed.tech/tags/danger-hiptop.md>), [developer](<https://devfeed.tech/tags/developer.md>), [devices](<https://devfeed.tech/tags/devices.md>), [emulator](<https://devfeed.tech/tags/emulator.md>), [encryption](<https://devfeed.tech/tags/encryption.md>), [feature-phone](<https://devfeed.tech/tags/feature-phone.md>), [features](<https://devfeed.tech/tags/features.md>), [functionality](<https://devfeed.tech/tags/functionality.md>), [hacking](<https://devfeed.tech/tags/hacking.md>), [hiptop](<https://devfeed.tech/tags/hiptop.md>), [java](<https://devfeed.tech/tags/java.md>), [key](<https://devfeed.tech/tags/key.md>), [mobile](<https://devfeed.tech/tags/mobile.md>), [mobile-devices](<https://devfeed.tech/tags/mobile-devices.md>), [modem](<https://devfeed.tech/tags/modem.md>), [network](<https://devfeed.tech/tags/network.md>), [sidekick](<https://devfeed.tech/tags/sidekick.md>), [thin-client](<https://devfeed.tech/tags/thin-client.md>), [tmobile](<https://devfeed.tech/tags/tmobile.md>)

### AI overview

The T-Mobile Sidekick depended on Danger's web services, so shutting down the servers disabled much of its functionality. To run software locally, [ashe] found the Java OS SDK and used CADO-NFS to crack the system's 512-bit developer-key encryption and generate a device key. They used it to port a visual novel to a Sidekick 3, with endings delivered as text notifications through an emulated modem. Re:Danger server work aims to restore more features, but the replication described here works only with an emulated Sidekick; connecting a physical device over a planned GSM network remains future work.

### Source excerpt

The early 2000s saw a Cambrian Explosion of form factors for mobile devices, and one of the most feature-rich phones of the time was the Danger Hiptop, better known as ...read more

## 5 Network Devices for work-from-home and Small Business

DevFeed: [5 Network Devices for work-from-home and Small Business](<https://devfeed.tech/articles/5-network-devices-for-work-from-home-and-small-business-124175.md>)

Original publisher: [Read original article](<https://linuxblog.io/5-network-devices-for-work-from-home-and-small-business/>)

Author: Hayden James

Published: 2026-11-09T12:03:35Z

Content type: article

Language: en

Sources: [Hayden James](<https://devfeed.tech/sources/hayden-james.md>)

Topics: [Network architectures](<https://devfeed.tech/topics/network-architectures.md>), [network security](<https://devfeed.tech/topics/network-security.md>), [Homelab](<https://devfeed.tech/topics/homelab.md>), [Virtual Private Network](<https://devfeed.tech/topics/vpn.md>), [Network Attached Storage (NAS)](<https://devfeed.tech/topics/network-attached-storage-nas.md>), [OpenWrt](<https://devfeed.tech/topics/openwrt.md>)

Tags: [blog](<https://devfeed.tech/tags/blog.md>), [business](<https://devfeed.tech/tags/business.md>), [devices](<https://devfeed.tech/tags/devices.md>), [home](<https://devfeed.tech/tags/home.md>), [home-network](<https://devfeed.tech/tags/home-network.md>), [home-office](<https://devfeed.tech/tags/home-office.md>), [homelab](<https://devfeed.tech/tags/homelab.md>), [linux](<https://devfeed.tech/tags/linux.md>), [network](<https://devfeed.tech/tags/network.md>), [network-security](<https://devfeed.tech/tags/network-security.md>), [pfsense](<https://devfeed.tech/tags/pfsense.md>), [security](<https://devfeed.tech/tags/security.md>), [small-business](<https://devfeed.tech/tags/small-business.md>), [sysadmins](<https://devfeed.tech/tags/sysadmins.md>), [work](<https://devfeed.tech/tags/work.md>), [work-from-home](<https://devfeed.tech/tags/work-from-home.md>)

### AI overview

The article presents five network devices for home offices and small businesses, with November 2026 updates to several models. MikroTik's hEX S is an inexpensive router with SFP connectivity and gigabit speeds in a basic setup, though RouterOS can be difficult to learn. The Firewalla Purple SE is a simple security appliance with WireGuard, but is suited to ISP speeds around 300-400 Mbps and offers limited control for some features. GL.iNet's Brume 2 is a budget OpenWrt option for VPN service or site-to-site networking; WireGuard is specified at about 355 Mbps. Netgear's Nighthawk M7 Pro can provide 5G connectivity for failover or dual WAN, but is expensive, carrier compatibility matters, and its internal antennas may struggle in fringe areas. Netgate's 1100 runs pfSense Plus and offers firewall and VPN features, with throughput up to 500 Mbps as a firewall; boot and rule-application times can be slow. The text also covers the ZimaBoard 832 as a compact server option and notes that ZimaBoard 2 replaces it.

### Source excerpt

Over the past few years, we've seen a mass migration from the work office to the home office. This continues to increase the requirements for better home network security, capacity, and additional capabilities. Continue reading...

## Metasploit Wrapup: Unauth RCE modules in Network Perimeter Devices and much more

DevFeed: [Metasploit Wrapup: Unauth RCE modules in Network Perimeter Devices and much more](<https://devfeed.tech/articles/metasploit-wrapup-unauth-rce-modules-in-network-perimeter-devices-and-much-more-121387.md>)

Original publisher: [Read original article](<https://www.rapid7.com/blog/post/pt-metasploit-wrapup-unauth-rce-modules-in-network-perimeter-devices-and-much-more>)

Author: Jack Heysel

Published: 2026-11-06T13:52:11Z

Content type: release

Language: en

Sources: [Rapid7 Cybersecurity](<https://devfeed.tech/sources/rapid7-cybersecurity-blog.md>)

Topics: [Regular expression](<https://devfeed.tech/topics/regular-expression.md>), [Network architectures](<https://devfeed.tech/topics/network-architectures.md>)

Tags: [ci-cd](<https://devfeed.tech/tags/ci-cd.md>), [cisco](<https://devfeed.tech/tags/cisco.md>), [cisco-secure-email](<https://devfeed.tech/tags/cisco-secure-email.md>), [citrix](<https://devfeed.tech/tags/citrix.md>), [citrix-netscaler](<https://devfeed.tech/tags/citrix-netscaler.md>), [cybersecurity-company](<https://devfeed.tech/tags/cybersecurity-company.md>), [devices](<https://devfeed.tech/tags/devices.md>), [exposure-assessment-platform](<https://devfeed.tech/tags/exposure-assessment-platform.md>), [exposure-management](<https://devfeed.tech/tags/exposure-management.md>), [gitlab](<https://devfeed.tech/tags/gitlab.md>), [gitlab-ci](<https://devfeed.tech/tags/gitlab-ci.md>), [integer-overflow](<https://devfeed.tech/tags/integer-overflow.md>), [managed-detection-and-response](<https://devfeed.tech/tags/managed-detection-and-response.md>), [managed-security-solutions](<https://devfeed.tech/tags/managed-security-solutions.md>), [metasploit](<https://devfeed.tech/tags/metasploit.md>), [metasploit-weekly-wrapup](<https://devfeed.tech/tags/metasploit-weekly-wrapup.md>), [modules](<https://devfeed.tech/tags/modules.md>), [network](<https://devfeed.tech/tags/network.md>), [products-and-tools](<https://devfeed.tech/tags/products-and-tools.md>), [rce](<https://devfeed.tech/tags/rce.md>), [release](<https://devfeed.tech/tags/release.md>), [remote-code-execution](<https://devfeed.tech/tags/remote-code-execution.md>), [vulnerability-management](<https://devfeed.tech/tags/vulnerability-management.md>)

### AI overview

This Metasploit Framework release adds unauthenticated RCE modules for Citrix NetScaler and Cisco Secure Email Gateway, plus GitLab CI/CD RCE requiring credentials with write access to a public project. Other additions include Flowise account takeover through a password reset token exposed in the API response, SPIP password changes without an authorization check, and OpenBullet2 RCE and NTLMv2 hash disclosure affecting releases from 0.2.5 onward. Portainer's module requires valid credentials and access to a managed Docker environment to run a command as host root. The release also adds LoongArch64 fetch payloads and Windows AArch64 SMB payload generation, alongside Docker persistence support on Windows and assorted scanner, cleanup, dependency, and documentation fixes. The supplied text describes the listed release changes; it does not establish broader coverage.

### Source excerpt

Buckle up Metasploit-Framework enthusiasts because we have another action packed release for you. I'm talking, unauthenticated remote code execution modules in some of the biggest names in network perimeter devices like Citrix NetScaler and Cisco Secure Email Gateway. That's not all, we have an authenticated GitLab CI/CD regular expression integer overflow RCE module that was recently making head lines among many other awesome exploit modules. Looking for auxiliary modules?

## More 100G in every rack: Meet the Cisco N9348C8D-H2

DevFeed: [More 100G in every rack: Meet the Cisco N9348C8D-H2](<https://devfeed.tech/articles/more-100g-in-every-rack-meet-the-cisco-n9348c8d-h2-117181.md>)

Original publisher: [Read original article](<https://blogs.cisco.com/datacenter/more-100g-in-every-rack-meet-the-cisco-n9348c8d-h2>)

Author: Adhiraj Lahiri

Published: 2026-11-04T16:00:25Z

Content type: article

Language: en

Sources: [Cisco Blogs](<https://devfeed.tech/sources/cisco-blogs.md>)

Topics: [Cisco](<https://devfeed.tech/topics/cisco.md>), [Network architectures](<https://devfeed.tech/topics/network-architectures.md>), [cloud-infrastructure](<https://devfeed.tech/topics/cloud-infrastructure.md>), [observability](<https://devfeed.tech/topics/observability.md>), [High-Performance Computing](<https://devfeed.tech/topics/high-performance-computing.md>)

Tags: [25g](<https://devfeed.tech/tags/25g.md>), [400g](<https://devfeed.tech/tags/400g.md>), [aci](<https://devfeed.tech/tags/aci.md>), [ai](<https://devfeed.tech/tags/ai.md>), [airflow](<https://devfeed.tech/tags/airflow.md>), [apic](<https://devfeed.tech/tags/apic.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [asic](<https://devfeed.tech/tags/asic.md>), [buffer](<https://devfeed.tech/tags/buffer.md>), [capacity](<https://devfeed.tech/tags/capacity.md>), [choice](<https://devfeed.tech/tags/choice.md>), [cisco](<https://devfeed.tech/tags/cisco.md>), [cisco-live](<https://devfeed.tech/tags/cisco-live.md>), [cisco-live-melbourne](<https://devfeed.tech/tags/cisco-live-melbourne.md>), [cisco-nexus](<https://devfeed.tech/tags/cisco-nexus.md>), [cisco-nexus-dashboard](<https://devfeed.tech/tags/cisco-nexus-dashboard.md>), [classification](<https://devfeed.tech/tags/classification.md>), [cloud-environments](<https://devfeed.tech/tags/cloud-environments.md>), [data-center](<https://devfeed.tech/tags/data-center.md>), [data-center-networking](<https://devfeed.tech/tags/data-center-networking.md>), [leaf-switch](<https://devfeed.tech/tags/leaf-switch.md>), [software](<https://devfeed.tech/tags/software.md>), [switch](<https://devfeed.tech/tags/switch.md>)

### AI overview

The Cisco N9348C8D-H2 packs 48 flexible 100G SFP-DD ports and eight 400G QSFP-DD uplinks into a fixed 1RU switch, addressing demand for dense leaf capacity alongside faster spine links. Its SFP-DD ports support 10G, 25G, 50G, and 100G, with supported breakouts to two 50G SFP56 endpoints; the uplinks support up to 400G and can break out to four 100G QSFP28 endpoints. The switch delivers up to 8 Tbps of forwarding capacity and supports either NX-OS or ACI, managed through Nexus Dashboard or APIC in the corresponding environment. Telemetry options include flow telemetry, flow table events, and streaming statistics export; PTP, reversible airflow, and AC or DC power options support varied operations and facilities. The source presents it as a platform for new 100G fabrics or transitions from slower access speeds.

### Source excerpt

See how the Cisco N9348C8D-H2 combines dense 100G ports, 400G uplinks, and software choice in a compact 1RU leaf switch.

## Marvell Proposes Acquiring Lumentum to Combine Optical Circuit Switching with AI Connectivity Silicon

DevFeed: [Marvell Proposes Acquiring Lumentum to Combine Optical Circuit Switching with AI Connectivity Silicon](<https://devfeed.tech/articles/marvell-proposes-acquiring-lumentum-to-combine-optical-circuit-switching-with-ai-connectivity-silicon-113893.md>)

Original publisher: [Read original article](<https://www.servethehome.com/marvell-to-acquire-lumentum-115-billion-optical-ai-connectivity/>)

Author: Cliff Robinson

Published: 2026-11-02T22:30:09Z

Content type: news

Language: en

Sources: [ServeTheHome](<https://devfeed.tech/sources/servethehome.md>)

Topics: [communications](<https://devfeed.tech/topics/communications.md>), [Network architectures](<https://devfeed.tech/topics/network-architectures.md>), [Chip design](<https://devfeed.tech/topics/chip-design.md>), [AI Infrastructure](<https://devfeed.tech/topics/ai-infrastructure.md>)

Tags: [acquisition](<https://devfeed.tech/tags/acquisition.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-clusters](<https://devfeed.tech/tags/ai-clusters.md>), [ai-connectivity](<https://devfeed.tech/tags/ai-connectivity.md>), [ai-infrastructure](<https://devfeed.tech/tags/ai-infrastructure.md>), [co-design](<https://devfeed.tech/tags/co-design.md>), [co-packaged-optics](<https://devfeed.tech/tags/co-packaged-optics.md>), [coherent](<https://devfeed.tech/tags/coherent.md>), [compute](<https://devfeed.tech/tags/compute.md>), [connectivity](<https://devfeed.tech/tags/connectivity.md>), [copper](<https://devfeed.tech/tags/copper.md>), [cpo](<https://devfeed.tech/tags/cpo.md>), [custom-silicon](<https://devfeed.tech/tags/custom-silicon.md>), [data-center](<https://devfeed.tech/tags/data-center.md>), [lumentum](<https://devfeed.tech/tags/lumentum.md>), [marvell](<https://devfeed.tech/tags/marvell.md>), [networking](<https://devfeed.tech/tags/networking.md>), [optical](<https://devfeed.tech/tags/optical.md>), [optical-connectivity](<https://devfeed.tech/tags/optical-connectivity.md>), [silicon](<https://devfeed.tech/tags/silicon.md>), [switching](<https://devfeed.tech/tags/switching.md>)

### AI overview

Marvell proposes acquiring Lumentum in an all-stock deal valued at about $115 billion, combining Marvell's interconnect and custom silicon capabilities with Lumentum's lasers, compound semiconductor manufacturing, and optical circuit switching (OCS). The stated aim is closer co-design across the signal chain as rising lane speeds bring copper's distance limits closer and AI clusters demand more connectivity. The combination could support tighter integration such as co-packaged optics: near-package optical engines shorten electrical paths, replacing long PCB traces with fiber runs and pluggable light sources. Lumentum's R300 OCS uses MEMS mirrors to establish direct optical paths, avoiding intermediate packet processing and optical-electrical-optical conversion on switched paths; Lumentum says this lowers latency and network power while improving signal integrity. The article describes those benefits as company claims. Marvell intends to bring more of the supply chain in-house and develop integrated, pre-validated solutions. The deal is expected to close in the first half of 2028; afterward, Marvell shareholders would own 67% and Lumentum shareholders 33%.

### Source excerpt

Marvell announced its intention to acquire Lumentum in a $115B acquisition to further optical connectivity in the AI era The post Marvell Proposes Acquiring Lumentum to Combine Optical Circuit Switching with AI Connectivity Silicon appeared first on ServeTheHome.

## Expect more from your wireless network: A playbook for growing businesses

DevFeed: [Expect more from your wireless network: A playbook for growing businesses](<https://devfeed.tech/articles/expect-more-from-your-wireless-network-a-playbook-for-growing-businesses-104751.md>)

Original publisher: [Read original article](<https://blogs.cisco.com/networking/expect-more-from-your-wireless-network-a-playbook-for-growing-businesses>)

Author: Amrit Nijjer

Published: 2026-10-28T15:00:41Z

Content type: tutorial

Language: en

Sources: [Cisco Blogs](<https://devfeed.tech/sources/cisco-blogs.md>)

Topics: [Wi-Fi](<https://devfeed.tech/topics/wi-fi.md>), [Network architectures](<https://devfeed.tech/topics/network-architectures.md>), [Cloud Networking](<https://devfeed.tech/topics/cloud-networking.md>), [network security](<https://devfeed.tech/topics/network-security.md>), [observability](<https://devfeed.tech/topics/observability.md>)

Tags: [2](<https://devfeed.tech/tags/2.md>), [2026](<https://devfeed.tech/tags/2026.md>), [3](<https://devfeed.tech/tags/3.md>), [access-point](<https://devfeed.tech/tags/access-point.md>), [access-points](<https://devfeed.tech/tags/access-points.md>), [acquisition](<https://devfeed.tech/tags/acquisition.md>), [adaptive](<https://devfeed.tech/tags/adaptive.md>), [agenticops](<https://devfeed.tech/tags/agenticops.md>), [agents](<https://devfeed.tech/tags/agents.md>), [business](<https://devfeed.tech/tags/business.md>), [can](<https://devfeed.tech/tags/can.md>), [complex](<https://devfeed.tech/tags/complex.md>), [devices](<https://devfeed.tech/tags/devices.md>), [infrastructure](<https://devfeed.tech/tags/infrastructure.md>), [it](<https://devfeed.tech/tags/it.md>), [network](<https://devfeed.tech/tags/network.md>), [network-management](<https://devfeed.tech/tags/network-management.md>), [network-security](<https://devfeed.tech/tags/network-security.md>), [networking](<https://devfeed.tech/tags/networking.md>), [operations](<https://devfeed.tech/tags/operations.md>), [security](<https://devfeed.tech/tags/security.md>), [wi-fi-7](<https://devfeed.tech/tags/wi-fi-7.md>), [wireless](<https://devfeed.tech/tags/wireless.md>), [wireless-networking](<https://devfeed.tech/tags/wireless-networking.md>), [with](<https://devfeed.tech/tags/with.md>)

### AI overview

As a business grows, its wireless network needs to support more locations, devices and operational demands while remaining manageable. The excerpt recommends testing Wi-Fi against important applications and devices at busy times and in challenging spaces, then evaluating how incidents are diagnosed and fixed, access policies are maintained across locations, and designs extend to future sites. It describes Cisco Cloud Control's Experience Metrics for examining failures across association, authentication, DHCP and roaming; Cisco AgenticOps for automating defined tasks with optional operator approval; and Meraki Adaptive Policy for deploying device groups and access rules to participating networks. The suggested evaluation uses four scenarios: a demanding site, a business-critical device, a previously encountered failure, and a policy that must work across locations. The excerpt does not establish that these capabilities work across every environment.

### Source excerpt

Your business is growing. Can your network infrastructure evolve with you? With wireless operations becoming more complex, IT leaders should ensure the network can handle more locations, devices, and security threats. Read our playbook to see how.

## Where Does My Call Go? Measuring Google Meet, Zoom, and Microsoft Teams on Starlink

DevFeed: [Where Does My Call Go? Measuring Google Meet, Zoom, and Microsoft Teams on Starlink](<https://devfeed.tech/articles/where-does-my-call-go-measuring-google-meet-zoom-and-microsoft-teams-on-starlink-104195.md>)

Original publisher: [Read original article](<https://arxiv.org/abs/2610.35874>)

Author: Kousar Malekinasab, Mostafa Abdollah, Jinwei Zhao, Jianping Pan

Published: 2026-10-28T04:00:00Z

Content type: news

Language: en

Sources: [arXiv: Networking](<https://devfeed.tech/sources/arxiv-networking.md>)

Topics: [Network architectures](<https://devfeed.tech/topics/network-architectures.md>), [Internet Traffic](<https://devfeed.tech/topics/internet-traffic.md>), [Google Meet](<https://devfeed.tech/topics/google-meet.md>), [Microsoft Teams](<https://devfeed.tech/topics/microsoft-teams.md>), [zoom](<https://devfeed.tech/topics/zoom.md>)

Tags: [cs-ni](<https://devfeed.tech/tags/cs-ni.md>), [google](<https://devfeed.tech/tags/google.md>), [leo](<https://devfeed.tech/tags/leo.md>), [low-earth-orbit](<https://devfeed.tech/tags/low-earth-orbit.md>), [microsoft](<https://devfeed.tech/tags/microsoft.md>), [microsoft-teams](<https://devfeed.tech/tags/microsoft-teams.md>), [performance](<https://devfeed.tech/tags/performance.md>), [starlink](<https://devfeed.tech/tags/starlink.md>), [zoom](<https://devfeed.tech/tags/zoom.md>)

### AI overview

Measurements from a Canada-wide testbed and over 24 hours of in-flight experiments found that Google Meet tends to select service points closer to Starlink's serving PoP, Zoom uses a regional selection pattern, and Microsoft Teams often stays tied to fixed service points. During in-flight PoP handovers, traffic egress can shift mid-session; platforms respond differently, sometimes choosing suboptimal service points and increasing round-trip time. The abstract suggests these results reflect a mismatch between Starlink's changing egress and RTC selection mechanisms shaped by terrestrial networks, and motivate further measurement and LEO-optimized placement and selection.

### Source excerpt

arXiv:2610.35874v1 Announce Type: new Abstract: Low-Earth-Orbit (LEO) satellite networks are expanding broadband access, but major Real-Time Communication (RTC) platforms, including Google Meet, Zoom, and Microsoft Teams, still rely on service-point selection mechanisms that appear to be largely shaped by terrestrial-network assumptions. As a result, they may not consistently account for LEO-specific dynamics such as satellite topology and Point-of-Presence (PoP) changes, especially during in-flight connectivity. To characterize RTC service-point selection over Starlink, we measure RTC performance using a Canada-wide testbed and more than 24 hours of in-flight experiments. Our results show clear platform differences. Google Meet tends to align more closely with the serving PoP, consistent with broader observed edge coverage. Zoom follows a regional service-point selection pattern, while Microsoft Teams often remains tied to fixed service points. Moreover, we show that in-flight PoP handovers can shift traffic egress points mid-session, and that RTC platforms respond differently to these changes. In some cases, this interaction leads to suboptimal service-point selections and RTT inflation. Overall, our findings suggest that LEO connectivity can expose mismatches between Starlink egress dynamics and RTC service-point selection, motivating further measurement and LEO-optimized designs for service placement and selection.

## Turning network requests into business-ready connectivity

DevFeed: [Turning network requests into business-ready connectivity](<https://devfeed.tech/articles/turning-network-requests-into-business-ready-connectivity-100829.md>)

Original publisher: [Read original article](<https://blogs.cisco.com/networking/turning-network-requests-into-business-ready-connectivity>)

Author: Lee Peterson

Published: 2026-10-26T19:30:56Z

Content type: article

Language: en

Sources: [Cisco Blogs](<https://devfeed.tech/sources/cisco-blogs.md>)

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

Tags: [activation](<https://devfeed.tech/tags/activation.md>), [application](<https://devfeed.tech/tags/application.md>), [automation](<https://devfeed.tech/tags/automation.md>), [bandwidth](<https://devfeed.tech/tags/bandwidth.md>), [cisco](<https://devfeed.tech/tags/cisco.md>), [cisco-router](<https://devfeed.tech/tags/cisco-router.md>), [connectivity](<https://devfeed.tech/tags/connectivity.md>), [demand](<https://devfeed.tech/tags/demand.md>), [edge](<https://devfeed.tech/tags/edge.md>), [fiber-network](<https://devfeed.tech/tags/fiber-network.md>), [ipv6](<https://devfeed.tech/tags/ipv6.md>), [lifecycle](<https://devfeed.tech/tags/lifecycle.md>), [manage](<https://devfeed.tech/tags/manage.md>), [monitor](<https://devfeed.tech/tags/monitor.md>), [network](<https://devfeed.tech/tags/network.md>), [network-edge](<https://devfeed.tech/tags/network-edge.md>), [network-services](<https://devfeed.tech/tags/network-services.md>), [networking](<https://devfeed.tech/tags/networking.md>), [networks](<https://devfeed.tech/tags/networks.md>), [operations](<https://devfeed.tech/tags/operations.md>), [routers](<https://devfeed.tech/tags/routers.md>), [srv6](<https://devfeed.tech/tags/srv6.md>)

### AI overview

Bell On-Demand Network combines Bell's fiber network and digital service experience with Cisco infrastructure to let customers order, activate, manage, and scale connectivity. Cisco 8000 Series Secure Routers bring routing, integrated security capabilities, policy controls, and operational visibility to the customer edge; the text says segmentation can limit how far a problem spreads and security policy can be applied as connectivity is provisioned. Bell uses SRv6 to steer traffic along selected paths, extending programmable traffic handling toward customer premises equipment. The article says this can simplify service creation, support application-aware engineering, and reduce demands on provider-edge routers. Repeatable, automated service changes are presented as a way to reduce manual coordination as bandwidth or site needs change.

### Source excerpt

How Cisco 8000 Series Secure Routers and SRv6 support Bell On-Demand Network

## Does Client Diversity Protect the Lightning Network? Evidence from the 2026 Core Lightning Shutdown

DevFeed: [Does Client Diversity Protect the Lightning Network? Evidence from the 2026 Core Lightning Shutdown](<https://devfeed.tech/articles/does-client-diversity-protect-the-lightning-network-evidence-from-the-2026-core-lightning-shutdown-94515.md>)

Original publisher: [Read original article](<https://arxiv.org/abs/2610.20952>)

Author: Saurabh Kumar

Published: 2026-10-22T04:00:00Z

Content type: article

Language: en

Sources: [arXiv: Cryptography and Security](<https://devfeed.tech/sources/arxiv-cryptography-and-security.md>)

Topics: [Network architectures](<https://devfeed.tech/topics/network-architectures.md>), [network security](<https://devfeed.tech/topics/network-security.md>), [tor](<https://devfeed.tech/topics/tor.md>)

Tags: [2023](<https://devfeed.tech/tags/2023.md>), [2026](<https://devfeed.tech/tags/2026.md>), [22](<https://devfeed.tech/tags/22.md>), [about](<https://devfeed.tech/tags/about.md>), [abstract](<https://devfeed.tech/tags/abstract.md>), [aliases](<https://devfeed.tech/tags/aliases.md>), [all](<https://devfeed.tech/tags/all.md>), [arxiv](<https://devfeed.tech/tags/arxiv.md>), [blast-radius](<https://devfeed.tech/tags/blast-radius.md>), [bug](<https://devfeed.tech/tags/bug.md>), [builds](<https://devfeed.tech/tags/builds.md>), [capacity](<https://devfeed.tech/tags/capacity.md>), [channel](<https://devfeed.tech/tags/channel.md>), [client](<https://devfeed.tech/tags/client.md>), [core](<https://devfeed.tech/tags/core.md>), [cs-cr](<https://devfeed.tech/tags/cs-cr.md>), [diversity](<https://devfeed.tech/tags/diversity.md>), [lightning](<https://devfeed.tech/tags/lightning.md>), [lightning-network](<https://devfeed.tech/tags/lightning-network.md>), [network](<https://devfeed.tech/tags/network.md>), [shutdown](<https://devfeed.tech/tags/shutdown.md>)

### AI overview

The 2026 Core Lightning (CLN) shutdown left 22% of CLN nodes offline overnight, and a third remained dark five weeks later, but overall network reachability fell only 7.8 percentage points. The study analyzes 805 gossip snapshots and 132,360 channel closes; the decline was unusually severe within CLN, while the rest of the network was little affected. Calibrated failure scenarios suggest the impact depends more on whether a failure reaches major hubs than on the number of nodes running an implementation: losing ACINQ's Eclair node alone reduced reachability four times as much as losing all 619 routable CLN nodes. The authors argue node-count diversity is a poor resilience measure and that the software used by hubs matters more. These findings are based on the abstract's reported analysis.

### Source excerpt

arXiv:2610.20952v2 Announce Type: replace Abstract: Client diversity is often cited as the Lightning Network's defence against a bug in any one implementation, yet LND runs 80% of public nodes (84% counting one operator's fleet of about 2,000 tiny nodes) and holds 84% of public channel capacity, a capacity share that has barely moved since 2023. We test what diversity buys with a natural experiment. On 26 August 2026, amid security fixes in every implementation, Core Lightning (CLN) maintainers told operators who could not upgrade to disconnect their nodes. Using 805 daily gossip snapshots, 132,360 on-chain channel closes and a client classifier validated against self-identifying aliases and against the wallet that builds each node's funding transactions, we find that 22% of CLN nodes went dark overnight, ten times the usual rate, mostly Tor-reachable ones; a third were still dark five weeks later. The rest of the network barely noticed. Reachability among all node pairs fell by 7.8 percentage points, a loss exceeded in 4 of 94 ordinary two-day windows and half that of a Tor denial-of-service wave in July, while among CLN pairs it fell by 24.5 points, more than in any ordinary window. Calibrated failure scenarios explain the containment: the blast radius depends on whether a failure reaches the hubs, not on how many nodes run the failing software. Losing ACINQ's Eclair node alone costs the surviving network four times the reachability lost with all 619 routable CLN nodes, and minority clients' reliance on LND for connectivity is what their size implies; CLN nodes in fact peer with each other more than chance. Diversity statistics that count nodes mislead; the quantity to track is which software the hubs run.

## Tenant Connectivity on VCF 9.1: Choosing a Design and Running It in Production (Part 6)

DevFeed: [Tenant Connectivity on VCF 9.1: Choosing a Design and Running It in Production (Part 6)](<https://devfeed.tech/articles/tenant-connectivity-on-vcf-9-1-choosing-a-design-and-running-it-in-production-part-6-91193.md>)

Original publisher: [Read original article](<https://blogs.vmware.com/cloud-foundation/2026/10/20/tenant-connectivity-on-vcf-9-1-choosing-a-design-and-running-it-in-production-part-6/>)

Author: mohammad saad

Published: 2026-10-20T17:25:07Z

Content type: tutorial

Language: en

Sources: [VMware](<https://devfeed.tech/sources/vmware-blogs.md>)

Topics: [vcf networking](<https://devfeed.tech/topics/vcf-networking.md>), [VMware Cloud Foundation](<https://devfeed.tech/topics/vcf-9-1.md>), [NAT and SNAT](<https://devfeed.tech/topics/nat-and-snat.md>), [CIDR and subnets](<https://devfeed.tech/topics/cidr-and-subnets.md>), [Network architectures](<https://devfeed.tech/topics/network-architectures.md>)

Tags: [2](<https://devfeed.tech/tags/2.md>), [3](<https://devfeed.tech/tags/3.md>), [allowed](<https://devfeed.tech/tags/allowed.md>), [article](<https://devfeed.tech/tags/article.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [cloud-infrastructure](<https://devfeed.tech/tags/cloud-infrastructure.md>), [connectivity](<https://devfeed.tech/tags/connectivity.md>), [design](<https://devfeed.tech/tags/design.md>), [enterprise](<https://devfeed.tech/tags/enterprise.md>), [external](<https://devfeed.tech/tags/external.md>), [first](<https://devfeed.tech/tags/first.md>), [foundation](<https://devfeed.tech/tags/foundation.md>), [multi-tenancy](<https://devfeed.tech/tags/multi-tenancy.md>), [network](<https://devfeed.tech/tags/network.md>), [network-design](<https://devfeed.tech/tags/network-design.md>), [nsx](<https://devfeed.tech/tags/nsx.md>), [packet](<https://devfeed.tech/tags/packet.md>), [production](<https://devfeed.tech/tags/production.md>), [providers](<https://devfeed.tech/tags/providers.md>), [running](<https://devfeed.tech/tags/running.md>), [series](<https://devfeed.tech/tags/series.md>), [vcf](<https://devfeed.tech/tags/vcf.md>), [vcf-9-1](<https://devfeed.tech/tags/vcf-9-1.md>), [vcf-networking](<https://devfeed.tech/tags/vcf-networking.md>), [vcf-networking-nsx](<https://devfeed.tech/tags/vcf-networking-nsx.md>), [vmware-cloud-service-providers](<https://devfeed.tech/tags/vmware-cloud-service-providers.md>), [vpc](<https://devfeed.tech/tags/vpc.md>)

### AI overview

A VCF 9.1 multi-connection Transit Gateway can combine three outbound source-address behaviors by exit: Default Outbound NAT for the Internet, Provider SNAT to present provider-owned addresses, or Private-TGW advertisement to expose workload addresses to an enterprise. Provider SNAT and advertisement are mutually exclusive on each connection; advertisement works only for Private-TGW subnets and requires both provider authorization and a tenant advertise rule. The profile has one Auto SNAT block, which should match the default-route connection, while other exits need their own SNAT or advertisement policy. The article gives live-change sequences and checks for gateway status, authorized blocks, routes, NAT rules and end-to-end translations. It warns that changing the Auto SNAT block requires briefly disabling Default Outbound NAT, disrupting some paths, and that moving from SNAT to advertisement leaves enterprise traffic unreachable until the tenant rule is installed.

### Source excerpt

This article is part of a six-part series on tenant external connectivity for cloud providers running VMware Cloud Foundation 9.1: Part 1: A Standard Network Design for Cloud Providers Part 2: What Decides a Packet's Source Address Part 3: When Only Provider Addresses Are Allowed Part 4: When the Enterprise Must See Real Workload Addresses ... Continued The post Tenant Connectivity on VCF 9.1: Choosing a Design and Running It in Production (Part 6) appeared first on VMware Blogs.

## Tenant Connectivity on VCF 9.1: Serving the Data Center, Shared Services and the Internet from One Gateway (Part 5)

DevFeed: [Tenant Connectivity on VCF 9.1: Serving the Data Center, Shared Services and the Internet from One Gateway (Part 5)](<https://devfeed.tech/articles/tenant-connectivity-on-vcf-9-1-serving-the-data-center-shared-services-and-the-internet-from-one-gateway-part-5-91194.md>)

Original publisher: [Read original article](<https://blogs.vmware.com/cloud-foundation/2026/10/20/tenant-connectivity-on-vcf-9-1-serving-the-data-center-shared-services-and-the-internet-from-one-gateway-part-5/>)

Author: mohammad saad

Published: 2026-10-20T17:24:32Z

Content type: tutorial

Language: en

Sources: [VMware](<https://devfeed.tech/sources/vmware-blogs.md>)

Topics: [vcf networking](<https://devfeed.tech/topics/vcf-networking.md>), [NAT and SNAT](<https://devfeed.tech/topics/nat-and-snat.md>), [VMware Cloud Foundation](<https://devfeed.tech/topics/vcf-9-1.md>), [CIDR and subnets](<https://devfeed.tech/topics/cidr-and-subnets.md>), [Network architectures](<https://devfeed.tech/topics/network-architectures.md>), [gateway](<https://devfeed.tech/topics/gateway.md>)

Tags: [2](<https://devfeed.tech/tags/2.md>), [3](<https://devfeed.tech/tags/3.md>), [allowed](<https://devfeed.tech/tags/allowed.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [cloud-infrastructure](<https://devfeed.tech/tags/cloud-infrastructure.md>), [connectivity](<https://devfeed.tech/tags/connectivity.md>), [data](<https://devfeed.tech/tags/data.md>), [data-center](<https://devfeed.tech/tags/data-center.md>), [design](<https://devfeed.tech/tags/design.md>), [enterprise](<https://devfeed.tech/tags/enterprise.md>), [external](<https://devfeed.tech/tags/external.md>), [first](<https://devfeed.tech/tags/first.md>), [foundation](<https://devfeed.tech/tags/foundation.md>), [gateway](<https://devfeed.tech/tags/gateway.md>), [internet](<https://devfeed.tech/tags/internet.md>), [multi-tenancy](<https://devfeed.tech/tags/multi-tenancy.md>), [network](<https://devfeed.tech/tags/network.md>), [nsx](<https://devfeed.tech/tags/nsx.md>), [packet](<https://devfeed.tech/tags/packet.md>), [services](<https://devfeed.tech/tags/services.md>), [source](<https://devfeed.tech/tags/source.md>), [vcf](<https://devfeed.tech/tags/vcf.md>), [vcf-9-1](<https://devfeed.tech/tags/vcf-9-1.md>), [vcf-networking](<https://devfeed.tech/tags/vcf-networking.md>), [vcf-networking-nsx](<https://devfeed.tech/tags/vcf-networking-nsx.md>), [vmware-cloud-service-providers](<https://devfeed.tech/tags/vmware-cloud-service-providers.md>), [vpc](<https://devfeed.tech/tags/vpc.md>)

### AI overview

The design gives tenant Riyadh three exits with distinct source-address rules: the enterprise data center receives Private-TGW addresses unchanged, shared services sees all tenant traffic through a provider-owned SNAT pool, and Internet traffic uses the tenant's Default Outbound NAT. It combines WAN advertisement of the Private-TGW block with Provider Outbound SNAT scoped to the shared-services connection; the provider SNAT pool is authorized there but never assigned to the tenant project. Private-VPC traffic is translated at its VPC gateway, so the data center sees its Auto SNAT address, and shared-services traffic is translated again at the CTGW. The excerpt specifies provider-first connection and block setup, followed by tenant gateway attachments, profile settings and a WAN advertise rule. It notes that each connection's settings are scoped independently, remote networks must be unique, and Provider SNAT and advertisement cannot coexist on the same connection.

### Source excerpt

This article is part of a six-part series on tenant external connectivity for cloud providers running VMware Cloud Foundation 9.1: Part 1: A Standard Network Design for Cloud Providers Part 2: What Decides a Packet's Source Address Part 3: When Only Provider Addresses Are Allowed Part 4: When the Enterprise Must See Real Workload Addresses ... Continued The post Tenant Connectivity on VCF 9.1: Serving the Data Center, Shared Services and the Internet from One Gateway (Part 5) appeared first on VMware Blogs.

## Tenant Connectivity on VCF 9.1: When the Enterprise Must See Real Workload Addresses (Part 4)

DevFeed: [Tenant Connectivity on VCF 9.1: When the Enterprise Must See Real Workload Addresses (Part 4)](<https://devfeed.tech/articles/tenant-connectivity-on-vcf-9-1-when-the-enterprise-must-see-real-workload-addresses-part-4-91197.md>)

Original publisher: [Read original article](<https://blogs.vmware.com/cloud-foundation/2026/10/20/tenant-connectivity-on-vcf-9-1-when-the-enterprise-must-see-real-workload-addresses-part-4/>)

Author: mohammad saad

Published: 2026-10-20T17:23:27Z

Content type: article

Language: en

Sources: [VMware](<https://devfeed.tech/sources/vmware-blogs.md>)

Topics: [NAT and SNAT](<https://devfeed.tech/topics/nat-and-snat.md>), [vcf networking](<https://devfeed.tech/topics/vcf-networking.md>), [VMware Cloud Foundation](<https://devfeed.tech/topics/vcf-9-1.md>), [Network architectures](<https://devfeed.tech/topics/network-architectures.md>), [CIDR and subnets](<https://devfeed.tech/topics/cidr-and-subnets.md>)

Tags: [advertisement](<https://devfeed.tech/tags/advertisement.md>), [alex](<https://devfeed.tech/tags/alex.md>), [bgp](<https://devfeed.tech/tags/bgp.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [cloud-infrastructure](<https://devfeed.tech/tags/cloud-infrastructure.md>), [connectivity](<https://devfeed.tech/tags/connectivity.md>), [data-center](<https://devfeed.tech/tags/data-center.md>), [design](<https://devfeed.tech/tags/design.md>), [enterprise](<https://devfeed.tech/tags/enterprise.md>), [firewall](<https://devfeed.tech/tags/firewall.md>), [gateway](<https://devfeed.tech/tags/gateway.md>), [gateways](<https://devfeed.tech/tags/gateways.md>), [integration](<https://devfeed.tech/tags/integration.md>), [multi-tenancy](<https://devfeed.tech/tags/multi-tenancy.md>), [network](<https://devfeed.tech/tags/network.md>), [network-design](<https://devfeed.tech/tags/network-design.md>), [nsx](<https://devfeed.tech/tags/nsx.md>), [packet](<https://devfeed.tech/tags/packet.md>), [providers](<https://devfeed.tech/tags/providers.md>), [vcf](<https://devfeed.tech/tags/vcf.md>), [vcf-9-1](<https://devfeed.tech/tags/vcf-9-1.md>), [vcf-networking](<https://devfeed.tech/tags/vcf-networking.md>), [vcf-networking-nsx](<https://devfeed.tech/tags/vcf-networking-nsx.md>), [vmware](<https://devfeed.tech/tags/vmware.md>), [vmware-cloud-foundation](<https://devfeed.tech/tags/vmware-cloud-foundation.md>), [vmware-cloud-service-providers](<https://devfeed.tech/tags/vmware-cloud-service-providers.md>), [vpc](<https://devfeed.tech/tags/vpc.md>)

### AI overview

The article presents two VCF 9.1 designs for Private-TGW workloads that need enterprise and Internet access. In both, Default Outbound NAT at the CTGW translates Internet-bound traffic to the Internet block. For use case B, the enterprise can route the tenant's private block and wants workload addresses visible: enable Private-Transit Gateway block advertisement on the enterprise connection, add a tenant advertise rule, and leave Provider SNAT off. The private block is then advertised into the enterprise routing domain; it must be unique and routable there. For use case C, the enterprise accepts only a provider-assigned range or cannot route the tenant block: disable the private-block toggle and advertisement, and enable Provider Outbound SNAT on the enterprise connection. These connection settings are mutually exclusive. Without that SNAT, enterprise traffic would use the Internet block and be unreachable on that connection; without Default Outbound NAT, Internet-bound Private-TGW traffic lacks an authorized source. The excerpt notes that Private-VPC workloads are SNATed before reaching the CTGW, while Private-TGW workloads retain their private address until CTGW processing.

### Source excerpt

This article is part of a six-part series on tenant external connectivity for cloud providers running VMware Cloud Foundation 9.1: Part 1: A Standard Network Design for Cloud Providers Part 2: What Decides a Packet's Source Address Part 3: When Only Provider Addresses Are Allowed Part 4: When the Enterprise Must See Real Workload Addresses ... Continued The post Tenant Connectivity on VCF 9.1: When the Enterprise Must See Real Workload Addresses (Part 4) appeared first on VMware Blogs.

## Tenant Connectivity on VCF 9.1: What Decides a Packet's Source Address (Part 2)

DevFeed: [Tenant Connectivity on VCF 9.1: What Decides a Packet's Source Address (Part 2)](<https://devfeed.tech/articles/tenant-connectivity-on-vcf-9-1-what-decides-a-packet-s-source-address-part-2-91195.md>)

Original publisher: [Read original article](<https://blogs.vmware.com/cloud-foundation/2026/10/20/tenant-connectivity-on-vcf-9-1-what-decides-a-packets-source-address-part-2/>)

Author: vmwareblogs

Published: 2026-10-20T17:21:48Z

Content type: article

Language: en

Sources: [VMware](<https://devfeed.tech/sources/vmware-blogs.md>)

Topics: [NAT and SNAT](<https://devfeed.tech/topics/nat-and-snat.md>), [vcf networking](<https://devfeed.tech/topics/vcf-networking.md>), [Network architectures](<https://devfeed.tech/topics/network-architectures.md>), [VMware Cloud Foundation](<https://devfeed.tech/topics/vcf-9-1.md>), [ip-address-planning](<https://devfeed.tech/topics/ip-address-planning.md>), [CIDR and subnets](<https://devfeed.tech/topics/cidr-and-subnets.md>)

Tags: [2](<https://devfeed.tech/tags/2.md>), [3](<https://devfeed.tech/tags/3.md>), [allowed](<https://devfeed.tech/tags/allowed.md>), [article](<https://devfeed.tech/tags/article.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [cloud-infrastructure](<https://devfeed.tech/tags/cloud-infrastructure.md>), [connectivity](<https://devfeed.tech/tags/connectivity.md>), [design](<https://devfeed.tech/tags/design.md>), [enterprise](<https://devfeed.tech/tags/enterprise.md>), [external](<https://devfeed.tech/tags/external.md>), [first](<https://devfeed.tech/tags/first.md>), [foundation](<https://devfeed.tech/tags/foundation.md>), [multi-tenancy](<https://devfeed.tech/tags/multi-tenancy.md>), [network](<https://devfeed.tech/tags/network.md>), [network-design](<https://devfeed.tech/tags/network-design.md>), [nsx](<https://devfeed.tech/tags/nsx.md>), [packet](<https://devfeed.tech/tags/packet.md>), [providers](<https://devfeed.tech/tags/providers.md>), [running](<https://devfeed.tech/tags/running.md>), [series](<https://devfeed.tech/tags/series.md>), [source](<https://devfeed.tech/tags/source.md>), [vcf](<https://devfeed.tech/tags/vcf.md>), [vcf-9-1](<https://devfeed.tech/tags/vcf-9-1.md>), [vcf-networking](<https://devfeed.tech/tags/vcf-networking.md>), [vcf-networking-nsx](<https://devfeed.tech/tags/vcf-networking-nsx.md>), [vmware-cloud-service-providers](<https://devfeed.tech/tags/vmware-cloud-service-providers.md>), [vpc](<https://devfeed.tech/tags/vpc.md>)

### AI overview

In VCF 9.1, a tenant Transit Gateway can use several External Connections, while the source address on each outbound packet depends on its route, NAT settings, and the address blocks authorized on the chosen connection. Default Outbound NAT uses the VPC Connectivity Profile's Auto SNAT block; because that block may be authorized on only one connection, other exits need Provider Outbound SNAT or, for Private-TGW subnets, a two-part advertisement setup: provider permission on the connection and a tenant advertise rule. Provider SNAT translates unauthorized sources per connection and passes authorized sources unchanged. The CTGW routes by destination before applying connection-level handling; only one default route is allowed, and each remote prefix can belong to only one connection. A source not authorized or advertised on the exit has no return path. The excerpt outlines provider and tenant setup steps and rules, with detailed packet walks deferred to later parts of the series.

### Source excerpt

This article is part of a six-part series on tenant external connectivity for cloud providers running VMware Cloud Foundation 9.1: Part 1: A Standard Network Design for Cloud Providers Part 2: What Decides a Packet's Source Address (this article) Part 3: When Only Provider Addresses Are Allowed Part 4: When the Enterprise Must See Real ... Continued The post Tenant Connectivity on VCF 9.1: What Decides a Packet's Source Address (Part 2) appeared first on VMware Blogs.

## Tenant Connectivity on VCF 9.1: A Standard Network Design for Cloud Providers (Part 1)

DevFeed: [Tenant Connectivity on VCF 9.1: A Standard Network Design for Cloud Providers (Part 1)](<https://devfeed.tech/articles/tenant-connectivity-on-vcf-9-1-a-standard-network-design-for-cloud-providers-part-1-91192.md>)

Original publisher: [Read original article](<https://blogs.vmware.com/cloud-foundation/2026/10/20/tenant-connectivity-on-vcf-9-1-a-standard-network-design-for-cloud-providers-part-1/>)

Author: vmwareblogs

Published: 2026-10-20T17:19:48Z

Content type: article

Language: en

Sources: [VMware](<https://devfeed.tech/sources/vmware-blogs.md>)

Topics: [vcf networking](<https://devfeed.tech/topics/vcf-networking.md>), [VMware Cloud Foundation](<https://devfeed.tech/topics/vcf-9-1.md>), [vcf automation](<https://devfeed.tech/topics/vcf-automation.md>), [NAT and SNAT](<https://devfeed.tech/topics/nat-and-snat.md>), [Network architectures](<https://devfeed.tech/topics/network-architectures.md>), [Cloud Networking](<https://devfeed.tech/topics/cloud-networking.md>), [Cloud Architecture](<https://devfeed.tech/topics/cloud-architecture.md>)

Tags: [cloud](<https://devfeed.tech/tags/cloud.md>), [cloud-infrastructure](<https://devfeed.tech/tags/cloud-infrastructure.md>), [connectivity](<https://devfeed.tech/tags/connectivity.md>), [design](<https://devfeed.tech/tags/design.md>), [multi-tenancy](<https://devfeed.tech/tags/multi-tenancy.md>), [network](<https://devfeed.tech/tags/network.md>), [network-design](<https://devfeed.tech/tags/network-design.md>), [nsx](<https://devfeed.tech/tags/nsx.md>), [providers](<https://devfeed.tech/tags/providers.md>), [series](<https://devfeed.tech/tags/series.md>), [standard](<https://devfeed.tech/tags/standard.md>), [vcf](<https://devfeed.tech/tags/vcf.md>), [vcf-9-1](<https://devfeed.tech/tags/vcf-9-1.md>), [vcf-networking](<https://devfeed.tech/tags/vcf-networking.md>), [vcf-networking-nsx](<https://devfeed.tech/tags/vcf-networking-nsx.md>), [vmware-cloud-service-providers](<https://devfeed.tech/tags/vmware-cloud-service-providers.md>), [vpc](<https://devfeed.tech/tags/vpc.md>)

### AI overview

The standard VCF 9.1 design separates provider-managed connectivity from tenant-managed networks so recurring exit and address-policy combinations can be configured as settings. The provider supplies routable External IP Blocks, External Connections on Tier-0 or VRF gateways, and a tenant Project; within it, the tenant uses one Centralized Transit Gateway (CTGW) and VPCs. VCF 9.1 lets a CTGW attach to multiple External Connections, with per-connection Provider Outbound SNAT to translate tenant traffic to provider-chosen addresses, or Private-TGW IP block advertisement to route tenant private addresses untranslated. Internet traffic must be hidden; enterprise and shared-service exits can follow different address policies. The series' scenarios were lab-tested end to end in NSX, but VCF Automation itself was not tested; the excerpt expects the underlying NSX behavior to match, while screens and click order may differ. The scope excludes Distributed Transit Gateways, EVPN/VXLAN, Avi, and vDefend.

### Source excerpt

This article is part of a six-part series on tenant external connectivity for cloud providers running VMware Cloud Foundation 9.1: Part 1: A Standard Network Design for Cloud Providers (this article) Part 2: What Decides a Packet's Source Address Part 3: When Only Provider Addresses Are Allowed Part 4: When the Enterprise Must See Real ... Continued The post Tenant Connectivity on VCF 9.1: A Standard Network Design for Cloud Providers (Part 1) appeared first on VMware Blogs.

## Wi-Fi 8: The next evolution in enterprise connectivity

DevFeed: [Wi-Fi 8: The next evolution in enterprise connectivity](<https://devfeed.tech/articles/wi-fi-8-the-next-evolution-in-enterprise-connectivity-91047.md>)

Original publisher: [Read original article](<https://blogs.cisco.com/networking/wi-fi-8-the-next-evolution-in-enterprise-connectivity>)

Author: Anand Gurumurthy

Published: 2026-10-20T15:00:25Z

Content type: article

Language: en

Sources: [Cisco Blogs](<https://devfeed.tech/sources/cisco-blogs.md>)

Topics: [Wi-Fi](<https://devfeed.tech/topics/wi-fi.md>), [Network architectures](<https://devfeed.tech/topics/network-architectures.md>), [smartdevices](<https://devfeed.tech/topics/smartdevices.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [bandwidth](<https://devfeed.tech/tags/bandwidth.md>), [cisco-wireless](<https://devfeed.tech/tags/cisco-wireless.md>), [connectivity](<https://devfeed.tech/tags/connectivity.md>), [enterprise](<https://devfeed.tech/tags/enterprise.md>), [evolution](<https://devfeed.tech/tags/evolution.md>), [future](<https://devfeed.tech/tags/future.md>), [network](<https://devfeed.tech/tags/network.md>), [networking](<https://devfeed.tech/tags/networking.md>), [planning](<https://devfeed.tech/tags/planning.md>), [roadmap](<https://devfeed.tech/tags/roadmap.md>), [wi-fi](<https://devfeed.tech/tags/wi-fi.md>), [wi-fi-7](<https://devfeed.tech/tags/wi-fi-7.md>)

### AI overview

Wi-Fi 8 (802.11bn) shifts enterprise Wi-Fi's emphasis from peak speed toward reliability, coordination and efficient spectrum use. The article describes features including Seamless Mobility Domain for smoother roaming, Dynamic Bandwidth Expansion for adjusting channel width to demand, coordinated access points to reduce contention, and DSO, NPCA and DUO for managing spectrum and device radio conflicts. It presents these as ways to improve consistency in dense, mobile environments, while Wi-Fi 8 remains under development: ratification is expected around 2028 and mainstream enterprise deployment is estimated 3-5 years away. The article recommends Wi-Fi 7 for current deployments, citing its mature ecosystem and production-ready performance.

### Source excerpt

Gain a strategic edge in your network planning by mastering the shift from raw speed to intelligent connectivity. Arm yourself with the insights to proactively guide your organization's future wireless roadmap.

## Snowflake PrivateLink Connectivity: Account Authorization, Endpoint Pinning, and Network Policies

DevFeed: [Snowflake PrivateLink Connectivity: Account Authorization, Endpoint Pinning, and Network Policies](<https://devfeed.tech/articles/snowflake-privatelink-connectivity-account-authorization-endpoint-pinning-and-network-policies-86550.md>)

Original publisher: [Read original article](<https://medium.com/snowflake/snowflake-privatelink-connectivity-account-authorization-endpoint-pinning-and-network-policies-1a782a7ef5f5?source=rss----34b6daafc07---4>)

Author: Amir Durrani

Published: 2026-10-13T19:01:02Z

Content type: article

Language: en

Sources: [Snowflake Builders](<https://devfeed.tech/sources/snowflake-builders.md>)

Topics: [Access Control](<https://devfeed.tech/topics/access-control.md>), [Authorization](<https://devfeed.tech/topics/authorization.md>), [Network architectures](<https://devfeed.tech/topics/network-architectures.md>), [control-plane](<https://devfeed.tech/topics/control-plane.md>)

Tags: [access-control](<https://devfeed.tech/tags/access-control.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [authorization](<https://devfeed.tech/tags/authorization.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-privatelink](<https://devfeed.tech/tags/aws-privatelink.md>), [cloud-security](<https://devfeed.tech/tags/cloud-security.md>), [network](<https://devfeed.tech/tags/network.md>), [network-policy](<https://devfeed.tech/tags/network-policy.md>), [network-security](<https://devfeed.tech/tags/network-security.md>), [snowflake](<https://devfeed.tech/tags/snowflake.md>)

### AI overview

For inbound AWS PrivateLink, Snowflake account authorization, VPCE pinning, and network-policy allowlisting are separate controls. Authorizing an AWS account lets it create endpoints but does not pin a particular endpoint or impose a configurable per-account VPCE quota. Pinning registers a VPCE ID to a Snowflake account; access requires the target account to register that VPCE, and the same VPCE may be registered to multiple accounts. An ingress network rule of type AWSVPCEID can allow specific endpoints. TLS or an HTTP response shows reachability, not successful Snowflake authentication or policy acceptance; validate with a Snowflake client login and query. The excerpt says VPCE ID pinning applies to AWS PrivateLink and Azure LinkIds, while GCP Private Service Connect is unsupported at the time described. It also distinguishes error 390431, a pinning relationship failure, from 390422, which requires checking effective network policy and endpoint details.

### Source excerpt

Private connectivity is often discussed as though it were a single control. In practice, a Snowflake deployment can involve several distinct controls: AWS account authorization, endpoint-specific pinning, network-policy allowlisting, and Snowflake authentication. This article focuses on inbound AWS PrivateLink connectivity to the Snowflake service. Understanding the difference matters when a customer asks questions such as: Can a specific AWS account create more than one PrivateLink endpoint? Does authorizing an AWS account automatically pin one endpoint? Does a successful TLS connection prove that the endpoint is permitted? Can Snowflake cap the number of VPCEs a customer creates? The short answer is: VPCE account pinning is supported where inbound private connectivity and endpoint pinning are available. AWS account authorization and VPCE pinning are different operations. Network policies provide the account-side control for allowing specific VPCE IDs. AWS PrivateLink does not provide a normal configurable provider-side quota that limits the number of VPCEs created by one consumer AWS account. Reading the Architecture Diagram The diagram has two layers: the traffic path and the control plane. Traffic path Customer workload -> customer VPC interface endpoint (VPCE) -> AWS PrivateLink endpoint service -> Snowflake-managed network load balancer and service edge -> target Snowflake account. The network load balancer provides the service transport on Snowflake's side. It is Snowflake-managed infrastructure, not a customer-configured authorization gate. Control plane Gate 1 -- Authorize the customer AWS account. The customer authorizes one or more AWS accounts to establish private connectivity using the Snowflake PrivateLink service endpoint. After authorization, those AWS accounts can create interface VPC endpoints in their VPCs that target Snowflake's PrivateLink endpoint service. Gate 2 -- Pin the VPC interface endpoint to a Snowflake account. After creating a VPC interface

## Meet Fred Mercer: Turning Customer Challenges Into Working Demos

DevFeed: [Meet Fred Mercer: Turning Customer Challenges Into Working Demos](<https://devfeed.tech/articles/meet-fred-mercer-turning-customer-challenges-into-working-demos-88580.md>)

Original publisher: [Read original article](<https://netboxlabs.com/blog/meet-fred-mercer/>)

Author: Meghna Khurana

Published: 2026-10-08T21:36:35Z

Content type: article

Language: en

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

Topics: [NetBox](<https://devfeed.tech/topics/netbox.md>), [Network architectures](<https://devfeed.tech/topics/network-architectures.md>), [implementation](<https://devfeed.tech/topics/implementation.md>), [gradio](<https://devfeed.tech/topics/gradio.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [api](<https://devfeed.tech/tags/api.md>), [automation](<https://devfeed.tech/tags/automation.md>), [blog](<https://devfeed.tech/tags/blog.md>), [build](<https://devfeed.tech/tags/build.md>), [culture](<https://devfeed.tech/tags/culture.md>), [customer](<https://devfeed.tech/tags/customer.md>), [customers](<https://devfeed.tech/tags/customers.md>), [demo](<https://devfeed.tech/tags/demo.md>), [dhcp](<https://devfeed.tech/tags/dhcp.md>), [dns](<https://devfeed.tech/tags/dns.md>), [feedback](<https://devfeed.tech/tags/feedback.md>), [hardware](<https://devfeed.tech/tags/hardware.md>), [homelab](<https://devfeed.tech/tags/homelab.md>), [ipam](<https://devfeed.tech/tags/ipam.md>)

### AI overview

Fred Mercer, a NetBox Labs senior solutions engineer, builds and validates customized demos and proofs of concept for customer network challenges. He describes modeling complex networks, creating a Python-generated fiber topology for cable tracing, and using Claude to help mock a power-monitoring device and connect its API. Mercer also says customer feedback from sales engineering reaches the product team.

### Source excerpt

The post Meet Fred Mercer: Turning Customer Challenges Into Working Demos appeared first on NetBox Labs.

## SASE in the AI Era: Why Secure Global Connectivity Matters More Than Ever

DevFeed: [SASE in the AI Era: Why Secure Global Connectivity Matters More Than Ever](<https://devfeed.tech/articles/sase-in-the-ai-era-why-secure-global-connectivity-matters-more-than-ever-63619.md>)

Original publisher: [Read original article](<https://blog.checkpoint.com/harmony-sase/sase-in-the-ai-era-why-secure-global-connectivity-matters-more-than-ever/>)

Author: anap@checkpoint.com

Published: 2026-10-01T13:02:57Z

Content type: article

Language: en

Sources: [Check Point Blog](<https://devfeed.tech/sources/check-point-blog.md>)

Topics: [Secure access service edge](<https://devfeed.tech/topics/secure-access-service-edge.md>), [Cloudflare One](<https://devfeed.tech/topics/cloudflare-one.md>), [Network architectures](<https://devfeed.tech/topics/network-architectures.md>), [Zero Trust](<https://devfeed.tech/topics/zero-trust.md>), [scalable-architecture](<https://devfeed.tech/topics/scalable-architecture.md>), [Local AI](<https://devfeed.tech/topics/local-ai.md>)

Tags: [ai-adoption](<https://devfeed.tech/tags/ai-adoption.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [infrastructure](<https://devfeed.tech/tags/infrastructure.md>), [network](<https://devfeed.tech/tags/network.md>), [sase](<https://devfeed.tech/tags/sase.md>)

### AI overview

The article argues that global enterprises face fragmented networking, security, and regulatory environments, with AI adoption adding demands for consistent access and policy enforcement. It presents unified SASE as a way to manage secure connectivity and performance across regions, using Check Point's China Premium Connectivity as an example of addressing a difficult market.

### Source excerpt

Where global enterprises lose ground Ask any global IT leader what slows their enterprise down, and they'll rarely identify the network itself as the issue. The friction often shows up at the borders, where one country's infrastructure meets another's regulations and coherence quietly falls apart. Every new region a company enters brings its own regulatory regime, infrastructure boundaries, and performance challenges. Stitch enough of these together, and the result is a patchwork architecture, held up by exceptions rather than one unified design. AI adoption is stretching that patchwork to its limits. It's compounding growing demands from distributed SaaS, always-on collaboration [...] The post SASE in the AI Era: Why Secure Global Connectivity Matters More Than Ever appeared first on Check Point Blog.

[Next page](<https://devfeed.tech/topics/network-architectures.md?cursor=WyIyMDI2LTEwLTAxVDEzOjAyOjU3KzAwOjAwIiwgIjdjMjQ5YjkzLWNmMjQtNDAwZS1iY2M1LTE4NTFhNGI4MDc3YyJd>)