vBET: a VM-based emulation testbed
MoMeTools '03 Proceedings of the ACM SIGCOMM workshop on Models, methods and tools for reproducible network research
Simulation with real world network stacks
WSC '05 Proceedings of the 37th conference on Winter simulation
NSOSS: the non-synchronized optical switch simulator
Proceedings of the 2nd international conference on Performance evaluation methodologies and tools
Tool-based performance evaluation of the blackboard communication system
Proceedings of the 2nd international conference on Performance evaluation methodologies and tools
P2P architecture over IPv6 for personal internetworking
International Journal of Internet Protocol Technology
VirtualMesh: an emulation framework for wireless mesh networks in OMNeT++
Proceedings of the 2nd International Conference on Simulation Tools and Techniques
A virtual platform for network experimentation
Proceedings of the 1st ACM workshop on Virtualized infrastructure systems and architectures
A real-time publish/subscribe driver alert system for accident avoidance due to red light running
Proceedings of the Third ACM International Conference on Distributed Event-Based Systems
Integration of a GIST implementation into OMNeT++
Proceedings of the 3rd International ICST Conference on Simulation Tools and Techniques
Proceedings of the 11th ACM international symposium on Mobility management and wireless access
| Hi-index | 0.00 |
The discrete event simulator OMNeT++, that is programmed in C++, shows a steady growing popularity. Due to its well-structured nature, it is easy to understand and easy to use. A shortcoming of it, however, is the limited number of available simulation models. Especially, for network simulations a validated TCP implementation was missing. In order to avoid a re-implementation of a full-featured TCP, including all potential implementation errors and costly validation tests, we integrated a TCP/IP stack of a real operating system into OMNeT++. In this paper we show that such a port is feasible with reasonable effort and we describe difficulties of the integration process as well as the applied solutions. We also present some evaluation results that outline memory and CPU usage.