IKEv2 routes all traffic over VPN tunnel

It seems that whenever I connect to a IKEv2 VPN, my routing table gets all messed up (I'm using route monitor to see the changes) and I also notice an entry in the console by nesessionmanager saying "Changing primary physical interface: ipsec0 => en0". Given that IKEv2 is not even present in the service order of interfaces, I find this very strange and disturbing.


Now, I don't know if this is built-in macOS behavior, but it's definitely not desirable in our corporate environment. Previously we used L2TP tunnels successfully, always unchecking the advanced option to "Send all traffic over VPN connection". There is, of course, no such option under advanced properties of IKEv2 connections.


Does anybody have any ideas or suggestions?


PS One more thing I have tried is to create the IKEv2 profile using the Apple Configurator 2, and I wanted to experiment with options, but so far I had no luck getting that to even work (unknown error when connecting to imported IKEv2 connection).



iMac 27", macOS 10.14

Posted on May 28, 2019 7:10 AM

Reply

Similar questions

10 replies

May 28, 2019 7:57 AM in response to BobTheFisherman

I am the admin. I tried calling Apple support to clarify this issue, but they told me they provide no such support and pointed me to the community. There is absolutely no reason that all traffic should be routed through the VPN tunnel unless specifically requested by either the server or the client.


If this is the wrong section, then move the discussion somewhere where it belongs, but please stick on topic.

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

IKEv2 routes all traffic over VPN tunnel

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.