<?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>DEV Community: Maksim Lanies</title>
    <description>The latest articles on DEV Community by Maksim Lanies (@ilanies).</description>
    <link>https://dev.to/ilanies</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.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3103025%2Fb8a112d3-2e9a-48fe-93a3-fd82e6389b55.jpg</url>
      <title>DEV Community: Maksim Lanies</title>
      <link>https://dev.to/ilanies</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/ilanies"/>
    <language>en</language>
    <item>
      <title>adqproxy: a Rust reverse proxy built on Cloudflare Pingora</title>
      <dc:creator>Maksim Lanies</dc:creator>
      <pubDate>Thu, 19 Nov 2026 23:18:28 +0000</pubDate>
      <link>https://dev.to/ilanies/adqproxy-a-rust-reverse-proxy-built-on-cloudflare-pingora-n0l</link>
      <guid>https://dev.to/ilanies/adqproxy-a-rust-reverse-proxy-built-on-cloudflare-pingora-n0l</guid>
      <description>&lt;p&gt;&lt;em&gt;How Cloudflare uses Pingora, how it differs from NGINX, and how adqproxy adds site configuration, routing, and systemd installation to a Rust proxy.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;code&gt;adqproxy&lt;/code&gt; is my Rust reverse proxy built on Cloudflare Pingora. Its command-line tool is &lt;code&gt;adqp&lt;/code&gt;. I wanted to combine programmable request handling with a familiar server workflow: site configuration, configuration checks, and a systemd service.&lt;/p&gt;

&lt;p&gt;When I returned to the project, I found a problem at the boundary between those parts. The package installed and its configuration check passed, but the process exited before serving its first HTTP request. While fixing installation and routing, I tested the path from installing the package to running the service.&lt;/p&gt;

&lt;p&gt;To explain adqproxy's design, I'll start with its foundation: what Pingora is, where Cloudflare uses it, and why people compare it with NGINX.&lt;/p&gt;

&lt;h2&gt;
  
  
  What a reverse proxy does, and where Pingora fits
&lt;/h2&gt;

&lt;p&gt;A reverse proxy accepts a client request and contacts an application on the client's behalf. The application can run on another port, another server, or in a container. The proxy selects a destination and returns the application's response to the client.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Client → reverse proxy → application or backend group
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;For example, one domain can route &lt;code&gt;/api/&lt;/code&gt; to an API service and other requests to a frontend. This layer can also terminate TLS and distribute requests across application instances.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Pingora is an asynchronous, multithreaded Rust framework for building network services&lt;/strong&gt;, including HTTP proxies. Cloudflare open-sourced it in February 2024. Developers use its libraries to build applications with their own traffic-handling logic. &lt;a href="https://blog.cloudflare.com/pingora-open-source/" rel="noopener noreferrer"&gt;Pingora open-source announcement&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;The project supports HTTP/1.1, HTTP/2, TLS, connection reuse, load balancing, and backend health checks. The application built on the framework determines which features it exposes and how operators configure them. &lt;a href="https://github.com/cloudflare/pingora" rel="noopener noreferrer"&gt;Pingora repository&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  How Cloudflare uses Pingora
&lt;/h2&gt;

&lt;p&gt;In the architecture Cloudflare described, Pingora handles requests from Cloudflare's network to origin servers: the servers hosting a customer's site or application.&lt;/p&gt;

&lt;p&gt;In its 2022 engineering article, Cloudflare explained a limitation of its previous NGINX-based system. Connection pools belonged to individual worker processes, so a request could not always reuse a connection opened by another process. Pingora's architecture allowed connections to be shared across threads, reducing the need for TCP/TLS handshakes. &lt;a href="https://blog.cloudflare.com/how-we-built-pingora-the-proxy-that-connects-cloudflare-to-the-internet/" rel="noopener noreferrer"&gt;How Cloudflare built Pingora&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Why Pingora is compared with NGINX
&lt;/h2&gt;

&lt;p&gt;Their responsibilities overlap in reverse proxying: accepting an HTTP request, selecting a backend, establishing a connection, and returning a response. An application built on Pingora can compete with NGINX on that part of the request path.&lt;/p&gt;

&lt;p&gt;NGINX provides a ready-to-run web server with configuration, modules, static file serving, proxying, and load balancing. Pingora provides a foundation for developing a network service. A useful comparison therefore considers the features and operation of specific applications. &lt;a href="https://nginx.org/en/" rel="noopener noreferrer"&gt;NGINX capabilities&lt;/a&gt; · &lt;a href="https://github.com/cloudflare/pingora" rel="noopener noreferrer"&gt;Pingora's purpose&lt;/a&gt;&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Question&lt;/th&gt;
&lt;th&gt;NGINX&lt;/th&gt;
&lt;th&gt;Pingora and an application built on it&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;How do you get started?&lt;/td&gt;
&lt;td&gt;Run and configure an existing server&lt;/td&gt;
&lt;td&gt;Develop or choose an application built on the framework&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Where is behavior defined?&lt;/td&gt;
&lt;td&gt;Configuration, modules, and extensions&lt;/td&gt;
&lt;td&gt;Rust code and the application's configuration interface&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Who defines the site configuration format?&lt;/td&gt;
&lt;td&gt;NGINX&lt;/td&gt;
&lt;td&gt;The application author&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;What needs checking before adoption?&lt;/td&gt;
&lt;td&gt;Configuration and required modules&lt;/td&gt;
&lt;td&gt;Application features, configuration, installation, and upgrades&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;The ability to express custom logic in Rust is one reason Pingora interests me. If a proxy needs application data to make routing decisions or must integrate with internal services, explicit extension points are useful.&lt;/p&gt;

&lt;p&gt;For straightforward proxying of a few sites, NGINX remains a practical choice. In my project, I evaluate Pingora primarily as a foundation for a programmable proxy. This work did not include an adqproxy-versus-NGINX benchmark under an identical workload.&lt;/p&gt;

&lt;h2&gt;
  
  
  How Pingora processes a request
&lt;/h2&gt;

&lt;p&gt;The &lt;code&gt;ProxyHttp&lt;/code&gt; interface exposes stages of request processing:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;code&gt;request_filter&lt;/code&gt;: validate the request or produce a response before contacting a backend.&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;upstream_peer&lt;/code&gt;: select a server and its connection parameters.&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;upstream_request_filter&lt;/code&gt;: modify the request before forwarding it.&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;response_filter&lt;/code&gt; and &lt;code&gt;logging&lt;/code&gt;: process the response and record the result.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;This is useful when backend selection requires more than a fixed path-to-address mapping. For example, the decision might depend on request context. The stages and retry behavior are described in the &lt;a href="https://github.com/cloudflare/pingora/blob/main/docs/user_guide/phase.md" rel="noopener noreferrer"&gt;request lifecycle guide&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  How adqproxy is put together
&lt;/h2&gt;

&lt;p&gt;In adqproxy, I add site configuration and its management workflow on top of Pingora: &lt;code&gt;sites-available&lt;/code&gt;, &lt;code&gt;sites-enabled&lt;/code&gt;, configuration validation, and a systemd service. This is the interface a server administrator works with.&lt;/p&gt;

&lt;p&gt;For this update, I upgraded Pingora from 0.6.0 to 0.9.1, adapted the cache and metrics integrations, and committed &lt;code&gt;Cargo.lock&lt;/code&gt;. I then tested specific adqproxy behavior: startup without upstreams, backend selection, TLS, and upgrades over edited configuration files. &lt;a href="https://github.com/cloudflare/pingora/releases/tag/0.9.1" rel="noopener noreferrer"&gt;Pingora 0.9.1 release&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Why the default install failed
&lt;/h2&gt;

&lt;p&gt;The installer enabled a &lt;code&gt;default&lt;/code&gt; site with a simple &lt;code&gt;return 200 "OK\n";&lt;/code&gt; rule for &lt;code&gt;/health&lt;/code&gt;. The proxy can serve that response directly. During startup, however, the binary always tried to take the first load balancer from its list of upstreams. The default site had none. The two pieces only failed when I ran them together.&lt;/p&gt;

&lt;p&gt;The proxy can now start with zero upstreams. On a fresh Linux install with systemd, the installer enables the default site and the service responds at &lt;code&gt;http://127.0.0.1:8080/health&lt;/code&gt;. Upgrades preserve &lt;code&gt;proxy.yaml&lt;/code&gt;, site files, and their symlinks. If an administrator disables the default site, it stays disabled after the upgrade. &lt;a href="https://github.com/Ad-Quest/adq-pingora/pull/3" rel="noopener noreferrer"&gt;Installer changes&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  The parts I kept from the NGINX workflow
&lt;/h2&gt;

&lt;p&gt;Site files live in &lt;code&gt;/etc/adq-pingora/sites-available/&lt;/code&gt;. Running &lt;code&gt;adq-ensite&lt;/code&gt; creates a symlink in &lt;code&gt;sites-enabled/&lt;/code&gt;. For example, &lt;code&gt;/etc/adq-pingora/sites-available/demo&lt;/code&gt; can map a path to a named backend group.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight nginx"&gt;&lt;code&gt;&lt;span class="n"&gt;server&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
    &lt;span class="n"&gt;listen&lt;/span&gt; &lt;span class="mi"&gt;8080&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
    &lt;span class="n"&gt;server_name&lt;/span&gt; &lt;span class="n"&gt;demo&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;example&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;

    &lt;span class="n"&gt;location&lt;/span&gt; &lt;span class="o"&gt;/&lt;/span&gt;&lt;span class="n"&gt;api&lt;/span&gt;&lt;span class="o"&gt;/&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
        &lt;span class="n"&gt;proxy_pass&lt;/span&gt; &lt;span class="n"&gt;demo_api&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
    &lt;span class="p"&gt;}&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;

&lt;span class="n"&gt;upstream&lt;/span&gt; &lt;span class="n"&gt;demo_api&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
    &lt;span class="n"&gt;server&lt;/span&gt; &lt;span class="mf"&gt;127.0&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="mf"&gt;0.1&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="mi"&gt;3000&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;A request to &lt;code&gt;/api/&lt;/code&gt; with &lt;code&gt;Host: demo.example&lt;/code&gt; goes to &lt;code&gt;demo_api&lt;/code&gt;. Before the fix, two routes with different &lt;code&gt;proxy_pass&lt;/code&gt; targets could end up at the same backend. I ran two local HTTP servers and checked the response bodies to see which one actually handled each request. For HTTPS, &lt;code&gt;listen … ssl&lt;/code&gt; now creates a TLS listener on the configured port and loads the certificate specified in the site file.&lt;/p&gt;

