Linux Kernel Support for Ad-hoc Routing
1
A CS395T Course Project Mobile Computing & Wireless Networks Spring 2001 C o u r s e w e b s i t e : h t t p : / / w w w . c s . u t e x a s . e d u / u s e r s / y g z / 3 9 5 T • I n s t r u c t o r : D r . Y o n g g u a n g Z h a n g ( y g z @ c s . u t e x a s . e d u ) Design Generic Interface for all ad-hoc routing protocols – Network Interface Module (NIM) – User Interface Module (UIM) NIM: Interface to Network Stack AKM: In Data Plane – Forwarding according to Ad-hoc protocol UIM: for data and control plane comm’n. AUD: In Control Plane – Ad-hoc Route maintenance New Ideas Many Ad-hoc Routing Protocols Exist Very few real implementations – High Complexity – Not enough tools for development – Performance claims based on simulation results Designed and developed a generic infrastructure – Provides a tool to evaluate Ad-hoc protocols Implementation & Testing Implemented in Linux 2.4.3 – Used Netfilter & IPTable support Tested multihop routing –Three hosts in broadcast setup Test Protocols: – Manual Configuration – AODV Can be extended to support multiple protocols simultaneously Project team: Puneet Chopra, Sumit Garg, Sugat Jain URL: http://www.cs.utexas.edu/users/puneet/mobcomp/proposal.html AKM:Ad-hoc Kernel Module AUD: Ad-hoc User Daemon ART: Ad-hoc Routing Table NIM: Network Interface Module UIM: User Interface Module Linux Kernel Support for Ad-hoc Routing
-
Upload
juancarlos-rodriguez -
Category
Documents
-
view
18 -
download
2
description
Linux Kernel Support for Ad-hoc Routing. New Ideas Many Ad-hoc Routing Protocols Exist Very few real implementations High Complexity Not enough tools for development Performance claims based on simulation results Designed and developed a generic infrastructure - PowerPoint PPT Presentation
Transcript of Linux Kernel Support for Ad-hoc Routing
A CS395T Course Project MobileComputing &
WirelessNetworks
Spring 2001C
ourse
we
b site
: http://w
ww
.cs.ute
xas.e
du
/use
rs/ygz/39
5T
• Instructo
r: Dr. Y
on
gg
uan
g Z
ha
ng
(ygz@
cs.ute
xas.ed
u)
Design Generic Interface for all ad-hoc routing
protocols– Network Interface Module (NIM)– User Interface Module (UIM)
NIM: Interface to Network Stack AKM: In Data Plane
– Forwarding according to Ad-hoc protocol UIM: for data and control plane comm’n. AUD: In Control Plane
– Ad-hoc Route maintenance
New Ideas Many Ad-hoc Routing Protocols Exist Very few real implementations
– High Complexity– Not enough tools for development– Performance claims based on simulation
results Designed and developed a generic
infrastructure– Provides a tool to evaluate Ad-hoc protocols
Implementation & Testing Implemented in Linux 2.4.3
– Used Netfilter & IPTable support Tested multihop routing
–Three hosts in broadcast setup Test Protocols:
– Manual Configuration – AODV
Can be extended to support multiple protocols simultaneously
Project team: Puneet Chopra, Sumit Garg, Sugat JainURL: http://www.cs.utexas.edu/users/puneet/mobcomp/proposal.html
AKM:Ad-hoc Kernel ModuleAUD: Ad-hoc User DaemonART: Ad-hoc Routing Table
NIM: Network Interface ModuleUIM: User Interface Module
Linux Kernel Support for Ad-hoc Routing
