Serverless IP Mobility

1
Server-less IP Mobility

• By Tiffanie Jones (Albany State University)
• Chuck Moran (Auburn University)
• Mid-Term Presentation- July 5, 2005

2
Abstract

• This project presents a new concept for achieving
  IP mobility. Currently, the concept that is often
  preferred to handle this form of mobility is a
  protocol called IP Mobility Support or simply
  Mobile IP. However, the Mobile IP Protocol
  implementation for IP mobility is too heavy
  weighted, expensive, and time consuming. Overall,
  the main focus of this project is to implement a
  less expensive and light weighted concept that
  conquers IP mobility in a conservative manner.

3
Introduction

• With todays increasing usage of wireless
  technology, mobile applications are in demand in
  the computing world. With such demands, the
  significance of supporting IP mobility is viewed
  as a priority. IP mobility is looked upon in this
  sense because when one uses a mobile
  application,for example VoIP, the ability to
  switch between networks and still maintain an
  active connection is relevant.

4
Disadvantages of Mobile IP

• Uses servers to track the mobile nodes
  movements to networks
• Relies on hardware
• Creates delay

5
IP Mobility Module

• Provides a similar function to that of Mobile IP
  
• Uses Host machines only

6
Concept of Module
7
(No Transcript)
8
Netfilter Hook Points

• PRE_ROUTING
• LOCAL_IN
• LOCAL_OUT
• POST_ROUTING

9
Dynamic list of Connections

• Source IP
• Destination IP
• Source Port
• Destination Port

10
Protocol 100

• Old IP
• New IP
• Time Stamp

11
LOCAL_OUT

• Checks outgoing packets
• It changes the IP to new address and recalculates
  the checksum before sending onto
  NF_IP_POST_ROUTING
• Checks to see if its own IP has changed

12
PRE_ROUTING

• Checks to see if its own IP address has changed

13
LOCAL_IN

• Checks the packet protocol
• If the packet is another protocol packet

14
Existing Module Problems

• Connection List
• TCP Code
• Packet loss and Latency times
• Handoff

15
Solutions to Problems

• Add the port information to connection list
• Check connection to see if it is still
  alive(ipconntrack )
• Code for testing the TCP portion of the module is
  currently being investigated
• Measure by checking the time between packets
  before, during, and after the IP change
• Implement SyncScan