# NAT and SNAT

Network Address Translation (NAT) modifies source or destination IP addresses in transit; Source Network Address Translation (SNAT) modifies the sender's IP address, commonly enabling private hosts to communicate with public Internet servers.

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

## AWS Network Firewall proxy and native NAT Gateway integration

DevFeed: [AWS Network Firewall proxy and native NAT Gateway integration](<https://devfeed.tech/articles/aws-network-firewall-proxy-and-native-nat-gateway-integration-144599.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/networking-and-content-delivery/aws-network-firewall-proxy-and-native-nat-gateway-integration/>)

Author: Tom Adamski

Published: 2026-11-19T20:49:47Z

Content type: release

Language: en

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

Topics: [AWS Network Firewall](<https://devfeed.tech/topics/aws-network-firewall.md>), [NAT and SNAT](<https://devfeed.tech/topics/nat-and-snat.md>), [Firewall](<https://devfeed.tech/topics/firewall.md>), [Amazon VPC](<https://devfeed.tech/topics/amazon-vpc.md>), [secure web gateway](<https://devfeed.tech/topics/secure-web-gateway.md>), [Cloud Networking](<https://devfeed.tech/topics/cloud-networking.md>), [Amazon Web Services](<https://devfeed.tech/topics/aws.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [announcements](<https://devfeed.tech/tags/announcements.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-network-firewall](<https://devfeed.tech/tags/aws-network-firewall.md>), [egress](<https://devfeed.tech/tags/egress.md>), [explicit-proxy](<https://devfeed.tech/tags/explicit-proxy.md>), [filter](<https://devfeed.tech/tags/filter.md>), [firewall](<https://devfeed.tech/tags/firewall.md>), [gateway](<https://devfeed.tech/tags/gateway.md>), [http](<https://devfeed.tech/tags/http.md>), [https](<https://devfeed.tech/tags/https.md>), [inspect](<https://devfeed.tech/tags/inspect.md>), [integration](<https://devfeed.tech/tags/integration.md>), [introduced](<https://devfeed.tech/tags/introduced.md>), [launch](<https://devfeed.tech/tags/launch.md>), [nat](<https://devfeed.tech/tags/nat.md>), [native](<https://devfeed.tech/tags/native.md>), [network](<https://devfeed.tech/tags/network.md>), [network-firewall](<https://devfeed.tech/tags/network-firewall.md>), [proxy](<https://devfeed.tech/tags/proxy.md>), [security-identity-compliance](<https://devfeed.tech/tags/security-identity-compliance.md>), [traffic](<https://devfeed.tech/tags/traffic.md>)

### AI overview

AWS Network Firewall now supports explicit HTTP/HTTPS proxying and routed firewall inspection through one firewall policy, with both traffic paths using the same egress IP addresses. For routed traffic, optional native NAT managed by Network Firewall can centralize egress from VPCs with overlapping or non-overlapping CIDRs without service chaining; without NAT, traffic returns through the endpoint as before. Proxy setup uses CONNECT requests and requires no route table changes. The source describes migration aids including custom proxy hostnames with an ACM certificate and a Squid-to-Suricata rule converter. TLS inspection can cover secondary endpoints only when they are in the firewall's account; domain-based selective TLS inspection applies to proxy traffic, not routed traffic. For domain filtering, it recommends pairing DNS rules that control proxy resolution with TLS SNI rules that check traffic inside established tunnels. Cached DNS responses honor TTLs of 5-3,600 seconds, so a new drop rule may not affect connections until the cached entry expires.

### Source excerpt

With this launch you can use your AWS Network Firewall to filter HTTP and HTTPS traffic as an explicit proxy, inspect all other traffic as a routed firewall, and centralize egress from overlapping and non-overlapping source VPC through a NAT Gateway that Network Firewall manages for you. In August 2026, we re-introduced Network Firewall proxy [...]

## 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.

## Virtual Private Clouds in VMware vSphere Kubernetes Service: The Recommended Network Stack

DevFeed: [Virtual Private Clouds in VMware vSphere Kubernetes Service: The Recommended Network Stack](<https://devfeed.tech/articles/virtual-private-clouds-in-vmware-vsphere-kubernetes-service-the-recommended-network-stack-138605.md>)

Original publisher: [Read original article](<https://blogs.vmware.com/cloud-foundation/2026/11/17/virtual-private-clouds-in-vmware-vsphere-kubernetes-service-the-recommended-network-stack/>)

Author: vmwareblogs

Published: 2026-11-17T14:00:00Z

Content type: article

Language: en

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

Topics: [vcf networking](<https://devfeed.tech/topics/vcf-networking.md>), [Cloud Networking](<https://devfeed.tech/topics/cloud-networking.md>), [VMware Cloud Foundation](<https://devfeed.tech/topics/vcf-9-1.md>), [Load Balancing](<https://devfeed.tech/topics/load-balancing.md>), [NAT and SNAT](<https://devfeed.tech/topics/nat-and-snat.md>), [container-networking](<https://devfeed.tech/topics/container-networking.md>), [private cloud](<https://devfeed.tech/topics/private-cloud.md>), [vcf automation](<https://devfeed.tech/topics/vcf-automation.md>), [self-service](<https://devfeed.tech/topics/self-service.md>)

Tags: [cloud](<https://devfeed.tech/tags/cloud.md>), [cloud-infrastructure](<https://devfeed.tech/tags/cloud-infrastructure.md>), [home-page](<https://devfeed.tech/tags/home-page.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [kubernetes-nodes](<https://devfeed.tech/tags/kubernetes-nodes.md>), [kubevm](<https://devfeed.tech/tags/kubevm.md>), [network](<https://devfeed.tech/tags/network.md>), [network-stack](<https://devfeed.tech/tags/network-stack.md>), [networking](<https://devfeed.tech/tags/networking.md>), [nsx](<https://devfeed.tech/tags/nsx.md>), [private](<https://devfeed.tech/tags/private.md>), [private-cloud](<https://devfeed.tech/tags/private-cloud.md>), [recommended](<https://devfeed.tech/tags/recommended.md>), [service](<https://devfeed.tech/tags/service.md>), [supervisor](<https://devfeed.tech/tags/supervisor.md>), [switch](<https://devfeed.tech/tags/switch.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>), [vks](<https://devfeed.tech/tags/vks.md>), [vks-vsphere-kubernetes-service](<https://devfeed.tech/tags/vks-vsphere-kubernetes-service.md>), [vmware-cloud-foundation](<https://devfeed.tech/tags/vmware-cloud-foundation.md>), [vmware-vsphere-kubernetes-service](<https://devfeed.tech/tags/vmware-vsphere-kubernetes-service.md>), [vpc](<https://devfeed.tech/tags/vpc.md>), [vsphere](<https://devfeed.tech/tags/vsphere.md>)

### AI overview

VCF Networking with VPC is the recommended VCF 9.1 stack for production VKS deployments and the required stack for VCF Automation environments. It places cluster nodes on private subnets and exposes needed endpoints through load balancing, with outbound NAT; its Virtual Network Appliance cluster scales to ten active/active nodes. The vSphere Distributed Switch option connects nodes to an existing VLAN and routes VIPs through one active/standby Foundation Load Balancer pair. VPC setup can start with one VLAN and grow to centralized Edge connectivity or Cisco and Arista EVPN/VXLAN integration. It also provides vCenter-based networking and Traceflow, multi-tenancy and self-service automation, and integrations including Infoblox and vDefend. A VLAN-backed VPC option in VCF 9.1.1 preserves the VPC workflow but removes private-network creation. The article says the Distributed Switch remains suited to VMware vSphere Foundation and smaller or lab environments.

### Source excerpt

Enabling the vSphere Supervisor in VMware Cloud Foundation (VCF) involves choosing a network stack for workloads running on vSphere Kubernetes Service (VKS), KubeVM Service, or Container Service - VCF Networking with Virtual Private Cloud (VPC), or the vSphere Distributed Switch. VCF Networking with VPC is the recommended, default option. It keeps Kubernetes nodes off the ... Continued The post Virtual Private Clouds in VMware vSphere Kubernetes Service: The Recommended Network Stack appeared first on VMware Blogs.

## Introducing 1:1 NAT on AWS Transit Gateway and AWS Cloud WAN

DevFeed: [Introducing 1:1 NAT on AWS Transit Gateway and AWS Cloud WAN](<https://devfeed.tech/articles/introducing-1-1-nat-on-aws-transit-gateway-and-aws-cloud-wan-137829.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/networking-and-content-delivery/introducing-11-nat-on-aws-transit-gateway-and-aws-cloud-wan/>)

Author: Shubham Singh

Published: 2026-11-16T20:10:05Z

Content type: release

Language: en

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

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

Tags: [amazon-ec2](<https://devfeed.tech/tags/amazon-ec2.md>), [amazon-vpc](<https://devfeed.tech/tags/amazon-vpc.md>), [announcements](<https://devfeed.tech/tags/announcements.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-cloud](<https://devfeed.tech/tags/aws-cloud.md>), [aws-cloud-wan](<https://devfeed.tech/tags/aws-cloud-wan.md>), [aws-direct-connect](<https://devfeed.tech/tags/aws-direct-connect.md>), [aws-site-to-site-vpn](<https://devfeed.tech/tags/aws-site-to-site-vpn.md>), [aws-transit-gateway](<https://devfeed.tech/tags/aws-transit-gateway.md>), [bgp](<https://devfeed.tech/tags/bgp.md>), [connect](<https://devfeed.tech/tags/connect.md>), [csp](<https://devfeed.tech/tags/csp.md>), [dns](<https://devfeed.tech/tags/dns.md>), [ecmp](<https://devfeed.tech/tags/ecmp.md>), [intermediate-200](<https://devfeed.tech/tags/intermediate-200.md>), [nat](<https://devfeed.tech/tags/nat.md>), [network](<https://devfeed.tech/tags/network.md>)

### AI overview

AWS Transit Gateway and AWS Cloud WAN now support static, stateless IPv4 1:1 NAT through Regional Private NAT Gateway integration to connect networks with overlapping CIDRs. Per attachment, rules map a source CIDR to a translated CIDR of the same prefix length; the host portion and ports remain unchanged, and translation works in both directions. NAT CIDRs must come from RFC 1918 or RFC 6598 ranges. A route to each translated range is required: system-route support lets AWS create it, while disabling that setting requires the network to advertise the NAT CIDR over BGP. The article illustrates use on overlapping VPCs, a Direct Connect gateway attachment for multicloud connectivity, and Cloud WAN VPN attachments for partner networks. Update DNS records to translated addresses because NAT does not rewrite DNS. System routes rank below static and above propagated routes; with system-route support enabled, original BGP attributes such as AS path and MED are not preserved. For VPN designs using ECMP or primary/standby, the article recommends disabling system-route support and having the partner advertise the NAT CIDR and stop advertising the overlapping original range. NAT is IPv4-only,

### Source excerpt

Overlapping IP addresses keep networks from connecting. With 1:1 NAT on AWS Transit Gateway and AWS Cloud WAN, each network gets a unique range through native Regional Private NAT Gateway integration, so you don't renumber networks or deploy a separate NAT solution.

## Hackers plant GSocket on Linux servers for persistent access

DevFeed: [Hackers plant GSocket on Linux servers for persistent access](<https://devfeed.tech/articles/hackers-plant-gsocket-on-linux-servers-for-persistent-access-130085.md>)

Original publisher: [Read original article](<https://www.bleepingcomputer.com/news/security/hackers-plant-gsocket-on-linux-servers-for-persistent-access/>)

Author: Bill Toulas

Published: 2026-11-12T09:38:00Z

Content type: news

Language: en

Sources: [BleepingComputer](<https://devfeed.tech/sources/bleepingcomputer.md>)

Topics: [Linux](<https://devfeed.tech/topics/linux.md>), [NAT and SNAT](<https://devfeed.tech/topics/nat-and-snat.md>), [Remote Access Trojan](<https://devfeed.tech/topics/remote-access-trojan.md>)

Tags: [computer-help](<https://devfeed.tech/tags/computer-help.md>), [computer-security](<https://devfeed.tech/tags/computer-security.md>), [computers](<https://devfeed.tech/tags/computers.md>), [dirty-frag](<https://devfeed.tech/tags/dirty-frag.md>), [evasion](<https://devfeed.tech/tags/evasion.md>), [exploited](<https://devfeed.tech/tags/exploited.md>), [gsocket](<https://devfeed.tech/tags/gsocket.md>), [hackers](<https://devfeed.tech/tags/hackers.md>), [infosec](<https://devfeed.tech/tags/infosec.md>), [infosec-computer-security](<https://devfeed.tech/tags/infosec-computer-security.md>), [linux](<https://devfeed.tech/tags/linux.md>), [mac](<https://devfeed.tech/tags/mac.md>), [malware](<https://devfeed.tech/tags/malware.md>), [malware-removal](<https://devfeed.tech/tags/malware-removal.md>), [persistence](<https://devfeed.tech/tags/persistence.md>), [plant](<https://devfeed.tech/tags/plant.md>), [security](<https://devfeed.tech/tags/security.md>), [servers](<https://devfeed.tech/tags/servers.md>), [spyware](<https://devfeed.tech/tags/spyware.md>), [support](<https://devfeed.tech/tags/support.md>), [tech-support](<https://devfeed.tech/tags/tech-support.md>), [technical-support](<https://devfeed.tech/tags/technical-support.md>), [virus](<https://devfeed.tech/tags/virus.md>), [virus-removal](<https://devfeed.tech/tags/virus-removal.md>), [windows](<https://devfeed.tech/tags/windows.md>)

### AI overview

Threat actors use GSocket to retain access to compromised Linux servers after the vulnerabilities used for initial entry are patched. Both the server and attacker initiate outbound connections to GSocket's Global Socket Relay Network, which brokers an encrypted session; this avoids an inbound listener or public IP and makes IP- or domain-based blocking less effective. Microsoft Defender for Endpoint detections rose 356.2% from March to August, with 87.1% of incidents involving web applications and hosting. Attackers used cron jobs, systemd services, and shell startup files for persistence, and sometimes attempted to exploit CVE-2026-43284 for root access. Microsoft recommends removing GSocket and related files, confirming relay connections have stopped, restricting outbound traffic to approved destinations, auditing persistence locations, and keeping systems and applications patched. The excerpt says inbound firewall rules may miss this traffic, while egress filtering and outbound monitoring can detect it.

### Source excerpt

Multiple threat actors are abusing GSocket, a legitimate open-source remote access tool, to maintain access to Linux servers even after patching the vulnerabilities exploited to gain initial access. [...]

## When Should You Remove NAT from an On-Prem Kubernetes Network?

DevFeed: [When Should You Remove NAT from an On-Prem Kubernetes Network?](<https://devfeed.tech/articles/when-should-you-remove-nat-from-an-on-prem-kubernetes-network-137129.md>)

Original publisher: [Read original article](<https://www.sitepoint.com/when-should-you-remove-nat-from-an-on-prem-kubernetes-network/>)

Author: Sergey Speranskiy

Published: 2026-11-11T21:34:09Z

Content type: comparison

Language: en

Sources: [SitePoint](<https://devfeed.tech/sources/sitepoint.md>)

Topics: [NAT and SNAT](<https://devfeed.tech/topics/nat-and-snat.md>), [on-prem](<https://devfeed.tech/topics/on-prem.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [ai-workloads](<https://devfeed.tech/tags/ai-workloads.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [bgp](<https://devfeed.tech/tags/bgp.md>), [black-box](<https://devfeed.tech/tags/black-box.md>), [cilium](<https://devfeed.tech/tags/cilium.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [cni](<https://devfeed.tech/tags/cni.md>), [conntrack](<https://devfeed.tech/tags/conntrack.md>), [cpu](<https://devfeed.tech/tags/cpu.md>), [data-center](<https://devfeed.tech/tags/data-center.md>), [ebpf](<https://devfeed.tech/tags/ebpf.md>), [ecmp](<https://devfeed.tech/tags/ecmp.md>), [fabric](<https://devfeed.tech/tags/fabric.md>), [failure](<https://devfeed.tech/tags/failure.md>), [high-availability](<https://devfeed.tech/tags/high-availability.md>), [implementation](<https://devfeed.tech/tags/implementation.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [nat](<https://devfeed.tech/tags/nat.md>), [network](<https://devfeed.tech/tags/network.md>), [on-prem](<https://devfeed.tech/tags/on-prem.md>)

### AI overview

Removing NAT can simplify inspection, reduce translation overhead, improve performance, lower node CPU use, and avoid conntrack exhaustion when Kubernetes pods are directly routable through a data center fabric. The article's example uses BIRD to advertise pod CIDRs and selected service addresses via BGP, with kube-router managing Kubernetes networking. This requires control of the physical network, available pod address space, and operators able to manage BGP and route filtering; NAT can still remain at the data center boundary. ECMP improves resilience only when nodes have multiple independent paths through redundant switches and uplinks. NAT suits clusters that need address-plan isolation or cannot route prefixes upstream; overlays offer portability and underlay abstraction, with another troubleshooting layer and possible encapsulation overhead. The article presents kube-router and BIRD as one implementation, while naming Calico and Cilium as alternatives for different needs. It also notes kube-proxy IPVS support is set to be dropped starting in Kubernetes 1.43, with nftables as the replacement.

### Source excerpt

null Continue reading When Should You Remove NAT from an On-Prem Kubernetes Network? on SitePoint.

## 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.

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

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

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

Author: Daniel Axelrod

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

Content type: release

Language: en

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

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

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

### AI overview

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

### Source excerpt

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

## Retrofitting Service Dependency Discovery in Distributed Systems

DevFeed: [Retrofitting Service Dependency Discovery in Distributed Systems](<https://devfeed.tech/articles/retrofitting-service-dependency-discovery-in-distributed-systems-101573.md>)

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

Author: Diogo Landau, Gijs Blanken, Jorge Barbosa, Nishant Saurabh

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

Content type: article

Language: en

Sources: [arXiv: Distributed Computing](<https://devfeed.tech/sources/arxiv-distributed-computing.md>)

Topics: [observability](<https://devfeed.tech/topics/observability.md>), [NAT and SNAT](<https://devfeed.tech/topics/nat-and-snat.md>), [systems](<https://devfeed.tech/topics/systems.md>), [network-intelligence](<https://devfeed.tech/topics/network-intelligence.md>), [distributed algorithm](<https://devfeed.tech/topics/distributed-algorithm.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [benchmarks](<https://devfeed.tech/tags/benchmarks.md>), [cs-dc](<https://devfeed.tech/tags/cs-dc.md>), [dependencies](<https://devfeed.tech/tags/dependencies.md>), [dependency](<https://devfeed.tech/tags/dependency.md>), [dependency-graph](<https://devfeed.tech/tags/dependency-graph.md>), [discovery](<https://devfeed.tech/tags/discovery.md>), [disruptive](<https://devfeed.tech/tags/disruptive.md>), [distributed](<https://devfeed.tech/tags/distributed.md>), [distributed-systems](<https://devfeed.tech/tags/distributed-systems.md>), [environments](<https://devfeed.tech/tags/environments.md>), [external](<https://devfeed.tech/tags/external.md>), [free](<https://devfeed.tech/tags/free.md>), [graph](<https://devfeed.tech/tags/graph.md>), [header](<https://devfeed.tech/tags/header.md>), [instrumentation](<https://devfeed.tech/tags/instrumentation.md>), [mechanism](<https://devfeed.tech/tags/mechanism.md>), [metadata](<https://devfeed.tech/tags/metadata.md>), [nat](<https://devfeed.tech/tags/nat.md>), [service](<https://devfeed.tech/tags/service.md>), [systems](<https://devfeed.tech/tags/systems.md>)

### AI overview

Ripple builds process-level service dependency graphs without source code instrumentation, addressing how NAT can obscure service hosts and undermine passive network-metadata approaches. It injects metadata into TCP packet headers while preserving protocol correctness across hosts; connections remain unaffected when a receiving agent is absent, enabling partial deployment. In tests against three state-of-the-art systems across nine scenarios, three network configurations, and three microservice benchmarks, Ripple was the only approach reported to perform consistently across configurations. Its precision and recall were 100% in the majority of scenarios, and its correctness was on par with or better than the compared systems.

### Source excerpt

arXiv:2510.15490v2 Announce Type: replace Abstract: Modern distributed systems rely on complex networks of interconnected services, creating direct or indirect dependencies that can propagate faults and cause cascading failures. To localize the root cause of performance degradation in these environments, constructing a service dependency graph is highly beneficial. However, building an accurate service dependency graph is impaired by complex routing techniques, such as Network Address Translation (NAT), an essential mechanism for connecting services across networks. NAT obfuscates the actual hosts running the services, causing existing run-time approaches that passively observe network metadata to fail in accurately inferring service dependencies. To this end, this paper introduces Ripple, a run-time system for constructing process-level service dependency graphs. It operates without source code instrumentation and remains resilient under complex network routing mechanisms, including NAT. Ripple implements a non-disruptive method of injecting metadata onto a TCP packet's header that maintains protocol correctness across host boundaries. In other words, if no receiving agent is present, the instrumentation leaves existing TCP connections unaffected, ensuring non-disruptive operation when it is partially deployed across hosts. We evaluated Ripple extensively against three state-of-the-art systems across nine scenarios, involving three network configurations (NAT-free, internal-NAT, external-NAT) and three microservice benchmarks. Ripple was the only approach that performed consistently across networking configurations. With regards to correctness, it performed on par with, or better than, the state-of-the-art with precision and recall values of 100% in the majority of the scenarios.

## GLP Networking API Specification

DevFeed: [GLP Networking API Specification](<https://devfeed.tech/articles/glp-networking-api-specification-100170.md>)

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

Author: Dan Bachar, Ehud Shapiro

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

Content type: article

Language: en

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

Topics: [Bluetooth LE](<https://devfeed.tech/topics/bluetooth-le.md>), [NAT and SNAT](<https://devfeed.tech/topics/nat-and-snat.md>), [Zero Trust](<https://devfeed.tech/topics/zero-trust.md>), [TLS (Transport Layer Security)](<https://devfeed.tech/topics/tls.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [agents](<https://devfeed.tech/tags/agents.md>), [api](<https://devfeed.tech/tags/api.md>), [apple](<https://devfeed.tech/tags/apple.md>), [application](<https://devfeed.tech/tags/application.md>), [asynchronous](<https://devfeed.tech/tags/asynchronous.md>), [atomic](<https://devfeed.tech/tags/atomic.md>), [attestation](<https://devfeed.tech/tags/attestation.md>), [bluetooth](<https://devfeed.tech/tags/bluetooth.md>), [bluetooth-low-energy](<https://devfeed.tech/tags/bluetooth-low-energy.md>), [cryptographic](<https://devfeed.tech/tags/cryptographic.md>), [cs-dc](<https://devfeed.tech/tags/cs-dc.md>), [cs-ni](<https://devfeed.tech/tags/cs-ni.md>), [cs-pl](<https://devfeed.tech/tags/cs-pl.md>), [delivered](<https://devfeed.tech/tags/delivered.md>), [delivery](<https://devfeed.tech/tags/delivery.md>), [developer](<https://devfeed.tech/tags/developer.md>), [ed25519](<https://devfeed.tech/tags/ed25519.md>), [google](<https://devfeed.tech/tags/google.md>), [graph](<https://devfeed.tech/tags/graph.md>), [handshake](<https://devfeed.tech/tags/handshake.md>), [networking](<https://devfeed.tech/tags/networking.md>), [specification](<https://devfeed.tech/tags/specification.md>)

### AI overview

The specification defines the networking layer madGLP needs for agents on smartphones to communicate over Bluetooth LE, local networks, and the Internet across NAT. It provides only services GLP cannot supply: networking, location, application attestation, and cryptographic primitives. PAN and LAN use rotating, key-derived recognition tokens; GLP sets whether an agent responds to unrecognized contacts. For WAN, a static-address rendezvous server coordinates hole punching without relaying payload or joining a social graph. Across all underlays, peers establish mutually authenticated Noise sessions using Ed25519 keys and attest, bound to the handshake, that they run an application published under its developer's key; verification uses Apple's and Google's roots without contacting a third party. A shared protocol over UDP datagrams and GATT writes provides the fair, unordered, atomic, authenticated delivery madGLP assumes.

### Source excerpt

arXiv:2610.32583v1 Announce Type: cross Abstract: Multiagent deterministic GLP (madGLP) runs Grassroots Logic Programs (GLP) as agents that communicate solely by asynchronous message passing, and assumes fair delivery: every message sent is eventually delivered. Each agent runs on a person's smartphone, named by the person's public key. A grassroots platform depends on no global resource but the network, so agents must reach one another over Bluetooth Low Energy, on a local network, and across the Internet from behind NAT, via rendezvous servers anyone can run. What madGLP requires of such a network, and what the network requires of the platform, has not been specified. We specify the networking layer beneath madGLP. Anything that can be done in GLP is done in GLP: the layer provides only what GLP cannot reach - the network stack, the location service, application attestation, and cryptographic primitives. Three transport underlays share one interface. Over PAN and LAN, an agent advertises a rotating recognition token derived from its key and time slot, so a peer who knows the key recognises it before contact and nobody else can track it; whether it answers unrecognised contacts is a per-underlay trust level set by GLP. Over WAN, a rendezvous server is a static-address host running the headless layer and a GLP rendezvous agent that coordinates hole punching, relays no payload, and belongs to no social graph. On every underlay, peers establish a mutually authenticated Noise session from Ed25519 keys, then attest, bound to the handshake hash, that each runs the application published under its developer's key, verified against Apple's and Google's roots with no third party contacted. One message protocol, over UDP datagrams and GATT writes, provides the fair, unordered, atomic and authenticated delivery madGLP assumes.

## 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.

## 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.

## Saving IPv4 Addresses on Interconnection with RFC8950

DevFeed: [Saving IPv4 Addresses on Interconnection with RFC8950](<https://devfeed.tech/articles/saving-ipv4-addresses-on-interconnection-with-rfc8950-89881.md>)

Original publisher: [Read original article](<https://labs.ripe.net/author/grueneberg/saving-ipv4-addresses-on-interconnection-with-rfc8950/>)

Author: André Grüneberg

Published: 2026-10-19T08:53:35Z

Content type: tutorial

Language: en

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

Topics: [IS-IS](<https://devfeed.tech/topics/is-is.md>), [NAT and SNAT](<https://devfeed.tech/topics/nat-and-snat.md>), [quasi-random network topology](<https://devfeed.tech/topics/quasi-random-network-topology.md>), [ip-address-planning](<https://devfeed.tech/topics/ip-address-planning.md>)

Tags: [arp](<https://devfeed.tech/tags/arp.md>), [bgp](<https://devfeed.tech/tags/bgp.md>), [conclusion](<https://devfeed.tech/tags/conclusion.md>), [configuration](<https://devfeed.tech/tags/configuration.md>), [connectivity](<https://devfeed.tech/tags/connectivity.md>), [core](<https://devfeed.tech/tags/core.md>), [cpu](<https://devfeed.tech/tags/cpu.md>), [discovery](<https://devfeed.tech/tags/discovery.md>), [dns](<https://devfeed.tech/tags/dns.md>), [dual-stack](<https://devfeed.tech/tags/dual-stack.md>), [ethernet](<https://devfeed.tech/tags/ethernet.md>), [ietf](<https://devfeed.tech/tags/ietf.md>), [internet-infrastructure](<https://devfeed.tech/tags/internet-infrastructure.md>), [internet-number-resources](<https://devfeed.tech/tags/internet-number-resources.md>), [ipv4](<https://devfeed.tech/tags/ipv4.md>), [ipv6](<https://devfeed.tech/tags/ipv6.md>), [ixp](<https://devfeed.tech/tags/ixp.md>), [ixps](<https://devfeed.tech/tags/ixps.md>), [networks](<https://devfeed.tech/tags/networks.md>), [practical](<https://devfeed.tech/tags/practical.md>), [reduce](<https://devfeed.tech/tags/reduce.md>), [rfc8950](<https://devfeed.tech/tags/rfc8950.md>), [stack](<https://devfeed.tech/tags/stack.md>)

### AI overview

The article explains how RFC8950 lets BGP advertise IPv4 routes with IPv6 next hops, allowing IXPs to reduce IPv4 address use on interconnection links. It outlines router and route-server configuration, compatibility considerations, and an IPv4/IPv6 translator approach for connecting members that support different next-hop families.

### Source excerpt

Many of us have been struggling with dual-stack IP address assignment on transfer networks. But what if we could reduce the work and concentrate on one IPv6 address per interconnection? Turns out, we already can. This article sheds some light on the practical implementation of RFC8950 at IXPs.

## Understanding iptables with WireGuard

DevFeed: [Understanding iptables with WireGuard](<https://devfeed.tech/articles/understanding-iptables-with-wireguard-86665.md>)

Original publisher: [Read original article](<https://spin.atomicobject.com/iptables-with-wireguard/>)

Author: Patrick Bacon

Published: 2026-10-14T12:00:22Z

Content type: tutorial

Language: en

Sources: [Atomic Object](<https://devfeed.tech/sources/atomic-object.md>)

Topics: [NAT and SNAT](<https://devfeed.tech/topics/nat-and-snat.md>)

Tags: [conntrack](<https://devfeed.tech/tags/conntrack.md>), [developer-tools](<https://devfeed.tech/tags/developer-tools.md>), [iptables](<https://devfeed.tech/tags/iptables.md>), [networking](<https://devfeed.tech/tags/networking.md>), [wireguard](<https://devfeed.tech/tags/wireguard.md>)

### AI overview

The tutorial explains iptables rules for forwarding WireGuard traffic and using MASQUERADE to enable replies from internal hosts. It covers Linux IP forwarding, stricter rules based on interfaces and client addresses, connection tracking for return traffic, and custom chains for organizing and removing rules.

### Source excerpt

I've been playing around with WireGuard a bit lately, and one of the things that keeps coming up is the iptables tool. Over the years, I've encountered iptables here and there, but it's always been a bit of a black box to me. I'd be trying to accomplish something that would need it, and while [...] The post Understanding iptables with WireGuard appeared first on Atomic Spin.

## Self-Hosting Matrix as a Discord Alternative: Setup and Maintenance Challenges

DevFeed: [Self-Hosting Matrix as a Discord Alternative: Setup and Maintenance Challenges](<https://devfeed.tech/articles/lead-a-discord-exodus-with-a-matrix-server-77206.md>)

Original publisher: [Read original article](<https://hackaday.com/2026/10/08/lead-a-discord-exodus-with-a-matrix-server/>)

Author: Bryan Cockfield

Published: 2026-10-08T14:00:07Z

Content type: article

Language: en

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

Topics: [Matrix](<https://devfeed.tech/topics/matrix-org.md>), [Discord](<https://devfeed.tech/topics/discord.md>), [Homelab](<https://devfeed.tech/topics/homelab.md>), [NAT and SNAT](<https://devfeed.tech/topics/nat-and-snat.md>), [virtual machines](<https://devfeed.tech/topics/virtual-machines.md>)

Tags: [cloudflare-tunnel](<https://devfeed.tech/tags/cloudflare-tunnel.md>), [discord](<https://devfeed.tech/tags/discord.md>), [end-to-end-encryption](<https://devfeed.tech/tags/end-to-end-encryption.md>), [featured](<https://devfeed.tech/tags/featured.md>), [interest](<https://devfeed.tech/tags/interest.md>), [matrix](<https://devfeed.tech/tags/matrix.md>)

### AI overview

The author describes running a Matrix server as an alternative to Discord, using Synapse and Element for encrypted chat. Adding voice and video required additional services and work around NAT, including a VPS and WireGuard connection. The account highlights control over messages alongside infrastructure complexity, maintenance demands and unresolved client issues.

### Source excerpt

The Internet, and large groups of people in general, tend to have a remarkably short collective memory. Whether it's the nature of algorithms or the people themselves to always be ...read more

## HPE ProLiant Gen13 Launches With the First Four AMD EPYC Venice Servers: Eight-GPU DL585a, 256-Core DL525, and OCP XD Nodes

DevFeed: [HPE ProLiant Gen13 Launches With the First Four AMD EPYC Venice Servers: Eight-GPU DL585a, 256-Core DL525, and OCP XD Nodes](<https://devfeed.tech/articles/hpe-proliant-gen13-launches-with-the-first-four-amd-epyc-venice-servers-eight-gpu-dl585a-256-core-dl525-and-ocp-xd-nodes-66840.md>)

Original publisher: [Read original article](<https://www.storagereview.com/news/hpe-proliant-gen13-first-four-amd-epyc-venice-servers>)

Author: Brian Beeler

Published: 2026-10-07T13:00:00Z

Content type: news

Language: en

Sources: [StorageReview.com](<https://devfeed.tech/sources/storagereview-com.md>)

Topics: [DS925neo+](<https://devfeed.tech/topics/ds925neo-plus.md>), [Infrastructure as a Service (IaaS)](<https://devfeed.tech/topics/infrastructure-as-a-service-iaas.md>), [AI Infrastructure](<https://devfeed.tech/topics/ai-infrastructure.md>), [NAT and SNAT](<https://devfeed.tech/topics/nat-and-snat.md>)

Tags: [amd](<https://devfeed.tech/tags/amd.md>), [amd-epyc](<https://devfeed.tech/tags/amd-epyc.md>), [cryptography](<https://devfeed.tech/tags/cryptography.md>), [enterprise](<https://devfeed.tech/tags/enterprise.md>), [epyc](<https://devfeed.tech/tags/epyc.md>), [has](<https://devfeed.tech/tags/has.md>), [launches](<https://devfeed.tech/tags/launches.md>), [memory](<https://devfeed.tech/tags/memory.md>), [proliant](<https://devfeed.tech/tags/proliant.md>), [server](<https://devfeed.tech/tags/server.md>), [servers](<https://devfeed.tech/tags/servers.md>), [venice](<https://devfeed.tech/tags/venice.md>), [with](<https://devfeed.tech/tags/with.md>)

### AI overview

HPE announced four ProLiant Gen13 servers based on 6th Gen AMD EPYC processors: the GPU dense DL585a, single socket DL525, and dense compute XD245 and XD285. The article describes their configurations, target workloads, cooling and power choices, availability, and iLO 8 security features, including automatic drive encryption, two person approval for high impact actions, and expanded post quantum cryptography.

### Source excerpt

HPE has announced the first four ProLiant Gen13 servers, and all of them run on 6th Gen AMD EPYC, the SP7-socket Venice parts AMD listed last month. The lineup is the two-socket, eight-GPU HPE ProLiant DL585a Gen13, the 1U single-socket HPE ProLiant DL525 Gen13 with up to 256 cores and 16-channel memory, and two Open The post HPE ProLiant Gen13 Launches With the First Four AMD EPYC Venice Servers: Eight-GPU DL585a, 256-Core DL525, and OCP XD Nodes appeared first on StorageReview.com.

## Self-Hosting Behind CGNAT

DevFeed: [Self-Hosting Behind CGNAT](<https://devfeed.tech/articles/self-hosting-behind-cgnat-60980.md>)

Original publisher: [Read original article](<https://david.alvarezrosa.com/posts/self-hosting-behind-cgnat/>)

Author: David Álvarez Rosa

Published: 2026-09-21T07:32:00Z

Content type: tutorial

Language: en

Sources: [David Álvarez Rosa](<https://devfeed.tech/sources/david-alvarez-rosa.md>)

Topics: [Homelab](<https://devfeed.tech/topics/homelab.md>), [Virtual Private Network](<https://devfeed.tech/topics/vpn.md>), [Self-hosted](<https://devfeed.tech/topics/self-hosted.md>), [NAT and SNAT](<https://devfeed.tech/topics/nat-and-snat.md>), [IP routing](<https://devfeed.tech/topics/ip-routing.md>)

Tags: [cgnat](<https://devfeed.tech/tags/cgnat.md>), [homelab](<https://devfeed.tech/tags/homelab.md>), [hosting](<https://devfeed.tech/tags/hosting.md>), [internet](<https://devfeed.tech/tags/internet.md>), [ipv4](<https://devfeed.tech/tags/ipv4.md>), [nat](<https://devfeed.tech/tags/nat.md>), [self-hosting](<https://devfeed.tech/tags/self-hosting.md>), [ssh](<https://devfeed.tech/tags/ssh.md>), [static](<https://devfeed.tech/tags/static.md>), [vps](<https://devfeed.tech/tags/vps.md>)

### AI overview

The article explains how to expose home-hosted services behind carrier-grade NAT by routing traffic through a VPS bridge over a bidirectional WireGuard tunnel. It describes the tunnel configuration, the added 39 ms round-trip-time penalty, and recovery options for failures.

### Source excerpt

There is nothing more satisfying than owning, end to end, the software and the hardware you use without relying on abusive cloud corporations. Internet is us, not them. Break free from censorship. Learn how to self-host at home, and be truly libre. In the past, self-hosting was easier. You just had to open a port on your router and forward it to any machine at home.1 Nowadays, the shortage of IPv4 addresses means routers share the same IP across your neighborhood. Requests are routed using carrier-grade NAT (CGNAT), a second-layer NAT inside the carrier's network, where your router's address is private and translated by the carrier on the way out. The public address is the carrier's, so port forwarding no longer works. Topology § My services run on a mid-range machine in my mother's basement in northern Spain, and are exposed to the Internet through a cheap VPS bridge in a French data center. +-------------------------------------+ | public Internet | +-------------------------------------+ ^ ^ | inbound | v | +------------+ | | bridge | | egress +------------+ | ^^ | || WireGuard | vv | +-------------------------------------+ | homelab | +-------------------------------------+ Code Snippet 1: Topology diagram. The homelab is exposed to the Internet through a WireGuard tunnel to a VPS bridge. A bidirectional WireGuard tunnel2 forwards all packets in all ports from the bridge to the homelab box, and vice versa. The beauty of this is that the tunnel is initiated by the homelab, so you don't need a static dedicated IP at home.3 The penalty of the bridge is 39 ms of RTT. Tunnel configuration § Bridge's wg0.conf.4 [Interface] Address = 10.0.0.1/24 PrivateKey = <bridge-private-key> ListenPort = 51820 PostUp = ... PostDown = ... [Peer] PublicKey = <homelab-public-key> AllowedIPs = 10.0.0.2/32 PostUp sets up NAT and forwarding rules at the kernel level.5 The first two exclude ports 2222 for SSH, and 51820 for the VPN tunnel itself. The last three forward all traffic in all

## Putting the ESP32 microcontroller on the Internet

DevFeed: [Putting the ESP32 microcontroller on the Internet](<https://devfeed.tech/articles/putting-the-esp32-microcontroller-on-the-internet-83314.md>)

Original publisher: [Read original article](<https://ngrok.com/blog/putting-the-esp32-microcontroller-on-the-internet>)

Author: Patrick McDowell

Published: 2023-01-12T00:00:00Z

Content type: tutorial

Language: en

Sources: [\[ngrok news\]](<https://devfeed.tech/sources/ngrok-news.md>)

Topics: [ESP32](<https://devfeed.tech/topics/esp32.md>), [ESP8266](<https://devfeed.tech/topics/esp8266.md>), [NAT and SNAT](<https://devfeed.tech/topics/nat-and-snat.md>), [Virtual Private Network](<https://devfeed.tech/topics/vpn.md>)

Tags: [active-directory](<https://devfeed.tech/tags/active-directory.md>), [arduino-ide](<https://devfeed.tech/tags/arduino-ide.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [custom-domain](<https://devfeed.tech/tags/custom-domain.md>), [esp32](<https://devfeed.tech/tags/esp32.md>), [firewall](<https://devfeed.tech/tags/firewall.md>), [ip](<https://devfeed.tech/tags/ip.md>), [ngrok](<https://devfeed.tech/tags/ngrok.md>), [ngrok-agent](<https://devfeed.tech/tags/ngrok-agent.md>), [secure-tunnels](<https://devfeed.tech/tags/secure-tunnels.md>)

### AI overview

This tutorial shows how to expose an ESP32 or ESP8266 web server to the internet using ngrok. It covers setup, authentication options, and protecting remote access to connected projects.

### Source excerpt

Put ESP32 and ESP8266 microcontroller projects online with ngrok, no port forwarding, static IP, or open firewall ports needed to control them remotely.

## SYN Flood Mitigation with synsanity

DevFeed: [SYN Flood Mitigation with synsanity](<https://devfeed.tech/articles/syn-flood-mitigation-with-synsanity-69639.md>)

Original publisher: [Read original article](<https://github.blog/engineering/platform-security/syn-flood-mitigation-with-synsanity/>)

Author: Theo Julienne

Published: 2016-07-12T07:00:00Z

Content type: article

Language: en

Sources: [GitHub Blog](<https://devfeed.tech/sources/github-engineering.md>), [GitHub Engineering](<https://devfeed.tech/sources/github.md>)

Topics: [DDoS](<https://devfeed.tech/topics/ddos.md>), [NAT and SNAT](<https://devfeed.tech/topics/nat-and-snat.md>), [Service fabric](<https://devfeed.tech/topics/service-fabric.md>)

Tags: [ddos](<https://devfeed.tech/tags/ddos.md>), [denial-of-service](<https://devfeed.tech/tags/denial-of-service.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [infrastructure](<https://devfeed.tech/tags/infrastructure.md>), [platform-security](<https://devfeed.tech/tags/platform-security.md>), [target](<https://devfeed.tech/tags/target.md>)

### AI overview

GitHub describes synsanity, an iptables module for Linux 3.x that mitigates SYN flood DDoS attacks. It generates and validates SYN cookies when the SYN queue overflows, avoiding the LISTEN socket lock while leaving subsequent connection packets to the standard Linux TCP stack. GitHub says the module helped mitigate attacks that would otherwise have caused partial or complete service outages and is open sourcing it.

### Source excerpt

GitHub hosts a wide range of user content, and like all large websites this often causes us to become a target of denial of service attacks. Around a year ago,...