<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>Forem: Diyarbek</title>
    <description>The latest articles on Forem by Diyarbek (@rocked).</description>
    <link>https://forem.com/rocked</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3813057%2F4bfe3ead-7760-4c68-977e-2f51881bfa09.png</url>
      <title>Forem: Diyarbek</title>
      <link>https://forem.com/rocked</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://forem.com/feed/rocked"/>
    <language>en</language>
    <item>
      <title>I built Tunn - a tunneling tool in Rust (ngrok alternative)</title>
      <dc:creator>Diyarbek</dc:creator>
      <pubDate>Sun, 08 Mar 2026 15:05:43 +0000</pubDate>
      <link>https://forem.com/rocked/i-built-tunn-a-tunneling-tool-in-rust-ngrok-alternative-40b0</link>
      <guid>https://forem.com/rocked/i-built-tunn-a-tunneling-tool-in-rust-ngrok-alternative-40b0</guid>
      <description>&lt;p&gt;Hey r/rust! I've been working on Tunn, a tunneling tool that exposes your localhost to the internet. Think ngrok, but built in Rust on top of QUIC.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Why I built it:&lt;/strong&gt;&lt;br&gt;
I was using ngrok for webhook testing and got frustrated with the latency and session time limits. TCP-based tunneling felt like it could be better, so I decided to try QUIC (using quinn).&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Results:&lt;/strong&gt;&lt;br&gt;
Benchmarked against ngrok with 500 requests (keep-alive, 10 concurrent):&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Tunn: 135ms avg, 65.9 req/s&lt;/li&gt;
&lt;li&gt;ngrok: 663ms avg, 15.0 req/s&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;QUIC multiplexing makes a big difference — one connection handles all requests, no per-request TLS handshakes.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Features:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;HTTP, TCP, and UDP tunneling&lt;/li&gt;
&lt;li&gt;Built-in web request inspector (localhost:4040)&lt;/li&gt;
&lt;li&gt;QR code in terminal for quick mobile access&lt;/li&gt;
&lt;li&gt;0-RTT reconnect on network changes&lt;/li&gt;
&lt;li&gt;Single binary, no dependencies&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Tech stack:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;quinn for QUIC transport&lt;/li&gt;
&lt;li&gt;axum for the inspector web server&lt;/li&gt;
&lt;li&gt;clap for CLI&lt;/li&gt;
&lt;li&gt;tokio for async runtime&lt;/li&gt;
&lt;li&gt;rustls (no native-tls, for easy cross-compilation)&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;GitHub: &lt;a href="https://github.com/Diyarbekoralbaev/tunn" rel="noopener noreferrer"&gt;https://github.com/Diyarbekoralbaev/tunn&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Install:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;curl -s https://tunn.uz/install | bash
tunn http 3000
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Would love feedback on the architecture and any rough edges you find. The QUIC implementation was the most interesting part to build — happy to discuss the details.&lt;/p&gt;

</description>
      <category>tunnel</category>
    </item>
    <item>
      <title>I built Tunn - a QUIC-based tunneling tool in Rust (ngrok alternative)</title>
      <dc:creator>Diyarbek</dc:creator>
      <pubDate>Sun, 08 Mar 2026 15:03:32 +0000</pubDate>
      <link>https://forem.com/rocked/i-built-tunn-a-quic-based-tunneling-tool-in-rust-ngrok-alternative-4eh3</link>
      <guid>https://forem.com/rocked/i-built-tunn-a-quic-based-tunneling-tool-in-rust-ngrok-alternative-4eh3</guid>
      <description>&lt;p&gt;Hey r/rust! I've been working on Tunn, a tunneling tool that exposes your localhost to the internet. Think ngrok, but built in Rust on top of QUIC.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Why I built it:&lt;/strong&gt;&lt;br&gt;
I was using ngrok for webhook testing and got frustrated with the latency and session time limits. TCP-based tunneling felt like it could be better, so I decided to try QUIC (using quinn).&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Results:&lt;/strong&gt;&lt;br&gt;
Benchmarked against ngrok with 500 requests (keep-alive, 10 concurrent):&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Tunn: 135ms avg, 65.9 req/s&lt;/li&gt;
&lt;li&gt;ngrok: 663ms avg, 15.0 req/s&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;QUIC multiplexing makes a big difference — one connection handles all requests, no per-request TLS handshakes.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Features:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;HTTP, TCP, and UDP tunneling&lt;/li&gt;
&lt;li&gt;Built-in web request inspector (localhost:4040)&lt;/li&gt;
&lt;li&gt;QR code in terminal for quick mobile access&lt;/li&gt;
&lt;li&gt;0-RTT reconnect on network changes&lt;/li&gt;
&lt;li&gt;Single binary, no dependencies&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Tech stack:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;quinn for QUIC transport&lt;/li&gt;
&lt;li&gt;axum for the inspector web server&lt;/li&gt;
&lt;li&gt;clap for CLI&lt;/li&gt;
&lt;li&gt;tokio for async runtime&lt;/li&gt;
&lt;li&gt;rustls (no native-tls, for easy cross-compilation)&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;GitHub: &lt;a href="https://github.com/Diyarbekoralbaev/tunn" rel="noopener noreferrer"&gt;https://github.com/Diyarbekoralbaev/tunn&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Install:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;curl -s https://tunn.uz/install | bash
tunn http 3000
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Would love feedback on the architecture and any rough edges you find. The QUIC implementation was the most interesting part to build — happy to discuss the details.&lt;/p&gt;

</description>
      <category>rust</category>
    </item>
  </channel>
</rss>
