Q22Mobile Computing
Question
Write a comprehensive note on Mobile IP, detailing the process of registration, tunneling, and reverse tunneling.
Answer
A definitive theoretical dissection of Mobile IP. Details the catastrophic failure of standard IP routing for mobility, and explains how the architectural pipeline of Agent Discovery, Registration, and IP-in-IP Encapsulation Tunneling mathematically shields the IP address from physical movement.
In standard TCP/IP architecture, an IP address serves two violently conflicting purposes: it is the mathematical Identity of the endpoint, and it is the physical Routing Coordinate. If a laptop moves from the Delhi network to the Mumbai network, its physical coordinate changes. Standard IP mathematically forces the laptop to drop its old IP and get a new one, catastrophically severing all active TCP connections. Mobile IP was engineered to violently shatter this link, decoupling Identity from Location.
- Home Address (HoA): The absolute, permanent mathematical Identity of the Mobile Node (MN) (e.g.,
192.168.1.50). - Care-of-Address (CoA): The temporary physical Routing Coordinate assigned to the MN when it roams to a foreign network (e.g.,
10.0.0.10). - Home Agent (HA): A router on the home network that mathematically defends the HoA.
- Foreign Agent (FA): A router on the visited network that assists the MN.
When the MN drives into the Mumbai network, it mathematically detects a new router (the FA) broadcasting ICMP Router Advertisements.
- The MN requests a temporary Care-of-Address (CoA) from the FA.
- The MN violently executes Registration. It sends a cryptographically signed message through the FA back to its Home Agent (HA) in Delhi, stating: "I am mathematically at CoA
10.0.0.10right now."
When a web server (Correspondent Node) sends a packet to the MN, it blindly addresses it to the permanent HoA (192.168.1.50).
- The packet physically arrives at the Delhi Home Network. The Home Agent violently intercepts it using Proxy ARP (telling the network, "I am the MN").
- The HA executes IP-in-IP Encapsulation. It takes the entire original IP packet and mathematically wraps it inside a brand new IP header addressed to the CoA (
10.0.0.10). - The HA blasts this encapsulated packet through the internet (the Tunnel).
- The Foreign Agent violently strips off the outer header and delivers the pristine original packet to the MN. The MN's TCP stack is completely unaware it ever moved.
Normally, the MN replies directly to the web server, bypassing the HA. However, enterprise firewalls execute strict "Ingress Filtering"—they will mathematically drop any packet exiting the Mumbai network that claims to have a Delhi Source IP (192.168.1.50). To survive this, the MN must violently execute Reverse Tunneling, encapsulating its outgoing packets and firing them backward through the FA to the HA, which then strips them and forwards them legally to the web server.