&lt;p&gt;Running the config check as the service user also checks that the process can read its configuration and TLS keys. Applying a change currently requires a systemd restart, so there can be an interruption.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;sudo adq-ensite demo
sudo -u adq-pingora adqp -t &lt;span class="o"&gt;&amp;amp;&amp;amp;&lt;/span&gt; sudo systemctl restart adq-pingora
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;I used a similar approach to configuration and runtime checks when &lt;a href="https://2x2.ceo/posts/nginx-http2-security-update/" rel="noopener noreferrer"&gt;checking and updating NGINX after six CVEs&lt;/a&gt;: I verified the configuration and installed package, then checked request handling after the update.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F7u5lkekzzxs76ht46di8.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F7u5lkekzzxs76ht46di8.png" alt="Kaku terminal showing the installed NGINX package version, a successful configuration check, an active service and an HTTP/2 200 response" width="800" height="520"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;NGINX verification on vm-voly in Kaku: package version, a successful nginx -t, an active service and an HTTP/2 200 response.&lt;/em&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  What CI checks before release
&lt;/h2&gt;

&lt;p&gt;CI builds the binary from the locked dependency set, installs it on Ubuntu, starts the installed systemd service, and checks that the default &lt;code&gt;/health&lt;/code&gt; route returns &lt;code&gt;OK&lt;/code&gt;. Separate tests cover an upgrade over an edited configuration, malformed syntax, a missing upstream, routing to two distinct backends, HTTPS, and the request counter at &lt;code&gt;/metrics&lt;/code&gt;. That exercises the installation a user gets as well as the proxy itself. &lt;a href="https://github.com/Ad-Quest/adq-pingora/actions/runs/44581830970" rel="noopener noreferrer"&gt;GitHub Actions run&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F9qfu63aptsdn3qt8b3mm.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F9qfu63aptsdn3qt8b3mm.png" alt="Kaku terminal showing the successful adqproxy CI job with build, unit tests, smoke tests and systemd service startup" width="800" height="520"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;A successful adqproxy CI run: build, unit tests, smoke tests and startup of the installed systemd service.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F528gdgfzr42cb3ozolnr.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F528gdgfzr42cb3ozolnr.png" alt="Kaku terminal displaying GitHub Actions test results for proxying, metrics, installation, configuration preservation and HTTPS" width="800" height="520"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;An excerpt from the same CI log: proxying, metrics, installation, configuration preservation and HTTPS checks. Tests run in GitHub Actions; Kaku displays their log.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;The source and build instructions are already on the main branch. Publication of the &lt;code&gt;adqproxy&lt;/code&gt; npm package is still pending. &lt;a href="https://github.com/Ad-Quest/adq-pingora" rel="noopener noreferrer"&gt;Project repository&lt;/a&gt;&lt;/p&gt;

</description>
      <category>rust</category>
      <category>opensource</category>
      <category>webdev</category>
      <category>devops</category>
    </item>
    <item>
      <title>MASQUE VPN in Go: tunneling IP over QUIC like ordinary HTTPS</title>
      <dc:creator>Maksim Lanies</dc:creator>
      <pubDate>Thu, 29 Oct 2026 13:59:30 +0000</pubDate>
      <link>https://dev.to/ilanies/masque-vpn-in-go-tunneling-ip-over-quic-like-ordinary-https-3e3a</link>
      <guid>https://dev.to/ilanies/masque-vpn-in-go-tunneling-ip-over-quic-like-ordinary-https-3e3a</guid>
      <description>&lt;p&gt;Most VPNs announce themselves. WireGuard has a recognizable handshake. Many TLS tunnels still look like long-lived VPN sessions once you inspect the flow.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;MASQUE&lt;/strong&gt; takes another route: proxy arbitrary IP traffic inside HTTP/3, so the outer session looks much closer to normal QUIC/HTTPS.&lt;/p&gt;

&lt;p&gt;We published an educational implementation under CloudBridge Research:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;&lt;a href="https://github.com/cloudbridge-research/masque-vpn" rel="noopener noreferrer"&gt;github.com/cloudbridge-research/masque-vpn&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;MIT · ~94★ · Go · CONNECT-IP over QUIC/HTTP3 · REST API · Prometheus · student docs in EN/RU/ZH&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;Lab / research code. Great for protocol study and teaching — not a hardened appliance with an SLA.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;It builds on the original work by &lt;a href="https://github.com/iselt/masque-vpn" rel="noopener noreferrer"&gt;&lt;code&gt;iselt/masque-vpn&lt;/code&gt;&lt;/a&gt;. CloudBridge Research forked and extended it into a fuller educational platform (custom CONNECT-IP path, API, tests, monitoring, labs).&lt;/p&gt;

&lt;h2&gt;
  
  
  Why CONNECT-IP?
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://datatracker.ietf.org/doc/html/rfc9484" rel="noopener noreferrer"&gt;RFC 9484&lt;/a&gt; defines &lt;strong&gt;CONNECT-IP&lt;/strong&gt;: tunnel IP packets through an HTTP connection. Over HTTP/3 that means:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Client opens a QUIC connection to the proxy.&lt;/li&gt;
&lt;li&gt;Client sends a MASQUE CONNECT-IP request.&lt;/li&gt;
&lt;li&gt;After success, IP packets ride QUIC streams / datagrams instead of a dedicated VPN UDP port with its own fingerprint.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Useful when you want to:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;learn QUIC / HTTP/3 beyond “JSON API over UDP”&lt;/li&gt;
&lt;li&gt;research DPI-resistant transports that blend with HTTPS&lt;/li&gt;
&lt;li&gt;teach how modern proxies move L3 traffic&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Inside CloudBridge this sits next to QUIC, WireGuard, WebRTC and AmneziaWG as one mesh transport option — so we needed a readable reference, not only a black box.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fr7eimz8ywnhq164t3dmh.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fr7eimz8ywnhq164t3dmh.png" alt="MASQUE VPN data-flow architecture" width="800" height="278"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  What’s in the repo
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Path&lt;/th&gt;
&lt;th&gt;Role&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;vpn_server/&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;CONNECT-IP handler, IP pool, optional TUN, metrics&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;vpn_client/&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;QUIC client that tunnels packets&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;REST API &lt;code&gt;:8080&lt;/code&gt;
&lt;/td&gt;
&lt;td&gt;health, status, clients, stats, config, logs&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;common/&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;custom MASQUE CONNECT-IP helpers&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;admin_webui/&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;admin UI&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;
&lt;code&gt;monitoring/&lt;/code&gt; + &lt;code&gt;grafana/&lt;/code&gt;
&lt;/td&gt;
&lt;td&gt;observability stack&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;docs/&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;architecture, API, student guide&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;tests/&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;unit / integration / load&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;docker-compose.yml&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;containerized bring-up&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;Also: mutual TLS, automatic client IP allocation, Makefile helpers, and functional protocol smoke tests.&lt;/p&gt;

&lt;p&gt;Stack: &lt;strong&gt;Go&lt;/strong&gt;, &lt;a href="https://github.com/quic-go/quic-go" rel="noopener noreferrer"&gt;quic-go&lt;/a&gt;, Gin, Zap, Prometheus client.&lt;/p&gt;

&lt;h2&gt;
  
  
  Local quick start
&lt;/h2&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;git clone https://github.com/cloudbridge-research/masque-vpn.git
&lt;span class="nb"&gt;cd &lt;/span&gt;masque-vpn

&lt;span class="nb"&gt;cd &lt;/span&gt;vpn_server &lt;span class="o"&gt;&amp;amp;&amp;amp;&lt;/span&gt; go build &lt;span class="nt"&gt;-o&lt;/span&gt; vpn-server &lt;span class="nb"&gt;.&lt;/span&gt;
&lt;span class="nb"&gt;cd&lt;/span&gt; ../vpn_client &lt;span class="o"&gt;&amp;amp;&amp;amp;&lt;/span&gt; go build &lt;span class="nt"&gt;-o&lt;/span&gt; vpn-client &lt;span class="nb"&gt;.&lt;/span&gt;

&lt;span class="nb"&gt;cd&lt;/span&gt; ../cert &lt;span class="o"&gt;&amp;amp;&amp;amp;&lt;/span&gt; ./generate-test-certs.sh   &lt;span class="c"&gt;# or generate-certs.ps1 on Windows&lt;/span&gt;

&lt;span class="nb"&gt;cd&lt;/span&gt; ../vpn_server
./vpn-server &lt;span class="nt"&gt;-c&lt;/span&gt; config.server.local.toml
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Local defaults:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;MASQUE / QUIC → &lt;code&gt;127.0.0.1:4433&lt;/code&gt;
&lt;/li&gt;
&lt;li&gt;REST API → &lt;code&gt;127.0.0.1:8080&lt;/code&gt;
&lt;/li&gt;
&lt;/ul&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;curl http://127.0.0.1:8080/health
curl http://127.0.0.1:8080/api/v1/status
curl http://127.0.0.1:8080/api/v1/clients
curl http://127.0.0.1:8080/metrics
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Point &lt;code&gt;vpn_client&lt;/code&gt; at the same address and start it. For a protocol-level check:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;go run test_masque_connection.go
&lt;span class="c"&gt;# or the full local suite&lt;/span&gt;
./scripts/test-local.sh
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Local server config keeps TUN empty so you can study MASQUE without fighting OS routing on day one:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight toml"&gt;&lt;code&gt;&lt;span class="n"&gt;listen_addr&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s"&gt;"127.0.0.1:4433"&lt;/span&gt;
&lt;span class="n"&gt;assign_cidr&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s"&gt;"10.0.0.0/24"&lt;/span&gt;
&lt;span class="n"&gt;tun_name&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s"&gt;""&lt;/span&gt;
&lt;span class="n"&gt;log_level&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s"&gt;"debug"&lt;/span&gt;

