Routing Misbehavior Detection In MANETs using 2ACK scheme : PROJECT PRESENTATION ON Routing Misbehavior Detection In MANETs using 2ACK scheme PROJECT GUIDE : S.NAGARJUNA REDDY TEAM MEMBERS: TEAM MEMBERS POOJITHA REDDY K.VIJITHA N.VIJAYA JYOTHSNA What is MANET?????: What is MANET????? A mobile ad hoc network (MANET) is a collection of mobile nodes (hosts) which communicate with each other via wireless links either directly or relying on other nodes as routers Applications for MANETs are wide ranging and have use in many critical situations. Purpose of project: Purpose of project MANETs are designed based on the assumption that all participating nodes are fully cooperative. There is a possibility that when a sender chooses an intermediate link to send some message to a destination, the intermediate link may pose problems such as, the intermediate node may not forward the packets to destination. Purpose of project: Purpose of project Selfish node may attempt to benefit from other nodes, but refuse to share its own resources. In MANETs, as there is no retransmission of packets once it is sent, care must be taken not to loose packets. Hence, we can use 2ACK scheme to detect and mitigate the effect of such routing misbehavior in MANETs . Overview Of The Project: Overview Of The Project Here in this 2ACK scheme the destination node of the next hop link will send back a 2 hop acknowledgement called 2ACK to indicate that the data packet has been received successfully. Overview Of The Project: Overview Of The Project This can be carried out in 4 ways If 2ACK time < wait time & contents not altered----message is given to sender that the link is working properly. If 2ACK time > wait time & contents not altered----message is given to sender that the link is misbehaving. If 2ACK time > wait time & contents altered----message is given to sender message is given to sender that the link is misbehaving and integrity is lost. Overview Of The Project: Overview Of The Project If 2ACK time < wait time & contents altered----message is given to sender message is given to sender that the link is working and integrity is lost. At destination, a hash code will be generated and compared with the sender’s hash code to check the integrity of message. Thus if link misbehaves, sender stops to transmit messages –no packets loss Division of modules: Division of modules Node creation, discovery of route and checking the path by source node to send message. Message Transfer to the available path. Route Maintenance. Cache Updating for misbehavior node identification. Node creation: Node creation T he node which is going to be created has node name, and destination node names. The node consists of message box where you can type the message. You can see the message tab along with node tab. We can select the active node or misbehavior by clicking on the radio button. We have to connect the particular node to database and type the message and then we have to click the send button. Route discovery: Route discovery Source node wants to send packets to a destination to which it does not have a route, it initiates a Route Discovery by broadcasting a ROUTE REQUEST. The node receiving a ROUTE REQUEST checks whether it has a route to the destination in its cache. If it has, it sends a ROUTE REPLY which is concatenation of cached route to the source route . B A S E F H J D C G I K M N L Route discovery: Route discovery If the node does not have a cached route to the destination, it adds its address to the source route and rebroadcasts the ROUTE REQUEST. When the destination receives the ROUTE REQUEST, it sends a ROUTE REPLY containing the source route to the source. After getting the route information when the sender wants to send the message the route status is checked. Message transfer to the available path: Message transfer to the available path The Message transfer relates with that the sender node wants to send a message to the destination node after the path is selected also find out that node is not a misbehavior node and status of the destination node through is true. The receiver node receives the message completely and then it send the acknowledgement to the sender node. B A S E F H J D C G I K M N L DATA [S,E,F,J,D] Packet header size grows with route length Route MAINTENANCE: Route MAINTENANCE Here the node forwarding a packet is responsible for confirming that the packet has been successfully received by the next hop. If no acknowledgement is received after the maximum number of retransmissions, the forwarding node sends a ROUTE ERROR to the source (also source easily understand that node is misbehavior),indicating the broken link. Cache updating for misbehavior node detection: Cache updating for misbehavior node detection When a node detects a link failure, our goal is to notify all reachable nodes that have cached that link to update their caches if it is not a misbehavior node. To achieve this goal, the node detecting a link failure, identifying the misbehavior node needs to know which nodes have cached the broken link and needs to notify such nodes efficiently. PowerPoint Presentation: USECASE DIAGRAM PowerPoint Presentation: CLASS DIAGRAM PowerPoint Presentation: SEQUENCE DIAGRAM PowerPoint Presentation: COLLABORATION DIAGRAM PowerPoint Presentation: ACTIVITY DIAGRAM PowerPoint Presentation: STATECHART DIAGRAM PowerPoint Presentation: ARCHITECTURAL DESIGN Dynamic Source Routing Protocol Route Request Message Transfer Route Maintenance Cache Update Route Add Route Find Receive Ack Send Data Update Cache Receive Link Failure Code implementation: Code implementation In order to implement the code required for our project we created four nodes, four message servers, four status servers. In the code which we used for generating the node we mainly used swing components to create labels, text fields, radio buttons, buttons, text areas etc..Based on the events generated we try to call particular event listeners like item event listener and action listeners to carry out respective functions. Code implementation: Code implementation In the code of message servers we mainly focus on transferring the message from the intermediate nodes to destination node and receiving the acknowledgement from the respective nodes. In the code of status server we try to update the status in cache tables of database when we detected the misbehavior nature of the particular node. Test results: Test results ACKNOWLEDGEMENT STATUS Test results: Test results ACKNOWLEDGEMENT STATUS Test results: Test results Destination status in source and Received status in Destination Test results: Test results FINDING MISBEHAVIOR NODE Test results: Test results ROUTE UPDATED STATUS Test results: Test results Warning we get when intermediate node is misbehaving Conclusion: Conclusion Manets, which has widespread application is highly dependent on the co-operation of all its members to perform networking functions. Hence misbehavior of some nodes is to be mitigated using 2ACK scheme to increase the performance since 2ACK scheme maintains up to 91% packet delivery ratio even when there are 40% misbehaving nodes in the MANETs Future Scope: Future Scope Here we focus only on the node misbehavior. In order to decide the behavior of a node and punish it, we may need to check the behavior of links around that node. This is potential direction for our future work. In our future work we will investigate how to add the 2ACK scheme to other types of routing schemes. references: references Referred the IEEE paper by Sunilkumar S. Manvi a, Lokesh B. Bhajantrib, and Vittalkumar K. Vagga on Routing Misbehavior Detection in MANETs Using 2ACK. Referred IEEE paper by Kejun Liu, Jing Deng, Member, IEEE, Pramod K. Varshney, Fellow, IEEE, and Kashyap Balakrishnan, Member, IEEE on An Acknowledgment-Based Approach for the Detection of Routing Misbehavior in MANETs. IEEE paper by H. Miranda and L. Rodrigues on “Preventing Selfishness in Open Mobile Ad Hoc Networks. PowerPoint Presentation: . THANK U!!!