Provision cloud hosts as exit-nodes for inlets with a single command.
- DigitalOcean support
- Scaleway support
- Add Civo.com
- Add poll interval
--poll 5sfor use with Civo that applies rate-limiting
- Add CLI flags to support Packet.com
Inlets is listed on the Cloud Native Landscape as a Service Proxy
- inlets - open-source L7 HTTP tunnel and reverse proxy
- inlets-pro - L4 TCP load-balancer
- inlets-operator - deep integration for inlets in Kubernetes, expose Service type LoadBalancer
- inletsctl - CLI tool to provision exit-nodes for use with inlets or inlets-pro
curl -sLSf https://raw.githubusercontent.com/inlets/inletsctl/master/get.sh | sudo sh
Costs for exit-nodes
See notes for inlets-operator
Examples on how to run
inletsctl to create an exit node.
- You will need inlets on your client
inletsctl create, the IP address of your exit-node will be returned along with a sample
inlets clientcommand, for instance:
Inlets OSS exit-node summary: IP: 18.104.22.168 Auth-token: qFyFzKYQvFSgtl7TM76p5SwWpmHaQGMT405HajiMzIYmwYVgJt1lvAMXfV4S3KlS Command: export UPSTREAM=http://127.0.0.1:8000 inlets client --remote "ws://22.214.171.124:8080" \ --token "qFyFzKYQvFSgtl7TM76p5SwWpmHaQGMT405HajiMzIYmwYVgJt1lvAMXfV4S3KlS" \ --upstream $UPSTREAM
You can delete your exit node using the
idgiven by your cloud provider
inletsctl delete --access-token-file ~/Downloads/do-access-token --id 164857028
Example usage with DigitalOcean
inletsctl create --access-token-file $HOME/Downloads/do-access-token \ --region="nyc1"
Example with inlets-pro
Let's say we want to forward TCP connections to the IP
192.168.0.26 within our client's network, using inlets-pro, we'd run this using the
inletsctl create digitalocean --access-token-file ~/Downloads/do-access-token \ --remote-tcp 192.168.0.26
Example usage with Scaleway
# Obtain from your Scaleway dashboard: export TOKEN="" export SECRET_KEY="" export ORG_ID="" inletsctl create --provider scaleway \ --access-token $TOKEN --secret-key $SECRET_KEY --organisation-id $ORG_ID
The region is hard-coded to France / Paris 1.
Add another cloud provisioner
Add a provisioner by sending a PR to the inlets-operator's provision package, once released, you can vendor the package here and add any flags that are required.
Note: only clouds that support cloud-init can be added