This shows you the differences between two versions of the page.
|
design:testbed [2010/03/10 10:07] roberto.riggio |
design:testbed [2010/03/11 09:57] (current) roberto.riggio |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== Testbed design ====== | ====== Testbed design ====== | ||
| + | |||
| ===== Overview ===== | ===== Overview ===== | ||
| Current configuration is based on 23 nodes deployed across two buildings, implementing two local indoor wireless mesh networks interconnected by an outdoor WiFi point-to-multipoint wireless link. Mesh routers build and maintain the multi-hop wireless back-haul and provide end-users with a standard 802.11 Access Point. Internet connectivity is delivered by a dedicated mesh routers equipped with an high bandwidth connection to the Internet backbone. A third tier providing Internet connectivity by means of a Point-to-Multipoint wireless technology (e.g. WiMAX, WiFi, or UMTS) is also supported. | Current configuration is based on 23 nodes deployed across two buildings, implementing two local indoor wireless mesh networks interconnected by an outdoor WiFi point-to-multipoint wireless link. Mesh routers build and maintain the multi-hop wireless back-haul and provide end-users with a standard 802.11 Access Point. Internet connectivity is delivered by a dedicated mesh routers equipped with an high bandwidth connection to the Internet backbone. A third tier providing Internet connectivity by means of a Point-to-Multipoint wireless technology (e.g. WiMAX, WiFi, or UMTS) is also supported. | ||
| + | |||
| + | {{:artwork:testbed.png?500|}} | ||
| The WING testbed is built on top of the Roofnet platform. Roofnet is an experimental WMN developed by the MIT and deployed in Cambridge, Massachusetts. Roofnet routes packets using a DSR-like routing protocol called SrcRR exploiting the Estimated Transmission Time (ETT) as routing metric and optimized for network scalability and throughput rather than for supporting mobility. The default Roofnet configuration has been extended with additional modules responsible for: | The WING testbed is built on top of the Roofnet platform. Roofnet is an experimental WMN developed by the MIT and deployed in Cambridge, Massachusetts. Roofnet routes packets using a DSR-like routing protocol called SrcRR exploiting the Estimated Transmission Time (ETT) as routing metric and optimized for network scalability and throughput rather than for supporting mobility. The default Roofnet configuration has been extended with additional modules responsible for: | ||
| Line 9: | Line 12: | ||
| * [[directions:opportunistic_scheduling|Opportunistic scheduling]], an opportunistic scheduler addressing the //IEEE 802.11 performance anomaly//. | * [[directions:opportunistic_scheduling|Opportunistic scheduling]], an opportunistic scheduler addressing the //IEEE 802.11 performance anomaly//. | ||
| * [[directions:qos_provisioning|QoS Provisioning]], a DiffServ-based framework providing soft QoS bounds. | * [[directions:qos_provisioning|QoS Provisioning]], a DiffServ-based framework providing soft QoS bounds. | ||
| - | * [[directions:channel_assignment|Interference and Traffic Aware Channel Assignment]], a dynamic channel selection scheme capable of taking into account both interference and traffic conditions. | + | * [[directions:channel_assignment|Multi-Radio]], a dynamic channel selection scheme capable of exploiting multiple radios in order to build and maintain the wireless backhaul. |
| + | |||
| + | ===== Software Architecture ===== | ||
| + | |||
| + | [[http://openwrt.org|OpenWRT]] has been selected as operative system for our testbed. OpenWRT provides an automated system to download the source code (both kernel and the userland tools) and compile it to work on any supported platform. Moreover, it is characterized by a small memory and disk footprint making it suitable for a wide rage of networking devices. Finally, it provides hardware configuration and maintenance abstraction through a custom system and package configuration facility called UCI. | ||
| + | |||
| + | Notwithstanding the fact that the PCEngines processor boards are based on the x86 architecture and then they do not require cross-compilation, we decided to use OpenWRT in order to abstract ourself from the underlying hardware architecture making the WING wireless mesh networking toolkit platform agnostic. | ||
| + | |||
| + | The following picture sketches the overall wireless mesh router architecture. | ||
| + | |||
| + | {{:artwork:router_architecture.png?500|}} | ||
| + | |||
| + | As it can be seen from the picture, the node supports multiple backhauling technologies (Wired, WiFi, and UMTS). The software can seamlessly switch from one backhaul link the the other. However, due to the use of Network Address Translation (NAT) techniques at the mesh gateway, existing connections exploiting stateful protocols, such as TCP, are terminated when the backhaul link is switched. Routing software is implemented using the [[http://www.read.cs.ucla.edu/click/|Click]] modular router. | ||
| ===== Features ===== | ===== Features ===== | ||
| Line 32: | Line 47: | ||
| Internet connectivity is provided by the Mesh Gateways using either wired or wireless links. This is useful in three-tiers architectures where the gateways are connected to a bandwidth aggregation point using point-to-multipoint wireless links, Currently supported technologies are: WiFi, WiMax, and UMTS. | Internet connectivity is provided by the Mesh Gateways using either wired or wireless links. This is useful in three-tiers architectures where the gateways are connected to a bandwidth aggregation point using point-to-multipoint wireless links, Currently supported technologies are: WiFi, WiMax, and UMTS. | ||
| + | |||
| ==== QoS Support ==== | ==== QoS Support ==== | ||
| Line 66: | Line 82: | ||
| * 6 Gateworks [[hardware:gw2358|GW2358-4]]. Indoor multi-channel mesh router. | * 6 Gateworks [[hardware:gw2358|GW2358-4]]. Indoor multi-channel mesh router. | ||
| - | ===== Operating system ===== | ||
| - | [[http://openwrt.org|OpenWRT]] has been selected as operative system for our testbed. OpenWRT provides an automated system to download the source code (both kernel and the userland tools) and compile it to work on any supported platform. Moreover, it is characterized by a small memory and disk footprint making it suitable for a wide rage of networking devices. Finally, it provides hardware configuration and maintenance abstraction through a custom system and package configuration facility called UCI. | ||
| - | |||
| - | Notwithstanding the fact that the PCEngines processor boards are based on the x86 architecture and then they do not require cross-compilation, we decided to use OpenWRT in order to abstract ourself from the underlying hardware architecture making the WING wireless mesh networking toolkit platform agnostic. | ||