IPv6 mobility: Mobile IPv6 and Network Mobility (NEMO)

Table of Contents

  1. Introduction
  2. Mobile IPv6
  3. Network Mobility (NEMO)
  4. Conclusion

Introduction

Internet Protocol version 6 (IPv6) is designed to provide better support for mobile devices than its predecessor, Internet Protocol version 4 (IPv4). IPv6 includes several features that enable mobile devices to move between different networks without losing their connections. In this blog post, we will discuss two important features of IPv6 mobility: Mobile IPv6 and Network Mobility (NEMO).

Mobile IPv6

Mobile IPv6 is a protocol that allows a mobile device to maintain its IP address and connection to the internet while moving between different networks. Mobile IPv6 enables a mobile device to change its point of attachment to the internet without changing its IP address. This allows the mobile device to maintain its connections and keep its session active while moving between networks.

Mobile IPv6 works by assigning a unique Home Address to the mobile device, which remains constant even when the device moves between networks. When the mobile device moves to a new network, it obtains a new Care-of Address from the new network. The Care-of Address is a temporary address assigned to the mobile device by the new network. The mobile device then sends a Binding Update message to its Home Agent, informing it of the new Care-of Address. The Home Agent updates its routing tables to ensure that traffic is forwarded to the mobile device's new Care-of Address.

Mobile IPv6 Components

Mobile IPv6 includes several components that enable a mobile device to maintain its connection while moving between networks. These components include:

Network Mobility (NEMO)

Network Mobility (NEMO) is a protocol that enables a mobile network to maintain its connections while moving between different networks. NEMO is designed for networks that have multiple mobile devices, such as vehicles or ships, that need to maintain their connections while moving between different networks.

NEMO works by assigning a unique Home Prefix to the mobile network, which remains constant even when the network moves between networks. When the network moves to a new network, it obtains a new Care-of Prefix from the new network. The Care-of Prefix is a temporary prefix assigned to the mobile network by the new network. The mobile network then sends a Binding Update message to its Home Agent, informing it of the new Care-of Prefix. The Home Agent updates its routing tables to ensure that traffic is forwarded to the mobile network's new Care-of Prefix.

NEMO Components

NEMO includes several components that enable a mobile network to maintain its connections while moving between networks. These components include:

Conclusion

IPv6 mobility provides several features that enable mobile devices and networks to move between different networks while maintaining their connections. Mobile IPv6 and Network Mobility (NEMO) are two important features of IPv6 mobility that enable mobile devices and networks to maintain their connections while moving between networks.

By using Mobile IPv6 and NEMO, mobile devices and networks can maintain their connections and keep their sessions active while moving between networks. This is especially important for mobile devices and networks that need to maintain their connections while on the move, such as vehicles, ships, or other mobile platforms.

Overall, Mobile IPv6 and NEMO are critical components of IPv6 mobility that network administrators need to understand to ensure that their networks are configured correctly to provide a seamless and uninterrupted mobile experience for their users.

170 Views
5 min. read
04 Feb 2023

Join our newsletter to keep updated from our news.

×

Your journey starts here; By completing the form below, you're taking the first step towards unlocking exclusive benefits tailored just for you.
Let's get started!

Full name

Email address ( please use corporate email )

I am interested in
Selling
I am interested in
Buying

Which RIR is acceptable?

RIPE
ARIN
APNIC

Which subnet size is acceptable?

/24 ( 256 IP Addresses )
/23 ( 512 IP Addresses )
/22 ( 1024 IP Addresses )
/21 ( 2048 IP Addresses )
/20 ( 4096 IP Addresses )
/19 ( 8192 IP Addresses )
/18 ( 16384 IP Addresses )
/17 ( 32768 IP Addresses )
/16 ( 65536 IP Addresses )
Other (Not in the list)

Select the RIR

RIPE
ARIN
APNIC

Select the subnet size ( select the biggest one if you have multiple subnets )

/24 ( 256 IP Addresses )
/23 ( 512 IP Addresses )
/22 ( 1024 IP Addresses )
/21 ( 2048 IP Addresses )
/20 ( 4096 IP Addresses )
/19 ( 8192 IP Addresses )
/18 ( 16384 IP Addresses )
/17 ( 32768 IP Addresses )
/16 ( 65536 IP Addresses )
Other (Not in the list)

Note

Send the form