Proceedings. International Conference on Parallel Processing Workshop
DOI: 10.1109/icppw.2002.1039723
|View full text |Cite
|
Sign up to set email alerts
|

System services for implementing ad-hoc routing protocols

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1

Citation Types

0
3
0

Publication Types

Select...
6
1

Relationship

0
7

Authors

Journals

citations
Cited by 8 publications
(3 citation statements)
references
References 10 publications
0
3
0
Order By: Relevance
“…A couple of requirements/system capabilities are required/called for in an efficient (and easy) implementation (all implementations thus far have implemented the following) [8]:…”
Section: Requirements and Related Workmentioning
confidence: 99%
“…A couple of requirements/system capabilities are required/called for in an efficient (and easy) implementation (all implementations thus far have implemented the following) [8]:…”
Section: Requirements and Related Workmentioning
confidence: 99%
“…There are other testbed works that can also abstract multiple real interfaces into a single virtual interface [5,11,23]. However, those approaches are not designed to support the notion of using multiple channels or interface switching between channels.…”
Section: Related Workmentioning
confidence: 99%
“…The first task is to run multiple routing daemons at different power levels. In Linux, route discovery and maintenance is done by user space programs called routing daemons, and the actual packet forwarding is done by consulting the kernel IP routing table, which is populated by the routing daemons (see [29]). Thus, running multiple routing daemons simply involves starting many of these routing daemons, one for each power level, on pre-assigned ports.…”
Section: Clusterpow Implementation and Software Architecturementioning
confidence: 99%