Skip to content

Fix a case where establishing an ESP session can take a long time

Andres Rodriguez requested to merge andresx7/openconnect:fix-for-long-esp-established into master

Fix a case where establishing an ESP session can take a long time

On my system, it takes 1 minute to establish an ESP session with the server. In this case the recv() calls all fail with EAGAIN since we have no data from the server.

Once we hit the vpninfo->dtls_attempt_period period (60s) timeout, then the server will reply with a ESP Legacy IP packet.

This change attempts to send ESP probes a little more eagerly if we are in a connecting state and we haven't received any data from the server.

Refer to: #601 (closed)

Merge request reports