1 / 9

Team _ - Jan 18 2005

Team _ - Jan 18 2005. Project Goal. The Goal The goal of our project is to create a working and user friendly simulation of the AODVS system The secondary goal is to improve upon the existing system by adding timeouts on SID packets (intrusion detection). Design Revisions.

alain
Download Presentation

Team _ - Jan 18 2005

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. Team _ - Jan 18 2005

  2. Project Goal • The Goal • The goal of our project is to create a working and user friendly simulation of the AODVS system • The secondary goal is to improve upon the existing system by adding timeouts on SID packets (intrusion detection)

  3. Design Revisions • Through discussions both with the professor and amongst the group the design has changed in several ways • Nodes will be told when to move, but not where to move, by the Monitor class • Our thoughts on the visualization of network traffic have changed more than once, and may change again

  4. Design Revisions (cont) • The Monitor class has had more things moved and added to it for coordination between the various layers of our program • External lookup tables for node and packet types have been added • “Big Picture” remains the same as in original designs

  5. Risk Analysis • Timing • Movement handled by coordinating through the Monitor and not leaving it up to the nodes • Cryptography • Pushed off until later, possibility of not getting to it • AODV algorithm not fully implemented or implemented incorrectly • Used an Internet Draft from Univ. of Calif.

  6. Schedule • This week • Monitor will be done • 50% of packets implemented and working • Visualization of these packets • Week 7 • Other 50% of packets implemented • Tokens working to tell good nodes from bad • Authority class working to start up system

  7. Schedule • Week 8 • Bad nodes implemented • Detection system in place to detect bad routing and dropping packets • Week 9 • Final testing and debugging • Trials to see if our improvement has worked • Week 10 • Evaluation and report

  8. Demo!

More Related