This dataset is part of the CRAWDAD archive. CRAWDAD is the Community Resource for Archiving Wireless Data At Dartmouth, a wireless network data resource for the research community. This archive was created to store wireless trace data from many contributing locations, and staff to develop better tools for collecting, anonymizing, and analyzing the data. The CRAWDAD archive was originally created and maintained by Dartmouth College and can now be on found on IEEE DataPort.
MANET dataset of outdoor experments for comparing differnet routing algorithms.
This dataset contains outdoor runs of MANET (Mobile Ad-hoc network) routing algorithms to compare the performance of four different routing algorithms.
https://doi.org/10.15783/C7301Z Nov 2006
Most comparisons of wireless ad hoc routing algorithms involve simulated or indoor trial runs, or outdoor runs with only a small number of nodes, potentially leading to an incorrect picture of algorithm performance. For outdoor comparison of four different routing algorithms, APRL, AODV, ODMRP, and STARA, we run on top of thirty-three 802.11-enabled laptops moving randomly through an athletic field. This comparison provides insight into the behavior of ad hoc routing algorithms at larger real-world scales than have been considered so far.
The outdoor routing experiment took place on a rectangular athletic field measuring approximately 225 (north-south) by 365 (eastwest) meters. This field can be roughly divided into four flat, equalsized sections, three of which are at the same altitude, and one of which (at the southeast corner) is approximately four to six meters lower. There was a short, steep slope between the upper and lower sections. We chose this particular athletic field because it was physically distant from campus and the campus wireless network, reducing potential interference.
We configured the 802.11 cards to use wireless channel 9 for maximum separation from the standard channels of 1, 6 and 11, further reducing potential interference. We used 41 laptops, 40 as application laptops, and one as a control laptop.
The routing experiments ran on top of a set of 41 Gateway Solo 9300 laptops, each with a 10GB disk, 128MB of main memory, and a 500MHz Intel Pentium III CPU with 256KB of cache. We used one laptop to control each experiment, leaving 40 laptops to actually run the ad hoc routing algorithms. Each laptop ran Linux kernel version 2.2.19 with PCMCIA card manager version 3.2.4 and had a Lucent (Orinoco) Wavelan Turbo Gold 802.11b wireless card. Although these cards can transmit at different bit rates, can auto-adjust this bit rate depending on the observed signal-to-noise ratio, and can auto-adjust the channel to arrive at a consistent channel for all the nodes in the ad hoc network, we used an ad hoc mode in which the transmission rate was fixed at 2 Mb/s, and in which the channel could be chosen manually but was fixed thereafter. Specifically, we used Lucent (Orinoco) firmware version 4.32 and the proprietary ad hoc "demo" mode originally developed by Lucent.
Although the demo mode has been deprecated in favor of the IEEEdefined IBSS, we used the demo mode to ensure consistency with a series of ad hoc routing experiments of which this outdoor experiment was a culminating event. 6 The fixed rate also made it much easier to analyze the routing results, since we did not need to account for automatic changes in each card's transmission rate. On the other hand, we would expect to see variation in the routing results if we had used IBSS instead, both due to its multi-rate capabilities and its general improvements over the demo mode. The routing results remain representative, however, since demo mode provides sufficient functionality to serve as a reasonable data-link layer. Finally, each laptop had a Garmin eTrex GPS unit attached via the serial port. These GPS units did not have differential GPS capabilities, but were accurate to within thirty feet during the experiment.
data collection methodology
We log the events of routing algorithms in each laptop. A GPS service runs on each laptop, reading and recording the current laptop position from the attached GPS unit.
disruptions to data collection
During the experiment, seven laptops generated no network traffic due to hardware and configuration issues, and an eighth laptop generated the position beacons only for the first half of the experiment. The seven complete failures left thirty-three laptops actually participating in the ad hoc routing.
This dataset contains the following traceset:
Traceset of outdoor MANET experments for comparing differnet routing algorithms.
reason for most recent change
the initial version
date/time of measurement start
date/time of measurement end
Measurement trace from wireless network at Dartmouth College.
This dataset includes measurement trace for over 450 access points and several thousand users at dartmouth college.
last modified: 2006-11-14
reason for most recent change: Infocom 2004 trace is added.
short description: Two-year records showing the location (AP association) of each wireless card seen on campus.
description: Over three years of nearly continuous records showing the location (access-point association) of each wireless card seen on campus. We used this data for our study of location predictors, published in [INFOCOM'04 paper] and a subsequent, expanded [technical report]. This data is derived from the syslog data.
The trace used for this paper is gzipped tar file [51MB].
release date: 2004-08-05
methodology: We extracted user traces from dartmouth/campus/syslog. Each user's trace is a series of locations, that is, access-point names. We introduced the special location 'OFF' to represent the user's departure from the network (which occurs when the user turns off their computer or their wireless card, or moves out of range of all access points). The traces varied widely in length (the number of locations in the sequence). Users with longer traces were either more active (using their card more), more mobile (thus changing access points more often), or used the network for a longer period (some users have been on the network since April 2001, and some others have only recently arrived on campus).
sanitization: same as dartmouth/campus/syslog
disruptions to data collection: same as dartmouth/campus/syslog
limitation: same as dartmouth/campus/syslog