Mobile IPv6 for Linux Guide (with USAGI patch)

For all nodes (HA, MN and CN)

• kernel umip-0.3 patch
  • kernel development git tree
• mip6d umip-0.3 (mipv6-daemon-umip-0.3.tar.gz or patch) - A set of patches for MIPL2 by USAGI
  • mip6d development git tree
• (optional for testing)iputils-mip6 - USAGI MIPv6 iputils tree

For HA

• radvd

For HA and MN

• IPsec-Tools (If you use IPsec with MIPv6, regarding as RFC3776)

HA specific configuration

• router: HA should be configured as an IPv6 router like accept_ra=0, forwarding=1.
• proxy ND: HA should be enabled proxy ND like proxy_ndp=1 (required to support returning-home).
• IPsec: See IPsec configuration.
• mip6d: See mip6d.conf(5). An example is mip6d-ha.conf.
• RD: Send RA with HA related options like "HA flag", HA address as network prefix and "router address flag" on prefix information. See also radvd.conf(5) for the detail if you use radvd. An example is radvd.conf.
  (optional): It is recommended smaller router advertisement interval. This also can be said to router on foreign link to where MN moves.
  

MN specific configuration

• IPsec: See IPsec configuration.
• mip6d: See mip6d.conf(5). An example is mip6d-mn.conf.

CN specific configuration

• See mip6d.conf(5) for mip6d. An example is mip6d-cn.conf.

IPsec configuration

• [HA,MN]See README.IPsec included by mip6d source tree. An example is setkey.conf.

HA boot sequence

1. Before starting mip6d, the following conditions should be satisfied:
   • Be ready as a router
   • Be ready for proxying ND (when using returing-home)
   • Assigned a global unicast address on home link interface, as HA address
   • Configured IPsec SA (when using IPsec with static keying)
   • (optional)syslogd is running
2. Run mip6d
3. After started mip6d:
   • Start RD

An easy example boot script to do the above is mipv6-ha.sh.

MN boot sequence

1. Before starting mip6d, the following conditions should be satisfied:
   • The interface is brought up before you run mip6d.
   • IPsec SA configuration (while using IPsec with static keying).
   • (optional)syslogd is running.
2. After you made sure these conditions, you can run mip6d.

An easy example boot script is mipv6-mn.sh.

CN boot sequence

1. Before starting mip6d, the following conditions should be satisfied:
   • (optional)syslogd is running
2. Run mip6d

An easy example boot script is mipv6-cn.sh.

Another examples

• experimental mip6d init script using LSB (for Debian Distribution)
  • Copy init_d-mip6d to /etc/init.d/mip6d
  • Copy default-mip6d to /etc/default/mip6d and edit it

Running

• When you have syslog, mip6d will say own start as a log. Then an easy way to verify the mip6d running is to take a look at it.
• [HA] Try virtual terminal to see mip6d information like below:
  $ telnet localhost 7777 Trying ::1... Trying 127.0.0.1... Connected to ip6-localhost. Escape character is '^]'. mip6d> pl eth1 3ffe:501:ffff:100:200:ff:fe00:a0a0/64 valid 2591997 / 2592000 preferred 604800 flags OAR mip6d>
  If you could get home prefix valid lifetime with positive value there, the HA is ready to serve. Otherwise, you should check the RA configuration.

Binding cache

• Try virtual terminal to see mip6d information like below:
  $ telnet localhost 7777 Trying ::1... Trying 127.0.0.1... Connected to ip6-localhost. Escape character is '^]'. mip6d> bc hoa 3ffe:501:ffff:100::1 status registered coa 3ffe:501:ffff:102::1 flags AH-- local 3ffe:501:ffff:100:200:ff:fe00:a0a0 lifetime 998 / 1000 seq 58722 unreach 0 mpa - / 0 retry 0 mip6d>
  If the node has binding cache correctly, you will get entries there with registered [HA], cached [CN] at "status" for each MN HoA respectively.

Binding update list

• [MN]Try virtual terminal to see mip6d information like below:
  $ telnet localhost 7777 Trying ::1... Connected to localhost. Escape character is '^]'. mip6d> bul == BUL_ENTRY == Home address 3ffe:501:ffff:100::1 Care-of address 3ffe:501:ffff:102::1 CN address 3ffe:501:ffff:100:200:ff:fe00:a0a0 lifetime = 262140, delay = 249033000 flags: IP6_MH_BU_HOME IP6_MH_BU_ACK ack ready lifetime 262124 / 262140 seq 26633 resend 0 delay 249033(after 249017s) mps 214747931 / 214747947 mip6d>
  If the MN sent BUs, you can find entries there for HA/CN respectively. To confirm home registration is completed, check the HA entry whose "ack" value is ready

Route optimization

We don't have an easy and good route optimization test for both-direction (other than using TAHI test or dumping packet). On the other hand, with ping6 command from USAGI git iputils-mip6 tree, you can check whether inbound echo reply is route-optimized or not.

• Prepare ping6 from iputils-mip6 git tree.
• Try ping6 with "-H" option to see extension headers carried by echo reply.

Examples:

• [HA,CN] Receiving a route-optimized echo reply from MN
  $ ping6 -H -I HACN_ADDR MN_ADDR ... 64 bytes from MN_ADDR[HAO]: icmp_seq=1 ttl=61 time=1.04 ms
• [MN] Receiving a route-optimized echo reply from HA,CN
  $ ping6 -H HACN_ADDR ... 64 bytes from HACN_ADDR[RT2]: icmp_seq=1 ttl=61 time=1.04 ms