close
Warning:
Can't synchronize with repository "(default)" ("(default)" is not readable or not a Git repository.). Look in the Trac log for more information.
- Timestamp:
-
Jun 22, 2012, 5:39:41 AM (12 years ago)
- Author:
-
romi
- Comment:
-
--
Legend:
- Unmodified
- Added
- Removed
- Modified
-
v1
|
v2
|
|
1 | 1 | == Project Objective: == |
2 | | |
| 2 | Extending GSTAR to support inter-domain routing |
| 3 | |
3 | 4 | |
4 | 5 | == Approach: == |
| 6 | 1. To understand the existing Generalized Storage Aware Routing Protocol(GSTAR)[[BR]] |
| 7 | 2. Performance Analysis of GSTAR on various intra-domain network topologies[[BR]] |
| 8 | 3. Extension of GSTAR to implement inter-domain routing |
5 | 9 | |
6 | 10 | |
… |
… |
|
11 | 15 | |
12 | 16 | == Work Log: == |
| 17 | Week 1: Understanding the existing ns-3 based implementation[[BR]] |
| 18 | |
| 19 | Week 2: Running sample MobilityFirst example scripts[[BR]] |
| 20 | |
| 21 | Week 3: Simulation script for the following wireless ad-hoc network was written and performance analysis was done[[BR]] |
| 22 | [[Image(scenario1_wireless.PNG)]][[BR]] |
| 23 | The following results were obtained:[[BR]] |
| 24 | [[Image(scenario1_results1.PNG)]][[BR]] |
| 25 | [[Image(scenario1_results2.PNG)]][[BR]] |
| 26 | |
| 27 | |
| 28 | Week 4: Simulation script for a mixed topology with some wired nodes and two wireless destination nodes, was written and performance analysis was carried out[[BR]] |
| 29 | |
| 30 | Week 5: This week's aim is to generate some mobility trace for the destination nodes, plug it into ns-3 and see how GSTAR performs when the destination nodes are randomly moving |