<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Wan-Emulation on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/wan-emulation/</link>
    <description>Recent content in Wan-Emulation on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 08 Jun 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/wan-emulation/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted WAN Emulation &amp; Network Simulation: Comcast vs Augmented Traffic Control vs Linux tc/netem</title>
      <link>https://www.pistack.xyz/posts/2026-06-08-self-hosted-wan-emulation-comcast-atc-tc-netem/</link>
      <pubDate>Mon, 08 Jun 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-06-08-self-hosted-wan-emulation-comcast-atc-tc-netem/</guid>
      <description>&lt;h2 id=&#34;introduction&#34;&gt;Introduction&lt;/h2&gt;&#xA;&lt;p&gt;When building distributed systems, microservices, or any application that communicates over a network, one of the hardest problems to test is how your software behaves under adverse network conditions. Packet loss, latency spikes, jitter, and bandwidth constraints are everyday realities in production — but rare in your local development environment.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
