1 / 8

MobileIP

MobileIP. MobileIP. Goal: Allow machines to roam around and maintain IP connectivity Problem: IP addresses => location This is important for efficient routing Solutions? DHCP? ok for relocation but not for ongoing connections

msneed
Download Presentation

MobileIP

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. MobileIP :

  2. MobileIP • Goal: Allow machines to roam around and maintain IP connectivity • Problem: IP addresses => location • This is important for efficient routing • Solutions? • DHCP? • ok for relocation but not for ongoing connections • Dynamic DNS (mobile nodes update name to IP address mapping as they move around)? • ok for relocation but not for ongoing connections :

  3. Mobile IP • Allows computer to roam and be reachable • Basic architecture • Home agent (HA) on home network • Foreign agent (FA) at remote network location • Home and foreign agents tunnel traffic • Non-optimal data flow :

  4. MobileIP • Mobile nodes have a permanent home address and a default local router called the “home agent” • The router nearest a nodes current location is called the “foreign agent” • Register with foreign agent when connect to network • Located much like the DHCP server :

  5. Forwarding Packets • Home agent impersonates the mobile host by changing the mapping from IP address to hardware address (“proxy ARP”) • Sends any packets destined for mobile host on to the foreign agent with IP encapsulation • Foreign agent strips off and does a special translation of the mobile nodes IP address to its current hardware address :

  6. 1. The Mobile Node registers itself with the Foreign Agent on the Foreign Subnet. The Foreign Agent opens an IP-IP tunnel to the Home Agent. The Home Agent begins listening for packets sent to 169.229.2.98. Register 2. The Fixed Node initiates a connection to the Mobile Node. It sends packets to the Mobile Node’s home IP address, 169.229.2.98. The packets are routed to the Home Subnet. 3. The Home Agent receives them, encapsulates them in IP-IP packets, and it sends them to the Foreign Agent. Encapsulated packets are addressed to 18.86.0.253. 4. The Foreign Agent decapsulates the IP-IP packets, and it sends them out on the Foreign Subnet. These packets will be addressed to 169.229.2.98. 5. The Mobile Node receives the packets, and it sends responses directly to the Fixed Node at 128.95.4.112. Mobile IP Example Foreign Agent Mobile Node 169.229.2.98 18.86.0.253 Foreign Subnet Fixed Node Internet 128.95.4.112 Home Subnet Home Agent 169.229.2.97 :

  7. Avoiding the Foreign Agent • Mobile host can also obtain a new IP address on the remote network and inform the home agent • The home agent can then resend the packet to the new IP address :

  8. Optimizations • What if two remote hosts are temporarily close together • If they want to send traffic to each other, why should it have to go all the way to their home agents and back again • Optimizations exist to allow the sending node to learn and cache the current location of a recipient to avoid this problem :

More Related