Contents

Contents ● Fireware Help

Internet Access Through a Mobile VPN with IKEv2 Tunnel

For Mobile VPN with IKEv2, we support default-route VPN only. Split tunnel VPN is not supported.

Default-route VPN is the most secure option because it requires all remote user Internet traffic to be routed through the VPN tunnel to the Firebox. Then, the traffic is sent back out to the Internet. With this configuration, the Firebox is able to examine all traffic and provide increased security, although it uses more processing power and bandwidth.

Firebox Configuration

Your Firebox must be configured with dynamic NAT to receive the traffic from an IKEv2 user. Any policy that manages traffic going out to the Internet from behind the Firebox must be configured to allow the IKEv2 user traffic.

When you configure your default-route VPN:

  • Make sure that the IP addresses you have added to the IKEv2 address pool are included in your dynamic NAT configuration on the Firebox. This allows remote users to browse the Internet when they send all traffic to the Firebox.
    From Policy Manager, select Network > NAT.
  • Edit your policy configuration to allow connections from the IKEv2 -Users group through the external interface.
    For example, if you use WebBlocker to control web access, add the IKEv2 -Users group to the proxy policy that is configured with WebBlocker enabled.

Client Configuration

For compatibility with the Firebox, make sure that your IKEv2 client is configured for default-route (full tunnel) VPN:

  • In Windows 10, change the default setting from split tunnel to default route in the adapter settings for the IKEv2 connection.
  • In Windows 8.1 or macOS, keep the default setting, which is default-route.

You cannot configure this setting on mobile operating systems.

WatchGuard provides interoperability instructions to help our customers configure WatchGuard products to work with products created by other organizations. If you need more information or technical support about configuring a non-WatchGuard product, see the documentation and support resources for that product.

Enable Default-Route (Full Tunnel) in Windows

To enable default-route in Windows 8.1 and Windows 10:Closed
  1. In the Windows 8.1 or Windows 10, search for the Network and Sharing Center.
  2. Click Change Adapter Settings.
  3. Right-click the VPN connection name.
  4. Click Properties.
    The VPN Connection Properties dialog box appears.
  5. Select the Networking tab.
  6. Select Internet Protocol Version 4 (TCP/IPv4) in the list and click Properties.
  7. On the General tab, click Advanced.
    The Advanced TCP/IP Settings dialog box appears.
  8. On the IP Settings tab, select the Use default gateway on remote network check box.
If you prefer to use Windows PowerShell, follow these steps in Windows 10 to disable split tunneling:Closed
  1. In the Windows search bar, type powershell.
  2. In the search results, select Windows PowerShell.
    The PowerShell command interface window appears.
  3. To see the list of VPNs, type this command: get-vpnconnection
    The configuration of all available Windows VPNs appears in the PowerShell window.
  4. Identify the name of the mobile VPN connection you want to change, for example My Mobile VPN.
  5. To disable split tunneling for this VPN connection and use default route instead, type:
    set -vpnconnection -Name "My Mobile VPN" -SplitTunneling $false
  6. To exit PowerShell, type exit.
To enable default-route in Windows 7:Closed
  1. Select Control Panel > Network and Internet > Connect to a network.
  2. Right-click the VPN connection and select Properties.
    The VPN properties dialog box appears.
  3. Select the Networking tab.
  4. Select Internet Protocol Version 4 (TCP/IPv4) in the list and click Properties.
  5. Click Advanced.
    The Advanced TCP/IP Settings dialog box appears.
  6. On the IP Settings tab, select the Use default gateway on remote network check box.

See Also

Add Network Dynamic NAT Rules

Mobile VPN with IKEv2

Edit the Mobile VPN with IKEv2 Configuration

Give Us Feedback  ●   Get Support  ●   All Product Documentation  ●   Technical Search

© 2019 WatchGuard Technologies, Inc. All rights reserved. WatchGuard, the WatchGuard logo, and Firebox are trademarks or registered trademarks of WatchGuard Technologies, Inc. in the United States and/or other countries. All other tradenames are the property of their respective owners.