Task #794
Create a couple test scenarios for OCEAN
| Status: | Closed | Start date: | 02/19/2009 | ||
|---|---|---|---|---|---|
| Priority: | Normal | Due date: | 02/28/2009 | ||
| Assignee: | Kirill Yudenok | % Done: | 50% |
||
| Category: | development | Spent time: | - | ||
| Target version: | ocean modeling | Estimated time: | 10.00 hours |
Description
Use Tcl
Read the documentation
Try to find use case fro OCEAN
* http://www.cs.fsu.edu/research/reports/TR-050111.pdf
* http://portal.acm.org/citation.cfm?id=1687361
History
Updated by Kirill Krinkin over 1 year ago
- Status changed from New to Active
Updated by Kirill Yudenok over 1 year ago
- % Done changed from 0 to 50
Цель OCEAN: Использование методов прямого непосредственного наблюдения за поведением узлов, без механизма репутации.
OCEAN is a layer that resides between the network and MAC layers of the protocol stack, and it helps nodes make
intelligent routing and forwarding decisions. OCEAN designed on top of the Dynamic Source Routing Protocol(DSR).
- NeighborWatch (сравнение контрольных сумм передаваемого пакета)
- RouteRanker (наблюдение за рейтингами узлов, составление faulty list)
- Rank-Based Routing (составление списка с узлами, которых стоит избегать)
- Malicious Traffic Rejection (отказ от вредоносного трафика)
- Second Chance Mechanism (предоставление второго шанса для неисправного узла)
- Misleading (node may respond positively to route requests but then fail to forward the actual packets, misleading other nodes into unsuccessfully sending their traffic through it)
- Selfish (node may not even respond to route requests but may nonetheless send its own traffic through the network, unfairly preserving its resources while exploiting others. Hard to detect.)
Default OCEAN parameters:
Neutral Rating = 0 (default node rating)
Positive Step = +1 (for chipcounts)
Negative Step = -2 (for chipcounts)
Faulty Threshold = -40 (for chipcounts)
- chipcounts mechanism (счетчик для соседей узлов, который увеличивается, либо уменьшается до определенного порога (Faulty Threshold), после которого передача через узел отвергается)
- two schemes: optimistic and pessimistic (Пессимистичная стоит по умолчанию, больше справляется с неисправными узлами, но страдает от проблемы тупика. Оптимистичная более мягкая к неисправным узлам)
- parameter Chip Accimulation Rate (CAR) (увеличивает chip в единицу времени, малое значение данного параметра более интенсивно справляется с неисправными узлами)
- parameters Faulty Threshold, Faulty Timeout (1. -40. 2. ?)
Set malicious nodes:
When running a simulation, if you want to have malicious, selfish and/or faulty nodes, create a file named "nodes.info" with the following structure:
[malicious]
0 1 2 3 4[selfish]
3 4 5 6[faulty]
7 10 20
8 11 15
The numbers should be replaced with the nodes you want to be malicious/selfish. If you dont want any malicious nodes, leave the line containing the numbers blank, same goes for selfish. The format for faulty nodes is <node_id> <begin_faulty_time> <end_faulty_time>. The "nodes.info" file should exist in the directory you run the simulation in, ie, where you execute the command "ns script.tcl".
Updated by Kirill Krinkin over 1 year ago
- Status changed from Active to Closed