Hi, I developed a system extension that uses the content filter providers of the network extension. When I am using a VPN, I turn on the network extension and the VPN is disconnected. Can this problem be avoided? How to prevent VPN disconnection
which should belong to B.
OK. That makes things tricky. DTS stopped supporting legacy ad hoc VPN techniques back when Apple introduced NE support on the Mac. That means I only have limited experience with them. However, the experience I do have suggests they use a variety of different techniques, meaning it’s hard to predict exact how they’ll interact with other NE providers.
is it true that when I turn on the network filter, the tcp connection that already exists with the ip will not be cut off by the NEFilterActionFilterData rule behind it.
No. As a general rule, starting an NE filter will close any existing network connections regardless of how the filter is configured. That gives the filter the opportunity to inspect the replacement connections.
Not all filters want this but, sadly, there’s no way to opt out. We have a bug on file requesting an API for that (r. 99402484).
The wrinkle here is VPN. I think that this closing of connections wouldn’t apply to an NE packet tunnel provider because it exists ‘lower’ in the networking stack. However, I haven’t ever testing that. And in this case it doesn’t really matter because the VPN isn’t using NE anyway.
Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"