#6733 Reduces log level of the "Couldn't find connection by IP" message so that it doesn't log each time a client disconnects.
#6845 Fixes connectivity issues on idle connections by entering an always-on, low-power mode instead of closing them.
Previous Gateway versions
Version
Date
Description
1.3.1
#6563 Removes unnecessary packet buffers for a minor performance increase.
1.3.0
#6434 Adds support for routing the Internet Resource for Clients.
1.2.0
#5901 Implements glob-like matching of domains for DNS resources.
1.1.5
#6276 Fixes a bug where relayed connections failed to establish after an idle period.
#6277 Fixes a bug where restrictive NATs caused connectivity problems.
1.1.4
Removes `FIREZONE_ENABLE_MASQUERADE` env variable. Masquerading is now always enabled unconditionally.
1.1.3
Fixes an issue where Gateways could become unresponsive after new versions of the Firezone infrastructure was deployed.
1.1.2
Reduces log noise for the default log level.
1.1.1
Fixes a minor connectivity issue that could occur for some DNS Resources.
1.1.0
This release introduces a new method of resolving and routing DNS Resources that is more reliable on some poorly-behaved networks. To use this new method, Client versions 1.1.0 or later are required. Client versions 1.0.x will continue to work with Gateway 1.1.x, but will not benefit from the new DNS resolution method.
Read more about this change in the announcement post here.
1.0.8
This is a maintenance release with no major user-facing changes.
1.0.7
This release fixes a bug where the incorrect Gateway version could be reported to the admin portal.
1.0.6
This release contains connectivity fixes and performance improvements and is recommended for all users.
1.0.5
Minor maintenance fixes.
1.0.4
Fixes an issue detecting the correct architecture during installation and upgrades.
#6017 Removes keyboard accelerators, which were not working.
#6071 Puts angle brackets around hyperlinks in the menu.
1.1.7
#5848 Stops the GUI and prompts you to re-launch it if you update Firezone while the GUI is running.
1.1.6
#5795 Unexpected IPC service stops are now reported as "IPC connection closed".
#5817 Shows different tray icons when signed out, signing in, and signed in.
1.1.5
#5793 The Linux GUI Client is now built for both x86-64 and ARM64.
1.1.4
#5700 Fixes an issue where a stale DNS cache could prevent traffic from routing to DNS Resources if they were updated while the Client was signed in.
1.1.3
Prevents Firezone's stub resolver from intercepting DNS record types besides A, AAAA, and PTR. These are now forwarded to your upstream DNS resolver.
1.1.2
Fixes an issue that could cause Resources to be unreachable a few hours after roaming networks.
Reduces noise in logs for the default log level.
1.1.1
This is a maintenance release with no user-facing changes.
1.1.0
Introduces the new DNS routing system supported by 1.1.0 Gateways which results in much more stable connections for DNS Resources, especially when wildcards are used.
Improves reliability when roaming between networks.
Closes idle connections to Gateways that have not seen traffic for more than 5 minutes which reduces power consumption when not accessing Resources.
Updates log file endings to JSONL and adds syslog-style logs for easier readability.
Note: Client versions 1.1.x are incompatible with Gateways running 1.0.x.
1.0.9
This release simplifies the Resource connected state icons in the menu to prevent issues with certain Linux distributions.
1.0.8
Fixes an issue in Windows that could cause the Wintun Adapter to fail to be created under certain conditions.
1.0.7
This release fixes a bug where the incorrect Client version was reported to the admin portal.
1.0.6
This release contains connectivity fixes and performance improvements and is recommended for all users.
1.0.5
This release adds an IPC service for Windows to allow for better process isolation.
1.0.4
This release fixes a bug on Windows where system DNS could break after the Firezone Client was closed.
1.0.3
Maintenance release.
1.0.2
This release reverts a change that could cause connectivity issues seen by some users.
1.0.1
Update the upgrade URLs used to check for new versions.
#6406 Shows the Git SHA corresponding to the build on the Settings -> Advanced screen.
#6424 Fixes a bug where packets would be lost when a connection is first established to a Gateway due to routes being updated with no actual change.
1.2.0
#5901 Implements glob-like matching of domains for DNS resources.
#6186 Adds the ability to mark Resources as favorites.
#6361 Connections to Gateways are now sticky for the duration of the Client's session. This fixes potential issues maintaining long-lived TCP connections to Gateways in a high-availability setup.
1.1.5
#6276 Fixes a bug where relayed connections failed to establish after an idle period.
#6277 Fixes a bug where restrictive NATs caused connectivity problems.
1.1.4
#6181 Improves reliability of DNS resolution of non-resources.
1.1.3
Fixes an issue where DNS queries could time out on some networks.
1.1.2
Prevents Firezone's stub resolver from intercepting DNS record types besides A, AAAA, and PTR. These are now forwarded to your upstream DNS resolver.
1.1.1
Fixes an issue that could cause Resources to be unreachable a few hours after roaming networks.
Reduces noise in logs for the default log level.
1.1.0
Introduces the new DNS routing system supported by 1.1.0 Gateways which results in much more stable connections for DNS Resources, especially when wildcards are used.
Improves reliability when roaming between networks.
Closes idle connections to Gateways that have not seen traffic for more than 5 minutes which reduces power consumption when not accessing Resources.
Updates log file endings to JSONL and adds syslog-style logs for easier readability.
Note: Client versions 1.1.x are incompatible with Gateways running 1.0.x.
1.0.5
This release introduces new Resource status updates in the Resource list.
#5795 Unexpected IPC service stops are now reported as "IPC connection closed".
#5827 Fixes a bug where DNS could stop working when you sign out.
#5817 Shows different tray icons when signed out, signing in, and signed in.
1.1.5
This is a maintenance release with no user-facing changes.
1.1.4
#5700 Fixes an issue where a stale DNS cache could prevent traffic from routing to DNS Resources if they were updated while the Client was signed in.
1.1.3
Prevents Firezone's stub resolver from intercepting DNS record types besides A, AAAA, and PTR. These are now forwarded to your upstream DNS resolver.
1.1.2
Fixes an issue that could cause Resources to be unreachable a few hours after roaming networks.
Reduces noise in logs for the default log level.
Substantially reduces memory usage for the IPC service.
1.1.1
This release fixes a performance issue.
1.1.0
Introduces the new DNS routing system supported by 1.1.0 Gateways which results in much more stable connections for DNS Resources, especially when wildcards are used.
Improves reliability when roaming between networks.
Closes idle connections to Gateways that have not seen traffic for more than 5 minutes which reduces power consumption when not accessing Resources.
Updates log file endings to JSONL and adds syslog-style logs for easier readability.
Fixes a hang that could occur when the Client is quit, preventing it from opening again.
Note: Client versions 1.1.x are incompatible with Gateways running 1.0.x.
1.0.9
This release simplifies the Resource connected state icons in the menu to prevent issues with certain Linux distributions.
1.0.8
Fixes an issue in Windows that could cause the Wintun Adapter to fail to be created under certain conditions.
1.0.7
This release fixes a bug where the incorrect Client version was reported to the admin portal.
1.0.6
This release contains connectivity fixes and performance improvements and is recommended for all users.
1.0.5
This release adds an IPC service for Windows to allow for better process isolation.
1.0.4
This release fixes a bug on Windows where system DNS could break after the Firezone Client was closed.
1.0.3
Maintenance release.
1.0.2
This release reverts a change that could cause connectivity issues seen by some users.
1.0.1
Update the upgrade URLs used to check for new versions.
#5901 Implements glob-like matching of domains for DNS resources.
#6361 Connections to Gateways are now sticky for the duration of the Client's session. This fixes potential issues maintaining long-lived TCP connections to Gateways in a high-availability setup.
1.1.6
#6276 Fixes a bug where relayed connections failed to establish after an idle period.
#6277 Fixes a bug where restrictive NATs caused connectivity problems.
1.1.5
#6107 Adds the ability to mark Resources as favorites.
#6181 Improves reliability of DNS resolution of non-resources.
1.1.4
Fixes an issue where DNS queries could time out on some networks.
1.1.3
Fixes an issue where the app would crash if IPv6 scopes were present in the DNS servers discovered on the local system.
1.1.2
Prevents Firezone's stub resolver from intercepting DNS record types besides A, AAAA, and PTR. These are now forwarded to your upstream DNS resolver.
1.1.1
Fixes an issue that could cause Resources to be unreachable a few hours after roaming networks.
Reduces noise in logs for the default log level.
1.1.0
Introduces the new DNS routing system supported by 1.1.0 Gateways which results in much more stable connections for DNS Resources, especially when wildcards are used.
Improves reliability when roaming between networks.
Closes idle connections to Gateways that have not seen traffic for more than 5 minutes which reduces power consumption when not accessing Resources.
Updates log file endings to JSONL and adds syslog-style logs for easier readability.
Fixes various crashes.
Note: Client versions 1.1.x are incompatible with Gateways running 1.0.x.
1.0.4
This release fixes a bug where the incorrect Client version could be reported to the admin portal.
1.0.3
This release contains connectivity bugfixes and performance improvements.
1.0.2
This release reverts a change that could cause connectivity issues in some cases.
1.0.1
This release contains reliability and performance fixes and is recommended for all users.
#5901 Implements glob-like matching of domains for DNS resources.
#6361 Connections to Gateways are now sticky for the duration of the Client's session to fix issues with long-lived TCP connections.
1.1.7
#6276 Fixes a bug where relayed connections failed to establish after an idle period.
#6277 Fixes a bug where restrictive NATs caused connectivity problems.
1.1.6
#6233 Fixes an issue where the IPC service can panic during DNS resolution.
1.1.5
#6163 Uses `systemd-resolved` DNS control by default on Linux
#6184 Mitigates a bug where the Client can panic if an internal channel fills up
#6181 Improves reliability of DNS resolution of non-resources.
1.1.4
#6143 Fixes an issue where DNS queries could time out on some networks.
1.1.3
Fixes an issue where a stale DNS cache could prevent traffic from routing to DNS Resources if they were updated while the Client was signed in.
1.1.2
Prevents Firezone's stub resolver from intercepting DNS record types besides A, AAAA, and PTR. These are now forwarded to your upstream DNS resolver.
1.1.1
Fixes an issue that could cause Resources to be unreachable a few hours after roaming networks.
Reduces noise in logs for the default log level.
1.1.0
Introduces the new DNS routing system supported by 1.1.0 Gateways which results in much more stable connections for DNS Resources, especially when wildcards are used.
Improves reliability when roaming between networks.
Closes idle connections to Gateways that have not seen traffic for more than 5 minutes which reduces power consumption when not accessing Resources.
Updates log file endings to JSONL and adds syslog-style logs for easier readability.
Note: Client versions 1.1.x are incompatible with Gateways running 1.0.x.
1.0.8
This is a maintenance release with no major user-facing changes.
1.0.7
This release fixes a bug where the incorrect Client version was reported to the admin portal.
1.0.6
This release contains connectivity fixes and performance improvements and is recommended for all users.
1.0.5
This is a maintenance release with no major user-facing changes.
1.0.4
This is a maintenance release with no major user-facing changes.
1.0.3
Maintenance release.
1.0.2
This release reverts a change that could cause connectivity issues seen by some users.
1.0.1
Update the upgrade URLs used to check for new versions.
