Mobility and Multihoming (MOBIKE)


- Configure MOBIKE service.


Though MOBIKE service is enabled by default, you can change the MOBIKE's configuration by adding related settings on VPN Configuration tab of Web console.

- VPN Configuration[Tab] > VPN Realms[Left-Tree] > Realm ID: Realm name[Left-Tree] > IKE SA Settings[Left-Tree]: Click this tree node and show IKE SA Detailed Settings pane.

  1. Click Add Setting button and show the Add a New IKE SA Setting dialog.

  2. Select a setting name and enter a setting value on the dialog, then click OK button.

  3. Save this realm's configuration.

Name Value Default value Description
mobike enable or disable enable Enable or disable mobike service. MOBIKE is enabled by default.
mobike_init_hold_time Number of seconds. 1800 (seconds) The number of seconds to hold a VPN connection after MOBIKE service detects network outage. This setting is for an initiator.
mobike_init_keep_alive_interval Number of seconds. 60 (seconds) The number of interval seconds to retransmit a keep-alive packet after MOBIKE service detects network outage. This setting is for an initiator.
mobike_init_cache_additional_address enable or disable disable If this value is enabled, Rockhopper caches a received additional address and tries to use it as a secondary address when reconnecting VPN with the remote peer. This setting is for an initiator.
mobike_resp_routability_check enable or disable enable Enable or disable return routability check. This setting is for a responder.
mobike_resp_keep_alive_interval Number of seconds. 600 (seconds) The number of interval seconds to transmit a keep-alive packet. This setting is for a responder.
mobike_resp_keep_alive_retry_interval Number of seconds. 300 (seconds) The number of interval seconds to retransmit a keep-alive packet after MOBIKE service detects network outage. This setting is for a responder. (*1)
mobike_resp_keep_alive_max_retries Retransmission times. 12 (times) Retransmission times of keep-alive packets after MOBIKE service detects network outage. This setting is for a responder.

(*1): By default, a MOBIKE responder keeps a VPN connection alive for at least 3600 seconds (mobike_resp_keep_alive_retry_interval x mobike_resp_keep_alive_max_retries (300 seconds x 12 times)) after network outage occurs or a MOBIKE initiator's computer is suspended.


- Trigger events watched by MOBIKE service.


  • Change of network interface's status (link-up and link-down). (NETLINK)
  • Assignment and change of a network interface's IPv4 address. (NETLINK)
  • Retransmission time-out of IKEv2 messages. In many cases, this failure is detected by IKEv2 keep-alive service.
  • Change of a reflexive address mapped (assigned) by NAT gateway. This is detected by IKEv2 keep-alive service.

- Manually start routability check.


By default, it may take more than one minute to detect outage on the network path by IKEv2 keep-alive service. If you don't want to wait, you can manually start MOBIKE's routability check on Web Console. This feature is enabled for a MOBIKE initiator (client).

- Top[Tab] > Realm ID: Realm Name[Left-Tree] > Peer ID[Left-Tree]

  1. Click this tree node and show Realm ID: Peer ID pane.
  2. Push the Restart routability check button.

In addition, you can start it on VPN Client GUI (by selecting the Routability Check menu item).


- Prioritize network connections.


To prioritize your computer's connection between networks available at the same time, you can configure Primary interface and Secondary interface on the Network Interface pane of Web Console (VPN Configuration [Tab] > Realm ID: Realm Name [Left-Tree] > Network Interface [Left-Tree]).

When you check Use default route on the same pane, a wired interface (ethN) has a higher priority than a wireless interface (wlanN). On the other hand, if multiple interfaces of the same type (wired or wireless) are connected and multiple default routes exist, the priority is not decisive.


- RFCs


Back to Top