Spokes v1.3.5 and Client v0.13.1

Published at January 9, 2022 ·  4 min read

Happy New Years!! It’s been some time since we last posted an upate but we’ve been very busy in the last few months of ‘21 and have published several releases of Spokes and our client software. I’ll summarize them below and describe the changes introduced in the newest releases - Spokes v1.3.5 and the Packetriot client v0.13.1. Spokes Updates Since Spokes v1.3.1 we’ve made three additional releases that lots of new features....

Client Update v0.11.2

Published at October 1, 2021 ·  2 min read

The v0.11.2 release fixes a bug in the client API endpoint that prevent Spokes users/administrators from remotely setting up custom certificates using the dashboard UI. We’ve improved our logging in this release as well. TLS Custom Certs We found a small bug in the client API endpoint that processed changes to HTTP traffic rules related to custom certificates. A small logic error prevented those certs from being saved to disk and then being enabled in the client....

Spokes v1.3.1 and Client v0.11.1

Published at September 12, 2021 ·  8 min read

Tody we’ve published software updates to Spokes and the Packetriot client program to enable convenient access to distributed services hosted behind by other tunnels connected to a Spokes server. Access to external services can be mapped as well. These new features establish an application-level mesh network similar to what Envoy or Linkerd provide. This enables developers to write programs that can access ports on 127.0.0.1 and connect to the actual service running on a different network or on completely different compute infrastructure....

Spokes v1.2.2

Published at June 13, 2021 ·  2 min read

Revision v1.2.2 is a bug fix release. You can find updates on Packetriot.com, via our Linux package repos and Docker Hub. Chrome Browsers The server configuration page in the Spokes Dashboard had issues with form submissions for Chrome-based browsers. When users attempted to make changes in the Tunnel or Proxies configuration options, the browser would fail to submit them. The root cause is this different behavior when you have multiple forms on a page and use <button> as the mechanism to submit the form....