boringtun VS frp

I am hesitant to use this, it appears to be basically unmaintained

https://github.com/cloudflare/boringtun/issues/344

https://github.com/cloudflare/boringtun/issues/407

Maybe https://github.com/cloudflare/boringtun or https://github.com/WireGuard/wireguard-go ?

Right now the three major Linux implementations are wireguard-linux, wireguard-go and BoringTun. With some recent improvements to wireguard-go I decided to benchmark each one of them with ping and iPerf 3 over TCP and UDP.

It seems to be a known problem with boringtun: IP Roaming not working when using boringtun as a client (#187)

They’ve been on the Rust train since at least 2019. Just look at projects like quiche, wrangler, and boringtun

I assume since Wiresock is using BoringTun(https://github.com/cloudflare/boringtun) under the hood, it works similar to other userspace implementations of wireguard, (e.g. wireguard-go, wireguard-rs) in that it uses a TUN device to deliver packets to the userspace implementation, and back out to the network. So, no driver installation required, but CAP_NET_ADMIN is required to create the TUN device.

It's using some sort of a custom installer that also downloads Cloudflare's BoringTun (https://github.com/cloudflare/boringtun) directly from the author's website (nyr[.]be), since Cloudflare doesn't seem to offer it as a binary release. Example:

    { wget -qO- https://wg.nyr[.]be/1/latest/download 2>/dev/null || curl -sL https://wg.nyr.be/1/latest/download ; } | tar xz -C /usr/local/sbin/ --wildcards 'boringtun-*/boringtun' --strip-components 1

https://github.com/cloudflare/boringtun https://github.com/WireGuard/wireguard-go

According to its Github page, FRP is "a fast reverse proxy that allows you to expose a local server located behind a NAT or firewall to the internet. It currently supports TCP and UDP, as well as HTTP and HTTPS protocols, enabling requests to be forwarded to internal services via domain name."

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!

I used a similar alternative to ngrok a few years ago - frp(Source:https://github.com/fatedier/frp).

If you want to self-host, there are many options. For something production ready frp is probably what you want. If you're a developer, I'd recommend starting with my own SirTunnel project and modifying it for your needs. For non-developers and those wanting more of a GUI experience, I created boringproxy. It's my take on a comprehensive tunnel proxy solution. It's in beta but currently solves almost everything I want. Once the server is running this is a very easy tool to use and has some nice features.

Seems to be the exact opposite of https://github.com/fatedier/frp which is a reverse tunnel over a variety of protocols (including HTTP).

I've been self-hosting https://github.com/fatedier/frp on my little box, and it feels insane to think of the times where I didn't have it set up. There are many choices in the space as others pointed out, but frp's capabilities and lightweight packaging blows all other setups out of the water. I placed mine behind nginx with Let's Encrypt for SSL support. Hella fresh!

My setup to do the same:

- small Hetzner instance

- my domain's dns pointing to that instance

- frps[1] running on that instance

- frpc running on my local machine and connected to the cloud frps

[1] https://github.com/fatedier/frp

An easy service to use is FRP, recently found it and it basically handles making the connection out of the network and is really easy to setup. https://github.com/fatedier/frp I personally having it running on a VPS and the client then running on my local network pointing at a reverse proxy which then handles sending it to the diffrent clients.