When a 3rd party VPN client is connected on macOS device the following messages are visible on the WSS Agent UI:
WSS Agent Status
Connected to WSS for 00:01:07
Cloud Firewall Services: Enabled
Username: DOMAIN\username
Protocol: UDP
Datacenter: GFRVE
Error retrieving connection information (310)
Using connections from cache
On the WSS Agent support logs we have the following details:
[13:40:02]: WSS Agent has closed the connection. A new connection attempt will be made.
[13:40:07]: CTC failed (ec: 310 - The operation couldn't be completed. (kCFErrorDomainCFNetwork error 310.))
[13:40:13]: CTC failed (ec: 310 - The operation couldn't be completed. (kCFErrorDomainCFNetwork error 310.))
[13:40:19]: CTC failed (ec: 310 - The operation couldn't be completed. (kCFErrorDomainCFNetwork error 310.))
[13:40:25]: CTC failed (ec: 310 - The operation couldn't be completed. (kCFErrorDomainCFNetwork error 310.))
[13:40:31]: CTC failed (ec: 310 - The operation couldn't be completed. (kCFErrorDomainCFNetwork error 310.))
[13:40:32]: Attempting direct CTC request after 5 failures
[13:40:37]: CTC failed (ec: -1001 - The request timed out.)
[13:40:43]: CTC failed (ec: 310 - The operation gouldn't be completed. (kCFErrorDomainCFNetwork error 310. ))
[13:40:43]: CTC: trying to use cached CL after 6 failures
[13:40:43]: CTC: using the connect list cached in memory
macOS devices (confirmed on Sonoma and later)
3rd party VPN client
WSS Agent 9.x
The 3rd party VPN client installs the following network extensions:
Here are the standard cases with the agent on macOS and the addition of this 3rd party VPN client:
Broadcom engineering confirmed that the problem is related to a macOS configuration change that is outside of the WSS Agent control, and as we rely on the macOS Core Foundation API, we cannot work around the macOS configuration problem and it has to be fixed on the 3rd party client configuraiton / OS interactions.