WITS: IPLS III

Trace Format ERF, captured using a DAG 6 card.
Volume on Disk 62 GB
Number of Traces 50
Capture Start (Local) Tue Jun 1 19:31:21 2004
Capture End (Local) Tue Jun 1 23:40:00 2004
Total Duration 0 Days, 4 Hours, 8 Minutes and 39 Seconds
Packets Captured 3,310 million
Total Traffic 2,733 GB
Contiguity Mostly contiguous, but a couple of gaps due to trace corruption.
Snapping Method Fixed-length 64 byte truncation.
Rotation Policy Files were rotated on 10 minute boundaries.
Anonymization IP addresses mapped into 10.*.*.* address space. Any payload after the transport header has been zeroed. Checksums have also been replaced.
Download Link
Download Link (RIPE repository)

This trace set is also known as Abilene III.

This is a (mostly) contiguous passive trace set taken the Indianapolis router node on the Abilene network, instrumenting the 10 Gigabit backbone. This particular trace set measures an OC192c Packet-over-SONET link towards Kansas City (KSCY) using a DAG 6.1 capture card.

When processing the traces to generate data for these webpages, we found that two of the traces appeared to be corrupted, i.e. invalid values were present in important fields such as the capture length or link type. As a result, we have truncated those traces at the point where we encountered the corrupt packet. It is not clear where the corruption has arisen from - there is no documentation to suggest that the traces were previously damaged. The original copies of the truncated traces have been placed in the archive/ directory on the FTP server. However, this does mean that the trace set is not completely contiguous.

Each trace file is named using the following format: yyyymmdd-HHMMSS-[direction].gz. The time and date refers to the local time when the capture was started. The direction refers to which half of the link is recorded in the trace. Direction 0 is westbound and direction 1 is eastbound.

The IP addresses in the traces have been replaced using a one-to-one mapping into the 10.0.0.0/8 address space. Each anonymised address is assigned sequentially so the first real-world address observed is mapped to 10.0.0.1, the next new address is 10.0.0.2 and so on. The mapping database is preserved across the entire trace set as far as we can tell.

Checksums have been replaced with zeroes in each packet and any retained payload following the transport header has also been zeroed.

The recommended method for processing these traces is to use Libtrace, which we have developed. There are a number of tools included with libtrace such as a packet dumping utility, a trace format converter (for example, to convert to pcap), a trace splitting/filtering tool and a few statistic generators. We suggest you examine the Libtrace Wiki for more details on the Libtrace tools and the library itself.

Acknowledgements: Some of the information presented on this page has bee sourced from the old NLANR page about this traceset.

