A wired-wireless testbed architecture for network layer experimentation based on ORBIT and VINI

George C. Hadjichristofi, Avi Brender, Marco Gruteser, Rajesh Mahindra, Ivan SeskarWiNTECH 2007 · DOI

TL;DR

This paper introduces a novel architecture that seamlessly integrates wired and wireless network testbeds, allowing researchers to conduct complex experiments spanning both domains. By leveraging existing platforms like ORBIT (wireless) and VINI/PlanetLab (wired), this work provides a unified environment for developing and testing next-generation internet protocols, particularly those addressing mobility and diverse network requirements.

What Problem Does This Paper Address?

The internet's original design faces limitations with increasing demands for host and router mobility, and the dynamic nature of wireless links. While separate testbeds exist for wired (e.g., PlanetLab, VINI) and wireless (e.g., ORBIT) networks, there's a significant gap in platforms that can effectively integrate both. This lack of a unified testbed hinders research into novel network architectures that must operate across both wired and wireless environments, especially for experiments requiring complex, custom topologies. Existing solutions often focus on one domain or offer limited integration, making it difficult to test protocols that rely on the interplay between wired and wireless communication.

Methods

The core of this work is the integration of the ORBIT wireless testbed with the VINI virtual network infrastructure, which runs on the PlanetLab wired testbed. The key innovation lies in creating a virtual Ethernet link between the two testbeds, enabling the seamless propagation of any Ethernet-encapsulated packet, including non-IP protocols.

  • VINI Modifications:
    • Ethernet Tunnels: OpenVPN was modified to use Ethernet tunnels (via Linux Tap devices) instead of IP tunnels. This allows for the transmission of non-IP and broadcast packets, which are crucial for many routing protocols.
  • Direct to UML: Ingress traffic from OpenVPN is now directly delivered to the User Mode Linux (UML) environment within VINI, bypassing the Click modular router. This simplifies packet handling and allows the experimenter to manage routing within UML using standard Linux tools.
  • Egress Traffic: A new virtual interface (eth3) was introduced in UML for egress traffic, allowing Click to process Ethernet packets from this interface and send them through OpenVPN links.
  • ORBIT Modifications:
    • Router Configuration: An ORBIT node is configured as a router, establishing an OpenVPN tunnel to the VINI network. This allows for the integration of multi-hop wireless networks with the wired testbed.
  • Bridge Configuration: An ORBIT node acts as a bridge, connecting its wireless interfaces to the OpenVPN interface. This effectively makes a VINI node appear as a wireless node on the ORBIT network, enabling simpler integration scenarios.
  • IP Address Management: To avoid conflicts between the private IP address ranges used by PlanetLab-VINI and ORBIT, alternative private IP ranges (172.16.0.0/12 and 192.168.0.0/16) were assigned to OpenVPN servers and clients.

Datasets

Not discussed in the paper. The paper focuses on a testbed architecture and experimental setup rather than training on specific datasets.

Key Insights and Ideas

  • Unified Experimentation: The most significant insight is the successful creation of a unified, global-scale testbed that bridges the wired and wireless domains. This opens up new avenues for research that were previously difficult or impossible to conduct.
  • Ethernet Tunnels for Flexibility: Using Ethernet tunnels via OpenVPN is a critical enabler. It breaks the reliance on IP-only communication, allowing for the testing of a wider range of protocols and network behaviors, including those that use non-IP or broadcast mechanisms.
  • Transparency for Users: By abstracting away the complexities of the underlying Click modular router and virtualization layers, the integrated testbed offers a more transparent experience for researchers. This reduces the learning curve and expedites experiment deployment.
  • Mobility Experimentation: The architecture is well-suited for studying mobility scenarios, as demonstrated by the hand-off experiment. The ability to integrate wireless access points with wired infrastructure is key to testing advanced mobility protocols.
  • Bottlenecks and QoS: The experimental results highlight that the throughput of the OpenVPN links can be a bottleneck. This underscores the importance of considering link characteristics and the need for Quality of Service (QoS) guarantees in future virtual overlay networks.

Key Results

  • Successful Integration: The paper demonstrates a functional integration of ORBIT and VINI, allowing for Layer 3 experiments across both wired and wireless nodes.
  • Mobility Scenario Performance: In a video hand-off experiment, the proposed setup achieved a packet delay of 225 msecs, significantly better than a Mobile IP setup (443 msecs).
  • Convergence Time: The experiment showed that new routing information propagates and video is restored within approximately 3.5 seconds after a hand-off event.
  • Throughput Characteristics: Throughput measurements indicated that OpenVPN links can be a bottleneck, with one link showing a throughput of 1.25 Mbps. The average throughput for different offered loads (1 Mbps and 50 Mbps) was found to be similar, around 0.9 Mbps.

Limitations and Future Work

  • UML Overhead: The paper acknowledges that running experiments within the UML kernel incurs a performance overhead of approximately 15% for forwarding data packets.
  • Wireless Node Virtualization: Direct virtualization of wireless nodes is not performed due to the need for access to lower-layer protocols (physical and MAC layers) for wireless experiments. Instead, wireless nodes are spatially segmented.
  • Concurrent Experiments: While ORBIT nodes have multiple wireless interfaces, the current control mechanism within UML does not support concurrent experiments on a single node.
  • Identity Management: A unified identity management federation across both testbeds is identified as a missing piece for seamless integration from an ORBIT user's perspective.
  • Future Work: The authors suggest extending the ORBIT control framework to include VINI nodes through a single programming script. They also highlight the need for QoS guarantees on PlanetLab nodes and the potential for integrating other wireless technologies (Zigbee, Bluetooth) and heterogeneous wireless networks. The work also lays the groundwork for future GENI efforts to address these challenges.

Summary updated

BibTeX
@inproceedings{hadjichristofi2007wired,
  author = {George C. Hadjichristofi and Avi Brender and Marco Gruteser and Rajesh Mahindra and Ivan Seskar},
  title = {{A wired-wireless testbed architecture for network layer experimentation based on ORBIT and VINI}},
  booktitle = {WiNTECH},
  year = {2007},
  doi = {10.1145/1287767.1287783},
}
Figure