1 / 12

MobileMan Meeting at HUT

MobileMan Meeting at HUT. Core Implementation Status Report Claudio.Lavecchia@eurecom.fr. CORE Implementation S tatus R eport. Design Routing protocol Design assumptions Architecture Project status Implementation Testing infrastructure Project goals. CORE Implementation: Design (1).

cameran-barrett
Download Presentation

MobileMan Meeting at HUT

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. MobileMan Meeting at HUT Core Implementation Status Report Claudio.Lavecchia@eurecom.fr Claudio Lavecchia

  2. CORE Implementation Status Report • Design • Routing protocol • Design assumptions • Architecture • Project status • Implementation • Testing infrastructure • Project goals Claudio Lavecchia

  3. CORE Implementation: Design (1) • Design choices: • CORE can work with different routing protocols • Selected OLSR as routing protocol for prototype • Proactive “hop by hop” protocol • Unik Implementation (http://www.olsr.org) • Good documentation • Good support • Plugins framework (access to data and services provided by routing daemon) Claudio Lavecchia

  4. CORE Implementation:Assumption (1) • Implication of OLSR: • Assumption: relay nodes correctly execute (syntax and semantics) the routing protocol • Packets are forwarded to the correct next-hop a b c MACa MACb IPa IPd pl MACb MACc IPa IPd pl MACb MACc IPa IPd pl d e Hash(pl) Expectations table Hash Src Dst At k node b is cooperating  Obs (k) = +1 Hash(pl) MACb, IPa IPd Claudio Lavecchia

  5. CORE Implementation:Assumption (2) • Previous assumption is not needed for source routing protocols such as DSR: • a knows the route to reach d R = <a,b,c,d> a b c MACa MACb IPa IPd pl MACb MACc IPa IPd pl MACb MACc IPa IPd pl d e Hash(pl) Src Dst pl MACb, IPa MACc,IPd Hash(pl) Claudio Lavecchia

  6. CORE Implementation: Design (2) Claudio Lavecchia

  7. CORE Implementation: Design (3) • Plug-in periodically polls OLSR data structures to update neighbors information • Plug-in passes updated neighbors information to CORE watchdog through sockets Claudio Lavecchia

  8. CORE Implementation: Design (4) • Sniffer passes all layer 2 packets to the watchdog • Watchdog analyses IP and MAC addresses of the packets and determines which “scenario” the packet belongs to (7 possible scenario) • Watchdog acts according to the scenario Claudio Lavecchia

  9. CORE Implementation: Status • Layer two sniffer is completed • OLSR plug-in implementation in progress • Watchdog implementation in progress • Hooks in CORE code to add support for other routing protocols Claudio Lavecchia

  10. Testing infrastructure • Defined a simple selfishness model • IPTABLES (chain FORWARD) policy DROP • Hardware testing platform up and running (successfully used to validate OLSR implementation) • Scripts allowing quick manual network configuration Claudio Lavecchia

  11. Goals • To establish CORE as the reference in cooperation enforcement mechanisms • No alternative available at the moment • Project is well perceived in the scientific community • INRIA, Unik are interested in the project • Documentation and dissemination is a main goal Claudio Lavecchia

  12. Advanced Topics • Cross-Layer design • Integration of OLSR_willingness in CORE • Power consumption analysis Claudio Lavecchia

More Related