Name Local Start Time Duration Total Packets Compressed Size
20040601-193121-0 Tue Jun 1 19:31:21 2004 0:08:39 56 million 1,138 MB
20040601-193121-1 Tue Jun 1 19:31:21 2004 0:08:39 68 million 1,273 MB
20040601-194000-0 Tue Jun 1 19:40:00 2004 0:10:00 60 million 1,256 MB
20040601-194000-1 Tue Jun 1 19:40:00 2004 0:10:00 71 million 1,376 MB
20040601-195000-0 Tue Jun 1 19:50:00 2004 0:10:00 60 million 1,247 MB
20040601-195000-1 Tue Jun 1 19:50:00 2004 0:10:00 72 million 1,386 MB
20040601-200000-0 Tue Jun 1 20:00:00 2004 0:10:00 60 million 1,263 MB
20040601-200000-1 Tue Jun 1 20:00:00 2004 0:10:00 72 million 1,402 MB
20040601-201000-0 Tue Jun 1 20:10:00 2004 0:10:00 62 million 1,288 MB
20040601-201000-1 Tue Jun 1 20:10:00 2004 0:10:00 75 million 1,437 MB
20040601-202000-0 Tue Jun 1 20:20:00 2004 0:10:00 61 million 1,269 MB
20040601-202000-1 Tue Jun 1 20:20:00 2004 0:10:00 73 million 1,403 MB
20040601-203000-0 Tue Jun 1 20:30:00 2004 0:10:00 78 million 1,478 MB
20040601-203000-1 Tue Jun 1 20:30:00 2004 0:10:00 72 million 1,380 MB
20040601-204000-0 Tue Jun 1 20:40:00 2004 0:10:00 74 million 1,404 MB
20040601-204000-1 Tue Jun 1 20:40:00 2004 0:10:00 72 million 1,377 MB
20040601-205000-0 Tue Jun 1 20:50:00 2004 0:10:00 78 million 1,443 MB
20040601-205000-1 Tue Jun 1 20:50:00 2004 0:10:00 70 million 1,350 MB
20040601-210000-0 Tue Jun 1 21:00:00 2004 0:10:00 99 million 1,705 MB
20040601-210000-1 Tue Jun 1 21:00:00 2004 0:10:00 69 million 1,334 MB
20040601-211000-0 Tue Jun 1 21:10:00 2004 0:10:00 83 million 1,527 MB
20040601-211000-1 Tue Jun 1 21:10:00 2004 0:10:00 73 million 1,394 MB
20040601-212000-0 Tue Jun 1 21:20:00 2004 0:10:00 78 million 1,457 MB
20040601-212000-1 Tue Jun 1 21:20:00 2004 0:10:00 72 million 1,387 MB
20040601-213000-0 Tue Jun 1 21:30:00 2004 0:10:00 59 million 1,229 MB
20040601-213000-1 Tue Jun 1 21:30:00 2004 0:10:00 70 million 1,352 MB
20040601-214000-0 Tue Jun 1 21:40:00 2004 0:10:00 57 million 1,200 MB
20040601-214000-1 Tue Jun 1 21:40:00 2004 0:10:00 69 million 1,322 MB
20040601-215000-0 Tue Jun 1 21:50:00 2004 0:10:00 59 million 1,220 MB
20040601-215000-1 Tue Jun 1 21:50:00 2004 0:10:00 69 million 1,306 MB
20040601-220000-0 Tue Jun 1 22:00:00 2004 0:03:52 22 million 565 MB
20040601-220000-1 Tue Jun 1 22:00:00 2004 0:10:00 70 million 1,343 MB
20040601-221000-0 Tue Jun 1 22:10:00 2004 0:10:00 58 million 1,215 MB
20040601-221000-1 Tue Jun 1 22:10:00 2004 0:10:00 68 million 1,308 MB
20040601-222000-0 Tue Jun 1 22:20:00 2004 0:10:00 58 million 1,210 MB
20040601-222000-1 Tue Jun 1 22:20:00 2004 0:10:00 67 million 1,294 MB
20040601-223000-0 Tue Jun 1 22:30:00 2004 0:10:00 59 million 1,219 MB
20040601-223000-1 Tue Jun 1 22:30:00 2004 0:10:00 69 million 1,307 MB
20040601-224000-0 Tue Jun 1 22:40:00 2004 0:10:00 59 million 1,214 MB
20040601-224000-1 Tue Jun 1 22:40:00 2004 0:10:00 68 million 1,297 MB
20040601-225000-0 Tue Jun 1 22:50:00 2004 0:10:00 58 million 1,197 MB
20040601-225000-1 Tue Jun 1 22:50:00 2004 0:01:05 7 million 165 MB
20040601-230000-0 Tue Jun 1 23:00:00 2004 0:10:00 60 million 1,240 MB
20040601-230000-1 Tue Jun 1 23:00:00 2004 0:10:00 69 million 1,323 MB
20040601-231000-0 Tue Jun 1 23:10:00 2004 0:10:00 63 million 1,293 MB
20040601-231000-1 Tue Jun 1 23:10:00 2004 0:10:00 73 million 1,388 MB
20040601-232000-0 Tue Jun 1 23:20:00 2004 0:10:00 61 million 1,262 MB
20040601-232000-1 Tue Jun 1 23:20:00 2004 0:10:00 72 million 1,363 MB
20040601-233000-0 Tue Jun 1 23:30:00 2004 0:10:00 61 million 1,240 MB
20040601-233000-1 Tue Jun 1 23:30:00 2004 0:10:00 70 million 1,327 MB