Dan Ouchterlony

Oskar Mattsson

Petra Nylund

Fredrik Lilieblad

Anders Roxenhag

The Mad-hoc team

ad-hoc

• formed for specific or immediate problems or needs

• fashioned from whatever is immediately available

ad-hoc

• no infrastructure

• increased reach

• increased connectivity

Time

Cost Quality

implement ad-hoc functionality

offer all key components

superior knowledge

Mission

Markets:

Wireless LAN

Games

WAP

Future markets

the ad-hoc company

Quality

Focus

Expansion

240 40 40

Market share - Business

15 BSEK

5%

Market share - Business

30%

231 MSEK

Market share - Entertainment

196 BSEK

5%

Market share - Entertainment

0.5%

49 MSEK

Ad-hoc routing protocolsPro-active (ex. STAR,TORA)

Re-active (ex. AODV, DSR)

Keeps track of all destinationsPeriodic updates

Request routes when needed

Only deals with used routes

AODV (Ad-hoc On demand Distance Vector)

High mobility

Loop free routes

Low byte overhead

Developed by Charles E. Perkins

A BD

AODV: A new node

C

Our addition (bi-directional requests)

A BD CE

AODV implementation

• Route table modifying process• Written in C under Linux using gcc• User space process

– no kernel modification– easy to install– portable

Open source

• GNU Public License - GPL– Free to copy, use and modify– May not be licensed by others

• First free implementation of AODV!• Other implementations soon

no use selling source code

Free implementation

Open source - benefits

•Development of source code•Spread usage of AODV

•Mad-hoc becomes well known•AODV becomes standard

Mad-hoc increases distance to competitors

Tested scenarios

• Multihop TCP & UDP support

• Quake gaming sessions• Cooperating team at Uppsala University

Contact

http://mad-hoc.flyinglinux.net

Welcome to M D-HOC at the workshop tomorrow for some

Quake & info!