<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Networking on The David Page</title><link>https://thedavidpage.pages.dev/tags/networking/</link><description>Recent content in Networking on The David Page</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Fri, 20 Feb 2026 09:00:00 +0700</lastBuildDate><atom:link href="https://thedavidpage.pages.dev/tags/networking/index.xml" rel="self" type="application/rss+xml"/><item><title>The MTU 9001 Trap: Flaky Connections Over VPC Peering and VPN</title><link>https://thedavidpage.pages.dev/posts/cloud/aws/networking/mtu-9001-path-mtu-discovery-black-hole/</link><pubDate>Fri, 20 Feb 2026 09:00:00 +0700</pubDate><guid>https://thedavidpage.pages.dev/posts/cloud/aws/networking/mtu-9001-path-mtu-discovery-black-hole/</guid><description>&lt;p&gt;&lt;strong&gt;Ping works. SSH works. But the moment the app sends a large payload over VPN or cross-region peering, it just&amp;hellip; hangs. This is why.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;Hi everyone 👋&lt;/p&gt;
&lt;p&gt;This is a classic debugging trap that can burn a new DevOps engineer several days, precisely because the system never throws a clear error log.&lt;/p&gt;
&lt;h2 id="-the-confusing-symptom"&gt;😱 The confusing symptom&lt;/h2&gt;
&lt;p&gt;Two EC2 instances in different VPCs, connected over VPC peering, VPN, or Direct Connect. Ping between them responds fine. SSH works fine too. But the moment the application transfers a large file, or sends a long JSON payload over an API call on that same connection, the request hangs indefinitely until it eventually times out.&lt;/p&gt;</description></item><item><title>The Hidden Cost of Cross-AZ Data Transfer on AWS</title><link>https://thedavidpage.pages.dev/posts/cloud/aws/networking/cross-az-data-transfer-cost/</link><pubDate>Wed, 14 Jan 2026 09:00:00 +0700</pubDate><guid>https://thedavidpage.pages.dev/posts/cloud/aws/networking/cross-az-data-transfer-cost/</guid><description>&lt;p&gt;&lt;strong&gt;Multi-AZ for high availability quietly turned into a network bill bigger than the compute bill — here&amp;rsquo;s why.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;Hi everyone 👋&lt;/p&gt;
&lt;p&gt;This is one of those &amp;ldquo;hidden landmines&amp;rdquo; on AWS: things that never throw a clear error, never show up in a StackOverflow top answer, but can quietly make a system flaky or burn thousands of dollars a month. First up: cross-AZ data transfer.&lt;/p&gt;
&lt;h2 id="-the-assumption-that-gets-everyone"&gt;😱 The assumption that gets everyone&lt;/h2&gt;
&lt;p&gt;Everyone knows data transfer &lt;em&gt;out to the internet&lt;/em&gt; costs money. Far fewer people realize that &lt;strong&gt;traffic between Availability Zones inside the same Region isn&amp;rsquo;t free either&lt;/strong&gt; — a lot of us assume &amp;ldquo;it&amp;rsquo;s all internal, so it&amp;rsquo;s free.&amp;rdquo;&lt;/p&gt;</description></item></channel></rss>