&lt;span class="k"&gt;[&lt;/span&gt;&lt;span class="n"&gt;api_server&lt;/span&gt;&lt;span class="k"&gt;]&lt;/span&gt;
&lt;span class="n"&gt;listen_addr&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s"&gt;"127.0.0.1:8080"&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h2&gt;
  
  
  Architecture notes
&lt;/h2&gt;

&lt;p&gt;Interesting files if you open the tree:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;code&gt;common/masque_connectip.go&lt;/code&gt; — MASQUE client side&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;common/masque_proxy.go&lt;/code&gt; — IP packet proxy helpers&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;vpn_server/internal/server/masque_handler.go&lt;/code&gt; — CONNECT-IP handler&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;packet_processor.go&lt;/code&gt; — TUN path when enabled&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;api_server.go&lt;/code&gt; / &lt;code&gt;metrics.go&lt;/code&gt; / &lt;code&gt;tls_config.go&lt;/code&gt; — control plane pieces&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Design choices we care about for teaching:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;custom MASQUE layer in-tree&lt;/strong&gt; (easy to step through)&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;QUIC streams&lt;/strong&gt; for control / reliable bits&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;QUIC datagrams&lt;/strong&gt; for packet carriage&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;optional TUN&lt;/strong&gt; — protocol testing without admin rights&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;REST + Prometheus&lt;/strong&gt; beside the data plane&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Specs in play: RFC 9484 (CONNECT-IP), RFC 9000 (QUIC), RFC 9114 (HTTP/3).&lt;/p&gt;

&lt;h2&gt;
  
  
  Security as shipped
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;mutual TLS between client and server&lt;/li&gt;
&lt;li&gt;per-client IP from the configured pool&lt;/li&gt;
&lt;li&gt;validation of MASQUE headers / parameters&lt;/li&gt;
&lt;li&gt;self-signed CA scripts for labs — swap to real certs before any serious deploy&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;If you enable TUN for a fuller tunnel, treat firewalling and certificate distribution as first-class work.&lt;/p&gt;

&lt;h2&gt;
  
  
  Who this is for
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;students and researchers studying QUIC / HTTP/3 / MASQUE&lt;/li&gt;
&lt;li&gt;people comparing VPN fingerprints and multi-transport meshes&lt;/li&gt;
&lt;li&gt;educators who want labs with a real Go codebase&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The repo ships a &lt;a href="https://github.com/cloudbridge-research/masque-vpn/blob/main/docs/development/student-guide.md" rel="noopener noreferrer"&gt;student guide&lt;/a&gt; with deployment, performance, protocol deep-dive and impaired-network exercises.&lt;/p&gt;

&lt;h2&gt;
  
  
  Links
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Repo: &lt;a href="https://github.com/cloudbridge-research/masque-vpn" rel="noopener noreferrer"&gt;cloudbridge-research/masque-vpn&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;Upstream base: &lt;a href="https://github.com/iselt/masque-vpn" rel="noopener noreferrer"&gt;iselt/masque-vpn&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;Research: &lt;a href="https://cloudbridge-research.ru/" rel="noopener noreferrer"&gt;cloudbridge-research.ru&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;Spec: &lt;a href="https://datatracker.ietf.org/doc/html/rfc9484" rel="noopener noreferrer"&gt;RFC 9484&lt;/a&gt;
&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Issues and lab write-ups welcome — especially anything that sharpens the student docs.&lt;/p&gt;

</description>
      <category>go</category>
      <category>networking</category>
      <category>quic</category>
      <category>opensource</category>
    </item>
    <item>
      <title>Remote office access without a public IP or a VPN</title>
      <dc:creator>Maksim Lanies</dc:creator>
      <pubDate>Thu, 29 Oct 2026 13:43:36 +0000</pubDate>
      <link>https://dev.to/ilanies/remote-office-access-without-a-public-ip-or-a-vpn-5b7b</link>
      <guid>https://dev.to/ilanies/remote-office-access-without-a-public-ip-or-a-vpn-5b7b</guid>
      <description>&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fmouzmbsd0iys1sf7x4jl.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fmouzmbsd0iys1sf7x4jl.png" alt="Landing hero of 2GC Tunnel" width="800" height="414"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Opening RDP or SSH to a machine at the office usually means a public IP and open ports, a company-wide VPN, or a pile of jump hosts.&lt;/p&gt;

&lt;p&gt;We wanted something narrower: &lt;strong&gt;access to a service, not to the whole network&lt;/strong&gt; — with roles, an audit trail, and a way to invite an external contractor without handing them the connector token.&lt;/p&gt;

&lt;p&gt;That product is &lt;strong&gt;&lt;a href="https://2gc.dev" rel="noopener noreferrer"&gt;2GC Tunnel&lt;/a&gt;&lt;/strong&gt; (CloudBridge).&lt;/p&gt;

&lt;h2&gt;
  
  
  The problem
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Port forwarding never stays temporary.&lt;/li&gt;
&lt;li&gt;A full VPN is overkill when someone only needs one box over RDP.&lt;/li&gt;
&lt;li&gt;Sharing access with a service partner often means sharing the tunnel token — which is full control of that tunnel.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Goals:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;No inbound ports on the customer network.&lt;/li&gt;
&lt;li&gt;Per-server grants (&lt;code&gt;view&lt;/code&gt; / &lt;code&gt;manage&lt;/code&gt;), not “everyone on the VPN”.&lt;/li&gt;
&lt;li&gt;Contractors as a &lt;strong&gt;separate organization&lt;/strong&gt;, view-only on selected servers.&lt;/li&gt;
&lt;li&gt;A desktop app that connects in one click after sign-in.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  What users see
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Dashboard.&lt;/strong&gt; Create a server — Cloudflare Tunnel and DNS are created for you. Add RDP, SSH, gRPC or HTTP; each service gets a hostname like &lt;code&gt;rdp-office.your-domain&lt;/code&gt;. Install &lt;code&gt;cloudflared&lt;/code&gt; once with the connector token from the UI.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F15psjl75asqfn8v4qx3d.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F15psjl75asqfn8v4qx3d.png" alt="2GC Dashboard" width="800" height="414"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Access.&lt;/strong&gt; Owners and admins invite members, use groups, and grant &lt;code&gt;view&lt;/code&gt; or &lt;code&gt;manage&lt;/code&gt; per server. A server you cannot see returns 404.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Contractors.&lt;/strong&gt; An external company is its own org. Both sides confirm the link; you open specific servers for &lt;strong&gt;view only&lt;/strong&gt; — no connector token, no admin of your org.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Desktop app.&lt;/strong&gt; Sign in (Clerk in the browser, or a personal access token). Pick a server, press Connect — Remote Desktop or a terminal opens against a local forward. Tokens live in the OS keychain; only a hash is stored on the server.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fyljdc0nj3m9fy03ztipw.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fyljdc0nj3m9fy03ztipw.png" alt="Desktop app login" width="800" height="995"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fe4kaho1dks1heifhg6c7.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fe4kaho1dks1heifhg6c7.png" alt="Desktop app servers" width="800" height="995"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Architecture
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Layer&lt;/th&gt;
&lt;th&gt;Choice&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Edge app&lt;/td&gt;
&lt;td&gt;Cloudflare Worker, TypeScript, server-rendered HTML&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Data&lt;/td&gt;
&lt;td&gt;D1: orgs, users, groups, servers, services, grants, API tokens&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Auth&lt;/td&gt;
&lt;td&gt;Clerk session; Worker verifies JWT locally&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Tunnels / DNS / Access&lt;/td&gt;
&lt;td&gt;Cloudflare REST API&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Desktop&lt;/td&gt;
&lt;td&gt;Tauri 2 (React + Rust), personal tokens&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Secrets&lt;/td&gt;
&lt;td&gt;Cloudflare Secrets Store&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;Deleting a server tears down Access apps (if any), DNS, and the tunnel, then the D1 row. If Cloudflare fails mid-delete, we keep the row so you can retry.&lt;/p&gt;

&lt;p&gt;Desktop Clerk sign-in uses a loopback callback: confirm in the browser, token goes only to &lt;code&gt;127.0.0.1&lt;/code&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  Security choices
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Outgoing only&lt;/strong&gt; — &lt;code&gt;cloudflared&lt;/code&gt; dials out; no inbound holes for the world.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Optional Cloudflare Access&lt;/strong&gt; in front of SSH/RDP.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;&lt;code&gt;manage&lt;/code&gt; includes the connector token&lt;/strong&gt; — treat it like root for that tunnel.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;CSRF&lt;/strong&gt; on every state-changing POST; CSP without inline scripts in the cabinet.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;API tokens&lt;/strong&gt; shown once, stored as SHA-256, recent re-auth to mint a new one.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;This is not a full Zero Trust program by itself. It is tunnels + tenancy + grants + a client.&lt;/p&gt;

&lt;h2&gt;
  
  
  What’s next: Zero Trust IdPs
&lt;/h2&gt;

&lt;p&gt;Today cabinet auth is Clerk; Access in front of SSH/RDP is optional. Next we make &lt;strong&gt;Cloudflare Zero Trust / Access&lt;/strong&gt; a first-class gate so each RDP/SSH connection authenticates with an IdP you already use.&lt;/p&gt;

&lt;p&gt;Planned providers (Cloudflare Access IdPs):&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Microsoft Entra ID (Azure AD)&lt;/li&gt;
&lt;li&gt;Okta, Google, GitHub, OneLogin, PingOne, Centrify&lt;/li&gt;
&lt;li&gt;LinkedIn, Facebook, Yandex&lt;/li&gt;
&lt;li&gt;OIDC and SAML&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Also: signed macOS/Windows builds, Access defaults for new servers, contractor UX.&lt;/p&gt;

&lt;p&gt;If you try this with a real contractor org, tell us where the model breaks — that is the part we care about most.&lt;/p&gt;

&lt;p&gt;Product: &lt;a href="https://2gc.dev" rel="noopener noreferrer"&gt;https://2gc.dev&lt;/a&gt;&lt;/p&gt;

