<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Fuckgfw on Margrop Blog</title>
    <link>https://blog.margrop.net/en/tag/fuckgfw/</link>
    <description>Recent content in Fuckgfw on Margrop Blog</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-US</language>
    <lastBuildDate>Mon, 10 Jun 2024 15:26:32 +0800</lastBuildDate>
    <atom:link href="https://blog.margrop.net/en/tag/fuckgfw/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Open Specific Ports on Ubuntu 22.04 with UFW or iptables</title>
      <link>https://blog.margrop.net/en/post/ubuntu-add-port-filter-using-iptables/</link>
      <pubDate>Sun, 26 Feb 2023 20:04:53 +0800</pubDate>
      <guid>https://blog.margrop.net/en/post/ubuntu-add-port-filter-using-iptables/</guid>
      <description>&lt;h1 id=&#34;add-firewall-rules-on-ubuntu-2204&#34;&gt;Add firewall rules on Ubuntu 22.04&lt;/h1&gt;&#xA;&lt;h2 id=&#34;check-firewall-status&#34;&gt;Check firewall status&lt;/h2&gt;&#xA;&lt;pre tabindex=&#34;0&#34;&gt;&lt;code&gt;ufw status&#xA;&lt;/code&gt;&lt;/pre&gt;&lt;h2 id=&#34;open-port-22&#34;&gt;Open port 22&lt;/h2&gt;&#xA;&lt;pre tabindex=&#34;0&#34;&gt;&lt;code&gt;ufw allow 22&#xA;&lt;/code&gt;&lt;/pre&gt;&lt;h2 id=&#34;check-firewall-status-again&#34;&gt;Check firewall status again&lt;/h2&gt;&#xA;&lt;pre tabindex=&#34;0&#34;&gt;&lt;code&gt;ufw status&#xA;&lt;/code&gt;&lt;/pre&gt;</description>
    </item>
    <item>
      <title>Using Cloudflare to Build gh-proxy for GitHub Acceleration</title>
      <link>https://blog.margrop.net/en/post/cloudflare-accelerate-github-speed/</link>
      <pubDate>Mon, 10 Jun 2024 15:26:32 +0800</pubDate>
      <guid>https://blog.margrop.net/en/post/cloudflare-accelerate-github-speed/</guid>
      <description>&lt;p&gt;In previous episodes, I&amp;rsquo;ve experimented with Qinglong Panel. However, when trying to pull GitHub repositories, you may encounter network issues leading to pull failures. Regular GitHub file downloads are also extremely slow. So I used the free Cloudflare to build gh-proxy for GitHub acceleration.&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;I. Prerequisites&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;p&gt;You need to prepare a Cloudflare account and a domain name (optional) in advance. For free domains, you can refer to the previous article &amp;lsquo;&lt;a href=&#34;http://mp.weixin.qq.com/s?__biz=MzIxMjE1NDQxNA==&amp;mid=2247483945&amp;idx=1&amp;sn=abe651003c71d37c25b29cd6ea54a775&amp;chksm=974b2368a03caa7e8ccdab8d0d104076540990a643731bd60bb9c3bbb04dc81c83dba4eedad9&amp;scene=21#wechat_redirect&#34;&gt;免费申请注册eu.org二级域名&lt;/a&gt;&amp;rsquo;&lt;/p&gt;</description>
    </item>
    <item>
      <title>Using Cloudflare Workers to Solve Docker Image Pull Issues</title>
      <link>https://blog.margrop.net/en/post/cloudflare-workers-slove-docker-mirrors-blocked/</link>
      <pubDate>Mon, 10 Jun 2024 14:16:26 +0800</pubDate>
      <guid>https://blog.margrop.net/en/post/cloudflare-workers-slove-docker-mirrors-blocked/</guid>
      <description>&lt;p&gt;Due to certain reasons, Docker images cannot be pulled normally in China. The method I wrote last year for accelerating image pulls is also no longer functional. Where there&amp;rsquo;s a will, there&amp;rsquo;s a way (not really). So I&amp;rsquo;ve written a new tutorial to solve the Docker image pull issue using Cloudflare Workers.&lt;/p&gt;&#xA;&lt;p&gt;This article uses Cloudflare Workers to solve the problem of being unable to pull images. I won&amp;rsquo;t go into too much detail about Cloudflare here, and Cloudflare Workers is also a free service. If you&amp;rsquo;re not familiar with it, you can check out previous articles like &amp;ldquo;&lt;a href=&#34;http://mp.weixin.qq.com/s?__biz=MzIxMjE1NDQxNA==&amp;mid=2247484002&amp;idx=1&amp;sn=5cf3b8876df7d871774641c5f24261d7&amp;chksm=974b2323a03caa35e053659efda5e285635f83d011cadf54e7c05288f40a4df1811fcf0338ff&amp;scene=21#wechat_redirect&#34;&gt;cloudflare加快github下载&lt;/a&gt;&amp;rdquo;. &lt;strong&gt;If you don&amp;rsquo;t want to follow this guide, you can reply with &amp;ldquo;jsdc&amp;rdquo; in the background to get the public service address I&amp;rsquo;ve set up.&lt;/strong&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>Bypassing the Firewall or Setting Up a Server Farm: V2Ray Configuration with WebSocket &#43; TLS &#43; Web &#43; CDN</title>
      <link>https://blog.margrop.net/en/post/fuckgfw-v2ray-websocket-tls-web-cdn/</link>
      <pubDate>Tue, 26 Jan 2021 13:44:36 +0800</pubDate>
      <guid>https://blog.margrop.net/en/post/fuckgfw-v2ray-websocket-tls-web-cdn/</guid>
      <description>&lt;p&gt;&lt;code&gt;v2ray&lt;/code&gt; The most secure configuration currently is &lt;code&gt;WebSocket + TLS + Web + CDN&lt;/code&gt;. It uses port &lt;code&gt;443&lt;/code&gt;: direct access shows a website, but after connecting with a client it becomes a proxy tool. From the outside it looks like an electric shaver, but it is actually a hair dryer.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
