I'm investigating an issue when deploying my VPN agent via Jamf during initial setup on clean macOS machines.
The Network Extension process starts immediately after installation, but its Transparent Proxy provider starts only after a user logs in. I tried to reboot, and still observed the transparent proxy start fails.
10:00:52 === system boot
10:00:57.535 NESMTransparentProxySession[Primary Tunnel:Prisma Access Agent:68CAC11B-...]: Received a start command from PASrv[303]
10:00:57.538 NESMTransparentProxySession[...]: No network available <<<<<<<<<
10:00:57.541 NESMTransparentProxySession[...]: status changed to disconnected, last stop reason No network available <<<<<<<<<
10:01:21.541 NESMTransparentProxySession[...]: handleChangeEventForRankedInterfaces - stopped 0 status disconnected includeAllNetworks 0
10:01:26.373 NESMTransparentProxySession[...]: handleChangeEventForRankedInterfaces - stopped 0 status disconnected includeAllNetworks 0
10:06:01.293 NESMTransparentProxySession[...]: Received a start command from user_context[1547]
10:06:01.615 NESMTransparentProxySession[...]: status changed to connectedOur product requires pre-login functionality. Is this behavior expected, and how can we enable the Transparent Proxy provider before user login?
I suspect a race between network availability and the attempt to start the Transparent Proxy. The issue does not occur with Ethernet, possibly because connectivity becomes available earlier than with Wi-Fi.
Should we call startVPNTunnel again once connectivity becomes available? If so, what is the recommended way to detect this network transition?
4
0
134