The Problem about Network Extension often killed in 3 minutes

Hi,

Our company is developing a VPN app on Mac. When I open the App And test, the VPN will be killed within 3 minutes sometimes . The information I get from /var/log/system.log is:

Jan 2 11:05:38 LEEdeMacBook-Pro com.apple.xpc.launchd[1] (com.skyvpn.app.mac.tunnel[3004]): Service exited due to signal: Killed: 9 sent by nesessionmanager[2566]

Jan 2 11:06:03 LEEdeMacBook-Pro com.apple.xpc.launchd[1] (com.skyvpn.app.mac.tunnel[3007]): Extension remained dirty for too long after trying to exit. Killing.

If I normally click the "dicConnect" button to disconnect VPN, the information obtained is:

Jan 2 11:07:21 LEEdeMacBook-Pro com.apple.xpc.launchd[1] (com.skyvpn.app.mac.tunnel[3035]): Service exited due to signal: Killed: 9 sent by nesessionmanager[2566]

We are very anxious to solve this problem, Can you give us some useful information, Thank you very much!

Anyone have idea,Thanks!

Anyone help me 😢

Some advice on how best to use DevForums:

  • The folks participating here come from all over the world, so it can take a while for the relevant people to see your post. Posting two pings within hours of your original quest doesn’t help.

  • What does help is posting your question to the right topic area. In this case the droid you’re looking for is Core OS > Networking. I’ve moved your post over there.

As to your technical question, I’m not sure what’s going on there. I’ll take a more detailed look the next time I swing by the Networking topic area.

Share and Enjoy

Quinn “The Eskimo!”
Apple Developer Relations, Developer Technical Support, Core OS/Hardware

let myEmail = "eskimo" + "1" + "@apple.com"

Could have a look at this old thread ; there are a lot of suggestions on possible causes for this type of problem. Written by Quinn, so trustworthy !

When I open the App and test, the VPN will be killed within 3 minutes sometimes.

There’s a specific known bug (r. 32073323) with Network Extension tunnel providers on macOS where the system will kill the provider after about 20 seconds. You can learn more about this in this thread.

However, this doesn’t really match the time you’ve described. Based on the info you’ve posted I don’t have any obvious things that you should look at. My recommendation is that you look deeper into the logging. On modern versions of macOS the system log (

/var/log/system.log
) only shows a tiny fraction of the logging that is available to you. You should run the Console app, enable Info and Debug messages, reproduce the problem, and then see if there are any other relevant log messages just before the kill.

Share and Enjoy

Quinn “The Eskimo!”
Apple Developer Relations, Developer Technical Support, Core OS/Hardware

let myEmail = "eskimo" + "1" + "@apple.com"

Hi eskimo,

Thank you very much for your patience and answer. As you mentioned, The more exact description of the bug I have encountered is that Network Extension tunnel providers on macOS where the system will kill the provider after about 20 seconds, rather than about 3 minutes, which is very similar with what mike.ly described in https://forums.developer.apple.com/message/252931#252931.


I get an important message in the the Console app when the Network Extension process was killed in that case again:


15:59:14.789551 +0800 neagent -[NEAgentExtension handleInitW:74 Extension com.skyvpn.app.mac.tunnel died unexpectedly


Is the same problem I encountered with the one that mike.ly encountered?

What should I do, very much looking forward to your reply again.

Thanks,

lslboy

The more exact description of the bug I have encountered is that Network Extension tunnel providers on macOS where the system will kill the provider after about 20 seconds …

OK, that does make it look like the same problem. Be aware that this problem has two aspects:

  • You must stop the tunnel and then start it again within about 5 seconds.

  • If you do that, the tunnel automatically stops after about 20 seconds.

Thus you can test whether this is really the same problem by adding a longer delay between the stop and start. Please do that and, once you’ve confirmed that you really are wrestling with the same issue, we can talk about mitigations.

Share and Enjoy

Quinn “The Eskimo!”
Apple Developer Relations, Developer Technical Support, Core OS/Hardware

let myEmail = "eskimo" + "1" + "@apple.com"

Hi eskimo,

I had tried many times and confirmed that I are wrestling with the same issue.

Next step, What should we do?

Thanks,

lslboy

What should we do?

You should feel free to file your own bug about this. While we already have a bug on file (r. 32073323), a few more dup’s won’t hurt.

On the workaround front, it’s really slim pickings. When the user is using your VPN app to start the VPN, you can avoid the problem by inserting an artificial delay between the VPN stopping and your next attempt to start it. Alas that doesn’t help if the user is starting your VPN via other means, like the menu extra or VPN On Demand.

Share and Enjoy

Quinn “The Eskimo!”
Apple Developer Relations, Developer Technical Support, Core OS/Hardware

let myEmail = "eskimo" + "1" + "@apple.com"
The Problem about Network Extension often killed in 3 minutes
 
 
Q