<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>STUN on Yash Chudasama</title>
    <link>https://www.yashchudasama.com/tags/stun/</link>
    <description>Recent content in STUN on Yash Chudasama</description>
    <generator>Hugo</generator>
    <language>en</language>
    <copyright>Copyright © 2026, Yash Chudasama; all rights reserved.</copyright>
    <lastBuildDate>Tue, 10 Mar 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.yashchudasama.com/tags/stun/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>WebRTC Debugging: Production Problems and Fixes</title>
      <link>https://www.yashchudasama.com/blog/tech/webrtc-production-debugging/</link>
      <pubDate>Tue, 10 Mar 2026 00:00:00 +0000</pubDate>
      <guid>https://www.yashchudasama.com/blog/tech/webrtc-production-debugging/</guid>
      <description>WebRTC documentation teaches you the happy path. Production teaches you everything else.&#xA;After years of building real-time communication infrastructure, I&amp;rsquo;ve compiled the debugging scenarios that consumed the most engineering hours — the ones that don&amp;rsquo;t appear in tutorials but appear in your error logs at 3 AM.&#xA;1. The Symmetric NAT Problem What the docs say &amp;ldquo;Use STUN to discover your public IP, then use it to establish a peer connection.</description>
    </item>
  </channel>
</rss>
