(Sorted by associated publication year, not by trace collection year.)
Data (timing and sizes of Tor traffic flows) and code (to parse the flows and build models) from this paper.
Patches to enable a simple timing attack on the OneSwarm peer-to-peer data sharing network, a trace of the results of executing this attack, and a Monte Carlo simulation to show the efficacy of this attack at scale. More details are in the paper and accompanying documentation.
(Note that the details of the optimistic ACKing attack are included in the 2011 entry below.)
Matlab code for performing a passive localization attack simulation on the Reality Mining dataset. More details are in the paper and accompanying documentation.
A collection of TCP packets and ethernet frames captured locally (and for the former, remotely), including some background traffic. More details are in the paper and accompanying documentation.
A collection of TCP (pcap) and GPS/signal strength (gpx) traces. The files were generated by streaming music to mobile phones in the Amherst area. The traces contain only the TCP headers, and not the payload. More details are in the paper and accompanying documentation.
A collection of traces of well-behaved and overly-optimistic TCP ACKing file retrievals. The files were retrieved either from a directly-connected host, or proxied by that host. The traces include only the TCP headers, and not the payload. Also available is the code necessary to reproduce the measurements. More details are in the paper and README.
These traces were collected in UMass DieselNet in the months October-November 2007. See the documentation and related publication for details.
This set of traces were collected from UMass DieselNet during the Fall semester of 2007. The traces contain connection times and durations between two buses and between a bus and an AP.
This set of DieselNet traces were compiled in December 2007 and contains the connection quality between one bus and APs on the road. The connection quality is measured using AP beacons heard by the bus on a per second granularity.
A collection of traces from a campus network measurement on YouTube traffic. This collection contains trace data about user requests for specific YouTube content. Detailed information about the measurement setup and procedure can be found in the paper below. The data covers a measurement period between June 2007 and March 2008.
The trace was collected during the throwbox deployment in Umass DieselNet in Summer 2006. The traces contain bus-bus transfer records and bus-throwbox transfer records. See the documentation for details
This trace was collected during the DieselNet deployment in Spring 2007 characterizing connection between a bus and an open access point.
This set of traces were collected from UMass DieselNet during the spring semester of 2007. See the documentaion and related publication for details.
This set of traces were collected from UMass DieselNet during the spring semester of 2006. In addition to the bus-to-bus transfer records, the traces also include the bus-to-AP checkin records, and dispatching records (bus id to shift mapping). See the documentaion and related publication for details.
A collection of traces from a wireless measurement with directional antennas. Contains Iperf throughput data, tcdump traces and wireless signal strength information. Detailed information about the measurement setup and the configuration of the wireless links can be found in the documentation below.
UMassDieselNet: A Bus-based Disruption Tolerant Network. This is a network operating between approximately 30 of the 40 buses running routes serviced by UMassTransit; schedules and routes may be found here. This set of DieselNet logs was compiled during the Spring semester of 2005. The full trace description is available below.
Gateway link trace from gigabit ethernet connection entering UMASS. The trace contains anonymized packet headers for all non-Internet2 traffic. A full description of the trace format and the utilities to parse the binary files are available with the documentation.
Gateway link trace from gigabit ethernet connection entering UMASS. The trace contains anonymized packet headers for non-Internet2 traffic sourced from/destined to the hosts connected to public wireless access points (AP) and computer science network at UMASS campus. A full description of the trace format and the utilities to parse the binary files are available with the documentation.
A collection of wireless traces from the University of Puerto Rico. Contains wireless signal strength measurements for Dell and Thinkpad laptops. Tests were performed over distances of 500 feet and one mile. Data is presented in .cap files giving TCP dump packet headers.
These traces were gathered as part of an undergraduate course taught by Jim Kurose and Mike Zink.
See http://www-net.cs.umass.edu/cs496a/ for details.
A collection of traces of web requests and responses over an encrypted SSH tunnel. The collection spans traces of connections to 2000 sites, collected four times a day over several months from February 2006 through April 2006. Each connection was encrypted; the traces include only the TCP headers, and not the payload. More details are in the paper and README.
Gateway link trace from gigabit ethernet connection entering UMASS. The trace contains anonymized packet headers for all non-Internet2 traffic. A full description of the trace format and the utilities to parse the binary files are available with the documentation.
This is a collection of traces taken at the UMASS OIT gateway router. The traces are collected every morning from 9:30 to 10:30 from July 9th, 2004 to July 22nd, 2004. They are in DAG format. All the IP addresses have been anonymized with prefix preserving algorithms. Part of the data is used in the paper "Detecting Anomalies in Network Traffic Using Maximum Entropy Estimation" by Yu Gu, Andrew McCallum and Don Towsley. More details are in the paper and README.
A collection of traces of web requests and responses. The collection spans traces of connections to 100 sites, collected hourly over several months from November 2003 through March 2004. Each connection was encrypted; the traces include only the TCP headers, and not the payload. More details are in the paper and README.
The data were collected from a campus network for P2P file sharing based on the OpenNap server. The data consist of records of all the mp3 files shared by and transferred between users during an 81-day period between February 28, 2003 and May 21, 2003. Trace documentation is available below.
Statistics pages from two large trackers, late 2003 to early 2004. The pages are HTML output from a PHP script, so you will need to parse them yourself to extract useful information. The data is sufficiently anonymized; the tracker did not provide IP address information about connected hosts nor did it provide information about the content of running torrents. Clients are identified using a session-unique 40-character ID, and torrents are uniquely identified using a similar key.