Original Publication Date: 04/18/2014
In September 2013, Apple posted the release of the iOS Edge Client version 1.0.6. The iOS Edge Client version 1.0.6 includes support for iOS 7. Users should download this new version from the app store. Please refer to the BIG-IP Edge Apps Client Compatibility Matrix to determine what app versions and hotfix versions are required for support with your BIG-IP version.
|430575||Edge Client was updated to handle UDID with iOS 7.|
|388675||Edge Client is now compatible with iOS 6.|
|397455||Edge Client is now compatible with iPhone 5 and iPod Touch 5th generation.|
With iOS Edge Client 1.0.6, Edge Client is no longer supported on iOS 5. iOS 5 users must remain on iOS Edge Client 1.0.5.
|430575||The session variable session.client.mac_address has been removed from the client info in this release.|
|438885||The documentation does not explicitly mention that public-side proxy servers are not supported.|
There are no fixes in this release.
|383083||Previously, when sending an Edge Client command through a URL, the Edge Client prompted the user for confirmation of any change. At present, the user is prompted only when creating a new server configuration on the Edge Client.|
|383086||The Disconnect Idle Timeout setting is now configurable through server settings in Access Policy Manager version 11.4, and set to 120 seconds for other server versions.|
|384830, 400979, 408517, 412478, 418457||Some vulnerabilities were fixed and improvements made, in handling of OpenSSL libraries, SSL renegotiation, TLS, and DTLS.|
|386713||Previously, a default IPv6 route was added when split tunneling was enabled. This route was used only if the client had no IPv6 configuration, but should have been inactive. At present, default IPv6 tunnels are inactive.|
|387521||Previously, specifying a route of 0.0.0.0/0.0.0.0 did not correctly force all traffic through the tunnel on iOS devices. At present, specifying such a route forces all traffic through the tunnel on iOS devices.|
|397177||Memory handling issues were fixed.|
|399931||Some screen alignment issues were fixed.|
|399938||Previously, if the Edge Client started an access policy that had no Logon Page access policy item, a blank page appeared in the Edge Client. At present, if the access policy does not include a Logon Page item, a blank page does not appear in Edge Client.|
|400144||Some wording errors were fixed in the client.|
|417727||Previously, if the Edge Client connected to a server that did not support IPv6, and the option Force all traffic through tunnel was enabled on the network access tunnel, IPv6 traffic was not blocked. At present, IPv6 traffic is not allowed by the client when the server does not support IPv6, and Force all traffic through tunnel is enabled.|
|419598||Previously, when using a managed Edge Client configuration created by MDM or iPCU, users could not enter passwords or user names, even when required. At present, user names and passwords can be entered in such configurations.|
For additional information, please visit http://www.f5.com.
You can find additional support resources and technical documentation through a variety of sources.
Free self-service tools give you 24x7 access to a wealth of knowledge and technical support. Whether it is providing quick answers to questions, training your staff, or handling entire implementations from design to deployment, F5 services teams are ready to ensure that you get the most from your F5 technology.
AskF5 is your storehouse for thousands of solutions to help you manage your F5 products more effectively. Whether you want to search the knowledge base periodically to research a solution, or you need the most recent news about your F5 products, AskF5 is your source.
The F5 DevCentral community helps you get more from F5 products and technologies. You can connect with user groups, learn about the latest F5 tools, and discuss F5 products and technology.