News

Join the CRAWDAD community

Reset your CRAWDAD account password

Datasets and tools by name

Datasets and tools by release date

Datasets and tools by keyword:

Datasets by measurement purpose:

About the CRAWDAD project

CRAWDAD references in CiteULike

CRAWDAD contributors by country

CRAWDAD members by country

CRAWDAD FAQ

Contact Us

CRAWDAD sponsors

Related websites

 

 Search CRAWDAD via Google:

The pdx/vwave dataset (v. 2009-07-04)  >  the wlan_pcap traceset

There are 6 traces in this traceset
last modified
2007-08-29
short description

Traceset of wireless LAN traffic around Portland, Oregon using a commercial sniffer VWave.

description

Traceset of six wireless LAN traffic traces around Portland, Oregon, collected using a commercial sniffer VWave which has a nano-second time resolution.

reason for most recent change
the initial version
release date
2007-08-13
date/time of measurement start
2006-06-12
date/time of measurement end
2006-07-24
network type
802.11 infrastructure
methodology

The WT20 hardware consists of two 802.11 reference radios, real-time linux, and two processors. The WT20 provides nanosecond resolution timestamps and it logs the time when it began seeing a frame and the time when the frame finished arriving.

We are using Veriwave WT20 in a somewhat novel way. It listens with two radios simultaneously on the same channel, recording frames to a per-radio, 256 MB, ring-buffer.

The WT20's firmware will discard any frames received with a signal less than -75 dBm, but the rest (Data and Management, but not Control) are logged without any scrubbing. A tclsh script, running on a laptop connected to the WT20 (via ethernet), grabs the contents of this ring-buffer from each radio in-turn, every 10 seconds.

This data is dumped as a VWR file, a proprietary Veriwave file format, and then converted to a libpcap file on the fly. At the end of a 4 hour capture we have 1440 files which are stitched together using a program we have developed for this purpose (after finding that existing tools like mergecap and tcpslice either contained bugs or didn't work with 802.11 traces).

 the pdx/vwave/wlan_pcap/psu-cs trace
 the pdx/vwave/wlan_pcap/library trace
 the pdx/vwave/wlan_pcap/cafeteria trace
 the pdx/vwave/wlan_pcap/pioneer-sq trace
 the pdx/vwave/wlan_pcap/urban-grind trace
 the pdx/vwave/wlan_pcap/powells trace
 how to cite this traceset