Proxy Protocol support for inlets uplink data plane

Changelog for 0.9.35:

Commits

Changes: 0.9.34...0.9.35

Generated by Derek

Proxy Protocol support for data plane behind a load-balancer

Proxy Protocol support for data plane behind a load-balancer

The --lb-proxy-protocol flag can be used behind a cloud load-balancer, HAProxy, or similar to receive a real client IP, this works for the data-plane ports on a tcp tunnel server.

Add --generate k8s_yaml to inlets-pro http server command

Changelog for 0.9.33:

Commits

Changes: 0.9.32...0.9.33

Generated by Derek

Fix for --token-file when generating HTTP server systemd units

Fix for --token-file when generating HTTP server systemd units, where the value of the --token-file was expanded into a --token parameter. It'll now read from the file specified.

Updates to tunnel code, don't expand token-file when generating systemd unit files, and add exponential backoff option for uplink clients

Changelog for 0.9.31:

• Updates to tunnel code
• Don't expand --token-file when generating systemd unit files for clients/servers
• Add exponential backoff option for uplink clients --reconnect-strategy=backoff

Add generate flag for uplink server command

Changelog for 0.9.30:

--generate=systemd added to inlets-pro uplink server command

Generated by Derek

Allow different orders for arguments to inlets-pro sshmux

Allow different orders for arguments to inlets-pro sshmux, previously the config file had to come first.

Disable proxy protocol by default for sshmux

Changelog for 0.9.28:

Commits

Changes: 0.9.27...0.9.28

Generated by Derek

Connect timeout for sshmux connect helper

Changelog for 0.9.27:

Commits

Changes: 0.9.26...0.9.27

Generated by Derek

Support K8s API server via TLS pass-through in sshmux

This release adds support K8s API server via TLS pass-through in inlets-pro sshmux server

Put this into config.yaml:

  - name: rpi-k8s.inlets
    upstream: "raspberrypi.local:6443"
    passthrough: true
  - name: rpi-ssh.inlets
    upstream: "raspberrypi.local:22"

Make sure raspberrypi.local is in /etc/hosts, or resolve the IP into config.yaml instead of using the .local domain.