Project

General

Profile

MOBIKE » History » Version 4

Martin Willi, 01.04.2008 11:13

1 1 Martin Willi
2 4 Martin Willi
h1. MOBIKE
3 4 Martin Willi
4 4 Martin Willi
5 1 Martin Willi
The MOBIKE IKEv2 extension allows an initiator to change its network attachement point (e.g. roam to an other interface/address).
6 1 Martin Willi
7 4 Martin Willi
strongSwan implements MOBIKE by watching interfaces, addresses and routes. If the configuration changes, route lookups are done to find a better path than the current one and changes this path using a MOBIKE update (_UPDATE_SA_ADDRESS_).
8 1 Martin Willi
9 4 Martin Willi
strongSwan is running the MOBIKE protocol per default as soon as you specify _keyexchange=ikev2_. MOBIKE can be disabled on a per-connection basis, though, by adding the parameter _mobike=no_ to the corresponding connection definition in _ipsec.conf_. Please be aware that with MOBIKE enabled, strongSwan will switch to UDP port 4500 starting with the IKE_AUTH request which includes a _MOBIKE_SUPPORTED_ notification even if no NAT has been detected. Thus make sure to open the NAT-traversal port UDP/4500 on any firewalls en route. 
10 2 Martin Willi
11 3 Martin Willi
strongSwan's MOBIKE implementation is currently usable, but needs further testing to work more reliable.