Original Publication Date: 07/28/2015
In June 2015, Apple posted the release of the iOS Edge Client version 2.0.5. Users should download this new version from the app store.
|383588||Edge Client now displays a diagnostics section that provides details on system and network information.|
|481019||Edge Client now supports widgets with iOS 8. User can quickly start VPN connections and connect to Edge Client.|
|483260||The Edge Client UI now supports iPhone 6 and iPhone 6 Plus devices.|
|487389||The client logs now displays session ID information to correlate with the server logs.|
|505302||Users can now access information such as VPN scope, tunnel type, and start type as session variables. The following session variables and their possible values are displayed below:
|476958||If a fully qualified host is specified in the proxy bypass list, users navigating to the host using the short form make use of the proxy in iOS 7, but this bypasses the proxy on iOS 8. iOS 8 takes into account the DNS suffix for proxy bypass.|
|519247||When users use a notification widget to connect to a VPN server that contains an untrusted server certificate, Edge Client rejects the connection attempt. Users fail to see a confirmation prompt. To establish a VPN connection using the notification widget, the device must trust the server certificate by default.|
|518473||On iOS 7, the native iOS Settings.app sometimes fails to display the changes users made in Edge Client. Use Edge Client instead of Settings.app.|
|516674||If users configure split tunneling in the network access resource, the "LAN address space" field is marked "required," while the "DNS Address Space" can be left blank. When "DNS Address Space" is left blank, Edge Client fails to pass DNS traffic through the VPN tunnel. To work around this issue, perform the following options:
|512960||When users trigger a VPN-on-Demand connection using Safari, it returns the following error message, Safari cannot open the page because the server cannot be found. This occurs even when users successfully establish the VPN tunnel and the VPN icon displays on the status bar. To work around this issue, refresh the page after establishing the VPN connection.|
|518576||After users trigger VPN-on-Demand, Safari displays the following error message, Safari could not open the page because the server stopped responding. Users fail to reach the internal resource until they refresh the web page. This only occurs when users try to reach a domain that ends in ".local."|
|499494||Previously, Edge Client might set an incorrect IPv6 DNS server after establishing a VPN connection. Edge Client now has validation to ensure the IPv6 DNS server values sent from the server are valid before applying them to the system.|
|491479||Previously, Edge Client used a hard-coded 15 minute timeout to re-establish tunnel connection. If Edge Client could not re-establish a connection to the server within that 15 minute timeout, the client automatically changed to the disconnected state. Edge Client now reconnects its tunnel connection based on the inactivity timeout value configured in the access policy. For on-demand connections, the reconnection timeout is the minimum value between inactivity timeout and on-demand disconnect timeout.|
|495151||Previously, after users installed Edge Client, the per-app VPN might not trigger on-demand unless the following options were performed:
|489485||In earlier versions, Edge Client collected device information when users launched the UI and started a VPN connection from the application. Some device information, however, was not available for on-demand connections unless users made a manual connection from the application. Unavailable device information included session.client.unique_id and session.client.platform_version. This issue is now fixed, and correctly reports device information to the APM server when using the iOS Connect On-Demand and iOS Per App VPN feature.|
|508385||On iOS 8, Apple’s VPN framework has a behavior change in which the “Never Connect” domains also affect DNS resolution rather than just VPN-on-Demand domain matching. In previous releases of iOS Edge Client, the VPN gateway (vpn.siterequest.com) was automatically added to the “Never Connect” domains. Because of that, on iOS 8 (and later), if the backend host names (example.vpn.siterequest.com) overlapped with the VPN gateway, the hostname would not be resolved by the internal DNS servers, even if VPN was already connected. This issue is now fixed; the VPN gateway is not automatically added to the “Never Connect” domains.|
|513114||Previously, on iOS 7 or later, Edge Client used a hard-coded link local IPv6 address for all devices. Edge Client now allows the server to determine its tunnel link local address for the client.|
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.