frp-flyapp VS rathole

You can host frp on fly.io for raw TCP traffic for free if you are within free tier. Also not randomized ports unlike ngrok.

You can use port-forwarded UDP, or TCP (e.g., DoH, or DoT) dnsproxy ports instead of local process to escape network restrictions (e.g., using rathole)

# core/docker-compose.local.yml services: rathole: # 1. default official x86 image image: rapiz1/rathole:v0.5.0 # 2. custom built ARM image (for Raspberry pi) # image: nemanjamitic/my-rathole-arm64:v1.0 # 3. build for arm - AVOID, use prebuilt ARM image above # build: https://github.com/rapiz1/rathole.git#main # platform: linux/arm64 container_name: rathole command: --client /config/rathole.client.toml restart: unless-stopped volumes: - ./rathole.client.toml:/config/rathole.client.toml:ro networks: - proxy traefik: image: 'traefik:v2.9.8' container_name: traefik restart: unless-stopped # for this to work both services must be defined in the same docker-compose.yml file depends_on: - rathole # other config... networks: - proxy # leave this commented out, just for explanation # Rathole will pass Traffic through proxy network directly on 80 and 443 # defined in rathole.client.toml # ports: # - '80:80' # - '443:443' # other config...

Another point to make is that the SSH tunnel technique is most suitable for temporarily exposing services for demo purposes. For permanent tunnels, you would need to add autossh to keep the connection alive, but there are better tools for permanent tunnels, such as rapiz1/rathole or fatedier/frp.

A hole-punching solution also written in Rust

Over the past couple of months, I've been working on connet. At this point, it is working pretty smoothly (in what I use it for), so I wanted to share it with more people and see what they think.

I know many other similar/reverse proxy solutions exist - like https://github.com/fatedier/frp, https://github.com/rapiz1/rathole, and a bunch more you can find at https://github.com/anderspitman/awesome-tunneling. However, I wanted to try and put my own little peer-to-peer twist on it.

Thanks for checking it out, and sharing any feedback you might have!

There’s actually a (really superb) Rust library/program for creating reverse tunnels over TCP, that’s called Rathole [0]. We used it [1] at my last startup and were mildly worried that one day we’d need to explain to a security auditor why we had a dependency called “rathole…”

[0] https://github.com/rapiz1/rathole

[1] https://www.splitgraph.com/jumpstart/tunnel

rathole - Similar to frp, including the config format, but with improved performance. Low resource consumption. Hot reload. Written in Rust.

rathole?

There is also this: https://github.com/rapiz1/rathole