<?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>Türk Telekom, CGNAT, PPPoE, Zapret, DPI, OpenWrt, R2, Cloudflare, IPv6, Networking on Peyloride - Okan Binli</title>
    <link>https://peyloride.com/tags/t%C3%BCrk-telekom-cgnat-pppoe-zapret-dpi-openwrt-r2-cloudflare-ipv6-networking/</link>
    <description>Recent content in Türk Telekom, CGNAT, PPPoE, Zapret, DPI, OpenWrt, R2, Cloudflare, IPv6, Networking on Peyloride - Okan Binli</description>
    <generator>Hugo -- 0.147.7</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 14 Aug 2026 12:00:00 +0300</lastBuildDate>
    <atom:link href="https://peyloride.com/tags/t%C3%BCrk-telekom-cgnat-pppoe-zapret-dpi-openwrt-r2-cloudflare-ipv6-networking/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>CGNAT&#39;s Sticky IP and Türk Telekom&#39;s DPI: The Zapret Fix</title>
      <link>https://peyloride.com/posts/cgnat-locked-ip-and-turk-telekoms-dpi-the-zapret-fix/</link>
      <pubDate>Fri, 14 Aug 2026 12:00:00 +0300</pubDate>
      <guid>https://peyloride.com/posts/cgnat-locked-ip-and-turk-telekoms-dpi-the-zapret-fix/</guid>
      <description>Why you can&amp;#39;t change your public IP on Türk Telekom&amp;#39;s CGNAT, and how zapret broke the DPI block on Cloudflare R2.</description>
    </item>
  </channel>
</rss>
