VPN not working after macos13 update with includeAllNetworks=true

Hi,

I have a problem with the VPN profile on macos 13 with some custom VPN protocol. I've run the VPN application when I had macos 12.x. The application worked fine, created system configuration. Then I've updated the os to 13.

After the update I'm not able to connect to VPN when includeAllNetworks=true. The defaultPath is always unsatisfied, so the tunnel is not able to connect to VPN server. The system routes seam to be ok using netstat and route.

If VPN is started with includeAllNetworks=false it works.

On logs I've saw that when includeAllNetworks=true, nesessionmanager prints the following errors:

error	08:01:59.652919+0100	nesessionmanager	-[NESMVPNSession setDefaultDropAll]: VPN addLocalNetworksExceptionWithOrder failed for Control priority
error	08:01:59.653105+0100	nesessionmanager	VPN-includeAllNetworks evaluateConfiguration failed
error	08:01:59.653479+0100	nesessionmanager	-[NESMVPNSession setDefaultDropAll]: VPN addLocalNetworksExceptionWithOrder failed for HighRestricted priority
error	08:01:59.653799+0100	nesessionmanager	VPN-includeAllNetworks evaluateConfiguration (High) failed
error	08:01:59.653894+0100	nesessionmanager	VPN Could not apply control policies
error	08:01:59.653908+0100	nesessionmanager	VPN Could not apply High control policies
....
info	08:01:59.774079+0100	nesessionmanager	nw_path_necp_update_evaluator_block_invoke [46BD53DF-BA48-4059-9DE6-9A2F61E97B1E <NULL> generic, attribution: developer]
	path: unsatisfied (Path was denied by NECP policy), interface: en0[802.11], ipv4, ipv6
.....
default	08:01:59.774149+0100	nesessionmanager	Changing primary wifi interface: en0 => (null)
default	08:01:59.774182+0100	nesessionmanager	Changing primary physical interface: en0 => (null)

If I delete the VPN profiles from system and the app recreates them, everything works also for includeAllNetworks=true.

Since no error is received, do you have any suggestions how to fix or detect this?

Thanks

Accepted Reply

Fixed with macos 13.3.

Add a Comment

Replies

Fixed with macos 13.3.

Add a Comment