EAACK - Enhanced Adaptive Acknowledgment
EAACK - Enhanced Adaptive Acknowledgment
Mathew5.
Abstract - Wireless networks are currently having the ability to move in all directions and can
dominating over wired networks in many forward packets dynamically. The proper
applications .Mobility and scalability are some of communication in MANET happens by nodes
the features that has led to make wireless networks cooperating with each other. The nodes are added
more popular. Out of the many wireless network
Mobile Ad-Hoc network (MANET) are the most and removed dynamically and this makes the
popular. They have a highly dynamic and random MANET having a dynamic network topology. The
topology. Essentially the ad hoc network is a communication among nodes within the MANET
collection of nodes communicating with each other can be done directly.
by forming a multi-hop network. MANET is used in
many military applications because of its self MANET is independent of centralized infrastructure
configuring nature. However Mobile Ad-Hoc and is used when there is no specific predefined
Network (MANET) has much vulnerability towards infrastructure. In MANET each node can be a
security attacks due to its features of open medium,
transmitter or receiver or can act as a router
limited physical security, dynamic changing
topology, lack of centralized monitoring and forwarding packet and thus provides the network to
organization point. work in a decentralized manner.
Index Terms – AACK, Watchdog scheme, The decentralized and dynamic nature of MANET
TWOACK, ACK, SACK, MRA makes this more exposed to malicious attack. The
presence of any kind of malicious nodes can affect
NOMENCLATURE the MANET and can lead to severe packet dropping
in transmission. Such defamatory nodes pretend to
The different abbreviations used in the paper are: be cooperative but will drop the packets instead of
ACK - acknowledgment forwarding it to the next hop. This will in turn affect
the performance of the network and hence proper
SACK - Secure acknowledgment detection of such defamatory nodes is necessary.
parts – Watchdog and Pathrater. Here each node acts as acknowledgment then the link is considered to be
a Watchdog node and continuously listens to its next misbehaving. TWOACK scheme can solve receiver
hop transmission[1]. If it understands that the next problem which is present with Watchdog scheme. But
node fails to forward the packet within a predefined it adds an additional overhead with the packets being
time limit it increments its failure counter. Once the sent such that it needs to provide acknowledgment to
failure counter reaches a particular limit the Watchdog nodes which are two hops away. MANET heavily
node will report it as misbehaving. Then it incorporates depends upon battery life of nodes and hence such
Pathrater which directs the routing protocols to avoid additional overheads can cause significant problems in
the reported nodes in the further transmissions. the life span of the network.
Pathrater picks reliable route based on the knowledge Fig 2.2 TWOACK Mechanism
about the misbehaving nodes. Each node uses this
information and creates path metric by calculating In TWOACK approach node Z needs to send an
average of node ratings created by each node about its acknowledgment to node X in case of successful
neighbour. Source node S can transfer packets to D if reception of data packet. Hence after every triplet of
there is a direct connection between them. If such a nodes, an acknowledgment is generated which denotes
path is absent it can make use of intermediate nodes the successful transmission of the data packet.
like X, Y and Z to send the packet. Here the dashed
2.3 AACK
lines shows that X is within transmission range of Y
and can overhear transmission of Y. Solid lines AACK stands for Adaptive Acknowledgment. AACK
represent the direct connections existing between was proposed as a system which incorporates the
nodes. S transfers packet to X and X forwards it to Y. X functionalities of both TWOACK and the normal end-
can overhear the transmission done by Y and can verify to-end acknowledgment passing scheme. The
if the packet is forwarded successfully. advantage of AACK is that it significantly decreases
network overhead for the packets being sent while
But Watchdog fails to detect misbehaving nodes in case
compared to TWOACK scheme. But both AACK and
of
TWOACK schemes cannot detect the malicious nodes
1. Ambiguous collision – Prevents X from in the network if any false misbehavior report or forged
overhearing if some other node is sending packets acknowledgment is created. If the sender has different
to X. destinations it will choose among two approaches –
2. Receiver collision – X cannot check if Z received AACK and TACK(similar to TWOACK). It will use a
packet forwarded by Y. switching system to select between this nodes. The
3. False misbehavior – Nodes can falsely produce default mode is AACK. On sending the data packet the
reports about nodes. sender will inform the intermediate nodes about the
4. Packet dropping – Nodes may drop packets. flow mode and acknowledgments will be sent
accordingly. In AACK mode the destination node sends
2.2 TWOACK only one acknowledgment to the sender node instead of
sending acknowledgments for every three consecutive
In this technique the packets send by a node are nodes. But here the long paths can cause delay and
expected to be received by those nodes which are two hence it may cause packet loss.
hops away from it. Thus it can detect the misbehaving
links by acknowledging every packets send over a set
of three consecutive nodes. A node is required to give
the acknowledgment to the node which is located two
hops away from it. If a node is not getting an
.SACK (Secure ACK): The client can be either a sender, a receiver or can be
any intermediate node. The sender transfer the file
If the receiver feels any data or packet loss in received through an optimal path an in case of any drop will find
data , the receiver send back an SACK. The SACK an alternate path. The receiver on receiving the entire
allows only the source node to be aware of the number packet send back corresponding acknowledgment.
of packets received properly at destination. These 5.0 MODULE DESCRIPTION
details will not be visible to intermediate nodes and
hence the acknowledgment is secured. As stated earlier there are different modules or
subsections on implementing EAACK. This
MRA (Misbehaviour Report Authentication): primarily includes two sides - Client side and Server
The MRA in the proposed system will find out the side. The admin of the EAACK network is on the
packet dropping at each node if there is any and server side and can do the tasks like configuration of
identifies the misbehaving node. In case of any nodes ad routes, conducting MRA analysis and so
misbehaviour report the same packets are sent through on. The client side where the users can actually send
an alternate route. and receive files as packets can be active only if
EAACK server is active. If the admin chooses to
There can be certain false misbehaving nodes within stop the server then the clients side can sent no more
the network. Some of the intermediate nodes will be data.
sending an ACK to the source node but the packets
need not be reached at the destination. For every
Node configuration
Once the admin has login it can configure the nodes Fig 5.2 Route Configuration
which needs to communicate with each other in the
File operations
network. Each node can be registered in the network
by using a node id - which will be the name of the In this module there are some file operations like file
particular node. Each node is uniquely identified by selection, file splitting, file transfer etc. These are
using its IP number and port number. A single operations done on the sender side. There are two
system can have more than one nodes. So the phases before sending the file and these are:
presence of port number helps in identifying the
nodes in such cases. 3.1. RSA encryption/decryption
Traffic log:
9.0 RESULT
Figure 9.5 Server not found pops out when the client helps in finding out the packet drops and the false
tries to login before the server starts. misbehavior of nodes. Apart from detecting the
malicious nodes this project helps at avoiding certain
problems with the previous implemented systems
which includes:
1. Ambiguous collision
2. Receiver collision
3. False misbehavior
4. Packet dropping
REFERENCES