Client v0.15.5

Published at February 15, 2025 ·  4 min read

We’re excited to announce v0.15.5 of the Packetriot client! This release includes significant updates, improvements, and bug fixes that enhance functionality and user experience. The updates are on our downloads page and apt and yum repositories. Containers for the client are available as well. Use the command below to grab the container for x86-64, arm32, or arm64 platforms. docker pull packetriot/pktriot:latest Authentication Enhancements We’ve added support for integrating OpenID Connect to HTTP/S traffic rules....

Client v0.15.3

Published at March 27, 2024 ·  2 min read

We’re pleased to announce v0.15.3 of the Packetriot client! This release fixes some minor bugs and adds support for connectivity and network monitoring on the client-side, and automatically recreating a tunnel session when changes or failures are detected. The Packetriot client now natively supports macOS ARM 64-bit builds for M1-M3 processors. The updates are on our downloads page and apt and yum repositories. Networking Monitoring This new version of the Packetriot client now supports network change and uptime monitoring....

Client v0.15.2

Published at June 11, 2023 ·  2 min read

We’re pleased to announce v0.15.2 of the Packetriot client! This release fixes some minor bugs and supports using a SOCKSv5 server for connecting to a Packetriot or Spokes server. The updates are on our downloads page and apt and yum repositories. SOCKSv5 Support This new support for SOCKSv5 was a user request to allow the pktriot client program to use a SOCKSv5 server to connect to a network server. The network server can be hosted by Packetriot....

Client v0.15.1

Published at April 23, 2023 ·  2 min read

We’re pleased to announce v0.15.1 of the Packetriot client! This release fixes some bugs and UIX issues in our client program pktriot. You can find the updates on our downloads page and apt and yum repositories. Tunnel Termination Language The languaged used for terminating, or permanently deleting, a tunnel has caused confusion over the years. It is some times misunderstood for just closing down a tunnel so it’s no longer running....

Client v0.15.0

Published at November 27, 2022 ·  4 min read

We’re excited to release v0.15.0 of the Packetriot client. This version include bug fixes and improvements in several areas. We’ve also been working toward refactoring the backend client library so we can introduce more features and work towards some that have been on our roadmap for some time, like an official graphical UI. All the details are below. Thanks to users who reported issues and sent recommendations! Client API & Docs An HTTP API for our client has existed for some time and we are slowly rolling this feature out along with documentation....

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 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....

Client v0.10.9

Published at May 10, 2021 ·  2 min read

In this new version of the client, v0.10.9, we’ve made several updates to allow the client to integrate better with Spokes servers. Service Health Checks Added a new API endpoint to the internal client API to allow the Spokes server to check the availability of the upstream services hosted behind tunnels. The checks are implemented using a HEAD request for HTTP-based services and a simple open TCP connection for others. The backend availability to returned to the Spokes server....

Client v0.10.8

Published at February 1, 2021 ·  4 min read

We’ve been quietly publishing client updates since last post in December ‘20. These have been bug fixes mostly. This release includes support for a new flag that can be used for specify the destination for HTTP/S traffic that is routed through tunnels. Upstream URL Destination We’ve added a new flag --upstream-url and can be used with the pktriot http command. It can also be used with persistent traffic rules with the pktriot tunnel http add command....

Client v0.10.4

Published at December 29, 2020 ·  5 min read

This is our last release for the year and our client has come a long way in 2020. Revision 0.10.4 includes some new features and some bug fixes. All of our downloads are available on our downloads page. Getting this update is really convenient if you’re using one of our Linux repos. # centos [user@host ] sudo yum clean expire-cache # refresh repos [user@host ] sudo yum upgrade pktriot # fedora, centos:8 [user@host ] sudo dnf clean expire-cache # refresh repos [user@host ] sudo dnf upgrade pktriot # debian, ubuntu [user@host ] apt-get install --only-upgrade pktriot Mac users can use brew....

Client v0.10.2

Published at November 1, 2020 ·  2 min read

We’ve had several issues reported recently that are all related to websockets. There have been reports in the past, however, I’ve been able to duplicate an issue by a user by working with them to duplicate their environment and track it down. Websocket Proxying The Packetriot client is written in Go and uses httputil.ReverseProxy for its reverse-proxying needs. I’ve been under the impression for some time that Go has support websockets in its reverse proxy code since version 1....

Client v0.10.1

Published at October 27, 2020 ·  2 min read

The v0.10.1 release includes some small UIX improvements. Host Headers We’ve add the --host-header and --redirect flags to both the pktriot http and pktriot inspect commands. These flags are available normally in the persistent traffic pktriot tunnel http command. Thanks to users for letting us know you wanted these flags and features in our instant HTTP hosting and inspector. It was always our intention to add it but reaching out to let us know helped us accelerate this....

Client v0.10.0

Published at October 14, 2020 ·  2 min read

The v0.10.0 release of our client includes support for Windows services. You’ll be able to install a Windows service that keeps the Packetriot client running 24/7 and between system restarts. This is a feature we’ve been wanting to add for some time. I’d like to thank for the users who reached out to use and expressed this would be an important and great feature to support their workflows. We have updated our docs with instructions on how to use the new Windows service integration....

HTTP Inspector

Published at August 18, 2020 ·  8 min read

Using the HTTP Inspector built into the Packertriot client will make writing and debugging applications that integrate with webhooks much easier. You’re not limited to webhooks either, you can debug any HTTP-based application. There’s lot of examples we could provide to illustrate how useful an HTTP inspector is during web development. In this post we’ll walk through creating a webhook for a GitHub repository so that we can receive notifications when changes are made to the repo....

Client v0.9.19

Published at August 18, 2020 ·  3 min read

This release includes a big update! For a while I’ve gone back and forth about adding an HTTP inspector. I wasn’t sure how difficult it would be to write a decent simple inspector and how muc time and effort would be required. So I delayed this feature and thought it might not be necessary. However, I’ve found it difficult to lure developers to Packetriot and I’ve had several customers and users ask for it since our launch....

Client v0.9.17

Published at July 21, 2020 ·  2 min read

This update includes a bug fix for secure redirection, HTTP->HTTPS, that affected traffic on wildcard domains when subsequent HTTP requests utilized POST/PUT/DELETE requests. Technical Details For some more background on this defect, the HTTP requests that pass through Hubs, our edge server software, is updated to included X-Forward-X headers. These header fields are processed by a “forwarder” and “secure-redirect” HTTP handler in the Packetriot client. The forwarder will attempt to set the X-Forwarded-For flag when possible if they were not present (e....

Client v0.9.16

Published at June 16, 2020 ·  2 min read

This update includes some bug fixes and some new features. We fixed a dead-lock in our client that preventing tunnels from re-connecting when disconnected so this update is highly recommended. Fixed Dead-Lock We discovered a dead-lock issue that was introduced in an earlier release that impacted clients that used Let’s Encrypt for custom domains. The client periodically checks for opportunities to renew certificates with Let’s Encrypt and then does. This dead-lock would basically lock up any requests to custom domain using Let’s Encrypt after 12 hours....

Client v0.9.10

Published at March 23, 2020 ·  3 min read

We added DNS-over-HTTPS support in the last release (v0.9.9). It looks like some users may have had some issues. I think it may be due to some network blocking DNS requests to non-managed servers. E.g (blocking 8.8.8.8, 1.1.1.1, …). Some corporate network admins do this. We’ve added a new flag --doh in the configure command and also a field in the configuration file that can be set so that the client will use DNS-over-HTTPS or not (the local DNS system resolver)....