<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>programming on monism.cc</title>
    <link>https://blog.monism.cc/tags/programming/</link>
    <description>Recent content in programming on monism.cc</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <lastBuildDate>Thu, 09 May 2024 00:00:00 +0800</lastBuildDate><atom:link href="https://blog.monism.cc/tags/programming/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Understanding NAT Traversal in Detail</title>
      <link>https://blog.monism.cc/posts/nat/</link>
      <pubDate>Thu, 09 May 2024 00:00:00 +0800</pubDate>
      
      <guid>https://blog.monism.cc/posts/nat/</guid>
      <description>Intro This post is a set of notes on my understanding of Tailscale&amp;rsquo;s How NAT traversal works, together with an overview of how several common NAT traversal techniques work.
NAT NAT (Network Address Translation) was introduced primarily to address the shortage of IPv4 addresses.
In simple terms, most machines use a private IP address, such as 192.168.1.2. When a device A with such an address needs to reach a device B on the public Internet, such as 8.</description>
    </item>
    
  </channel>
</rss>
