<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Network on Blog | lddi</title>
    <link>https://blog.lddi.net/en/tags/network/</link>
    <description>Recent content in Network on Blog | lddi</description>
    <generator>Hugo</generator>
    <language>en-US</language>
    <lastBuildDate>Sat, 06 Jun 2026 14:00:00 +0800</lastBuildDate>
    <atom:link href="https://blog.lddi.net/en/tags/network/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Setting Up VLESS &#43; REALITY and VLESS &#43; WS &#43; CDN</title>
      <link>https://blog.lddi.net/en/posts/vps-vless-setup/</link>
      <pubDate>Sat, 06 Jun 2026 14:00:00 +0800</pubDate>
      <guid>https://blog.lddi.net/en/posts/vps-vless-setup/</guid>
      <description>A follow-up to the concepts post — this time we actually stand up both REALITY and WS + CDN on a single VPS, covering only the key steps and common pitfalls.</description>
    </item>
    <item>
      <title>VLESS, REALITY and CDN: Three Pieces of the Modern Proxy Puzzle</title>
      <link>https://blog.lddi.net/en/posts/net-proxy/</link>
      <pubDate>Sat, 06 Jun 2026 10:00:00 +0800</pubDate>
      <guid>https://blog.lddi.net/en/posts/net-proxy/</guid>
      <description>Starting from one core idea — evading detection rather than encryption — this post explains what VLESS, VLESS + REALITY and CDN each solve, and how to choose between them.</description>
    </item>
    <item>
      <title>Cloudflare&#39;s Three Certificate Types: Edge, Client, Origin Server</title>
      <link>https://blog.lddi.net/en/posts/cloudflare-certificates/</link>
      <pubDate>Mon, 01 Jun 2026 16:00:00 +0800</pubDate>
      <guid>https://blog.lddi.net/en/posts/cloudflare-certificates/</guid>
      <description>Using one idea — a single HTTPS connection split into two hops by Cloudflare — to explain what Edge, Origin Server and Client certificates each do.</description>
    </item>
  </channel>
</rss>
