On October 27th 2015, OpenDNS released the Roaming Client for Windows version 2.0.33 for all customers on the stage track.
On November 2nd 2015, OpenDNS released the Roaming Client for Windows version 2.0.33 for customers on the first wave of the production release track.
On November 9th, 2015, OpenDNS released the Roaming Client for Windows version 2.0.33 for all customers on the second wave of the production release track. As customers on this release track are on on 1.7.269, they will receive the update to 2.0.33 which will include all changes in versions 2.0.1, 1.7.31 and 1.7.320. The exact changes in each of these version is noted below.
On December 2nd, 2015, OpenDNS released the Roaming Client for Windows version 2.0.33 for all customers on the final wave of the production release track. As customers on this release track are on on 1.7.269, they will receive the update to 2.0.33 which will include all changes in versions 2.0.1, 1.7.31 and 1.7.320. The exact changes in each of these version is noted below.
CHANGE SUMMARY (2.0.1 to 2.0.33)
- Resolved conflict between the F5 SSL VPN client and the Roaming Client in regard to a local NIC DNS storage interop failure
- Fixed a case where dnscyrpt's resolv.conf files could be erroneously populated with 127.0.0.1 (localhost)
- Improved handling of original persistent DNS settings, resolving issues that relate to restoring original settings in a variety of scenarios involving sleep, loss of power, ERC service shut down, restarting the ERC after it has crashed, VPN connections, etc.
- Minor fix to reset Umbrella IP blocking VPN tunnel when the Junos Pulse VPN disconnects
- The Roaming Client now uses the default store rather than separate memory and disk caching schemes
- Various logging improvements
Customers in the later release tracks (second stage of production release onward) will receive all of the changes in these previous versions in their single update:
CHANGE SUMMARY (1.7.371 to 2.0.1)
This version is functionally identical to version 1.7.371. The version number is incremented to reflect a new feature, IP Layer Enforcement, which will become available in the Umbrella dashboard over the next few weeks. Information about IP Layer Enforcement will become available in documentation and release emails.
- No change other than the version numbering.
CHANGE SUMMARY (1.7.320 to 1.7.371)
- Updated copyright and company branding to be Cisco compliant
- Unify the probes for both the Virtual Appliances and Trusted Networks, resulting in approximately %33 less probing.
- For any POST/GET/HEAD errors, the Roaming Client will retry using system proxy
- Implement a back-off process for normal registration and roaming profile creation (1 minute incremental back-off per registration failure to a max of 15 minutes)
- Send Virtual Appliance probes as EDNS with a bigger payload size to avoid truncation, and remove the deviceID in the Virtual Appliance probe.
- AnyConnect interoperability improvements. "Disable" IP Blocking while AnyConnect is connected: Umbrella interface is disconnected and IP blocking list downloads and tunnel probes are suspended until AnyConnect disconnects.
- Added additional logging to help diagnose a potential deadlock on disconnect/cleanup of failed VPN connections
- Added metrics for IP blocking VPN status
CHANGE SUMMARY (1.7.269 to 1.7.320)
This release includes a new feature that allows for the blocking of requests to malicious IP addresses that bypass DNS lookups from the Roaming Client. This feature is covered in more depth here: https://support.opendns.com/entries/58422194 and is an 'opt-in' feature that is not enabled by default.
In addition, the following changes are a part of this release:
- Resolved IP blocking connection-related race conditions
- Reduced the delay for newly registered Roaming Clients before an attempt to connect to the VPN IP blocking tunnel
- Improved handling of network location changes and fixed issue with set network location retries
- Suppressed network location pop-up on first IP blocking connection
- Handled adapter recovery with statically set DNS
- Updated to use a Microsoft FIPS-compliant version of AES
PREVIOUS RELEASE NOTES AVAILABLE HERE: