<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Nat on SANJAY REGMI</title>
    <link>https://sanjayregmi.com/tags/nat/</link>
    <description>Recent content in Nat on SANJAY REGMI</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    
    <lastBuildDate>Thu, 15 Jan 2026 16:29:04 -0800</lastBuildDate><atom:link href="https://sanjayregmi.com/tags/nat/index.xml" rel="self" type="application/rss+xml" />
    
    <item>
      <title>How to Get the Best Throughput - Both Upload and Download - From Remote Servers When Connected via Tailscale and Using Pfsense Firewall</title>
      <link>https://sanjayregmi.com/posts/how-to-get-the-best-throughput-both-upload-and-download-from-remote-servers-when-connected-via-tailscale-and-using-pfsense-firewall/</link>
      <pubDate>Thu, 15 Jan 2026 16:29:04 -0800</pubDate>
      
      <guid>https://sanjayregmi.com/posts/how-to-get-the-best-throughput-both-upload-and-download-from-remote-servers-when-connected-via-tailscale-and-using-pfsense-firewall/</guid>
      <description>&lt;p&gt;If you’ve had a VPS with Hetzner in Europe (very competitive hosting rates) and you’re a &lt;a href=&#34;https://sanjayregmi.com/tags/tailscale/&#34; &gt;Tailscale aficionado&lt;/a&gt; you’ve probably &lt;a href=&#34;https://sanjayregmi.com/posts/how-to-install-tailscale-on-freebsd/&#34; &gt;used Tailscale&lt;/a&gt; and been unhappy with upload/download speeds in kilobytes when connected via Tailscale over SSH. It turns out one reason for the low throughput is that you use &lt;a href=&#34;https://sanjayregmi.com/tags/pfsense/&#34; &gt;pfSense&lt;/a&gt; as your firewall, and it can be difficult for Tailscale to punch a hole through pfSense. As a result, it falls back to its DERP servers, which are shared resources for all Tailscale users and often have poor throughput. With that said, here’s a quick change to apply on pfSense to alleviate the problem.&lt;/p&gt;</description>
      
    </item>
    
  </channel>
</rss>
