Knowledge Articles
Security Advisories
Related Articles
KB44610 - Pulse iOS Client : External release of 9.5.0 Pulse iOS Beta Client
KB40385 - Layer 4 (L4) Per App VPN does not tunnel UDP based traffic on iOS devices.
KB43813 - Certificate authentication fails with error "Missing or Invalid Certificate" or other applications that rely on certificate authentication may fail after upgrading to the Pulse Mobile 7.0.0 for iOS
KB40340 - Support for Fully Qualified Domain Name (FQDN) Split Tunneling with Per-App VPN in Pulse Mobile for iOS 6.1.0
KB44592 - Pulse Desktop Client for macOS Open Issues on Big Sur
KB40909 - Fully Qualified Domain Name (FQDN) Split Tunnel or Layer 3 Per-App VPN does not support split tunneling with Pulse Mobile for iOS
KB9218 - What client side logs are required when I open a Network Connect (NC) or Pulse Secure Client VPN case?
KB40360 - VPN On Demand for iOS with Pulse WorkSpace and Pulse Connect Secure
KB43785 - Pulse Mobile for iOS is intermittently disconnecting and end users are unable to connect after upgrading to Pulse Mobile for iOS 6.7.0.76583
KB43890 - iOS device certificate details are password protected until installed after enrolling the device using Microsoft InTune with Pulse for iOS 7.0.0
What would you like to know?
Reset Search
Search
< Back to search results
KB44591 - Pulse iOS Client : L4 Per App VPN traffic flow stops intermittently in iOS 14
Printable View
«
Go Back
Information
Last Modified Date
9/19/2020 4:39 AM
Synopsis
Pulse iOS Client : L4 Per App VPN traffic flow stops intermittently in iOS 14
This article describes the scenario where L4 Per-App VPN traffic stops intermittently during certain conditions on iOS 14.
Problem or Goal
L4 Per app VPN traffic flow stops working intermittently in iOS 14 for the following conditions:
When streaming apps are used, the traffic gets stuck but recovers from the same point or from the start depending on the application in use.
When downloads greater than 10 MB are initiated, the flow gets stuck and never recovers.
Note:
Web Pages are not affected by this issue.
Pulse iOS clients 9.2.0 or prior are affected.
Cause
Unknown (Work in progress to determine cause)
Solution
Currently, there are no workarounds. However, the fix will be part of Pulse iOS 9.4.0 (Early Dec 2020 Release - Tentative)
Related Links
Attachment 1
Created By
Raghu Kumar
Feedback
Was this article helpful?
Feedback
Please tell us how we can make this article more useful.
Characters Remaining:
255