IKEv2

  • warning: Creating default object from empty value in /var/sites/e/enterpriseios.com/public_html/modules/taxonomy/taxonomy.pages.inc on line 33.
  • strict warning: Only variables should be passed by reference in /var/sites/e/enterpriseios.com/public_html/sites/all/modules/contrib/captcha/captcha.inc on line 61.
  • strict warning: Declaration of views_handler_field_user_name::init() should be compatible with views_handler_field_user::init(&$view, $data) in /var/sites/e/enterpriseios.com/public_html/sites/all/modules/contrib/views/modules/user/views_handler_field_user_name.inc on line 61.

APNs with Always-On IKEv2 VPN

RDowson's picture
Your rating: None (6 votes)

We have an always-on IKEv2 VPN with a Global HTTP Proxy profile pointing to our internal proxy server.

We are using AirWatch in the cloud to manage the devices.

When the VPN is on APNs doesn't seem to be connecting the devices.

We have opened up the full 17.0.0.0/8 address block into our environment for TCP ports 5523, 2195, 2196 and 443 as described in this apple document - https://support.apple.com/en-gb/HT203609

Do we also need to apply the rule the other way so that the devices can connect back to APNs?

AirWatch seem to suggest that the devices don'e connect back to APNs and instead connect straight back to the console.

Can someone help with this please?

Recent Activity