Reset Search
 

 

Article

KB40891 - Pulse Secure Client for Linux tunnel is disconnected after 3 ESP key exchanges (~45 - 60 minutes) due to incorrect TCP keep alive timer

« Go Back

Information

 
Last Modified Date8/28/2017 9:01 PM
Synopsis
This article describes an issue where Pulse Secure client for Linux fails to keep a stable tunnel and disconnecting after 3 ESP exchanges (roughly 45 - 60 minutes) due to incorrect TCP keep alive timer.
Problem or Goal
When using Pulse Secure client for Linux, the tunnel will remain stable for a specific time period and consistently disconnect at the same time interval.  

This behavior will largely depend on setting for idle or max. time for TCP connections within the network.  For example, if the idle or max. time for a TCP connection is set to 10 mins, end user may experience a disconnect every 10 mins.
Cause
This issue occurs due to TCP keep alive is determined by the operating system for Pulse Secure client for Linux. In most cases, Pulse Secure has found the TCP keep alive was set to 120 minutes.

This issue is only applicable to Pulse Secure client for Linux.  For Pulse Secure desktop client for macOS and Windows, the keep-alive on socket is set as 2 mins.
Solution
To resolve this issue, please upgrade Pulse Secure client for Linux to 5.2R9 and 5.3R2 or later.  The TCP keep alive has determined and set to 2 mins within the Pulse Secure for Linux client.
Related Links
Attachment 1 
Created ByVignesh Ramanan

Feedback

 

Was this article helpful?


   

Feedback

Please tell us how we can make this article more useful.

Characters Remaining: 255