Connet.dev – high performance reverse proxy to connect devices privately

by Ingon • 1 year ago

10 14 1 year ago

Ingon5• 1 year ago

Hi All,

This is a hosted version of connet[1]. In addition, it allows users to expose their endpoints directly on the internet (optional and still in progress)

[1] https://github.com/connet-dev/connet

andrewfromx• 1 year ago

I like it. Here's how I see the marketplace:

Quick demonstrations & development: ngrok

Low-resource environments (IoT, embedded): rathole

Privacy-focused deployments: connet

Production with active community: FRP

Self-hosting with direct connections: connet

https://gist.github.com/andrewarrow/d0e41dd954485a8574b9ea74...

srichard16• 1 year ago

Curious: why do you see ngrok as just for testing and dev when thousands of users use ngrok in production?

Full disclosure I work there.

ghoshbishakh• 1 year ago

Why route all traffic through a tunnel for a production setup? On-premise solutions will use static IPs from their ISPs.

Full disclosure - I work at https://pinggy.io

Ingon5• 1 year ago

Very cool comparison, thank you!

One new feature I haven't highlighted yet, is that you can, in addition, encrypt traffic as it goes through relays (both via tls or noise-inspired protocol, dhxcp). This enhances privacy, even when you are using public (e.g. not owned by you relays), covering a case like https://connet.dev nicely.

PLG883• 1 year ago

Sounds like what zrok.io does ... do you also support completely E2E private shares like it does - https://docs.zrok.io/docs/concepts/sharing-private/. This means the resource does not have a public IP at all (note, zrok also does public shares).

yair99dd• 1 year ago

I'm a zrok.io fan

PLG883• 1 year ago

I would say zrok.io is more privacy-focused, particularly with its frontdoor and private sharing features.

Ingon5• 1 year ago

connet itself doesn't have a notion of public share at all - you need clients/peers on both ends (destination and source) to "project" a remote service. connet.dev do enhance this, by running the source clients publicly, but you need to specifically enable this, and it is best used as a break-glass option, since obviously makes things less-private.

In any case, zrok.io is cool, it is certainly more mature and feature rich project.

sylens• 1 year ago

Interestingly I just did this with my own reverse proxy recently; nginx proxy manager in a container running on the network of a Tailscale container on the same host, connected to a Tailscale exit node on internal network. Will take a look at whether this is better.

Ingon5• 1 year ago

Thanks, it would be great to hear if you tried connet and how it went!

In any case, homegrown solutions are great, they offer the most flexibility, but also require the biggest time investment (and knowledge of course).

vimredo• 1 year ago

This reminds me a bit about gsocket[1], except that it seems slightly more configurable and not just intended to be a backdoor.

[1] https://gsocket.io/

Connet.dev – high performance reverse proxy to connect devices privately

Related Stories