MC Unit3
MC Unit3
MC Unit3
Design Goals: Mobile IP was developed as a means for transparently dealing with problems
of mobile users. Mobile IP was designed to make the size and the frequency of required
routing updates as small as possible. It was designed to make it simple to implement mobile
node software. It was designed to avoid solutions that require mobile nodes to use multiple
addresses.
Requirements: There are several requirements for Mobile IP to make it as a standard. Some
of them are:
1. Compatibility: The whole architecture of internet is very huge and a new standard
cannot introduce changes to the applications or network protocols already in use.
Mobile IP is to be integrated into the existing operating systems. Also, for routers
also it may be possible to enhance its capabilities to support mobility instead of
changing the routers which is highly impossible. Mobile IP must not require special
media or MAC/LLC protocols, so it must use the same interfaces and mechanisms to
access the lower layers as IP does. Finally, end-systems enhanced with a mobile IP
implementation should still be able to communicate with fixed systems without
mobile IP.
2. Transparency: Mobility remains invisible for many higher layer protocols and
applications. Higher layers continue to work even if the mobile computer has
Mobile IP UNIT- II
DHCP
changed its point of attachment to the network and even notice a lower bandwidth
and some interruption in the service. As many of today’s applications have not been
designed to use in mobile environments, the effects of mobility will be higher delay
and lower bandwidth.
3. Scalability and efficiency: The efficiency of the network should not be affected even
if a new mechanism is introduced into the internet. Enhancing IP for mobility must
not generate many new messages flooding the whole network. Special care is
necessary to be taken considering the lower bandwidth of wireless links. Many
mobile systems have a wireless link to an attachment point. Therefore, only some
additional packets must be necessary between a mobile system and a node in the
network. It is indispensable for a mobile IP to be scalable over a large number of
participants in the whole internet, throughout the world.
4. Security: Mobility possesses many security problems. A minimum requirement is the
authentication of all messages related to the management of mobile IP. It must be
sure for the IP layer if it forwards a packet to a mobile host that this host really is the
receiver of the packet. The IP layer can only guarantee that the IP address of the
receiver is correct. There is no way to prevent faked IP addresses and other attacks.
The goal of a mobile IP can be summarized as: ‘supporting end-system mobility while
maintaining scalability, efficiency, and compatibility in all respects with existing applications
and Internet protocols’.
Foreign agent (FA): The FA can provide several services to the MN during its visit to the
foreign network. The FA can have the COA, acting as tunnel endpoint and forwarding
packets to the MN. The FA can be the default router for the MN. FAs can also provide
security services because they belong to the foreign network as opposed to the MN
which is only visiting. FA is implemented on a router for the subnet the MN attaches to.
Care-of address (COA): The COA defines the current location of the MN from an IP
point of view. All IP packets sent to the MN are delivered to the COA, not directly to the
IP address of the MN. Packet delivery toward the MN is done using a tunnel, i.e., the
COA marks the tunnel endpoint, i.e., the address where packets exit the tunnel. There
are two different possibilities for the location of the COA:
Foreign agent COA: The COA could be located at the FA, i.e., the COA is an IP
address of the FA. The FA is the tunnel end-point and forwards packets to the MN.
Many MN using the FA can share this COA as common COA.
Co-located COA: The COA is co-located if the MN temporarily acquired an
additional IP address which acts as COA. This address is now topologically correct,
and the tunnel endpoint is at the MN. Co-located addresses can be acquired using
services such as DHCP.
Home agent (HA): The HA provides several services for the MN and is located in the
home network. The tunnel for packets toward the MN starts at the HA. The HA
maintains a location registry, i.e., it is informed of the MN’s location by the current COA.
Three alternatives for the implementation of an HA exist.
1. The HA can be implemented on a router that is responsible for the home network.
This is obviously the best position, because without optimizations to mobile IP, all
packets for the MN have to go through the router anyway.
2. If changing the router’s software is not possible, the HA could also be implemented
on an arbitrary node in the subnet. One disadvantage of this solution is the double
3
Mobile IP UNIT- II
DHCP
crossing of the router by the packet if the MN is in a foreign network. A packet for
the MN comes in via the router; the HA sends it through the tunnel which again
crosses the router.
3. Finally, a home network is not necessary at all. The HA could be again on the ‘router’
but this time only acting as a manager for MNs belonging to a virtual home network.
All MNs are always in a foreign network with this solution.
A CN is connected via a router to the internet, as are the home network and the foreign
network. The HA is implemented on the router connecting the home network with the
internet, an FA is implemented on the router to the foreign network. The MN is currently in
the foreign network. The tunnel for packets toward the MN starts at the HA and ends at the
FA, for the FA has the COA in the above example.
IP packet delivery
Consider the above example in which a correspondent node (CN) wants to send an IP packet
to the MN. One of the requirements of mobile IP was to support hiding the mobility of the
MN. CN does not need to know anything about the MN’s current location and sends the
packet as usual to the IP address of MN as shown below.
5
Mobile IP UNIT- II
DHCP
Sending packets from the mobile node (MN) to the CN is comparatively simple. The
MN sends the packet as usual with its own fixed IP address as source and CN’s address as
destination (step 4). The router with the FA acts as default router and forwards the packet in
the same way as it would do for any other node in the foreign network. As long as CN is a
fixed node the remainder is in the fixed internet as usual. If CN were also a mobile node
residing in a foreign network, the same mechanisms as described in steps 1 through 3 would
apply now in the other direction.
Working of Mobile IP:- Mobile IP has two addresses for a mobile host: one home address and one
care- of address. The home address is permanent; the care-of address changes as the mobile host
moves from one network to another. To make the change of address transparent to the rest of
the Internet requires a home agent and a foreign agent. The specific function of an agent is
performed in the application layer. When the mobile host and the foreign agent are the same,
the care-of address is called a co-located care-of address. To communicate with a remote host, a
mobile host goes through three phases: agent discovery, registration, and data transfer.
Consider the scenario where there is one client and two servers are present. A typical
initialization of a DHCP client is shown below:
the client broadcasts a DHCPDISCOVER into the subnet. There might be a relay to forward
this broadcast. In the case shown, two servers receive this broadcast and determine the
configuration they can offer to the client. Servers reply to the client’s request with
DHCPOFFER and offer a list of configuration parameters. The client can now choose one of
the configurations offered. The client in turn replies to the servers, accepting one of the
configurations and rejecting the others using DHCPREQUEST. If a server receives a
DHCPREQUEST with a rejection, it can free the reserved configuration for other possible
Mobile IP UNIT- II
DHCP
clients. The server with the configuration accepted by the client now confirms the configuration with
DHCPACK. This completes the initialization phase. If a client leaves a subnet, it should release the
configuration received by the server using DHCPRELEASE. Now the server can free the context stored
for the client and offer the configuration again. The configuration a client gets from a server is only
leased for a certain amount of time, it has to be reconfirmed from time to time. Otherwise the server
will free the configuration. This timeout of configuration helps in the case of crashed nodes or nodes
moved away without releasing the context.
DHCP is a good candidate for supporting the acquisition of care-of addresses for mobile nodes.
The same holds for all other parameters needed, such as addresses of the default router, DNS servers,
the timeserver etc. A DHCP server should be located in the subnet of the access point of the mobile
node, or at least a DHCP relay should provide forwarding of the messages. RFC 3118 specifies
authentication for DHCP messages so as to provide protection from malicious DHCP servers. Without
authentication, a DHCP server cannot trust the mobile node and vice versa…
Mobile Ad hoc Networks (MANETs): Overview, Properties of a MANET,
spectrum of MANET, applications, routing and various routing algorithms,
security
in
MANET’s.
Mobile Ad hoc NETworks (MANETs) are wireless networks which are characterized by dynamic
topologies and no fixed infrastructure. Each node in a MANET is a computer that may be
required to act as both a host and a router and, as much, may be required to forward packets
between nodes which cannot directly communicate with one another. Each MANET node has
much smaller frequency spectrum requirements that that for a node in a fixed infrastructure
network. A MANET is an autonomous collection of mobile users that communicate over
relatively bandwidth constrained wireless links. Since the nodes are mobile, the network
topology may change rapidly and unpredictably over time. The network is decentralized, where
all network activity including discovering the topology and delivering messages must be
executed by the nodes themselves, i.e., routing functionality will be incorporated into mobile
nodes.
A mobile ad hoc network is a collection of wireless nodes that can dynamically be set up
anywhere and anytime without using any pre-existing fixed networkinfrastructure.
MANET- Characteristics
Dynamic network topology
Bandwidth constraints and variable link capacity
Energy constrained nodes
Multi-hop communications
Limited security
Autonomous terminal
Distributed operation
Light-weight terminals
1
Mobile Computing Unit-5
Mobile Ad Hoc Networks (MANETs)
Properties of MANETs
MANET enables fast establishment of networks. When anew network is to be established,
the only requirement is to provide a new set of nodes with limited wireless communication
range. A node has limited capability, that is, it can connect only to the nodes which are
nearby. Hence it consumes limited power.
A MANET node has the ability to discover a neighboring node and service. Using a service
discovery protocol, a node discovers the service of a nearby node and communicates to a
remote node in the MANET.
MANET nodes have peer-to-peer connectivity among themselves.
MANET nodes have independent computational, switching (or routing), and communication
capabilities.
The wireless connectivity range in MANETs includes only nearest node connectivity.
The failure of an intermediate node results in greater latency in communicating with the
remote server.
Limited bandwidth available between two intermediate nodes becomes a constraint for the
MANET. The node may have limited power and thus computations need to be energy-
efficient.
There is no access-point requirement in MANET. Only selected access points are provided
for connection to other networks or other MANETs.
MANET nodes can be the iPods, Palm handheld computers, Smartphones, PCs, smart labels,
smart sensors, and automobile-embedded systems\
MANET nodes can use different protocols, for example, IrDA, Bluetooth, ZigBee, 802.11,
GSM, and TCP/IP.MANET node performs data caching, saving, andaggregation.
MANET mobile device nodes interact seamlessly when they move with the nearby wireless
nodes, sensor nodes, and embedded devices in automobiles so that the seamless connectivity
is maintained between the devices.
2
Mobile Computing Unit-5
Mobile Ad Hoc Networks (MANETs)
MANET challenges
To design a good wireless ad hoc network, various challenges have to be taken into account:
Dynamic Topology: Nodes are free to move in an arbitrary fashion resulting in the topology
changing arbitrarily. This characteristic demands dynamic configuration of the network.
Limited security: Wireless networks are vulnerable to attack. Mobile ad hoc networks are
more vulnerable as by design any node should be able to join or leave the network at any
time. This requires flexibility and higher openness.
Limited Bandwidth: Wireless networks in general are bandwidth limited. In an ad hoc
network, it is all the more so because there is no backbone to handle or multiplex higher
bandwidth
Routing: Routing in a mobile ad hoc network is complex. This depends on many factors,
including finding the routing path, selection of routers, topology, protocol etc.
Applications of MANETS
The set of applications for MANETs is diverse, ranging from small, static networks that are
constrained by power sources, to large-scale, mobile, highly dynamic networks. The design of
network protocols for these networks is a complex issue. Regardless of the application, MANETs
need efficient distributed algorithms to determine network organization, link scheduling, and
routing. Some of the main application areas of MANET’s are:
Military battlefield– soldiers, tanks, planes. Ad- hoc networking would allow the military
to take advantage of commonplace network technology to maintain an information
network between the soldiers, vehicles, and military information headquarters.
Mobile Computing Unit-5
Mobile Ad Hoc Networks (MANETs)
Routing in MANET’s
Routing in Mobile Ad hoc networks is an important issue as these networks do not have
fixed infrastructure and routing requires distributed and cooperative actions from all nodes in
the network. MANET’s provide point to point routing similar to Internet routing. The major
difference between routing in MANET and regular internet is the route discovery mechanism.
Internet routing protocols such as RIP or OSPF have relatively long converge times, which is
acceptable for a wired network that has infrequent topology changes. However, a MANET has
a rapid topology changes due to node mobility making the traditional internet routing protocols
inappropriate. MANET-specific routing protocols have been proposed, that handle topology
changes well, but they have large control overhead and are not scalable for large networks.
Another major difference in the routing is the network address. In internet routing, the network
address (IP address) is hierarchical containing a network ID and a computer ID on that network.
In contrast, for most MANET’s the network address is simply an ID of the node in the network
and is not hierarchical. The routing protocol must use the entire address to decide the next
hop.
Mobile Computing Unit-5
Mobile Ad Hoc Networks (MANETs)
Unit-5
Mobile Ad Hoc Networks (MANETs)
• Hybrid algorithms: maintain routes to nearby nodes even if they are not
needed and maintain routes to far away nodes only when needed.
Example is Zone Routing Protocol (ZRP).
Which approach achieves a better trade-off depends on the traffic and mobilitypatterns.