</description>
      <category>cloudflare</category>
      <category>security</category>
      <category>typescript</category>
      <category>showdev</category>
    </item>
    <item>
      <title>Stop Mixing Up Your RDP Sessions: Auto-Label Remote Desktop Windows</title>
      <dc:creator>Maksim Lanies</dc:creator>
      <pubDate>Fri, 12 Dec 2025 07:57:46 +0000</pubDate>
      <link>https://dev.to/ilanies/stop-mixing-up-your-rdp-sessions-auto-label-remote-desktop-windows-3mop</link>
      <guid>https://dev.to/ilanies/stop-mixing-up-your-rdp-sessions-auto-label-remote-desktop-windows-3mop</guid>
      <description>&lt;h2&gt;
  
  
  The Problem Every SysAdmin Knows Too Well
&lt;/h2&gt;

&lt;p&gt;You have 8 Remote Desktop windows open. One is &lt;strong&gt;PROD-DB&lt;/strong&gt;, one is &lt;strong&gt;TEST-APP&lt;/strong&gt;, another is your local dev box. They all look identical. You need to restart a service... and you click the wrong window.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Production is down.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Sound familiar? The native Windows MSTSC client doesn't give you visual cues. Sure, you can hover over the taskbar to see the hostname, but when you're moving fast, mistakes happen.&lt;/p&gt;

&lt;h2&gt;
  
  
  The "Old School" Workaround (And Why It Sucks)
&lt;/h2&gt;

&lt;p&gt;Most admins resort to:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Editing the remote machine's hostname&lt;/strong&gt; to include &lt;code&gt;[PROD]&lt;/code&gt; or &lt;code&gt;[TEST]&lt;/code&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Using third-party RDP managers&lt;/strong&gt; like mRemoteNG or RD Tabs&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Just being really, really careful&lt;/strong&gt; (spoiler: doesn't work)&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;But what if you could keep using the &lt;strong&gt;native MSTSC&lt;/strong&gt; client and still get instant visual feedback?&lt;/p&gt;




&lt;h2&gt;
  
  
  Introducing: RDP Title Master
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;RDP Title Master&lt;/strong&gt; is a tiny background utility that:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Monitors all your RDP windows in real-time&lt;/li&gt;
&lt;li&gt;Matches window titles against your custom rules (IP addresses, hostnames)&lt;/li&gt;
&lt;li&gt;Overlays a &lt;strong&gt;color-coded badge&lt;/strong&gt; directly on the MSTSC toolbar&lt;/li&gt;
&lt;/ul&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Note:&lt;/strong&gt; I'd love to show you a screenshot, but ironically, I switched to macOS right after building this tool! If you try it out, please share a screenshot in the comments — I'd genuinely love to see it in action. 😅&lt;/p&gt;
&lt;/blockquote&gt;

&lt;h3&gt;
  
  
  Example Config (&lt;code&gt;settings.json&lt;/code&gt;)
&lt;/h3&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight json"&gt;&lt;code&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="w"&gt;
  &lt;/span&gt;&lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="w"&gt;
    &lt;/span&gt;&lt;span class="nl"&gt;"Pattern"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"prod"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt;
    &lt;/span&gt;&lt;span class="nl"&gt;"Label"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"🔥 PRODUCTION"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt;
    &lt;/span&gt;&lt;span class="nl"&gt;"ColorHex"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"#e74c3c"&lt;/span&gt;&lt;span class="w"&gt;
  &lt;/span&gt;&lt;span class="p"&gt;},&lt;/span&gt;&lt;span class="w"&gt;
  &lt;/span&gt;&lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="w"&gt;
    &lt;/span&gt;&lt;span class="nl"&gt;"Pattern"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"192.168"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt;
    &lt;/span&gt;&lt;span class="nl"&gt;"Label"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"🏠 LOCAL"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt;
    &lt;/span&gt;&lt;span class="nl"&gt;"ColorHex"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"#2ecc71"&lt;/span&gt;&lt;span class="w"&gt;
  &lt;/span&gt;&lt;span class="p"&gt;},&lt;/span&gt;&lt;span class="w"&gt;
  &lt;/span&gt;&lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="w"&gt;
    &lt;/span&gt;&lt;span class="nl"&gt;"Pattern"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"test"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt;
    &lt;/span&gt;&lt;span class="nl"&gt;"Label"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"🧪 TEST"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt;
    &lt;/span&gt;&lt;span class="nl"&gt;"ColorHex"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"#3498db"&lt;/span&gt;&lt;span class="w"&gt;
  &lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="w"&gt;
&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;&lt;span class="w"&gt;
&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;When you connect to &lt;code&gt;prod-db-01.company.com&lt;/code&gt;, the toolbar instantly shows a &lt;strong&gt;red badge&lt;/strong&gt; saying "PRODUCTION". No more guessing.&lt;/p&gt;




&lt;h2&gt;
  
  
  How It Works (Technical Deep Dive)
&lt;/h2&gt;

&lt;h3&gt;
  
  
  1. Window Detection
&lt;/h3&gt;

&lt;p&gt;The tool uses &lt;code&gt;EnumWindows&lt;/code&gt; to scan all top-level windows, looking for the RDP window class:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight csharp"&gt;&lt;code&gt;&lt;span class="k"&gt;private&lt;/span&gt; &lt;span class="k"&gt;static&lt;/span&gt; &lt;span class="kt"&gt;bool&lt;/span&gt; &lt;span class="nf"&gt;IsRdpWindow&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;IntPtr&lt;/span&gt; &lt;span class="n"&gt;hwnd&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;span class="p"&gt;{&lt;/span&gt;
    &lt;span class="kt"&gt;string&lt;/span&gt; &lt;span class="n"&gt;className&lt;/span&gt; &lt;span class="p"&gt;=&lt;/span&gt; &lt;span class="nf"&gt;GetClassName&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;hwnd&lt;/span&gt;&lt;span class="p"&gt;);&lt;/span&gt;
    &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="n"&gt;className&lt;/span&gt; &lt;span class="p"&gt;==&lt;/span&gt; &lt;span class="s"&gt;"TscShellContainerClass"&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h3&gt;
  
  
  2. Title Matching
&lt;/h3&gt;

&lt;p&gt;Once an RDP window is found, we grab its title (which usually contains the hostname or IP):&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight csharp"&gt;&lt;code&gt;&lt;span class="kt"&gt;string&lt;/span&gt; &lt;span class="n"&gt;title&lt;/span&gt; &lt;span class="p"&gt;=&lt;/span&gt; &lt;span class="nf"&gt;GetWindowTitle&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;hwnd&lt;/span&gt;&lt;span class="p"&gt;);&lt;/span&gt;
&lt;span class="kt"&gt;var&lt;/span&gt; &lt;span class="n"&gt;rule&lt;/span&gt; &lt;span class="p"&gt;=&lt;/span&gt; &lt;span class="n"&gt;_configs&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;FirstOrDefault&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;c&lt;/span&gt; &lt;span class="p"&gt;=&amp;gt;&lt;/span&gt; 
    &lt;span class="n"&gt;title&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;Contains&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;c&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;Pattern&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;StringComparison&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;OrdinalIgnoreCase&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;span class="p"&gt;);&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h3&gt;
  
  
  3. GDI+ Overlay
&lt;/h3&gt;

&lt;p&gt;We create a transparent bitmap with &lt;strong&gt;anti-aliased text&lt;/strong&gt; and a &lt;strong&gt;rounded badge background&lt;/strong&gt;, then apply it using &lt;code&gt;UpdateLayeredWindow&lt;/code&gt;:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight csharp"&gt;&lt;code&gt;&lt;span class="k"&gt;using&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;Graphics&lt;/span&gt; &lt;span class="n"&gt;g&lt;/span&gt; &lt;span class="p"&gt;=&lt;/span&gt; &lt;span class="n"&gt;Graphics&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;FromImage&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;bmp&lt;/span&gt;&lt;span class="p"&gt;))&lt;/span&gt;
&lt;span class="p"&gt;{&lt;/span&gt;
    &lt;span class="n"&gt;g&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;SmoothingMode&lt;/span&gt; &lt;span class="p"&gt;=&lt;/span&gt; &lt;span class="n"&gt;SmoothingMode&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;AntiAlias&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
    &lt;span class="n"&gt;g&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;TextRenderingHint&lt;/span&gt; &lt;span class="p"&gt;=&lt;/span&gt; &lt;span class="n"&gt;TextRenderingHint&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;AntiAliasGridFit&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;

    &lt;span class="c1"&gt;// Draw rounded rectangle badge&lt;/span&gt;
    &lt;span class="nf"&gt;FillRoundedRectangle&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;g&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;bgBrush&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;badgeRect&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="m"&gt;10&lt;/span&gt;&lt;span class="p"&gt;);&lt;/span&gt;

    &lt;span class="c1"&gt;// Draw text on top&lt;/span&gt;
    &lt;span class="n"&gt;g&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;DrawString&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;text&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;font&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;textBrush&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;x&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;y&lt;/span&gt;&lt;span class="p"&gt;);&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h3&gt;
  
  
  4. Daemon Mode
&lt;/h3&gt;

&lt;p&gt;The app runs in an infinite loop (every 3 seconds), checking for new RDP windows. This means you can start it once in the morning and forget about it.&lt;/p&gt;




