Nowa aplikacja QPKG w sklepie Qnapclub Store: Inlets CLI
Cloud Native Tunnel,Expose your local endpoints to the Internet or within a remote network, without touching firewalls.
https://github.com/inlets/inlets
inlets ® is how you connect services between different networks. You won't have to think about managing firewalls, NAT or VPNs again. Services can be tunnelled securely over a websocket and accessed on a remote network privately, or exposed on the Internet using an exit-server (5-10USD / mo).
Why do we need this project? Similar tools such as ngrok and Argo Tunnel from Cloudflare are closed-source, have limits built-in, can work out expensive, and have limited support for arm/arm64, Docker and Kubernetes. Ngrok's domain is also often banned by corporate firewall policies meaning it can be unusable. Other open-source tunnel tools are designed to only set up a single static tunnel.
With inlets you can set up your own self-hosted tunnel, copy over the static binary and start tunnelling traffic without any arbitrary limits or restrictions. When used with TLS, inlets can be used with most corporate HTTP proxies.
inlets uses a websocket to create to create a tunnel between a client and a server. The server is typically a machine with a public IP address, and the client is on a private network with no public address.
inlets is considered production-ready, but you should do some testing before you depend on it. For a commercially-supported solution, see inlets PRO, which enables additional use-cases, has more thorough testing and secure defaults.
Private or public tunnels?
A private tunnel is where you start a tunnel to a server and only expose it on the server's LAN address (this can replace the use-cases where you would use a VPN or Kubernetes federation)
A public tunnel is where you expose the private service to users via the server's public IP
Features
Tunnel HTTP or websockets
Client announces the tunnelled services to the server
Expose multiple sites on same port through the use of DNS entries and a Host header
Upgrade to link encryption using TLS for websockets (wss://) with an external add-on, or inlets PRO
Shared authentication token for the client and server
Automatic reconnects for when the connection drops
Distribution:
Binaries and Docker images for multiple architecture - Intel and ARM
Kubernetes YAML files and Dockerfile
systemd unit file for client/server
Native Kubernetes Service and LoadBalancer integration with inlets-operator
Going to production with inlets PRO
The following features / use-cases are covered by inlets PRO:
Tunnel L4 TCP traffic such as websockets, databases, reverse proxies, remote desktop and SSH
Tunnel L7 HTTPS / REST traffic - with automated Let's Encrypt support
Expose multiple ports from the same client - i.e. 80 and 443
Run a reverse proxy or Kubernetes IngressController directly on your host
Automated TLS for the control-plane
Commercial services & support
Documentation, blog posts, tutorials and videos
TIP ME !!
Your gratitude and finance will help me to continue integration of this QPKG and maintain up to date versions.
Modele: TS-XA28A,TS-NASX86 64bits,TS-X31,TS-X41
Kontynuuj czytanie...
