2021-02-23 17:14:08 +00:00
|
|
|
**Experimental**: This is a new format for release notes. The format and availability is subject to change.
|
|
|
|
|
|
2021-03-23 15:31:46 +00:00
|
|
|
## 2021.3.2
|
2021-02-05 01:44:03 +00:00
|
|
|
|
|
|
|
|
### New Features
|
|
|
|
|
|
2021-03-15 18:30:17 +00:00
|
|
|
- It is now possible to obtain more detailed information about the cloudflared connectors to Cloudflare Edge via
|
|
|
|
|
`cloudflared tunnel info <name/uuid>`. It is possible to sort the output as well as output in different formats,
|
|
|
|
|
such as: `cloudflared tunnel info --sort-by version --invert-sort --output json <name/uuid>`.
|
|
|
|
|
You can obtain more information via `cloudflared tunnel info --help`.
|
2021-02-05 01:44:03 +00:00
|
|
|
|
|
|
|
|
### Bug Fixes
|
|
|
|
|
|
|
|
|
|
- Don't look for configuration file in default paths when `--config FILE` flag is present after `tunnel` subcommand.
|
2021-03-23 15:31:46 +00:00
|
|
|
- cloudflared access token command now functions correctly with the new token-per-app change from 2021.3.0.
|
2021-02-05 01:44:03 +00:00
|
|
|
|
|
|
|
|
|
2021-03-15 10:08:04 +00:00
|
|
|
## 2021.3.0
|
2021-02-23 19:48:32 +00:00
|
|
|
|
|
|
|
|
### New Features
|
|
|
|
|
|
2021-02-26 09:50:19 +00:00
|
|
|
- [Cloudflare One Routing](https://developers.cloudflare.com/cloudflare-one/tutorials/warp-to-tunnel) specific commands
|
|
|
|
|
now show up in the `cloudflared tunnel route --help` output.
|
2021-03-15 10:08:04 +00:00
|
|
|
- There is a new ingress type that allows cloudflared to proxy SOCKS5 as a bastion. You can use it with an ingress
|
|
|
|
|
rule by adding `service: socks-proxy`. Traffic is routed to any destination specified by the SOCKS5 packet but only
|
|
|
|
|
if allowed by a rule. In the following example we allow proxying to a certain CIDR but explicitly forbid one address
|
|
|
|
|
within it:
|
|
|
|
|
```
|
|
|
|
|
ingress:
|
|
|
|
|
- hostname: socks.example.com
|
|
|
|
|
service: socks-proxy
|
|
|
|
|
originRequest:
|
|
|
|
|
ipRules:
|
|
|
|
|
- prefix: 192.168.1.8/32
|
|
|
|
|
allow: false
|
|
|
|
|
- prefix: 192.168.1.0/24
|
|
|
|
|
ports: [80, 443]
|
|
|
|
|
allow: true
|
|
|
|
|
```
|
|
|
|
|
|
2021-02-23 19:48:32 +00:00
|
|
|
|
|
|
|
|
### Improvements
|
|
|
|
|
|
|
|
|
|
- Nested commands, such as `cloudflared tunnel run`, now consider CLI arguments even if they appear earlier on the
|
|
|
|
|
command. For instance, `cloudflared --config config.yaml tunnel run` will now behave the same as
|
|
|
|
|
`cloudflared tunnel --config config.yaml run`
|
2021-02-28 23:24:38 +00:00
|
|
|
- Warnings are now shown in the output logs whenever cloudflared is running without the most recent version and
|
|
|
|
|
`no-autoupdate` is `true`.
|
2021-03-15 10:08:04 +00:00
|
|
|
- Access tokens are now stored per Access App instead of per request path. This decreases the number of times that the
|
|
|
|
|
user is required to authenticate with an Access policy redundantly.
|
2021-02-23 19:48:32 +00:00
|
|
|
|
|
|
|
|
### Bug Fixes
|
|
|
|
|
|
2021-03-09 17:16:17 +00:00
|
|
|
- GitHub [PR #317](https://github.com/cloudflare/cloudflared/issues/317) was broken in 2021.2.5 and is now fixed again.
|
|
|
|
|
|
2021-02-23 17:14:08 +00:00
|
|
|
## 2021.2.5
|
|
|
|
|
|
|
|
|
|
### New Features
|
|
|
|
|
|
2021-02-23 19:48:32 +00:00
|
|
|
- We introduce [Cloudflare One Routing](https://developers.cloudflare.com/cloudflare-one/tutorials/warp-to-tunnel) in
|
|
|
|
|
beta mode. Cloudflare customer can now connect users and private networks with RFC 1918 IP addresses via the
|
|
|
|
|
Cloudflare edge network. Users running Cloudflare WARP client in the same organization can connect to the services
|
|
|
|
|
made available by Argo Tunnel IP routes. Please share your feedback in the GitHub issue tracker.
|
2021-02-23 09:58:39 +00:00
|
|
|
|
2021-02-23 12:33:37 +00:00
|
|
|
## 2021.2.4
|
|
|
|
|
|
|
|
|
|
### Bug Fixes
|
2021-02-23 17:14:08 +00:00
|
|
|
|
2021-02-23 19:48:32 +00:00
|
|
|
- Reverts the Improvement released in 2021.2.3 for CLI arguments as it introduced a regression where cloudflared failed
|
|
|
|
|
to read URLs in configuration files.
|
|
|
|
|
- cloudflared now logs the reason for failed connections if the error is recoverable.
|
2021-02-23 12:33:37 +00:00
|
|
|
|
2021-02-23 09:58:39 +00:00
|
|
|
## 2021.2.3
|
2021-02-23 19:48:32 +00:00
|
|
|
|
2021-02-23 09:58:39 +00:00
|
|
|
### Backward Incompatible Changes
|
2021-02-23 19:48:32 +00:00
|
|
|
|
|
|
|
|
- Removes db-connect. The Cloudflare Workers product will continue to support db-connect implementations with versions
|
|
|
|
|
of cloudflared that predate this release and include support for db-connect.
|
|
|
|
|
|
2021-02-23 09:58:39 +00:00
|
|
|
### New Features
|
2021-02-23 19:48:32 +00:00
|
|
|
|
2021-02-23 17:14:08 +00:00
|
|
|
- Introduces support for proxy configurations with websockets in arbitrary TCP connections (#318).
|
2021-02-23 19:48:32 +00:00
|
|
|
|
2021-02-23 09:58:39 +00:00
|
|
|
### Improvements
|
2021-02-23 19:48:32 +00:00
|
|
|
|
|
|
|
|
- (reverted) Nested command line argument handling.
|
|
|
|
|
|
2021-02-23 09:58:39 +00:00
|
|
|
### Bug Fixes
|
2021-02-23 19:48:32 +00:00
|
|
|
|
|
|
|
|
- The maximum number of upstream connections is now limited by default which should fix reported issues of cloudflared
|
|
|
|
|
exhausting CPU usage when faced with connectivity issues.
|
2021-02-23 09:58:39 +00:00
|
|
|
|