&lt;h2&gt;
  
  
  Why C# and Not Python/PowerShell?
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Short answer:&lt;/strong&gt; Performance and distribution.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Single .exe&lt;/strong&gt;: No runtime dependencies. Just download and run.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;GDI+ Quality&lt;/strong&gt;: Native access to Windows graphics APIs for smooth rendering.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Size&lt;/strong&gt;: With trimming enabled, the final binary is ~50MB (self-contained .NET 8).&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The original prototype was in Python (still available in the repo's &lt;code&gt;legacy_python/&lt;/code&gt; folder), but C# made it production-ready.&lt;/p&gt;




&lt;h2&gt;
  
  
  Installation &amp;amp; Usage
&lt;/h2&gt;

&lt;h3&gt;
  
  
  Quick Start
&lt;/h3&gt;

&lt;ol&gt;
&lt;li&gt;Download the latest release from &lt;a href="https://github.com/mlanies/mstsc_title_bar/releases" rel="noopener noreferrer"&gt;GitHub&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;Edit &lt;code&gt;settings.json&lt;/code&gt; with your server patterns&lt;/li&gt;
&lt;li&gt;Run &lt;code&gt;MstscTitleBar.exe&lt;/code&gt;
&lt;/li&gt;
&lt;li&gt;Open any RDP session and watch the magic happen&lt;/li&gt;
&lt;/ol&gt;

&lt;h3&gt;
  
  
  Building from Source
&lt;/h3&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;git clone https://github.com/mlanies/mstsc_title_bar.git
&lt;span class="nb"&gt;cd &lt;/span&gt;mstsc_title_bar/MstscTitleBar
dotnet run
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;To create a portable executable:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;dotnet publish &lt;span class="nt"&gt;-c&lt;/span&gt; Release &lt;span class="nt"&gt;-r&lt;/span&gt; win-x64 &lt;span class="nt"&gt;--self-contained&lt;/span&gt; &lt;span class="nt"&gt;-p&lt;/span&gt;:PublishSingleFile&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="nb"&gt;true&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;






&lt;h2&gt;
  
  
  Real-World Use Cases
&lt;/h2&gt;

&lt;h3&gt;
  
  
  1. Multi-Environment Management
&lt;/h3&gt;

&lt;p&gt;If you manage DEV/STAGE/PROD environments, color-code them:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;🔴 Red = Production (danger zone)&lt;/li&gt;
&lt;li&gt;🟡 Yellow = Staging (proceed with caution)&lt;/li&gt;
&lt;li&gt;🟢 Green = Dev (break things freely)&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  2. Client Segregation
&lt;/h3&gt;

&lt;p&gt;Consultants managing multiple clients can use patterns like:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight json"&gt;&lt;code&gt;&lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nl"&gt;"Pattern"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"client-a"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nl"&gt;"Label"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"Client A"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nl"&gt;"ColorHex"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"#9b59b6"&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="w"&gt;
&lt;/span&gt;&lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nl"&gt;"Pattern"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"client-b"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nl"&gt;"Label"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"Client B"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nl"&gt;"ColorHex"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"#f39c12"&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="w"&gt;
&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h3&gt;
  
  
  3. Datacenter Identification
&lt;/h3&gt;

&lt;p&gt;Label servers by location:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight json"&gt;&lt;code&gt;&lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nl"&gt;"Pattern"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"us-east"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nl"&gt;"Label"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"🇺🇸 Virginia"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nl"&gt;"ColorHex"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"#3498db"&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="w"&gt;
&lt;/span&gt;&lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nl"&gt;"Pattern"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"eu-west"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nl"&gt;"Label"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"🇪🇺 Ireland"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nl"&gt;"ColorHex"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"#2ecc71"&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="w"&gt;
&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;






&lt;h2&gt;
  
  
  Known Limitations
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Windowed Mode Only&lt;/strong&gt;: Full-screen RDP hides the toolbar (by design).&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Windows 10/11&lt;/strong&gt;: Uses WinAPI calls specific to modern Windows.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Refresh Delay&lt;/strong&gt;: 3-second polling interval (configurable in code).&lt;/li&gt;
&lt;/ul&gt;




&lt;p&gt;Want to contribute? PRs welcome!&lt;/p&gt;




&lt;h2&gt;
  
  
  Conclusion
&lt;/h2&gt;

&lt;p&gt;If you've ever typed &lt;code&gt;rm -rf /&lt;/code&gt; in the wrong terminal or restarted the wrong server, you know the value of visual cues. &lt;strong&gt;RDP Title Master&lt;/strong&gt; is a simple, zero-configuration tool that makes your daily workflow safer.&lt;/p&gt;

&lt;p&gt;Try it out and let me know what you think in the comments!&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;GitHub:&lt;/strong&gt; &lt;a href="https://github.com/mlanies/mstsc_title_bar" rel="noopener noreferrer"&gt;https://github.com/mlanies/mstsc_title_bar&lt;/a&gt;  &lt;/p&gt;




&lt;p&gt;&lt;em&gt;Have you built tools to prevent "production accidents"? Share your stories below!&lt;/em&gt;&lt;/p&gt;

</description>
      <category>windows</category>
      <category>sysadmin</category>
      <category>devops</category>
      <category>csharp</category>
    </item>
    <item>
      <title>Quic-test: an open tool for testing QUIC, BBRv3, and FEC under real-world network conditions</title>
      <dc:creator>Maksim Lanies</dc:creator>
      <pubDate>Thu, 11 Dec 2025 19:05:53 +0000</pubDate>
      <link>https://dev.to/cloudbridge/quic-test-an-open-tool-for-testing-quic-bbrv3-and-fec-under-real-world-network-conditions-2791</link>
      <guid>https://dev.to/cloudbridge/quic-test-an-open-tool-for-testing-quic-bbrv3-and-fec-under-real-world-network-conditions-2791</guid>
      <description>&lt;p&gt;&lt;em&gt;This article was prepared as part of the CloudBridge Research project focused on optimizing network protocols (BBRv3, MASQUE, FEC, QUIC).&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Project:&lt;/strong&gt; &lt;a href="https://github.com/cloudbridge-research/quic-test" rel="noopener noreferrer"&gt;github.com/cloudbridge-research/quic-test&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;&lt;a href="https://github.com/user-attachments/assets/b3124696-1ab8-48e3-8b04-1cec3881c3a4" rel="noopener noreferrer"&gt;Video demo of quic-test&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  &lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fdial92u6kqjijvk9hwwn.jpg" alt="Screenshot of interface" width="800" height="543"&gt;
&lt;/h2&gt;

&lt;h2&gt;
  
  
  Why we built this
&lt;/h2&gt;

&lt;p&gt;When we began studying the behavior of QUIC, BBRv3, and Forward Error Correction in real networks — from Wi-Fi to mobile networks and regional backbones — we ran into a simple problem: there were almost &lt;strong&gt;no tools capable of accurately reproducing real-world network conditions&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;You can use iperf3, but it’s about TCP and basic UDP. You can take standalone QUIC libraries, but they lack visualization and load generation. You can write custom simulators, but they do not reflect real channel behavior. Want to test how BBRv3 performs between Moscow and Novosibirsk? Please: find three servers across different datacenters, configure netem, manually collect metrics and &lt;em&gt;hope&lt;/em&gt; results will be reproducible.&lt;/p&gt;

&lt;p&gt;There was no comprehensive QUIC tester with charts, channel profiles, FEC, BBRv3 support, TUI, and Prometheus metrics.&lt;br&gt;
So we built &lt;strong&gt;quic-test&lt;/strong&gt; — an open tool we use inside CloudBridge Research for all experiments. And now we share it with the community, universities, and engineers.&lt;/p&gt;


&lt;h2&gt;
  
  
  What is quic-test
&lt;/h2&gt;

&lt;p&gt;A fully open laboratory environment for analyzing the behavior of QUIC, BBRv3, and FEC in real networks.&lt;br&gt;
Not a simulator, but a real engineering instrument — all our research is based on measurements collected with it.&lt;/p&gt;
&lt;h3&gt;
  
  
  Who quic-test is for
&lt;/h3&gt;

&lt;p&gt;&lt;strong&gt;Network engineers&lt;/strong&gt; — compare TCP/QUIC/BBRv3 in your own networks and understand where QUIC provides real benefits.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;SRE and DevOps teams&lt;/strong&gt; — test service behavior under packet loss and high RTT, prepare for production issues before they appear.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Educators and students&lt;/strong&gt; — run modern labs on transport protocols with real metrics and visualization.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Researchers&lt;/strong&gt; — gather datasets for ML routing models, publish reproducible results.&lt;/p&gt;
&lt;h3&gt;
  
  
  Key capabilities
&lt;/h3&gt;

&lt;p&gt;&lt;strong&gt;Protocols:&lt;/strong&gt; QUIC (RFC 9000), HTTP/3, 0-RTT resumption.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Congestion Control:&lt;/strong&gt; BBRv2 (stable), BBRv3 (experimental), CUBIC, Reno.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Forward Error Correction:&lt;/strong&gt; XOR-FEC (working), RS-FEC (in development).&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Network profiles:&lt;/strong&gt; mobile (4G/LTE), Wi-Fi, lossy (3–5% loss), high-latency (regional routes).&lt;br&gt;
All profiles are based on real measurements from our CloudBridge Edge PoPs.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Metrics:&lt;/strong&gt; Prometheus, Grafana, TUI visualization (&lt;strong&gt;quic-bottom&lt;/strong&gt; in Rust).&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Comparison:&lt;/strong&gt; TCP vs QUIC under identical conditions.&lt;/p&gt;


&lt;h2&gt;
  
  
  Quick Start
&lt;/h2&gt;
&lt;h3&gt;
  
  
  Docker
&lt;/h3&gt;

&lt;p&gt;The simplest way to start is with ready Docker images:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;&lt;span class="c"&gt;# Run client (performance test)&lt;/span&gt;
docker run mlanies/quic-test:latest &lt;span class="nt"&gt;--mode&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;client &lt;span class="nt"&gt;--server&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;demo.quic.tech:4433

&lt;span class="c"&gt;# Run server&lt;/span&gt;
docker run &lt;span class="nt"&gt;-p&lt;/span&gt; 4433:4433/udp mlanies/quic-test:latest &lt;span class="nt"&gt;--mode&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;server
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h3&gt;
  
  
  Build from source
&lt;/h3&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;git clone https://github.com/twogc/quic-test
&lt;span class="nb"&gt;cd &lt;/span&gt;quic-test

&lt;span class="c"&gt;# Build FEC library (requires clang)&lt;/span&gt;
&lt;span class="nb"&gt;cd &lt;/span&gt;internal/fec &lt;span class="o"&gt;&amp;amp;&amp;amp;&lt;/span&gt; make &lt;span class="o"&gt;&amp;amp;&amp;amp;&lt;/span&gt; &lt;span class="nb"&gt;cd&lt;/span&gt; ../..

&lt;span class="c"&gt;# Build main tool (requires Go 1.21+)&lt;/span&gt;
go build &lt;span class="nt"&gt;-o&lt;/span&gt; quic-test cmd/quic-test/main.go

&lt;span class="c"&gt;# Run&lt;/span&gt;
./quic-test &lt;span class="nt"&gt;--mode&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;client &lt;span class="nt"&gt;--server&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;demo.quic.tech:4433
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;






&lt;h2&gt;
  
  
  First test: QUIC vs TCP
&lt;/h2&gt;

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

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;./quic-test &lt;span class="nt"&gt;--mode&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;server &lt;span class="nt"&gt;--listen&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;:4433
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



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

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;./quic-test &lt;span class="nt"&gt;--mode&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;client &lt;span class="nt"&gt;--server&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;127.0.0.1:4433 &lt;span class="nt"&gt;--duration&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;30s
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;QUIC vs TCP comparison:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;./quic-test &lt;span class="nt"&gt;--mode&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;client &lt;span class="nt"&gt;--server&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;127.0.0.1:4433 &lt;span class="nt"&gt;--compare-tcp&lt;/span&gt; &lt;span class="nt"&gt;--duration&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;30s
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;TUI visualization:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;quic-bottom &lt;span class="nt"&gt;--server&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;127.0.0.1:4433
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The results include RTT, jitter, throughput, retransmissions, packet loss, FEC recovery, and fairness under parallel tests.&lt;br&gt;
These are the exact metrics we used when achieving jitter &amp;lt;1 ms on PoP↔PoP.&lt;/p&gt;


&lt;h2&gt;
  
  
  Real network profiles
&lt;/h2&gt;

&lt;p&gt;Profiles are based on actual measurements from CloudBridge Edge PoPs (Moscow, Frankfurt, Amsterdam).&lt;/p&gt;
&lt;h3&gt;
  
  
  Mobile (4G/LTE)
&lt;/h3&gt;

&lt;p&gt;RTT 50–150 ms (avg ~80), throughput 5–50 Mbps (avg ~20), 0.1–2% loss, jitter 10–30 ms.&lt;br&gt;
On this profile we tested FEC and achieved ~+10% goodput at 5% loss.&lt;/p&gt;
&lt;h3&gt;
  
  
  Wi-Fi
&lt;/h3&gt;

&lt;p&gt;Burst losses and micro-drop behavior typical for office/home Wi-Fi.&lt;/p&gt;
&lt;h3&gt;
  
  
  Lossy
&lt;/h3&gt;

&lt;p&gt;3–5% stable loss — ideal for testing FEC recovery efficiency.&lt;/p&gt;
&lt;h3&gt;
  
  
  High-latency
&lt;/h3&gt;

&lt;p&gt;RTT 50–150 ms — typical interregional RU↔EU routes that we tested.&lt;/p&gt;

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

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;./quic-test &lt;span class="nt"&gt;--mode&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;client &lt;span class="nt"&gt;--profile&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;mobile &lt;span class="nt"&gt;--compare-tcp&lt;/span&gt; &lt;span class="nt"&gt;--duration&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;60s
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h3&gt;
  
  
  Custom profiles
&lt;/h3&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;./quic-test &lt;span class="nt"&gt;--mode&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;client &lt;span class="nt"&gt;--profile&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;custom &lt;span class="se"&gt;\&lt;/span&gt;
  &lt;span class="nt"&gt;--rtt&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;100ms &lt;span class="se"&gt;\&lt;/span&gt;
  &lt;span class="nt"&gt;--bandwidth&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;10mbps &lt;span class="se"&gt;\&lt;/span&gt;
  &lt;span class="nt"&gt;--loss&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;1% &lt;span class="se"&gt;\&lt;/span&gt;
  &lt;span class="nt"&gt;--jitter&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;20ms
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;






&lt;h2&gt;
  
  
  Metrics &amp;amp; Grafana integration
&lt;/h2&gt;

&lt;p&gt;Server with Prometheus:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;./quic-test &lt;span class="nt"&gt;--mode&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;server &lt;span class="nt"&gt;--prometheus-port&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;9090
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h3&gt;
  
  
  Available metrics
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;&lt;code&gt;quic_rtt_ms&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code&gt;quic_jitter_ms&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code&gt;quic_loss_total&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code&gt;fec_recovered&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code&gt;tcp_goodput_mbps&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code&gt;quic_goodput_mbps&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code&gt;bbrv3_bandwidth_est&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code&gt;quic_datagram_rate&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code&gt;connection_drops&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code&gt;queue_delay_ms&lt;/code&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;We use these metrics in Grafana and in &lt;a href="https://github.com/twogc/ai-routing-lab" rel="noopener noreferrer"&gt;AI Routing Lab&lt;/a&gt;.&lt;/p&gt;




&lt;h2&gt;
  
  
  Research examples
&lt;/h2&gt;

&lt;h3&gt;
  
  
  Case 1: Mobile profile (5% loss)
&lt;/h3&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Metric&lt;/th&gt;
&lt;th&gt;Baseline QUIC&lt;/th&gt;
&lt;th&gt;QUIC + FEC 10%&lt;/th&gt;
&lt;th&gt;Gain&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Goodput&lt;/td&gt;
&lt;td&gt;3.628 Mbps&lt;/td&gt;
&lt;td&gt;3.991 Mbps&lt;/td&gt;
&lt;td&gt;&lt;strong&gt;+10%&lt;/strong&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Jitter&lt;/td&gt;
&lt;td&gt;0.72 ms&lt;/td&gt;
&lt;td&gt;0.72 ms&lt;/td&gt;
&lt;td&gt;stable&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;RTT P50&lt;/td&gt;
&lt;td&gt;51.25 ms&lt;/td&gt;
&lt;td&gt;51.25 ms&lt;/td&gt;
&lt;td&gt;stable&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;TCP CUBIC shows 4–6× degradation here.&lt;/p&gt;

&lt;h3&gt;
  
  
  Case 2: VPN tunnels with 10% loss
&lt;/h3&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Metric&lt;/th&gt;
&lt;th&gt;TCP&lt;/th&gt;
&lt;th&gt;QUIC&lt;/th&gt;
&lt;th&gt;QUIC + FEC 15%&lt;/th&gt;
&lt;th&gt;Gain&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Throughput&lt;/td&gt;
&lt;td&gt;25 Mbps&lt;/td&gt;
&lt;td&gt;45 Mbps&lt;/td&gt;
&lt;td&gt;68 Mbps&lt;/td&gt;
&lt;td&gt;&lt;strong&gt;+172%&lt;/strong&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Retransmissions&lt;/td&gt;
&lt;td&gt;18,500&lt;/td&gt;
&lt;td&gt;12,200&lt;/td&gt;
&lt;td&gt;3,800&lt;/td&gt;
&lt;td&gt;&lt;strong&gt;-79%&lt;/strong&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;P99 RTT&lt;/td&gt;
&lt;td&gt;450 ms&lt;/td&gt;
&lt;td&gt;320 ms&lt;/td&gt;
&lt;td&gt;210 ms&lt;/td&gt;
&lt;td&gt;&lt;strong&gt;-53%&lt;/strong&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;h3&gt;
  
  
  Other results
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;PoP↔PoP (Moscow—Frankfurt—Amsterdam): jitter &amp;lt;1 ms, connection time 9.20 ms&lt;/li&gt;
&lt;li&gt;BBRv2 vs BBRv3 on satellite-like profiles: +16% throughput&lt;/li&gt;
&lt;li&gt;Production profile: 9.258 Mbps goodput at 30 connections&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;More in &lt;code&gt;docs/reports/&lt;/code&gt;.&lt;/p&gt;




&lt;h2&gt;
  
  
  Usage in universities
&lt;/h2&gt;

&lt;p&gt;quic-test was originally designed as a teaching laboratory environment.&lt;/p&gt;

&lt;h3&gt;
  
  
  Available lab works
&lt;/h3&gt;

&lt;p&gt;&lt;strong&gt;Lab #1: QUIC basics&lt;/strong&gt; — RTT, jitter, handshake, 0-RTT, connection migration.&lt;br&gt;
&lt;strong&gt;Lab #2: TCP vs QUIC&lt;/strong&gt; — losses, HOL blocking, performance.&lt;br&gt;
&lt;strong&gt;Lab #3: Losses &amp;amp; FEC&lt;/strong&gt; — redundancy trade-offs.&lt;br&gt;
&lt;strong&gt;Lab #4: BBRv3 vs CUBIC&lt;/strong&gt; — congestion control comparison.&lt;br&gt;
&lt;strong&gt;Lab #5: NAT traversal&lt;/strong&gt; — ICE/STUN/TURN.&lt;br&gt;
&lt;strong&gt;Lab #6: HTTP/3 performance&lt;/strong&gt; — multiplexing vs HOL-blocked HTTP/2.&lt;/p&gt;

&lt;p&gt;Materials are available in &lt;code&gt;docs/labs/&lt;/code&gt;.&lt;/p&gt;


&lt;h2&gt;
  
  
  Architecture
&lt;/h2&gt;

&lt;p&gt;Detailed scheme in &lt;code&gt;docs/ARCHITECTURE.md&lt;/code&gt;. Summary:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Go core&lt;/strong&gt; — transport, QUIC, measurements (quic-go v0.40, BBRv2 and experimental BBRv3).&lt;br&gt;
&lt;strong&gt;Rust TUI&lt;/strong&gt; — &lt;em&gt;quic-bottom&lt;/em&gt; real-time visualization.&lt;br&gt;
&lt;strong&gt;C++ FEC module&lt;/strong&gt; — AVX2 SIMD optimized, stable XOR-FEC, experimental RS-FEC.&lt;br&gt;
&lt;strong&gt;Metrics&lt;/strong&gt; — Prometheus, HDR histograms.&lt;br&gt;
&lt;strong&gt;Network emulation&lt;/strong&gt; — token bucket, delay queue, random drop.&lt;/p&gt;


&lt;h2&gt;
  
  
  Project status
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Stable&lt;/strong&gt; — QUIC client/server, TCP vs QUIC comparison, profiles, Prometheus, TUI.&lt;br&gt;
&lt;strong&gt;Experimental&lt;/strong&gt; — BBRv3, RS-FEC, MASQUE CONNECT-IP, TCP-over-QUIC.&lt;br&gt;
&lt;strong&gt;Planned&lt;/strong&gt; — automatic plotting, eBPF latency inspector, mini-PoP container.&lt;/p&gt;


&lt;h2&gt;
  
  
  Why we opened the project
&lt;/h2&gt;

&lt;p&gt;CloudBridge Research is an independent research center (ANO "Center for Network Technology Research and Development", founded in 2025).&lt;br&gt;
Our goal is to create an open stack of tools for engineers and universities.&lt;br&gt;
We believe that open research accelerates technological progress and makes it accessible to everyone.&lt;/p&gt;


&lt;h2&gt;
  
  
  Related projects
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;&lt;a href="https://github.com/twogc/ai-routing-lab" rel="noopener noreferrer"&gt;AI Routing Lab&lt;/a&gt;&lt;/strong&gt; — uses quic-test metrics to train delay prediction models (&amp;gt;92% accuracy target).&lt;br&gt;
&lt;strong&gt;&lt;a href="https://github.com/twogc/masque-vpn" rel="noopener noreferrer"&gt;masque-vpn&lt;/a&gt;&lt;/strong&gt; — QUIC/MASQUE VPN load-tested with quic-test, including high-loss scenarios.&lt;/p&gt;


&lt;h2&gt;
  
  
  How to reproduce our results
&lt;/h2&gt;

&lt;p&gt;All configs and commands are in the repo.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Production profile (0.1% loss, 20 ms RTT):&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;./quic-test &lt;span class="nt"&gt;--mode&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;server &lt;span class="nt"&gt;--listen&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;:4433 &lt;span class="nt"&gt;--prometheus-port&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;9090

./quic-test &lt;span class="nt"&gt;--mode&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;client &lt;span class="se"&gt;\&lt;/span&gt;
  &lt;span class="nt"&gt;--server&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&amp;lt;server-ip&amp;gt;:4433 &lt;span class="se"&gt;\&lt;/span&gt;
  &lt;span class="nt"&gt;--connections&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;30 &lt;span class="se"&gt;\&lt;/span&gt;
  &lt;span class="nt"&gt;--duration&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;60s &lt;span class="se"&gt;\&lt;/span&gt;
  &lt;span class="nt"&gt;--congestion&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;bbrv3 &lt;span class="se"&gt;\&lt;/span&gt;
  &lt;span class="nt"&gt;--profile&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;custom &lt;span class="se"&gt;\&lt;/span&gt;
  &lt;span class="nt"&gt;--rtt&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;20ms &lt;span class="se"&gt;\&lt;/span&gt;
  &lt;span class="nt"&gt;--loss&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;0.1%
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Mobile profile (5% loss) with FEC:&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;./quic-test &lt;span class="nt"&gt;--mode&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;server &lt;span class="se"&gt;\&lt;/span&gt;
  &lt;span class="nt"&gt;--listen&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;:4433 &lt;span class="se"&gt;\&lt;/span&gt;
  &lt;span class="nt"&gt;--fec&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="nb"&gt;true&lt;/span&gt; &lt;span class="se"&gt;\&lt;/span&gt;
  &lt;span class="nt"&gt;--fec-redundancy&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;0.10

./quic-test &lt;span class="nt"&gt;--mode&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;client &lt;span class="se"&gt;\&lt;/span&gt;
  &lt;span class="nt"&gt;--server&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&amp;lt;server-ip&amp;gt;:4433 &lt;span class="se"&gt;\&lt;/span&gt;
  &lt;span class="nt"&gt;--profile&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;mobile &lt;span class="se"&gt;\&lt;/span&gt;
  &lt;span class="nt"&gt;--fec&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="nb"&gt;true&lt;/span&gt; &lt;span class="se"&gt;\&lt;/span&gt;
  &lt;span class="nt"&gt;--fec-redundancy&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;0.10 &lt;span class="se"&gt;\&lt;/span&gt;
  &lt;span class="nt"&gt;--duration&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;60s
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Other scenarios are described in &lt;code&gt;scripts/&lt;/code&gt; and &lt;code&gt;docs/reports/&lt;/code&gt;.&lt;/p&gt;




&lt;h2&gt;
  
  
  Contributions &amp;amp; feedback
&lt;/h2&gt;

&lt;p&gt;We welcome issues, PRs, test reports, feature proposals, and integrations into university courses.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;GitHub:&lt;/strong&gt; &lt;a href="https://github.com/cloudbridge-research/quic-test" rel="noopener noreferrer"&gt;https://github.com/cloudbridge-research/quic-test&lt;/a&gt;&lt;br&gt;
&lt;strong&gt;Email:&lt;/strong&gt; &lt;a href="mailto:info@cloudbridge-research.ru"&gt;info@cloudbridge-research.ru&lt;/a&gt;&lt;br&gt;
&lt;strong&gt;Blog:&lt;/strong&gt; &lt;a href="https://cloudbridge-research.ru" rel="noopener noreferrer"&gt;https://cloudbridge-research.ru&lt;/a&gt;&lt;/p&gt;




&lt;h2&gt;
  
  
  Conclusion
&lt;/h2&gt;

&lt;p&gt;If you need to honestly evaluate how QUIC, BBRv3, and FEC behave in real networks — from Wi-Fi to mobile to regional backbones — try &lt;strong&gt;quic-test&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;All results are reproducible, all tools are open, and this is a living engineering project that evolves with the community.&lt;/p&gt;

&lt;p&gt;Try it, reproduce our findings, share your results — together we make networks better.&lt;/p&gt;

</description>
      <category>tooling</category>
      <category>testing</category>
      <category>opensource</category>
      <category>networking</category>
    </item>
    <item>
      <title>Desktop UI for Cloudflare Tunnel: Making Remote Access Simple</title>
      <dc:creator>Maksim Lanies</dc:creator>
      <pubDate>Fri, 05 Dec 2025 18:40:58 +0000</pubDate>
      <link>https://dev.to/ilanies/a-simple-desktop-ui-for-cloudflare-tunnels-rdp-ssh-tcp-3dj9</link>
      <guid>https://dev.to/ilanies/a-simple-desktop-ui-for-cloudflare-tunnels-rdp-ssh-tcp-3dj9</guid>
      <description>&lt;h2&gt;
  
  
  What is Cloudflare Tunnel?
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://developers.cloudflare.com/cloudflare-one/connections/connect-networks/" rel="noopener noreferrer"&gt;Cloudflare Tunnel&lt;/a&gt; provides you with a secure way to connect your resources to Cloudflare &lt;strong&gt;without a publicly routable IP address&lt;/strong&gt;. &lt;/p&gt;

&lt;p&gt;Instead of sending traffic to an external IP, a lightweight daemon (&lt;code&gt;cloudflared&lt;/code&gt;) in your infrastructure creates &lt;strong&gt;outbound-only connections&lt;/strong&gt; to Cloudflare's global network. This means:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;✅ &lt;strong&gt;No inbound ports to open&lt;/strong&gt; - Your firewall stays closed&lt;/li&gt;
&lt;li&gt;✅ &lt;strong&gt;No exposed origin IP&lt;/strong&gt; - Your infrastructure stays hidden&lt;/li&gt;
&lt;li&gt;✅ &lt;strong&gt;Bidirectional communication&lt;/strong&gt; - Despite being outbound-only, traffic flows both ways&lt;/li&gt;
&lt;li&gt;✅ &lt;strong&gt;Protection from bypass attacks&lt;/strong&gt; - All traffic routes through Cloudflare's edge&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  What Can You Connect?
&lt;/h3&gt;

&lt;p&gt;Cloudflare Tunnel can securely connect:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;HTTP/HTTPS web servers&lt;/strong&gt; - Expose web applications&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;SSH servers&lt;/strong&gt; - Secure shell access (&lt;a href="https://developers.cloudflare.com/cloudflare-one/connections/connect-networks/use-cases/ssh/" rel="noopener noreferrer"&gt;guide&lt;/a&gt;)&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;RDP (Remote Desktop)&lt;/strong&gt; - Windows remote desktop (&lt;a href="https://developers.cloudflare.com/cloudflare-one/connections/connect-networks/use-cases/rdp/" rel="noopener noreferrer"&gt;guide&lt;/a&gt;)&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;TCP services&lt;/strong&gt; - Databases, custom applications, any TCP protocol&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;SMB file shares&lt;/strong&gt; - Network file access&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;gRPC services&lt;/strong&gt; - Modern API protocols&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Learn more in the &lt;a href="https://developers.cloudflare.com/cloudflare-one/connections/connect-networks/" rel="noopener noreferrer"&gt;official documentation&lt;/a&gt;.&lt;/p&gt;




&lt;h2&gt;
  
  
  The Challenge
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://github.com/cloudflare/cloudflared" rel="noopener noreferrer"&gt;&lt;code&gt;cloudflared&lt;/code&gt;&lt;/a&gt; is an amazing tool — lightweight, secure, and battle-tested by millions of connections daily.&lt;/p&gt;

&lt;p&gt;But there's a common pain point:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;For quick, ad-hoc connections, the CLI/YAML workflow can feel heavy.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;If you want to:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Quickly RDP into a remote Windows machine&lt;/li&gt;
&lt;li&gt;Open an SSH tunnel for a few minutes&lt;/li&gt;
&lt;li&gt;Share a local dev server with a colleague&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;You typically need to:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Write or edit a YAML configuration file
&lt;/li&gt;
&lt;li&gt;Remember specific CLI flags and syntax
&lt;/li&gt;
&lt;li&gt;Manually manage tunnel processes
&lt;/li&gt;
&lt;li&gt;Track which ports are in use&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;For production deployments, this workflow makes sense. But for &lt;strong&gt;temporary, one-off connections&lt;/strong&gt;, it can slow you down.&lt;/p&gt;




&lt;h1&gt;
  
  
  The Solution: A Desktop UI for cloudflared
&lt;/h1&gt;

&lt;p&gt;What if you could:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Click "Connect to RDP" and get instant access?&lt;/li&gt;
&lt;li&gt;See all your active tunnels in one place?&lt;/li&gt;
&lt;li&gt;Never worry about port conflicts or process management?&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;I built exactly that:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;&lt;a href="https://github.com/makslanies/desktop-argo-tunnel" rel="noopener noreferrer"&gt;https://github.com/makslanies/desktop-argo-tunnel&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;

&lt;h3&gt;
  
  
  Dashboard
&lt;/h3&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fiy90v1mkax85w4mvk00w.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fiy90v1mkax85w4mvk00w.png" alt="Dashboard" width="799" height="546"&gt;&lt;/a&gt;&lt;/p&gt;




&lt;h1&gt;
  
  
  What the app does
&lt;/h1&gt;

&lt;p&gt;The UI wraps &lt;code&gt;cloudflared&lt;/code&gt; to make common tasks instant:&lt;/p&gt;

&lt;h3&gt;
  
  
  Core Features
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;One-Click Connections&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Launch RDP tunnels instantly&lt;/li&gt;
&lt;li&gt;Connect to SSH servers with a button click&lt;/li&gt;
&lt;li&gt;Forward any TCP service without typing commands&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Zero Configuration&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;App automatically downloads and installs &lt;code&gt;cloudflared&lt;/code&gt; if needed&lt;/li&gt;
&lt;li&gt;No manual setup required&lt;/li&gt;
&lt;li&gt;Works out of the box&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Intelligent Port Management&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Automatic port assignment (10000-60000 range)&lt;/li&gt;
&lt;li&gt;No port conflicts&lt;/li&gt;
&lt;li&gt;See exactly which local port each tunnel uses&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Secure Credential Storage&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Built-in KeePass (.kdbx) integration&lt;/li&gt;
&lt;li&gt;AES-256 encrypted password storage&lt;/li&gt;
&lt;li&gt;Import/export existing KeePass databases&lt;/li&gt;
&lt;li&gt;Password quality analysis&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Real-Time Monitoring&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;View all active tunnels with their PIDs&lt;/li&gt;
&lt;li&gt;Monitor connection health&lt;/li&gt;
&lt;li&gt;Track recent activity&lt;/li&gt;
&lt;li&gt;Stop tunnels with one click&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;No YAML files.&lt;br&gt;&lt;br&gt;
No terminal commands.&lt;br&gt;&lt;br&gt;
Just "Connect" and "Disconnect".&lt;/p&gt;


&lt;h1&gt;
  
  
  Why build this?
&lt;/h1&gt;
&lt;h3&gt;
  
  
  The Use Case Gap
&lt;/h3&gt;

&lt;p&gt;Cloudflare Tunnel documentation covers two main scenarios well:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Production deployments&lt;/strong&gt; - Full YAML configs, ingress rules, DNS routing&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Cloudflare Access integration&lt;/strong&gt; - Zero Trust with identity policies&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;But there's a third scenario that's less documented:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Quick, temporary TCP tunneling&lt;/strong&gt; - "I just need to RDP into that server right now"&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;This app fills that gap.&lt;/p&gt;
&lt;h3&gt;
  
  
  Who Benefits?
&lt;/h3&gt;

&lt;p&gt;&lt;strong&gt;DevOps Engineers&lt;/strong&gt;&lt;br&gt;&lt;br&gt;
Quick access to remote servers without VPN overhead&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Support Teams&lt;/strong&gt;&lt;br&gt;&lt;br&gt;
Non-technical staff can connect to services without CLI knowledge&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Developers&lt;/strong&gt;&lt;br&gt;&lt;br&gt;
Instant SSH/RDP access during debugging sessions&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Small Teams&lt;/strong&gt;&lt;br&gt;&lt;br&gt;
Simple remote access without complex Zero Trust setup&lt;/p&gt;


&lt;h1&gt;
  
  
  How it works
&lt;/h1&gt;

&lt;p&gt;The app acts as a friendly wrapper around &lt;a href="https://github.com/cloudflare/cloudflared" rel="noopener noreferrer"&gt;&lt;code&gt;cloudflared&lt;/code&gt;&lt;/a&gt;:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Auto-Installation&lt;/strong&gt;: Downloads and installs &lt;code&gt;cloudflared&lt;/code&gt; if not present&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Command Generation&lt;/strong&gt;: Translates UI actions into correct &lt;code&gt;cloudflared&lt;/code&gt; CLI arguments&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Process Management&lt;/strong&gt;: Starts, monitors, and stops &lt;code&gt;cloudflared&lt;/code&gt; processes&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Visual Feedback&lt;/strong&gt;: Shows active connections, local ports, and process IDs&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Under the hood, it's using &lt;code&gt;cloudflared access tcp&lt;/code&gt; commands like:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;cloudflared access tcp &lt;span class="nt"&gt;--hostname&lt;/span&gt; ssh.example.com &lt;span class="nt"&gt;--url&lt;/span&gt; localhost:12345
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;But you never have to type that.&lt;/p&gt;

&lt;h3&gt;
  
  
  Technical Architecture
&lt;/h3&gt;

&lt;p&gt;Built with modern, performant technologies:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Rust + Tauri 2.0&lt;/strong&gt; - Lightweight native backend (~50MB total)&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;React 18 + TypeScript&lt;/strong&gt; - Type-safe, responsive UI&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;KeePass integration&lt;/strong&gt; - Secure credential storage&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Cross-platform&lt;/strong&gt; - Windows, macOS, and Linux&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;For technical details, see the &lt;a href="https://github.com/makslanies/desktop-argo-tunnel/blob/main/docs/ARCHITECTURE.md" rel="noopener noreferrer"&gt;Architecture Documentation&lt;/a&gt;.&lt;/p&gt;




&lt;h1&gt;
  
  
  Key Features in Detail
&lt;/h1&gt;

&lt;h3&gt;
  
  
  Zero Configuration
&lt;/h3&gt;

&lt;p&gt;The app can automatically download and install &lt;a href="https://github.com/cloudflare/cloudflared" rel="noopener noreferrer"&gt;&lt;code&gt;cloudflared&lt;/code&gt;&lt;/a&gt; if it's not present on your system. No manual setup required.&lt;/p&gt;

&lt;h3&gt;
  
  
  Secure Credential Management
&lt;/h3&gt;

&lt;p&gt;Built-in KeePass (.kdbx) database support:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Create and manage password containers&lt;/li&gt;
&lt;li&gt;Store credentials with AES-256 encryption&lt;/li&gt;
&lt;li&gt;Import/export existing KeePass databases&lt;/li&gt;
&lt;li&gt;Password quality analysis and security scoring&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  Real-time Monitoring
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;View all active tunnels with local ports and PIDs&lt;/li&gt;
&lt;li&gt;Monitor connection health and statistics&lt;/li&gt;
&lt;li&gt;Track recent activity and connection history&lt;/li&gt;
&lt;li&gt;Copy local ports to clipboard&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  Multi-language Support
&lt;/h3&gt;

&lt;p&gt;Full internationalization with English and Russian support (more languages coming soon).&lt;/p&gt;




&lt;h1&gt;
  
  
  Comparison with Standard Workflow
&lt;/h1&gt;

&lt;h3&gt;
  
  
  Traditional CLI Approach
&lt;/h3&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;&lt;span class="c"&gt;# 1. Remember the syntax&lt;/span&gt;
cloudflared access tcp &lt;span class="nt"&gt;--hostname&lt;/span&gt; rdp.example.com &lt;span class="nt"&gt;--url&lt;/span&gt; localhost:3389

&lt;span class="c"&gt;# 2. Keep track of the process&lt;/span&gt;
&lt;span class="c"&gt;# 3. Remember to kill it when done&lt;/span&gt;
&lt;span class="c"&gt;# 4. Hope you didn't forget which port you used&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h3&gt;
  
  
  With Desktop UI
&lt;/h3&gt;

&lt;ol&gt;
&lt;li&gt;Click server name&lt;/li&gt;
&lt;li&gt;Click "Connect"&lt;/li&gt;
&lt;li&gt;See local port displayed&lt;/li&gt;
&lt;li&gt;Click "Disconnect" when done&lt;/li&gt;
&lt;/ol&gt;




&lt;h1&gt;
  
  
  Looking for feedback
&lt;/h1&gt;

&lt;p&gt;I would love to hear your thoughts:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Does this fill a real need in your workflow?&lt;/li&gt;
&lt;li&gt;What other features would make this more useful?&lt;/li&gt;
&lt;li&gt;Should Cloudflare consider an official desktop UI?&lt;/li&gt;
&lt;li&gt;Any UX suggestions or improvements?&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;I'm actively collecting feedback to shape the next iteration.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Repo:&lt;/strong&gt; &lt;a href="https://github.com/makslanies/desktop-argo-tunnel" rel="noopener noreferrer"&gt;https://github.com/makslanies/desktop-argo-tunnel&lt;/a&gt;  &lt;/p&gt;




&lt;h1&gt;
  
  
  Resources
&lt;/h1&gt;

&lt;h3&gt;
  
  
  Official Cloudflare Documentation
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://developers.cloudflare.com/cloudflare-one/connections/connect-networks/" rel="noopener noreferrer"&gt;Cloudflare Tunnel Overview&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://developers.cloudflare.com/cloudflare-one/connections/connect-networks/get-started/how-tunnel-works/" rel="noopener noreferrer"&gt;How Tunnel Works&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://developers.cloudflare.com/cloudflare-one/connections/connect-networks/use-cases/ssh/" rel="noopener noreferrer"&gt;SSH Use Case&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://developers.cloudflare.com/cloudflare-one/connections/connect-networks/use-cases/rdp/" rel="noopener noreferrer"&gt;RDP Use Case&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://github.com/cloudflare/cloudflared" rel="noopener noreferrer"&gt;cloudflared GitHub&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  This Project
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://github.com/makslanies/desktop-argo-tunnel" rel="noopener noreferrer"&gt;GitHub Repository&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://github.com/makslanies/desktop-argo-tunnel/blob/main/docs/ARCHITECTURE.md" rel="noopener noreferrer"&gt;Architecture Documentation&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://github.com/makslanies/desktop-argo-tunnel/blob/main/docs/USER_GUIDE.md" rel="noopener noreferrer"&gt;User Guide&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;




&lt;p&gt;&lt;strong&gt;Note&lt;/strong&gt;: This is a community project, not an official Cloudflare tool. It's designed to complement &lt;code&gt;cloudflared&lt;/code&gt; for specific use cases, not replace it.&lt;/p&gt;

&lt;p&gt;Thanks for reading and huge respect to the Cloudflare team for building an amazing tunneling ecosystem!&lt;/p&gt;

</description>
      <category>cloud</category>
      <category>tooling</category>
      <category>productivity</category>
      <category>ui</category>
    </item>
  </channel>
</rss>
