Changes between Version 20 and Version 21 of Documentation/FAQ
- Timestamp:
- Dec 10, 2005, 4:40:39 AM (18 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Documentation/FAQ
v20 v21 28 28 The ORBIT radio grid emulator is an indoor wireless network testbed. It supports experimental research on a broad range of wireless networking issues and application concepts with various network topologies and network layer protocol options. It also support virtual mobility for mobile network protocol and application research. The ORBIT radio grid emulator currently uses 802.11a/b/g based radio cards. Some examples of systems and protocol designs that can be investigated on the ORBIT Testbed include: 29 29 30 * Large-scale wireless access networks based on 802.11a , b,g radios along with new protocols for discovery, routing, mobility management, security, etc. under various indoor and outdoor usage scenarios and network topologies.30 * Large-scale wireless access networks based on 802.11a/b/g radios along with new protocols for discovery, routing, mobility management, security, etc. under various indoor and outdoor usage scenarios and network topologies. 31 31 * Mobile ad hoc networks (MANET), typically based on 802.11x radios, along with multi-hop ad hoc routing protocols such as AODV, DSR and new protocols. 32 32 * Wireless sensor networks and pervasive computing applications. … … 34 34 35 35 In the future, the ORBIT Testbed will support other radio interfaces such as Blootooth, Zigbee, GNU Radio, and allow research on heterogenerous wireless networks. It can also accommodate new technologies such as UWB as they emerge. 36 36 37 37 38 Can I test my new physical layer model on ORBIT? … … 46 47 Yes and No. The ORBIT radio grid emulator currently uses standard 802.11a/b/g radio interface cards with Linux drivers (Intel IPW2200 and Atheros MADwifi). The drivers allow changing certain parameters such as channel, TX power, TX rate, etc. but not all. We are actively developing our drivers and are in constant contact with the card manufacturers to help expose whatever functionality the hardware is capable of. Stay tuned. 47 48 49 50 48 51 Do you support AODV? 49 52 -------------------- 50 53 51 Yes. We currently support AODV-UU routing protocol implementation version 0.9.1 that runs on kernel 2.6.12. Please refer to [http://svn.orbit-lab.org/projects/orbit/wiki/AODV AODV] for more details. 54 Yes. We currently support AODV-UU routing protocol implementation version 0.9.1 that runs on kernel 2.6.12. Please refer to http://svn.orbit-lab.org/projects/orbit/wiki/AODV for more details. 55 56 52 57 53 58 How is the mobility supported by ORBIT? … … 56 61 The ORBIT radio grid emulator support virtual mobility. Virtual mobiles are introduced for discretized grid mobility. Physically located off the radio grid, a virtual mobile has a network driver that delivers packets to a mobility controller. Via high speed wired Ethernet, the mobility controller encapsulates and forwards these packets to a radio grid node i, which simply decapsulates and transmits each packet. In addition, packets received by grid node i will be forwarded via the mobility controller to the virtual mobile. In short, the virtual mobile will appear to be at grid location i by using radio grid node i for transmitting and receiving packets. It will use grid radio node j when it "moves" to grid location j. Grid mobility can support discretized versions of commonly used mobility models such as Brownian motion or the random waypoint model. In addition to virtual grid mobility, we plan on a small number of programmable mobile robots. These mobiles will communicate with the radio grid and allow experimentation with finer grain mobility experiments. 57 62 63 58 64 What radio parameters can I measure? 59 65 ------------------------------------ 60 66 61 Currently, RSSI, TX_power, noise, throughput, offered-load, and the number of packet retransmissions can be measured and collected. Users can select one or more of these parameters to be collected and stored in the database. 67 Currently, RSSI, TX_power, noise, throughput, offered-load, and the number of frame retransmissions can be measured and collected. Users can select one or more of these parameters to be collected and stored in the database. 68 62 69 63 70 Getting Started 64 71 =============== 65 72 73 66 74 Who is eligible to use ORBIT? 67 75 ----------------------------- … … 69 77 As ORBIT name (Open-Access Research Testbed for Next-Generation Wireless Networks) says, almost all research or educational uses by those that have a need for it are appropriate and encouraged. These include use by universities, industrial research labs, and both US and non-US institutions. With some provisions, use for product development and evaluation by companies is also acceptable. Please email us if you are interested. 70 78 79 80 71 81 How do I start a project? 72 82 ------------------------- … … 74 84 ORBIT is still under development. Please email us if you are interested in doing experiments with the ORBIT testbed. In the future there will be a web interface for the project application. 75 85 86 87 76 88 Using the ORBIT Testbed 77 89 ======================= 90 78 91 Is there a tutorial? 79 92 -------------------- 80 93 81 94 Yes, it is available at http://svn.orbit-lab.org/projects/orbit/wiki/Tutorial. 95 82 96 83 97 Who do I email to request a time slot on a sandbox? … … 87 101 You will need your orbit username and password. 88 102 89 How do I just request any available sandbox (are they all the same)? 103 104 How do I request any available sandbox? 90 105 -------------------------------------------------------------------- 91 106 92 107 The reservation schedule will show you all the sandboxes and their 93 availabilities. Please refer http://svn.orbit-lab.org/projects/orbit/wiki/SandBoxes for more details on the sandboxes 108 availability. Please refer http://svn.orbit-lab.org/projects/orbit/wiki/SandBoxes for more details on the sandboxes. 109 94 110 95 111 Do I get root access on my radio nodes? … … 98 114 Yes. The nodes are yours to do what you will during your slot. Just ssh root@nodeX-Y and be greeted by the familiar root@node:~/# prompt. 99 115 116 100 117 Do my nodes have consoles I can look at? 101 118 ---------------------------------------- … … 103 120 Yes. Each of the radio nodes has its own serial console with which you can interact through the chasis manager (CM). From the experiment console machine, telnet 10.1.X.Y 3025 in the case of the grid, and telnet 10.1.10N.XXXXYYYY 3025 in the case of the sandbox where N is the sandbox number. 104 121 105 Can I reboot (power cycle) my nodes? 122 123 Can I reboot or power cycle my nodes? 106 124 ------------------------------------ 107 125 … … 117 135 Hardware Setup 118 136 ============== 137 119 138 How many radio nodes are there? 120 139 ------------------------------- … … 122 141 Currently, we support 64 nodes in a 8*8 grid, and 10 1*2 node sandboxes. In the near future, this will be increased to 400 nodes in a 20*20 grid as well as an outdoor testbed consisting of 50 nodes located in and around Rutgers University, Busch Campus. 123 142 143 124 144 How many radio interfaces on each node? 125 145 --------------------------------------- … … 127 147 There are two mini-PCI 802.11 a/b/g interfaces cards on each node. In addition to that, there will be USB-based Bluetooth and Zygbee interfaces. 128 148 149 129 150 Which wireless cards are used on Orbit nodes? 130 151 --------------------------------------------- … … 135 156 What OS do the nodes run? 136 157 ------------------------- 137 The default Operating Systems that run on each of the radio nodes is Linux (Debian GNU/Linux 3.0 with Linux kernel 2.6.4). But every experimenter can load any OS they want. 158 The default Operating Systems that run on each of the radio nodes is Linux (Debian GNU/Linux 3.0 with Linux kernel 2.6). But every experimenter can load any OS they want. 159 138 160 139 161 Can I run my own Operating System?
