[Dataset] uw/sigcomm2004 (v. 2006-10-17)

top

split a big pcap file into small (less than 1GB) pcap files and create a download directory for each trace

The changed components are as follows:

@MISC{uw-sigcomm2004-2006-10-17,
  author = {Maya Rodrig and Charles Reis and Ratul Mahajan and David Wetherall and John Zahorjan and Ed Lazowska},
  title = {{CRAWDAD} data set uw/sigcomm2004 (v. 2006-10-17)}, 
  howpublished = {Downloaded from http://crawdad.cs.dartmouth.edu/uw/sigcomm2004},
  month = oct,  
  year = 2006
}
					

We are trying to understand how well 802.11 networks work 
in practice and how they can be improved. This dataset includes the traces 
collected by wireless monitoring and wired monitoring using tcpdump.

Our trace environment is the open wireless network provided to
roughly 550 participants who attended the SIGCOMM conference
in Portland, Oregon from 8/30/04 to 9/03/04. We view this 
as characteristic of a large and busy hotspot setting. 
The conference took place in a hotel with a layout depicted 
in the collection map below (in download url section).

A wireless network comprised of 5 APs was set up for the conference, 
operating in 802.11b mode1 on channels 1, 8 and 11 (even though 
channels 8 and 11 are not orthogonal). Internet connectivity was 
provided by four separate DSL access lines.  

AP channels are as follows (see the collection map below (in download url section) 
for the location of each AP):

channel 1: sigcomm-nat,sigcomm-public-3,sigcomm-public-1
channel 8: sigcomm-nat-foyer
channel 11: sigcomm-public-2

We monitored the activity on the wireless network in two ways.
The first method was wireless monitors. 
The second monitoring method was traditional wired traces.

MAC addresses and IP addresses have been anonymized using a tool 
from CRAWDAD project.  Anonymization is consistent across trace files 
(IP-x maps to IP-y in all of them).

1. One limitation that was beyond our control is that the SIGCOMM
network was hampered by intermittent usability problems. We understand
that these problems stemmed from the DHCP and DNS
configurations and caused Internet connectivity to become unavailable
to some clients. 

2. A second limitation is that the different APs were assigned to
logically different networks (with different SSIDs), such that users
or their operating systems selected one AP for connectivity.

[Traceset] uw/sigcomm2004/wireless (v. 2006-10-17)

top

split a big pcap file into small (less than 1GB) pcap files and create a download directory for each trace

The changed components are as follows:

@MISC{uw-sigcomm2004-wireless-2006-10-17,
  author = {Maya Rodrig and Charles Reis and Ratul Mahajan and David Wetherall and John Zahorjan and Ed Lazowska},
  title = {{CRAWDAD} trace set uw/sigcomm2004/wireless (v. 2006-10-17)}, 
  howpublished = {Downloaded from http://crawdad.cs.dartmouth.edu/uw/sigcomm2004/wireless},
  month = oct,  
  year = 2006
}
					

Traceset of wireless monitoring

The first method was wireless monitors. We placed five PCs, each
with three Netgear WAG311 wireless adapters, near the APs. Each
monitor listened on all three active channels, using external antennas
which we placed at least a foot apart from each other to avoid
interference. Multiple monitors were within the range of each AP
to provide information on the spatial diversity of transmission and
reception.
We logged all observed activity using tcpdump, capturing 802.11
control and management packets as well as data packets and writing
complete packets to disk. The PHY information includes a receive
signal strength indicator (RSSI) and the transmission rate.
The MAC information is the entire 802.11 frame header and CRC.
We also customized our MADWiFi driver to log reception errors
that provide information on periods when transmissions were detected
but not correctly decoded.  

Monitor channels (primarily) are as follows: ath0=1, ath1=8, ath2=11. 
Exception is that the APs switched from channel 8 to channel 6 on Wednesday 
morning (9/1/2004); kalahari switched ath1 to channel 6 Wednesday at 12:24 pm, 
and sahara, chihuahuan, and sonoran switched ath1 to channel 6 Friday at 8:30 am.

1. We used the noise field of the prism frame to encode 
error status of frames, so be sure to filter down to only those frames 
with noise values of zero. others are errored packets 
(corrupt or not fully received).  

2. The clocks on different machines were not synchronized; 
chihuahuan's clock is the most accurate

three of the ath2 traces (chihuahuan, mojave, and sonoran) 
were very large. the split command was used to break them up into 
1G segments to allow sharing them online. you will need to 
cat the segments of each before unzipping.

[Traceset] uw/sigcomm2004/tcpdump (v. 2005-08-01)

top

the initial version

@MISC{uw-sigcomm2004-tcpdump-2005-08-01,
  author = {Maya Rodrig and Charles Reis and Ratul Mahajan and David Wetherall and John Zahorjan and Ed Lazowska},
  title = {{CRAWDAD} trace set uw/sigcomm2004/tcpdump (v. 2005-08-01)}, 
  howpublished = {Downloaded from http://crawdad.cs.dartmouth.edu/uw/sigcomm2004/tcpdump},
  month = aug,  
  year = 2005
}
					

Traceset of wired sniffer

The second monitoring method was traditional wired traces, collected
using tcpdump on the network segment connected to the
APs. This provides a view of packets exchanged between the APs
and the Internet.

[Trace] uw/sigcomm2004/wireless/chihuahuan (v. 2006-10-17)

top

split a big pcap file into small (less than 1GB) pcap files and create a download directory for each trace

@MISC{uw-sigcomm2004-wireless-chihuahuan-2006-10-17,
  author = {Maya Rodrig and Charles Reis and Ratul Mahajan and David Wetherall and John Zahorjan and Ed Lazowska},
  title = {{CRAWDAD} trace uw/sigcomm2004/wireless/chihuahuan (v. 2006-10-17)}, 
  howpublished = {Downloaded from http://crawdad.cs.dartmouth.edu/uw/sigcomm2004/wireless/chihuahuan},
  month = oct,  
  year = 2006
}
					

Trace of wireless sniffer (chihuahuan)

For hw/sw configuration, see the methodology section of 
the parent traceset uw/sigcomm2004/wireless. For the location of wireless sniffer,
see the collection map linked in the dataset uw/sigcomm2004.

tcpdump format (including Prism header). 
contents above the transport layer have been removed.

[Trace] uw/sigcomm2004/wireless/kalahari (v. 2006-10-17)

top

split a big pcap file into small (less than 1GB) pcap files and create a download directory for each trace

@MISC{uw-sigcomm2004-wireless-kalahari-2006-10-17,
  author = {Maya Rodrig and Charles Reis and Ratul Mahajan and David Wetherall and John Zahorjan and Ed Lazowska},
  title = {{CRAWDAD} trace uw/sigcomm2004/wireless/kalahari (v. 2006-10-17)}, 
  howpublished = {Downloaded from http://crawdad.cs.dartmouth.edu/uw/sigcomm2004/wireless/kalahari},
  month = oct,  
  year = 2006
}
					

Trace of wireless sniffer (kalahari)

For hw/sw configuration, see the methodology section of 
the parent traceset uw/sigcomm2004/wireless. For the location of wireless sniffer,
see the collection map linked in the dataset uw/sigcomm2004.

tcpdump format (including Prism header).
contents above the transport layer have been removed.

[Trace] uw/sigcomm2004/wireless/mojave (v. 2006-10-17)

top

split a big pcap file into small (less than 1GB) pcap files and create a download directory for each trace

@MISC{uw-sigcomm2004-wireless-mojave-2006-10-17,
  author = {Maya Rodrig and Charles Reis and Ratul Mahajan and David Wetherall and John Zahorjan and Ed Lazowska},
  title = {{CRAWDAD} trace uw/sigcomm2004/wireless/mojave (v. 2006-10-17)}, 
  howpublished = {Downloaded from http://crawdad.cs.dartmouth.edu/uw/sigcomm2004/wireless/mojave},
  month = oct,  
  year = 2006
}
					

Trace of wireless sniffer (mojave)

For hw/sw configuration, see the methodology section of 
the parent traceset uw/sigcomm2004/wireless. For the location of wireless sniffer,
see the collection map linked in the dataset uw/sigcomm2004.

tcpdump format (including Prism header). 
contents above the transport layer have been removed.

[Trace] uw/sigcomm2004/wireless/sahara (v. 2006-10-17)

top

split a big pcap file into small (less than 1GB) pcap files and create a download directory for each trace

@MISC{uw-sigcomm2004-wireless-sahara-2006-10-17,
  author = {Maya Rodrig and Charles Reis and Ratul Mahajan and David Wetherall and John Zahorjan and Ed Lazowska},
  title = {{CRAWDAD} trace uw/sigcomm2004/wireless/sahara (v. 2006-10-17)}, 
  howpublished = {Downloaded from http://crawdad.cs.dartmouth.edu/uw/sigcomm2004/wireless/sahara},
  month = oct,  
  year = 2006
}
					

Trace of wireless sniffer (sahara)

For hw/sw configuration, see the methodology section of 
the parent traceset uw/sigcomm2004/wireless. For the location of wireless sniffer,
see the collection map linked in the dataset uw/sigcomm2004.

tcpdump format (including Prism header).
contents above the transport layer have been removed.

[Trace] uw/sigcomm2004/wireless/sonoran (v. 2006-10-17)

top

split a big pcap file into small (less than 1GB) pcap files and create a download directory for each trace

@MISC{uw-sigcomm2004-wireless-sonoran-2006-10-17,
  author = {Maya Rodrig and Charles Reis and Ratul Mahajan and David Wetherall and John Zahorjan and Ed Lazowska},
  title = {{CRAWDAD} trace uw/sigcomm2004/wireless/sonoran (v. 2006-10-17)}, 
  howpublished = {Downloaded from http://crawdad.cs.dartmouth.edu/uw/sigcomm2004/wireless/sonoran},
  month = oct,  
  year = 2006
}
					

Trace of wireless sniffer (sonoran)

For hw/sw configuration, see the methodology section of 
the parent traceset uw/sigcomm2004/wireless. For the location of wireless sniffer,
see the collection map linked in the dataset uw/sigcomm2004.

tcpdump format (including Prism header). 
contents above the transport layer have been removed.

[Trace] uw/sigcomm2004/tcpdump/greatvictoria (v. 2005-08-01)

top

the initial version

@MISC{uw-sigcomm2004-tcpdump-greatvictoria-2005-08-01,
  author = {Maya Rodrig and Charles Reis and Ratul Mahajan and David Wetherall and John Zahorjan and Ed Lazowska},
  title = {{CRAWDAD} trace uw/sigcomm2004/tcpdump/greatvictoria (v. 2005-08-01)}, 
  howpublished = {Downloaded from http://crawdad.cs.dartmouth.edu/uw/sigcomm2004/tcpdump/greatvictoria},
  month = aug,  
  year = 2005
}
					

Trace of wired sniffer (greatvictoria)

For hw/sw configuration, see the methodology section of 
the parent traceset uw/sigcomm2004/tcpdump. For the location of wireless sniffer,
see the collection map linked in the dataset uw/sigcomm2004.

tcpdump format (wired). 
contents above the transport layer have been removed.

[Author] Maya Rodrig

top

[Author] Charles Reis

top

[Author] Ratul Mahajan

top

[Author] David Wetherall

top

[Author] John Zahorjan

top

[Author] Ed Lazowska

top

[Paper] rodrig-hotspot

top