Yes, it will then be routed through the VPN (logged out the INET type of the packets to verify).
So the behaviour is what can be expected, either the traffic goes through the VPN or the app(s) won't get any traffic through at all (as opposed to the destination IP mode which let traffic go outside the VPN if one doesn't setup the NEIPvX settings).
Thanks for your time!
patrikk
Users receive reputation points by contributing quality content to the forums.
Posts include post and replies published on the forums.
Post authors can mark replies as Accepted to indicate successful solutions.
Apple Developer Forums admins can mark replies as Apple Recommended to indicate an approved solution
Last seen
User for
Post
Replies
Boosts
Views
Activity
Thanks for your reply.
I cannot test binding on the macOS side since it is an iOS/iPadOS only app (what I know of, until silicon I guess :) ). I guess I could bind manually in a test-app though..
I tested it with and without settings for v6, and without it the app doesn't get internet (when using a ipv6-only address).
So I tested without settings for v4 as well (so we don't get any traffic at all), and then the app(s) got no internet connection at all.
So it seems that a Per-App VPN forces the traffic through, and if we don't register for packets/traffic the app(s) won't get internet.
My customer don't really want anyone to be able to alter them.. Not really sure why this is of great concern (since I don't really see any sensitive data that we store there..). Just thought it would be nice to be able to tell them if it is safe or not.Thanks for the answers!
Thanks eskimo.One more question; do you know if the configurations are encrypted (e.g. not only the sensistive parts which are stored in the keychain)? Our main concern is if it would be possible to access the configuration (rooted phone or so) and modify it..
The wake/sleep happens when the device goes into "real" sleep, e.g. it is NOT the same as locked. I think that the OS wakes the phone when e.g. some app have scheduled background fetch or when you receive background push (maybe the system periodically wakes as well). During sleep you won't get any cpu time at all (according to my observations).You should note that the OS shuts off WiFi when going into sleep and starts it when waking up.Depending on how often you need to send the heartbeat, you should probably re-establish the tunnel upon waking up.
Alright.. Do you happen to know why they do so?Thx for taking time to inform me at least 🙂