Is there an answer in another thread, or is this just being ignored? With remote work requirements due to the pandemic this is a big issue for us. We don't have someone there to physically check the device a couple of times a day.

Hi Matt. We're not gathering configuration information when we see the error message I included. That's when we're trying to open the actual VPN connection to the Gateway. How are we supposed to open the socket that's going to carry the gateway traffic in this case? That is, what Network Extension calls need to be completed before it will let us communicate with the Gateway? Kevin

includeAllNetworks covers a lot more than setting the default route. We need the extra assurance that all traffic will be handled, and that the tunnel won't leak. Defining it at config definition time is a pain, but I can work around that. The main issue I see at this point is that when I define includeAllNetworks and it takes effect, I can no longer connect to the gateway, even by IP address.

This happens when I try a connection using raw BSD socket() calls as well. What am I missing here?

The main problem is UI testing with XCTest, although it also happens with plain debugging. I've set a symbolic breakpoint on NSApplicationMain, and am runniing process handle -s false SIGCONT with an automatic continue. It works the first time, but if I stop and re-run the application it will occasionally still break with a SIGCONT, which is a little odd. Much, much, less frequent though.