Mobile IPv6
Laboratory Work
Introduction
This work consists in configuring an IPv6 network supporting mobility and
in making a set of experiences used to improve your understanding about
Mobile IPv6. The software installed in the lab computers is the
MIPL Mobile IPV6 for Linux
which implements the mobile IPv6
draft-ietf-mobileip-ipv6-24.txt.
In order to become familiar with the MIPL software package you should read
first the following man pages and configuration examples:
This work will also demand the configuration and the activation of
radvd, which is responsible for the periodic dissemination of router
advsertisment messages. The following information shall be
studied:
The MIPv6 Configuration
The laboratory will be configured as follows.
quadro
porta
banc_3 banc_6
pc4---[HUB]---pc3----+ +----pc3---[HUB]---pc4
2000:0:0:3::/64 | | 2000:0:0:6::/64
| |
banc_2 | | banc_5
pc4---[HUB]---pc3--[HUB]-+ +-[HUB]--pc3---[HUB]---pc4
2000:0:0:2::/64 | | | | | | 2000:0:0:5::/64
| | | | | |
banc_1 | | | | | | banc_4
pc4---[HUB]---pc3---+ | | | | +----pc3---[HUB]---pc4
2000:0:0:1::/64 | | | | 2000:0:0:4::/64
| | | |
cne | | cnd
2000:0:0:e::c | | 2000:0:0:d::c
| |
2000:0:0:e::/64| |2000:0:0:d::/64
| |
[routerv6]
Each group is responsible for configuring its
PCs (tuxy4 and tuxy3) as follows:
tuxy4, Mobile Node (MN)
eth0=2000:0:0:y::1
|
| rede da bancada y = 2000:0:0:y::/64
|
eth0=2000:0:0:y::aa
tuxy3, router da rede y, Home Agent (HA), and radvd for 2000:0:0:y::/64
eth1= 2000:0:0:e|d::y
|
| rede de interligacao:
| - do lado esquerdo do lab 2000:0:0:e::/64 (e, de esquerdo)
| - do lado direito do lab 2000:0:0:d::/64 (d, de direito)
|
eth?=2000:0:0:e|d::aa
routerv6 (este router e' configurado pelo Prof/Tecnico)
Steps of the work
The following steps shall be carried out:
- Interconnect tuxy3 and tuxy4 by a hub/switch. Make sure
that this layer 2 network is isolated.
- Interconnect tuxy3 to the lab linux router via
the direita/esquerda hub/switch.
- Make a connection between your bancada and one of the
other bancadas of your side of the lab, so that the mobile
node (tuxy4) may visit another bancada.
- Configure tuxy3 as a router and verify its connecivity using
the ping6 command. As usual, you can use the commands:
- ifconfig (ex. /sbin/ifconfig eth0 inet6 add 2000:0:0:4::1/64),
- route, (ex. /sbin/route -A inet6 add 2000::/3 gw 2000:0:0:1::aa)
- route, (ex. /sbin/route -A inet6 add 2000:0:0:4::/64 dev eth0)
Do not forget to do
- /etc/network/options, set_ip_forward=yes
- echo "1" > /proc/sys/net/ipv6/conf/all/fowarding
- Configure and start radvd in tuxy3, so that so tuxy3 can start
announcing the network prefix for your bancada network (2000:0:0:y::/64).
Make sure the home agent facility is configured and observe the
router advertisment messages by using ethereal and capturing
messages in eth0
- Configure and start tuxy3 as an HomeAgent
- Start Ethereal in tuxy4, eth0.
- Configure and start tuxy4 as a Mobile Node.
- Observe the IP addresses of tuxy4, in particular the auto-configured
addresses. Save them
- Observe the routes in tuxy3.
- Ping6 the Correspondant Node of the other side of the lab.
- Make the Mobile Node to visit the network of another bancada.
While doing that, observe the output of ping6
- As soon as the ping6 resumes, on the visited bancada, stop
the ethereal and save the log. Observe also the IP addresses
of tuxy4, in the visited network.
- Observe the interfaces and routes configured in tuxy3. Save both
of them.
- Try to understand the ethereal log and, in particular,
the messages which are relevant to mobility.
Questions to answer at home
Please remember: 1) not more than 2 A4 pages; 2) deliver it in the
next lab.
- When the MN is at home, what are the IPv6 addresses associated
to eth0 and how were they formed?
- When the MN is at the visited network, what are the routes defined
at the HA? Please explain them.
- Using the ethernet log obtained in tuxy4, please identify the signalling
messages taht are related to mobility. Please explain their meaning.
- After route optimisation, the MN and the CN exchange packets directly.
Identify the echo request and echo reply packets observed
after route optimisation, and explain the values observed for each
of the fields related to mobility (IP addresses, destination and
routing headers).