# CIDR and subnets

CIDR and subnets are Internet networking technologies for assigning and dividing IP address space into classless prefixes and logically visible subnetworks, supporting routing aggregation and scalable network operation.

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

## VCF 9.1 VPC Networking, Part 2: IP Blocks, External Connections, Transit Gateways, Subnets, and NAT

DevFeed: [VCF 9.1 VPC Networking, Part 2: IP Blocks, External Connections, Transit Gateways, Subnets, and NAT](<https://devfeed.tech/articles/vcf-9-1-vpc-networking-part-2-ip-blocks-external-connections-transit-gateways-subnets-and-nat-145842.md>)

Original publisher: [Read original article](<https://blogs.vmware.com/cloud-foundation/2026/11/19/vcf-9-1-vpc-networking-part-2-ip-blocks-external-connections-transit-gateways-subnets-and-nat/>)

Author: vmwareblogs

Published: 2026-11-20T06:09:37Z

Content type: article

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>), [CIDR and subnets](<https://devfeed.tech/topics/cidr-and-subnets.md>), [VMware Cloud Foundation](<https://devfeed.tech/topics/vcf-9-1.md>), [routing-system](<https://devfeed.tech/topics/routing-system.md>)

Tags: [active-directory](<https://devfeed.tech/tags/active-directory.md>), [application](<https://devfeed.tech/tags/application.md>), [avi-load-balancer](<https://devfeed.tech/tags/avi-load-balancer.md>), [back-end](<https://devfeed.tech/tags/back-end.md>), [blocks](<https://devfeed.tech/tags/blocks.md>), [boundary](<https://devfeed.tech/tags/boundary.md>), [broadcom](<https://devfeed.tech/tags/broadcom.md>), [cloud-infrastructure](<https://devfeed.tech/tags/cloud-infrastructure.md>), [communication](<https://devfeed.tech/tags/communication.md>), [data-centre](<https://devfeed.tech/tags/data-centre.md>), [database](<https://devfeed.tech/tags/database.md>), [dhcp](<https://devfeed.tech/tags/dhcp.md>), [external](<https://devfeed.tech/tags/external.md>), [ip](<https://devfeed.tech/tags/ip.md>), [nat](<https://devfeed.tech/tags/nat.md>), [networking](<https://devfeed.tech/tags/networking.md>), [nsx](<https://devfeed.tech/tags/nsx.md>), [subnets](<https://devfeed.tech/tags/subnets.md>), [transit](<https://devfeed.tech/tags/transit.md>), [vcf](<https://devfeed.tech/tags/vcf.md>), [vcf-9-1](<https://devfeed.tech/tags/vcf-9-1.md>), [vcf-platform](<https://devfeed.tech/tags/vcf-platform.md>), [vpc](<https://devfeed.tech/tags/vpc.md>)

### AI overview

VCF 9.1 VPC networking separates address ownership, routing paths and visibility: IP blocks supply addresses, External Connections connect a Transit Gateway to outside networks, and Connectivity Profiles bind that routing and address model to each VPC. Subnets define reach: Private VPC stays within one VPC, Private TGW reaches VPCs on the same Transit Gateway, and Public is reachable from the outside data centre network. NAT provides outbound access or address translation; it does not replace route visibility decisions. The excerpt distinguishes centralized connections through NSX Edge and Tier-0, distributed VLAN connections without Edge nodes or dynamic routing, and distributed VXLAN connections requiring EVPN components in 9.1.1 and later. It also details advertisement controls, project sharing constraints, and design checks for route uniqueness, CIDR overlap, return paths and NAT configuration.

### Source excerpt

Series - Part 2 of 6 The VCF 9.1 VPC Networking Mental Model 1VCF 9.1 VPC Networking, Part 1: From External Connection to VPC 2VCF 9.1 VPC Networking, Part 2: IP Blocks, External Connections, Transit Gateways, Subnets, and NATYou are here 3VCF 9.1 VPC Networking, Part 3: The Distributed Transit GatewayComing soon 4VCF 9.1 VPC ... Continued The post VCF 9.1 VPC Networking, Part 2: IP Blocks, External Connections, Transit Gateways, Subnets, and NAT appeared first on VMware Blogs.

## From instant Aurora PostgreSQL databases to production-ready in your VPC

DevFeed: [From instant Aurora PostgreSQL databases to production-ready in your VPC](<https://devfeed.tech/articles/from-instant-aurora-postgresql-databases-to-production-ready-in-your-vpc-144611.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/database/from-instant-aurora-postgresql-databases-to-production-ready-in-your-vpc/>)

Author: Saurabh Kothawade

Published: 2026-11-19T22:13:11Z

Content type: tutorial

Language: en

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

Topics: [Amazon Aurora](<https://devfeed.tech/topics/amazon-aurora.md>), [PostgreSQL](<https://devfeed.tech/topics/postgresql.md>), [CIDR and subnets](<https://devfeed.tech/topics/cidr-and-subnets.md>), [ReAct agent Python](<https://devfeed.tech/topics/react-agent-python.md>)

Tags: [access-management](<https://devfeed.tech/tags/access-management.md>), [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [agent](<https://devfeed.tech/tags/agent.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agent](<https://devfeed.tech/tags/ai-agent.md>), [amazon-aurora](<https://devfeed.tech/tags/amazon-aurora.md>), [amazon-vpc](<https://devfeed.tech/tags/amazon-vpc.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-cli](<https://devfeed.tech/tags/aws-cli.md>), [cli](<https://devfeed.tech/tags/cli.md>), [cluster](<https://devfeed.tech/tags/cluster.md>), [configuration](<https://devfeed.tech/tags/configuration.md>), [console](<https://devfeed.tech/tags/console.md>), [data](<https://devfeed.tech/tags/data.md>), [databases](<https://devfeed.tech/tags/databases.md>), [express](<https://devfeed.tech/tags/express.md>), [iam](<https://devfeed.tech/tags/iam.md>), [networking](<https://devfeed.tech/tags/networking.md>), [postgresql](<https://devfeed.tech/tags/postgresql.md>), [production](<https://devfeed.tech/tags/production.md>), [technical-how-to](<https://devfeed.tech/tags/technical-how-to.md>), [verify](<https://devfeed.tech/tags/verify.md>), [vpc](<https://devfeed.tech/tags/vpc.md>)

### AI overview

Aurora PostgreSQL clusters created with express configuration can now move into a VPC through one modify operation, keeping their data and endpoint. The move briefly drops existing connections, switches off the internet access gateway, and requires a prepared DB subnet group, security group, private network path for every client, and suitable IAM permissions. Afterward, verify that the cluster is available with VPC networking enabled and the gateway disabled, then confirm clients reconnect; failed moves can return to gateway access and emit an RDS event. The same operation can be run through the console, AWS CLI, or an AI agent. Agent roles can be scoped to approved clusters and explicitly denied permission to move databases back out of a VPC. Creating directly in a VPC is also supported, though it takes longer than the seconds-long default setup. Moving back to gateway access briefly interrupts connections, requires IAM database authentication, and is blocked while VPC-dependent features are active.

### Source excerpt

Amazon Aurora PostgreSQL express configuration now supports VPC networking. You can move an existing cluster into your VPC with a single modify operation, keeping its data and endpoint, from the console, the AWS CLI, or an AI agent. This post shows how to move and verify a cluster, and how to let an agent do it with IAM guardrails.

## Introducing policy-based routing for AWS Transit Gateway

DevFeed: [Introducing policy-based routing for AWS Transit Gateway](<https://devfeed.tech/articles/introducing-policy-based-routing-for-aws-transit-gateway-144603.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/networking-and-content-delivery/introducing-policy-based-routing-for-aws-transit-gateway/>)

Author: Arshdeep Grover

Published: 2026-11-19T21:06:11Z

Content type: article

Language: en

Sources: [Networking & Content Delivery](<https://devfeed.tech/sources/networking-content-delivery.md>)

Topics: [Cloud Networking](<https://devfeed.tech/topics/cloud-networking.md>), [Amazon VPC](<https://devfeed.tech/topics/amazon-vpc.md>), [Amazon Web Services](<https://devfeed.tech/topics/aws.md>), [AWS Network Firewall](<https://devfeed.tech/topics/aws-network-firewall.md>), [Firewall](<https://devfeed.tech/topics/firewall.md>), [CIDR and subnets](<https://devfeed.tech/topics/cidr-and-subnets.md>), [AWS IAM](<https://devfeed.tech/topics/aws-iam.md>)

Tags: [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [announcements](<https://devfeed.tech/tags/announcements.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-transit-gateway](<https://devfeed.tech/tags/aws-transit-gateway.md>), [based](<https://devfeed.tech/tags/based.md>), [cases](<https://devfeed.tech/tags/cases.md>), [class](<https://devfeed.tech/tags/class.md>), [console](<https://devfeed.tech/tags/console.md>), [gateway](<https://devfeed.tech/tags/gateway.md>), [ip](<https://devfeed.tech/tags/ip.md>), [policy](<https://devfeed.tech/tags/policy.md>), [port](<https://devfeed.tech/tags/port.md>), [post](<https://devfeed.tech/tags/post.md>), [protocol](<https://devfeed.tech/tags/protocol.md>), [reference](<https://devfeed.tech/tags/reference.md>), [reference-architecture](<https://devfeed.tech/tags/reference-architecture.md>), [route](<https://devfeed.tech/tags/route.md>), [routing](<https://devfeed.tech/tags/routing.md>), [setup](<https://devfeed.tech/tags/setup.md>), [source](<https://devfeed.tech/tags/source.md>), [transit](<https://devfeed.tech/tags/transit.md>)

### AI overview

AWS Transit Gateway policy-based routing (PBR) evaluates traffic against ordered rules matching any combination of source and destination CIDRs, protocol, and ports, then sends the first match to a target route table for normal destination-based forwarding. It supports path selection, segmentation, and selective inspection or bypass. Configure a policy table in the VPC console, add rules, and associate it with attachments; each attachment uses either a policy table or a route table. Unmatched traffic is dropped, and protocol- or port-based rules might not apply to fragmented packets. Plan matching return paths for stateful inspection. Associating a policy table with Site-to-Site VPN or Connect attachments stops BGP route advertisement; Direct Connect gateway attachments retain allowed-prefix advertisements. PBR is unavailable in AWS GovCloud (US) Regions and adds no charge beyond standard Transit Gateway pricing.

### Source excerpt

Policy-based routing (PBR) for AWS Transit Gateway matches traffic on its 5-tuple (source and destination IP, source and destination port, and protocol) and sends each class to a different route table. This post explains how PBR works and walks through a reference architecture, console setup, and three use cases.

## VCF 9.1 VPC Networking, Part 1: From External Connection to Virtual Private Cloud

DevFeed: [VCF 9.1 VPC Networking, Part 1: From External Connection to Virtual Private Cloud](<https://devfeed.tech/articles/vcf-9-1-vpc-networking-part-1-from-external-connection-to-virtual-private-cloud-143634.md>)

Original publisher: [Read original article](<https://blogs.vmware.com/cloud-foundation/2026/11/18/vcf-9-1-vpc-networking-part-1-from-external-connection-to-virtual-private-cloud/>)

Author: vmwareblogs

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

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>), [CIDR and subnets](<https://devfeed.tech/topics/cidr-and-subnets.md>), [NAT and SNAT](<https://devfeed.tech/topics/nat-and-snat.md>)

Tags: [cloud-infrastructure](<https://devfeed.tech/tags/cloud-infrastructure.md>), [external](<https://devfeed.tech/tags/external.md>), [networking](<https://devfeed.tech/tags/networking.md>), [nsx](<https://devfeed.tech/tags/nsx.md>), [vcf](<https://devfeed.tech/tags/vcf.md>), [vcf-9-1](<https://devfeed.tech/tags/vcf-9-1.md>), [vcf-platform](<https://devfeed.tech/tags/vcf-platform.md>), [vpc](<https://devfeed.tech/tags/vpc.md>)

### AI overview

VCF 9.1 VPC networking is built as a provider-to-project hand-off: the provider creates External IP Blocks and an External Connection in the default project, shares the needed constructs, and the project builds a Transit Gateway, VPC with matching connectivity and service profiles, then workload subnets. Connection types differ: Centralized uses an NSX Edge Tier-0 and supports listed stateful services; Distributed VLAN avoids Edge nodes and dynamic routing, with VNAs for stateful services; Distributed VXLAN integrates with EVPN-VXLAN, requiring EVPN Route Controller nodes and VNAs. Avi integration requires enabling its VPC toggle, a private IP block, and an assigned edge cluster. The excerpt's validation checks include successful realization, correct project delegation and profiles, nonoverlapping external IP blocks, intended subnet types, routes, and tested NAT, firewall, and external reachability.

### Source excerpt

Series - Part 1 of 6 The VCF 9.1 VPC Networking Mental Model 1VCF 9.1 VPC Networking, Part 1: From External Connection to VPCYou are here 2VCF 9.1 VPC Networking, Part 2: IP Blocks, External Connections, Transit Gateways, Subnets and NATComing soon 3VCF 9.1 VPC Networking, Part 3: The Distributed Transit GatewayComing soon 4VCF 9.1 ... Continued The post VCF 9.1 VPC Networking, Part 1: From External Connection to Virtual Private Cloud appeared first on VMware Blogs.

## AWS PrivateLink Tunnel Endpoints Open a Whole CIDR Range to Another Account

DevFeed: [AWS PrivateLink Tunnel Endpoints Open a Whole CIDR Range to Another Account](<https://devfeed.tech/articles/aws-privatelink-tunnel-endpoints-open-a-whole-cidr-range-to-another-account-140159.md>)

Original publisher: [Read original article](<https://www.infoq.com/news/2026/11/aws-privatelink-tunnel-endpoints/>)

Author: Steef-Jan Wiggers

Published: 2026-11-18T09:29:00Z

Content type: news

Language: en

Sources: [InfoQ](<https://devfeed.tech/sources/infoq.md>)

Topics: [Cloud Networking](<https://devfeed.tech/topics/cloud-networking.md>), [CIDR and subnets](<https://devfeed.tech/topics/cidr-and-subnets.md>), [Amazon Web Services](<https://devfeed.tech/topics/aws.md>), [Amazon VPC](<https://devfeed.tech/topics/amazon-vpc.md>), [Resource Access Manager (RAM)](<https://devfeed.tech/topics/resource-access-manager-ram.md>)

Tags: [access-manager](<https://devfeed.tech/tags/access-manager.md>), [architecture-design](<https://devfeed.tech/tags/architecture-design.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-privatelink](<https://devfeed.tech/tags/aws-privatelink.md>), [aws-privatelink-tunnel-endpoints](<https://devfeed.tech/tags/aws-privatelink-tunnel-endpoints.md>), [client](<https://devfeed.tech/tags/client.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [clusters](<https://devfeed.tech/tags/clusters.md>), [consumer](<https://devfeed.tech/tags/consumer.md>), [development](<https://devfeed.tech/tags/development.md>), [devops](<https://devfeed.tech/tags/devops.md>), [dns](<https://devfeed.tech/tags/dns.md>), [haproxy](<https://devfeed.tech/tags/haproxy.md>), [http](<https://devfeed.tech/tags/http.md>), [logs](<https://devfeed.tech/tags/logs.md>), [network](<https://devfeed.tech/tags/network.md>), [networking](<https://devfeed.tech/tags/networking.md>), [news](<https://devfeed.tech/tags/news.md>), [resource](<https://devfeed.tech/tags/resource.md>), [space](<https://devfeed.tech/tags/space.md>), [tcp](<https://devfeed.tech/tags/tcp.md>), [traffic](<https://devfeed.tech/tags/traffic.md>), [tunnel](<https://devfeed.tech/tags/tunnel.md>), [type](<https://devfeed.tech/tags/type.md>), [vpc](<https://devfeed.tech/tags/vpc.md>)

### AI overview

AWS PrivateLink tunnel endpoints let a consumer VPC reach all addresses in a shared CIDR range in another account, including resources added later. The provider shares a CIDR resource configuration through AWS Resource Access Manager; the consumer connects through a tunnel endpoint. Unlike VPC peering, this exposes a selected range in one direction, permits overlapping CIDRs, and allows connections only from the consumer. Consumer traffic must be wrapped in GENEVE over UDP port 6081, with endpoint and resource gateway subnets in matching Availability Zones. Inner traffic supports TCP and DNS only; ICMP, fragments, and private DNS names are unsupported. Logs identify the consumer endpoint but not the workload behind it. Sharing broad ranges such as 0.0.0.0/0 can expose routed networks beyond the provider VPC, so the excerpt recommends narrow ranges. A reported overlapping-CIDR setup required per-destination routes or an added relay/proxy hop. Charges include endpoint hours and processed data, with provider-side data billed through VPC Lattice.

### Source excerpt

AWS has detailed tunnel endpoints, a PrivateLink endpoint type that gives a consumer VPC access to an entire network segment in another account rather than one resource at a time, over an overlapping address space and with consumer-initiated connections only. The consumer must wrap traffic in GENEVE; only TCP and DNS pass, and access logs cannot attribute traffic to a workload behind the endpoint. By Steef-Jan Wiggers

## UDP Broadcasting Meets the More Focused Multicasting

DevFeed: [UDP Broadcasting Meets the More Focused Multicasting](<https://devfeed.tech/articles/udp-broadcasting-meets-the-more-focused-multicasting-123906.md>)

Original publisher: [Read original article](<https://hackaday.com/2026/11/09/udp-broadcasting-meets-the-more-focused-multicasting/>)

Author: Maya Posch

Published: 2026-11-09T18:00:41Z

Content type: article

Language: en

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

Topics: [QUIC](<https://devfeed.tech/topics/quic.md>), [CIDR and subnets](<https://devfeed.tech/topics/cidr-and-subnets.md>)

Tags: [broadcasting](<https://devfeed.tech/tags/broadcasting.md>), [comparisons](<https://devfeed.tech/tags/comparisons.md>), [hackaday-columns](<https://devfeed.tech/tags/hackaday-columns.md>), [ipv4](<https://devfeed.tech/tags/ipv4.md>), [ipv6](<https://devfeed.tech/tags/ipv6.md>), [multicast](<https://devfeed.tech/tags/multicast.md>), [network-hacks](<https://devfeed.tech/tags/network-hacks.md>), [networking](<https://devfeed.tech/tags/networking.md>), [subnets](<https://devfeed.tech/tags/subnets.md>), [udp](<https://devfeed.tech/tags/udp.md>)

### AI overview

IPv4 UDP service discovery has three options in the article: send to an interface's directed broadcast address, use 255.255.255.255, or multicast to 224.0.0.1, which is intended to reach all nodes on the local network without router forwarding. Directed broadcast is the author's tentative preference because it identifies the interface used and can simplify sorting responses; the text cautions that determining an interface's broadcast address may be unreliable, with a Poco fix expected in version 1.16.0 and a workaround available. The all-nodes multicast option depends on IGMP being supported and working correctly. The author finds no clearly best choice and presents IPv4's alternatives as carrying different complications, while noting IPv6 uses link-local multicast in place of broadcast.

### Source excerpt

After previously exploring the basics of UDP broadcasting, why IPv4 subnets are an exciting feature that you really want to dive into, as well as the contentious topic of IPv6, ...read more

## StarLoc: A Practical Approach to Encoding Geographic Locators in IPv6 for Starlink

DevFeed: [StarLoc: A Practical Approach to Encoding Geographic Locators in IPv6 for Starlink](<https://devfeed.tech/articles/starloc-a-practical-approach-to-encoding-geographic-locators-in-ipv6-for-starlink-123728.md>)

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

Author: Vanya Singla, Mostafa Abdollahi, Jinwei Zhao, Jianping Pan

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

Content type: article

Language: en

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

Topics: [CIDR and subnets](<https://devfeed.tech/topics/cidr-and-subnets.md>), [Internet](<https://devfeed.tech/topics/internet.md>), [ip-address-planning](<https://devfeed.tech/topics/ip-address-planning.md>), [Encoding](<https://devfeed.tech/topics/encoding.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [abstract](<https://devfeed.tech/tags/abstract.md>), [adaptive](<https://devfeed.tech/tags/adaptive.md>), [approach](<https://devfeed.tech/tags/approach.md>), [arxiv](<https://devfeed.tech/tags/arxiv.md>), [away](<https://devfeed.tech/tags/away.md>), [balance](<https://devfeed.tech/tags/balance.md>), [based](<https://devfeed.tech/tags/based.md>), [can](<https://devfeed.tech/tags/can.md>), [cells](<https://devfeed.tech/tags/cells.md>), [challenges](<https://devfeed.tech/tags/challenges.md>), [change](<https://devfeed.tech/tags/change.md>), [connectivity](<https://devfeed.tech/tags/connectivity.md>), [covers](<https://devfeed.tech/tags/covers.md>), [cs-ni](<https://devfeed.tech/tags/cs-ni.md>), [customer](<https://devfeed.tech/tags/customer.md>), [encoding](<https://devfeed.tech/tags/encoding.md>), [existing](<https://devfeed.tech/tags/existing.md>), [ipv6](<https://devfeed.tech/tags/ipv6.md>), [practical](<https://devfeed.tech/tags/practical.md>), [starlink](<https://devfeed.tech/tags/starlink.md>)

### AI overview

StarLoc proposes encoding terminal location in Starlink IPv6 addresses to make geolocation more representative of users' physical locations. Analysis of 925 GeoFeed snapshots, a year of PoP mappings, and over 7.9 million observed addresses found little geographic structure in customer prefixes; prefix labels were a median 540 km from their PoPs, and relabeling one /40 could affect reported locations for up to 65,536 possible /56 delegations. StarLoc adds a resolution-adaptive H3 Locator while preserving existing prefixes, /56 delegations, and stable Endpoint Identifiers. For privacy, it can reveal only cells meeting a minimum terminal count, cap resolution in sensitive regions, or withhold location. Its locators represent physical location and can follow moving users, unlike topology-based schemes.

### Source excerpt

arXiv:2611.08772v1 Announce Type: new Abstract: LEO satellite networks such as Starlink provide Internet connectivity across continents, oceans, and airspace. IP geolocation providers map Starlink's IPv6 prefixes to locations mainly through its self-published GeoFeed. However, users may be far away from their assigned Points of Presence (PoPs), one label covers an entire prefix, and labels and PoP mappings can change while addresses stay the same. We characterize Starlink's IPv6 addressing using 925 historical GeoFeed snapshots (2024--2026), one year of PoP mappings, and over 7.9 million observed IPv6 addresses. Our findings reveal that customer prefixes lack clear geographic structure, prefix labels lie a median of 540km from their PoPs, and relabeling a single /40 can affect the reported locations of up to 65,536 possible /56 delegations. To address these challenges, we propose StarLoc, a geographic Locator--Identifier separation scheme that embeds terminal location into IPv6 addresses using a resolution-adaptive H3 Locator while preserving existing Starlink prefixes, /56 delegations, and stable Endpoint Identifiers. To balance accuracy and privacy, StarLoc reveals only cells with at least a certain number of terminals, and operators can cap resolution in sensitive regions or withhold location entirely. Unlike topology-based schemes, StarLoc encodes physical location and lets Locators follow moving users.

## Tailscale Part 2: Access Your Entire Homelab With Subnet Routing

DevFeed: [Tailscale Part 2: Access Your Entire Homelab With Subnet Routing](<https://devfeed.tech/articles/tailscale-part-2-access-your-entire-homelab-with-subnet-routing-122128.md>)

Original publisher: [Read original article](<https://noted.lol/tailscale-subnet-routing-homelab/>)

Author: Jeremy

Published: 2026-11-07T12:27:19Z

Content type: tutorial

Language: en

Sources: [Noted](<https://devfeed.tech/sources/noted.md>)

Topics: [tailscale](<https://devfeed.tech/topics/tailscale.md>), [Homelab](<https://devfeed.tech/topics/homelab.md>), [Network Configuration](<https://devfeed.tech/topics/network-configuration.md>), [CIDR and subnets](<https://devfeed.tech/topics/cidr-and-subnets.md>), [IP routing](<https://devfeed.tech/topics/ip-routing.md>)

Tags: [firewall](<https://devfeed.tech/tags/firewall.md>), [gateway](<https://devfeed.tech/tags/gateway.md>), [home-network](<https://devfeed.tech/tags/home-network.md>), [homelab](<https://devfeed.tech/tags/homelab.md>), [ip](<https://devfeed.tech/tags/ip.md>), [ipv4](<https://devfeed.tech/tags/ipv4.md>), [linux](<https://devfeed.tech/tags/linux.md>), [nas](<https://devfeed.tech/tags/nas.md>), [routing](<https://devfeed.tech/tags/routing.md>), [subnet](<https://devfeed.tech/tags/subnet.md>), [tailscale](<https://devfeed.tech/tags/tailscale.md>)

### AI overview

Tailscale subnet routing lets one always-on Tailscale-connected Linux server act as a gateway to homelab devices that do not run Tailscale, using their existing local IP addresses. Enable Linux IP forwarding, advertise the home subnet with `tailscale set --advertise-routes`, then approve the route in the admin dashboard unless automatic approval is configured. Tailnet access policies must permit connections; on Linux clients, enable route acceptance with `tailscale set --accept-routes`, while phones and Windows devices normally pick up approved routes automatically. Access still depends on the gateway being available and routing and firewall settings allowing the connection.

### Source excerpt

Learn how Tailscale subnet routing lets you securely access your entire homelab remotely without installing Tailscale on every device.

## Introducing tunnel endpoints for private access to network segments

DevFeed: [Introducing tunnel endpoints for private access to network segments](<https://devfeed.tech/articles/introducing-tunnel-endpoints-for-private-access-to-network-segments-119793.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/networking-and-content-delivery/introducing-tunnel-endpoints-for-private-access-to-network-segments/>)

Author: Bruce Pinsky

Published: 2026-11-05T16:48:12Z

Content type: release

Language: en

Sources: [Networking & Content Delivery](<https://devfeed.tech/sources/networking-content-delivery.md>)

Topics: [Cloud Networking](<https://devfeed.tech/topics/cloud-networking.md>), [Network Segmentation](<https://devfeed.tech/topics/network-segmentation.md>), [CIDR and subnets](<https://devfeed.tech/topics/cidr-and-subnets.md>), [Virtual Private Network](<https://devfeed.tech/topics/vpn.md>), [Access Control](<https://devfeed.tech/topics/access-control.md>), [NAT and SNAT](<https://devfeed.tech/topics/nat-and-snat.md>), [Resource Access Manager (RAM)](<https://devfeed.tech/topics/resource-access-manager-ram.md>), [VXLAN](<https://devfeed.tech/topics/vxlan.md>)

Tags: [2](<https://devfeed.tech/tags/2.md>), [3](<https://devfeed.tech/tags/3.md>), [about](<https://devfeed.tech/tags/about.md>), [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [amazon-vpc-lattice](<https://devfeed.tech/tags/amazon-vpc-lattice.md>), [announcements](<https://devfeed.tech/tags/announcements.md>), [application](<https://devfeed.tech/tags/application.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-privatelink](<https://devfeed.tech/tags/aws-privatelink.md>), [created](<https://devfeed.tech/tags/created.md>), [gives](<https://devfeed.tech/tags/gives.md>), [inside](<https://devfeed.tech/tags/inside.md>), [ip](<https://devfeed.tech/tags/ip.md>), [network](<https://devfeed.tech/tags/network.md>), [one](<https://devfeed.tech/tags/one.md>), [private](<https://devfeed.tech/tags/private.md>), [private-access](<https://devfeed.tech/tags/private-access.md>), [range](<https://devfeed.tech/tags/range.md>), [resource](<https://devfeed.tech/tags/resource.md>), [resources](<https://devfeed.tech/tags/resources.md>), [shares](<https://devfeed.tech/tags/shares.md>), [type](<https://devfeed.tech/tags/type.md>), [vpc](<https://devfeed.tech/tags/vpc.md>)

### AI overview

AWS PrivateLink tunnel endpoints let a consumer VPC reach an entire provider-defined CIDR range through a consumer-initiated GENEVE tunnel, so resources added later are reachable without sharing each one separately. Providers define allowed ranges, protocols, and ports in a CIDR resource configuration, attach it to an IN_VPC resource gateway, and share it through AWS RAM; traffic outside those ranges is dropped. DNS can also be resolved through the tunnel in the provider's network. Access remains subject to provider-side security controls, and logs do not reveal the consumer workload's inner source address. Setup requires overlapping Availability Zones and UDP 6081 between the consumer endpoint and compute. Application traffic must be TCP (DNS is the only supported UDP traffic); ICMP and IP fragments are not forwarded, and connections can only be initiated by the consumer.

### Source excerpt

Tunnel endpoints are a new VPC endpoint type, powered by AWS PrivateLink, that gives an application in one VPC private access to an entire range of IP addresses in another VPC. The network owner shares a CIDR block once, and every resource inside it becomes reachable, including resources created later.

## IP geolocation now covers more visitors at higher resolution

DevFeed: [IP geolocation now covers more visitors at higher resolution](<https://devfeed.tech/articles/ip-geolocation-now-covers-more-visitors-at-higher-resolution-106552.md>)

Original publisher: [Read original article](<https://vercel.com/changelog/improved-ip-geolocation-data>)

Author: Sage Abraham

Published: 2026-10-29T17:00:00Z

Content type: release

Language: en

Sources: [Vercel News](<https://devfeed.tech/sources/vercel-news.md>)

Topics: [CIDR and subnets](<https://devfeed.tech/topics/cidr-and-subnets.md>), [Virtual Private Network](<https://devfeed.tech/topics/vpn.md>)

Tags: [access-controls](<https://devfeed.tech/tags/access-controls.md>), [compliance](<https://devfeed.tech/tags/compliance.md>), [country](<https://devfeed.tech/tags/country.md>), [data](<https://devfeed.tech/tags/data.md>), [data-center](<https://devfeed.tech/tags/data-center.md>), [documentation](<https://devfeed.tech/tags/documentation.md>), [fields](<https://devfeed.tech/tags/fields.md>), [functions](<https://devfeed.tech/tags/functions.md>), [geolocation](<https://devfeed.tech/tags/geolocation.md>), [headers](<https://devfeed.tech/tags/headers.md>), [hosting](<https://devfeed.tech/tags/hosting.md>), [internet](<https://devfeed.tech/tags/internet.md>), [ip](<https://devfeed.tech/tags/ip.md>), [keep](<https://devfeed.tech/tags/keep.md>), [localization](<https://devfeed.tech/tags/localization.md>), [location](<https://devfeed.tech/tags/location.md>), [middleware](<https://devfeed.tech/tags/middleware.md>), [network](<https://devfeed.tech/tags/network.md>), [no-code](<https://devfeed.tech/tags/no-code.md>), [projects](<https://devfeed.tech/tags/projects.md>)

### AI overview

Vercel geolocation now provides city-level results for nearly all requests and postal-code results for 90% of traffic, with more frequent refreshes as IP ranges and routing change. It is enabled for all projects without code or configuration changes; existing geolocation headers and the `geolocation()` helper in `@vercel/functions` return the same fields for Vercel Functions and Routing Middleware. For access controls, localization, or compliance, some visitors--especially those using VPNs, hosting providers, or leased IP ranges--may resolve to a different city or country. Hosting-provider subnets announced from a country different from their RIR record resolve to the data center where traffic terminates. Test geo-dependent rules against an IP's active network location rather than its registry allocation.

### Source excerpt

IP geolocation on Vercel now resolves visitor locations with finer network granularity, delivering city-level data for nearly all requests and postal-code data for 90% of traffic. Geolocation data is now refreshed more often, so locations keep up as IP ranges are reassigned and routing changes. This is enabled for all projects with no code or configuration changes required. Existing geolocation headers along with the geolocation() helper in @vercel/functions, return the same fields for Vercel Functions and Routing Middleware. If you use geolocation for access controls, localization, or compliance, some visitors will now resolve to a different city or country, most often traffic from VPNs, hosting providers, and leased IP ranges: Physical termination location: Subnets announced from a hosting provider in a different country than their regional internet registry (RIR) record now resolve to the data center where the traffic actually terminates. Testing geo-dependent routes: Verify access rules against an IP's active network location rather than its static registry allocation. Read the request headers documentation for all available geolocation headers and fields. Read more

## 11 Networking Concepts Explained in 11 Minutes

DevFeed: [11 Networking Concepts Explained in 11 Minutes](<https://devfeed.tech/articles/11-networking-concepts-explained-in-11-minutes-97839.md>)

Original publisher: [Read original article](<https://newsletter.systemdesign.one/p/computer-networking-fundamentals-for-software-engineers>)

Author: Neo Kim

Published: 2026-10-23T16:06:14Z

Content type: article

Language: en

Sources: [System Design Newsletter](<https://devfeed.tech/sources/system-design-newsletter.md>)

Topics: [Ethernet](<https://devfeed.tech/topics/ethernet.md>), [network troubleshooting commands](<https://devfeed.tech/topics/network-troubleshooting-commands.md>), [Cloud Networking](<https://devfeed.tech/topics/cloud-networking.md>), [CIDR and subnets](<https://devfeed.tech/topics/cidr-and-subnets.md>), [MTU mismatch](<https://devfeed.tech/topics/mtu-mismatch.md>), [Tool](<https://devfeed.tech/topics/tool.md>)

Tags: [concepts](<https://devfeed.tech/tags/concepts.md>), [networking](<https://devfeed.tech/tags/networking.md>)

### AI overview

The excerpt explains how local and routed network communication works and how to investigate common connectivity issues. Ethernet carries IP packets in frames; switches learn MAC-to-port mappings and flood frames when a destination is unknown, while routers forward IP packets between networks. DHCP assigns leased addresses and settings such as the gateway and DNS servers; static addresses provide predictable assignments. Devices send remote traffic to a default gateway, and routers use static routes or OSPF to direct packets. Static routes require manual updates when paths change, while OSPF shares topology information and recalculates paths after failures, with convergence depending on detection, topology, and configuration. Wi-Fi performance varies with band, range, interference, signal quality, and retransmissions. ICMP reports errors and supports diagnostics but can be blocked or dropped and does not repair connections. Ping measures ICMP response time and missing replies; a successful ping does not establish that an application service is available. The excerpt recommends tools including `ip route`, `mtr`, `tcpdump`, and Wireshark for examining network behavior.

### Source excerpt

#195: Part 2 - Break Into Computer Networking

## ChainSEED: A Scalable, High-Fidelity Blockchain Emulator

DevFeed: [ChainSEED: A Scalable, High-Fidelity Blockchain Emulator](<https://devfeed.tech/articles/chainseed-a-scalable-high-fidelity-blockchain-emulator-97341.md>)

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

Author: Qishu Jin, Wenliang Du, Kairui Feng

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

Content type: article

Language: en

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

Topics: [Blockchain](<https://devfeed.tech/topics/blockchain.md>), [Ethereum](<https://devfeed.tech/topics/ethereum.md>), [Solana](<https://devfeed.tech/topics/solana.md>), [Distributed Systems & Parallel Computing](<https://devfeed.tech/topics/distributed-systems-parallel-computing.md>), [CIDR and subnets](<https://devfeed.tech/topics/cidr-and-subnets.md>)

Tags: [apis](<https://devfeed.tech/tags/apis.md>), [attacks](<https://devfeed.tech/tags/attacks.md>), [blockchain](<https://devfeed.tech/tags/blockchain.md>), [client](<https://devfeed.tech/tags/client.md>), [consensus](<https://devfeed.tech/tags/consensus.md>), [cpu](<https://devfeed.tech/tags/cpu.md>), [cs-ni](<https://devfeed.tech/tags/cs-ni.md>), [discovery](<https://devfeed.tech/tags/discovery.md>), [eclipse](<https://devfeed.tech/tags/eclipse.md>), [emulator](<https://devfeed.tech/tags/emulator.md>), [ethereum](<https://devfeed.tech/tags/ethereum.md>), [execution](<https://devfeed.tech/tags/execution.md>), [genesis](<https://devfeed.tech/tags/genesis.md>), [hardware](<https://devfeed.tech/tags/hardware.md>), [memory](<https://devfeed.tech/tags/memory.md>), [monitoring](<https://devfeed.tech/tags/monitoring.md>), [multiplexing](<https://devfeed.tech/tags/multiplexing.md>), [network](<https://devfeed.tech/tags/network.md>), [pow](<https://devfeed.tech/tags/pow.md>), [server](<https://devfeed.tech/tags/server.md>), [solana](<https://devfeed.tech/tags/solana.md>)

### AI overview

ChainSEED combines real blockchain clients with a configurable routed network, separating blockchain setup from client placement to enable controlled experiments. For Ethereum PoS it configures execution, consensus, and validator clients separately, with APIs for genesis state, peer connections, and client software; it also supports Monero and Solana. To fit larger experiments within limited hardware, the authors describe reducing beacon-node memory, allocating execution-client memory, and multiplexing validator clients. On one server with about 1 TiB of memory and 384 logical CPU cores, it deploys 400 beacon nodes, 400 execution nodes, and 60,000 validator identities at about 20 TPS. The abstract also reports emulation of a 1,200-node Monero network and a 200-node Solana network, plus case studies of routing and amplification attacks, Monero eclipse attacks, topology discovery, and network configuration.

### Source excerpt

arXiv:2610.31188v1 Announce Type: new Abstract: Researchers need blockchain experimental environments with configurable workloads, controllable network conditions, and observable outcomes. Public blockchains and testnets limit experimental control, model-based simulators omit real client implementations, and real-client environments face challenges in combining network control with resource-efficient deployment. We present ChainSEED, a scalable, high-fidelity blockchain emulator built on the SEED Internet Emulator. It separates blockchain configuration from client placement on a configurable routed network. For Ethereum PoS, it organizes separately configured execution, consensus, and validator clients and provides APIs for customizing genesis state, peer connections, and client software. A transaction generator informed by Ethereum mainnet activity, application interfaces, and chain- and node-level monitoring support experiments. ChainSEED also supports Monero and Solana. We examine beacon-node memory reduction, execution-client memory allocation, and validator-client multiplexing to support larger experiments within limited hardware budgets. On a single server with approximately 1 TiB of memory and 384 logical CPU cores, ChainSEED deploys 400 beacon nodes, 400 execution nodes, and 60,000 validator identities while sustaining approximately 20 TPS. It also emulates a 1,200-node Monero network with up to 200 active single-threaded PoW miners and a 200-node Solana network with sustained finalization. Case studies demonstrate routing attacks, blockchain amplification attacks, Monero eclipse attacks, topology-discovery benchmarking against known peer graphs, and network-configuration experiments.

## Part 2: Building VPC Networking with OpenStack Neutron and OVN

DevFeed: [Part 2: Building VPC Networking with OpenStack Neutron and OVN](<https://devfeed.tech/articles/part-2-building-vpc-networking-with-openstack-neutron-and-ovn-91424.md>)

Original publisher: [Read original article](<https://superuser.openinfra.org/articles/part-2-building-vpc-networking-with-openstack-neutron-and-ovn/>)

Author: Moonsang Yoo and Chanyeol Yoon

Published: 2026-10-21T07:00:03Z

Content type: article

Language: en

Sources: [Superuser](<https://devfeed.tech/sources/superuser.md>)

Topics: [openstack](<https://devfeed.tech/topics/openstack.md>), [Cloud Networking](<https://devfeed.tech/topics/cloud-networking.md>), [Cloud Architecture](<https://devfeed.tech/topics/cloud-architecture.md>), [Software-defined networking](<https://devfeed.tech/topics/sdn.md>), [container-networking](<https://devfeed.tech/topics/container-networking.md>), [observability](<https://devfeed.tech/topics/observability.md>), [CIDR and subnets](<https://devfeed.tech/topics/cidr-and-subnets.md>), [VPC Flow Logs](<https://devfeed.tech/topics/vpc-flow-logs.md>)

Tags: [access-control](<https://devfeed.tech/tags/access-control.md>), [api](<https://devfeed.tech/tags/api.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [audit](<https://devfeed.tech/tags/audit.md>), [auditability](<https://devfeed.tech/tags/auditability.md>), [automation](<https://devfeed.tech/tags/automation.md>), [aws](<https://devfeed.tech/tags/aws.md>), [cache](<https://devfeed.tech/tags/cache.md>), [certification](<https://devfeed.tech/tags/certification.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [cloud-management](<https://devfeed.tech/tags/cloud-management.md>), [cloud-native](<https://devfeed.tech/tags/cloud-native.md>), [design](<https://devfeed.tech/tags/design.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [networking](<https://devfeed.tech/tags/networking.md>), [news](<https://devfeed.tech/tags/news.md>), [openstack](<https://devfeed.tech/tags/openstack.md>), [openstack-neutron](<https://devfeed.tech/tags/openstack-neutron.md>), [ovn](<https://devfeed.tech/tags/ovn.md>), [sovereign-cloud](<https://devfeed.tech/tags/sovereign-cloud.md>), [technical-deep-dive](<https://devfeed.tech/tags/technical-deep-dive.md>), [uncategorized](<https://devfeed.tech/tags/uncategorized.md>), [vpc](<https://devfeed.tech/tags/vpc.md>), [vpc-flow-logs](<https://devfeed.tech/tags/vpc-flow-logs.md>)

### AI overview

KCP turns OpenStack Neutron resources into a customer-facing VPC service and uses OVN as a distributed network plane shared by OpenStack and Kubernetes through Kube-OVN. It enables VM-to-Pod paths with non-overlapping address spaces, routing, and NAT, while keeping each controller's desired state and resource ownership distinct. In a shared OVN Northbound DB, Kube-OVN reconciliation deleted Neutron Security Group ACLs; kt cloud reproduced the issue and proposed recording ACL origin and controller ownership so garbage collection stays within each controller's scope. KCP separates stateful, port-level Security Groups from stateless subnet or router-boundary NACLs. For auditability, it samples ACL-matched traffic through OVN and exports IPFIX; a per-compute-node Goflow2 Collector enriches records with tenant, interface, action, and direction metadata before sending Protobuf records to Kafka. The excerpt notes this can reduce central collection bottlenecks, while Neutron's VPC service layer must coordinate multiple resources, quotas, partial failures, and cleanup.

### Source excerpt

How kt cloud built a Multi-AZ VPC architecture with OpenStack Neutron and OVN, integrated it with Kubernetes networking through Kube-OVN, added VPC Flow Logs, and aligned the design with sovereign cloud principles.

## 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: When Only Provider Addresses Are Allowed (Part 3)

DevFeed: [Tenant Connectivity on VCF 9.1: When Only Provider Addresses Are Allowed (Part 3)](<https://devfeed.tech/articles/tenant-connectivity-on-vcf-9-1-when-only-provider-addresses-are-allowed-part-3-91196.md>)

Original publisher: [Read original article](<https://blogs.vmware.com/cloud-foundation/2026/10/20/tenant-connectivity-on-vcf-9-1-when-only-provider-addresses-are-allowed-part-3/>)

Author: mohammad saad

Published: 2026-10-20T17:22:42Z

Content type: article

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>)

Tags: [cloud-infrastructure](<https://devfeed.tech/tags/cloud-infrastructure.md>), [connectivity](<https://devfeed.tech/tags/connectivity.md>), [enterprise](<https://devfeed.tech/tags/enterprise.md>), [multi-tenancy](<https://devfeed.tech/tags/multi-tenancy.md>), [network-design](<https://devfeed.tech/tags/network-design.md>), [nsx](<https://devfeed.tech/tags/nsx.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

For Cairo, whose enterprise accepts only provider-assigned addresses, keep the VPC Connectivity Profile's single Auto SNAT block set to the Internet range (10.100.20.0/24) and enable Provider Outbound SNAT on the enterprise connection with its authorized range (10.100.10.0/24). NSX creates the VPC's default outbound NAT rule and connection-scoped Provider SNAT and No-SNAT rules; no per-workload NAT rules are needed. Internet traffic is translated once at the VPC gateway, while enterprise traffic is translated there and again at the CTGW. Each destination sees its provider-owned range, never the workload's private address. The tradeoff is double translation and reliance on CTGW NAT state to map enterprise-side logs back to workloads. The excerpt also describes failure states when the Internet connection or enterprise Provider SNAT is missing.

### 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 (this article) Part 4: When the Enterprise Must See Real ... Continued The post Tenant Connectivity on VCF 9.1: When Only Provider Addresses Are Allowed (Part 3) 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.

## IPv6 reachability

DevFeed: [IPv6 reachability](<https://devfeed.tech/articles/ipv6-reachability-89158.md>)

Original publisher: [Read original article](<https://specification.website/spec/resilience/ipv6/>)

Author: Joost de Valk

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

Content type: tutorial

Language: en

Sources: [The Website Specification](<https://devfeed.tech/sources/the-website-specification.md>)

Topics: [Domain Name System (DNS)](<https://devfeed.tech/topics/dns-resolution-process.md>), [authoritative name server](<https://devfeed.tech/topics/authoritative-name-server.md>), [CIDR and subnets](<https://devfeed.tech/topics/cidr-and-subnets.md>)

Tags: [authoritative-server](<https://devfeed.tech/tags/authoritative-server.md>), [dns](<https://devfeed.tech/tags/dns.md>), [dual-stack](<https://devfeed.tech/tags/dual-stack.md>), [https](<https://devfeed.tech/tags/https.md>), [ipv4](<https://devfeed.tech/tags/ipv4.md>), [ipv6](<https://devfeed.tech/tags/ipv6.md>), [load-balancer](<https://devfeed.tech/tags/load-balancer.md>), [monitoring](<https://devfeed.tech/tags/monitoring.md>), [recommended](<https://devfeed.tech/tags/recommended.md>), [resilience](<https://devfeed.tech/tags/resilience.md>)

### AI overview

This tutorial explains how to make a website reachable over IPv6 alongside IPv4. It covers publishing AAAA records for the web host and authoritative name servers, configuring servers, firewalls, load balancers, certificates, and redirects for consistent IPv6 service, and monitoring both protocols separately. It also describes fallback delays and failures that can affect IPv6-only clients.

### Source excerpt

Publish AAAA records for the web server and the authoritative name servers, make sure every IPv6 address actually answers, and serve the same site over IPv6 as over IPv4.

## Kubernetes VPC on OpenShift with Isovalent Networking for Virtualization

DevFeed: [Kubernetes VPC on OpenShift with Isovalent Networking for Virtualization](<https://devfeed.tech/articles/kubernetes-vpc-on-openshift-with-isovalent-networking-for-virtualization-65674.md>)

Original publisher: [Read original article](<https://isovalent.com/blog/post/kubernetes-vpc-on-openshift/>)

Author: Christian Hernandez

Published: 2026-10-05T22:01:00Z

Content type: article

Language: en

Sources: [Isovalent](<https://devfeed.tech/sources/isovalent-the-latest-articles-covering-ebpf-based-networking-observability-and-security.md>)

Topics: [virtualization](<https://devfeed.tech/topics/virtualization.md>), [Cloud Networking](<https://devfeed.tech/topics/cloud-networking.md>), [CIDR and subnets](<https://devfeed.tech/topics/cidr-and-subnets.md>), [OpenFaaS](<https://devfeed.tech/topics/openfaas.md>)

Tags: [builds](<https://devfeed.tech/tags/builds.md>), [isovalent](<https://devfeed.tech/tags/isovalent.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [networking](<https://devfeed.tech/tags/networking.md>), [networks](<https://devfeed.tech/tags/networks.md>), [openshift](<https://devfeed.tech/tags/openshift.md>), [vpc](<https://devfeed.tech/tags/vpc.md>)

### AI overview

The post presents Isovalent Private Networks as a Kubernetes VPC and describes two demo builds using isolated private networks with overlapping CIDRs on an OpenShift Virtualization cluster.

### Source excerpt

In this post we explore how Isovalent Networking for Virtualization with Isovalent Private Networks, and why they are best understood as the Kubernetes VPC. In this post, we'll focus on two demo builds using isolated private networks with overlapping CIDRs on an OpenShift Virtualization cluster.

## IP Functions are Generally Available, bringing high-performance network analytics to the Lakehouse

DevFeed: [IP Functions are Generally Available, bringing high-performance network analytics to the Lakehouse](<https://devfeed.tech/articles/ip-functions-are-generally-available-bringing-high-performance-network-analytics-to-the-lakehouse-63035.md>)

Original publisher: [Read original article](<https://www.databricks.com/blog/ip-functions-are-generally-available-bringing-high-performance-network-analytics-lakehouse>)

Author: Michael Andersen; Benjamin Mathew

Published: 2026-10-01T01:46:05Z

Content type: release

Language: en

Sources: [Databricks](<https://devfeed.tech/sources/databricks.md>)

Topics: [databricks](<https://devfeed.tech/topics/databricks.md>), [CIDR and subnets](<https://devfeed.tech/topics/cidr-and-subnets.md>)

Tags: [analytics](<https://devfeed.tech/tags/analytics.md>), [ip](<https://devfeed.tech/tags/ip.md>), [ipv4](<https://devfeed.tech/tags/ipv4.md>), [ipv6](<https://devfeed.tech/tags/ipv6.md>), [lakehouse](<https://devfeed.tech/tags/lakehouse.md>), [observability](<https://devfeed.tech/tags/observability.md>)

### AI overview

Databricks announces general availability of built-in IP functions for SQL analytics on the lakehouse. The functions support IPv4, IPv6, and CIDR notation, with engine integration that enables optimizer and Photon acceleration. They address network security and observability workflows that previously required custom code and maintained UDF libraries.

### Source excerpt

IP data is warehousing dataEvery firewall, load balancer, VPN, CDN edge, DNS resolver,...

## Prefix Sets: Simplifying netlab ACLs and Prefix Filters

DevFeed: [Prefix Sets: Simplifying netlab ACLs and Prefix Filters](<https://devfeed.tech/articles/prefix-sets-simplifying-netlab-acls-and-prefix-filters-60743.md>)

Original publisher: [Read original article](<https://blog.ipspace.net/2026/09/netlab-prefix-sets/>)

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

Content type: tutorial

Language: en

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

Topics: [CIDR and subnets](<https://devfeed.tech/topics/cidr-and-subnets.md>), [Scapy](<https://devfeed.tech/topics/scapy.md>)

Tags: [cisco](<https://devfeed.tech/tags/cisco.md>), [eos](<https://devfeed.tech/tags/eos.md>), [ideas](<https://devfeed.tech/tags/ideas.md>), [ipv4](<https://devfeed.tech/tags/ipv4.md>), [ipv6](<https://devfeed.tech/tags/ipv6.md>), [netlab](<https://devfeed.tech/tags/netlab.md>), [prefix-lists](<https://devfeed.tech/tags/prefix-lists.md>), [vlan](<https://devfeed.tech/tags/vlan.md>), [yaml](<https://devfeed.tech/tags/yaml.md>)

### AI overview

The article describes a redesign of netlab's prefix filters and ACLs into generic prefix sets. The change allows lists of IPv4 and IPv6 addresses, prefixes, and object descriptors, reducing repetitive YAML and generating device configurations such as Arista EOS ACLs, Cisco IOS XR prefix sets, and prefix lists.

### Source excerpt

When I implemented prefix filters in netlab (release 1.9.0), I wanted them to match the final device configurations as closely as possible, including the one prefix per entry rule to match the device configuration sequence numbers. That worked well, but resulted in YAML bloat, since each matching prefix requires several lines of YAML. We tried to use the same approach with ACLs but quickly gave up when we realized the port not in range operation requires multiple ACL entries on most platforms. With the matching sequence numbers paradigm gone with the wind, it made no sense to limit ourselves to one prefix per ACL entry - the initial ACL entry implementation already accepted lists of prefixes and expanded them into ACL entries. Read more ...

## Network Rack for Small Office (Build Guide)

DevFeed: [Network Rack for Small Office (Build Guide)](<https://devfeed.tech/articles/network-rack-for-small-office-build-guide-20879.md>)

Original publisher: [Read original article](<https://linuxblog.io/network-rack-for-small-office/>)

Author: Hayden James

Published: 2026-06-22T12:58:14Z

Content type: tutorial

Language: en

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

Topics: [CIDR and subnets](<https://devfeed.tech/topics/cidr-and-subnets.md>)

Tags: [access-points](<https://devfeed.tech/tags/access-points.md>), [admin](<https://devfeed.tech/tags/admin.md>), [airflow](<https://devfeed.tech/tags/airflow.md>), [ata](<https://devfeed.tech/tags/ata.md>), [blog](<https://devfeed.tech/tags/blog.md>), [build](<https://devfeed.tech/tags/build.md>), [community-forums](<https://devfeed.tech/tags/community-forums.md>), [core](<https://devfeed.tech/tags/core.md>), [functional](<https://devfeed.tech/tags/functional.md>), [future](<https://devfeed.tech/tags/future.md>), [general](<https://devfeed.tech/tags/general.md>), [growth](<https://devfeed.tech/tags/growth.md>), [guide](<https://devfeed.tech/tags/guide.md>), [homelab](<https://devfeed.tech/tags/homelab.md>), [isp](<https://devfeed.tech/tags/isp.md>), [network](<https://devfeed.tech/tags/network.md>), [office](<https://devfeed.tech/tags/office.md>), [online](<https://devfeed.tech/tags/online.md>), [power](<https://devfeed.tech/tags/power.md>), [rack](<https://devfeed.tech/tags/rack.md>), [room](<https://devfeed.tech/tags/room.md>), [small](<https://devfeed.tech/tags/small.md>), [space](<https://devfeed.tech/tags/space.md>), [storage](<https://devfeed.tech/tags/storage.md>), [sysadmins](<https://devfeed.tech/tags/sysadmins.md>)

### AI overview

The guide describes a small-office network rack built to keep core services running through brief brown-outs and outages while leaving room to expand. It uses a wheeled, open-frame 20U rack, a UniFi Dream Machine Pro router/firewall with dual-WAN, and a fan-free UniFi Pro Max 16 PoE switch rated at 180 W. CyberPower CP1500PFCLCD units are said to provide roughly two hours of backup for the router, switch, and Wi-Fi; a separate 900 VA unit powers VoIP gear. A modular 24-port Cat-6 patch panel, labeled patch leads, cable-management panels, and a 10G fiber router-to-switch uplink complete the setup. The excerpt says SFP+ ports provide expansion headroom, including for future cameras, a second ISP, or a Linux server. It cuts off while describing the battery layout, so further details are unavailable.

### Source excerpt

Last week I walked into an empty 5 x 4 ft storage room. By the end of the week, that blank space held a fully functional network core designed to keep a small professional office online through power cuts, ISP hiccups, and future growth. Continue reading...

## Adjust Docker's Default Address Pool to Prevent Network Conflicts

DevFeed: [Adjust Docker's Default Address Pool to Prevent Network Conflicts](<https://devfeed.tech/articles/fixing-docker-s-network-problem-before-it-breaks-yours-65770.md>)

Original publisher: [Read original article](<https://noted.lol/fixing-docker-network-problem/>)

Author: Jeremy

Published: 2025-11-14T14:33:45Z

Content type: tutorial

Language: en

Sources: [Noted](<https://devfeed.tech/sources/noted.md>)

Topics: [Docker](<https://devfeed.tech/topics/docker.md>), [CIDR and subnets](<https://devfeed.tech/topics/cidr-and-subnets.md>), [ip-address-planning](<https://devfeed.tech/topics/ip-address-planning.md>), [Network Configuration](<https://devfeed.tech/topics/network-configuration.md>)

Tags: [configuration](<https://devfeed.tech/tags/configuration.md>), [containers](<https://devfeed.tech/tags/containers.md>), [docker](<https://devfeed.tech/tags/docker.md>), [homelab](<https://devfeed.tech/tags/homelab.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [ip](<https://devfeed.tech/tags/ip.md>), [learn](<https://devfeed.tech/tags/learn.md>), [network](<https://devfeed.tech/tags/network.md>), [subnets](<https://devfeed.tech/tags/subnets.md>)

### AI overview

Docker's default address pools can consume available IP space and overlap with home networks as containers and networks are added. The tutorial shows how to configure smaller subnets in Docker's default address pool and recreate stacks to address conflicts and the no-available-networks error.

### Source excerpt

Docker's default network settings can consume your IP space and cause conflicts on your home network. Learn how to adjust the default address pool to prevent overlapping subnets and fix the "no available networks" error before it happens.

[Next page](<https://devfeed.tech/topics/cidr-and-subnets.md?cursor=WyIyMDI1LTExLTE0VDE0OjMzOjQ1KzAwOjAwIiwgImU1MGY3ZDExLTNlNGUtNGY1MC05MzBiLTllZmM2NTkwNzczMSJd>)