WITS: Auckland V

Trace Format ATM cell header capture.
Volume on Disk 8 GB
Number of Traces 30
Capture Start (Local) Thu Jan 25 17:30:00 2001
Capture End (Local) Fri Jan 26 00:59:59 2001
Total Duration 0 Days, 7 Hours, 30 Minutes and 0 Seconds
Packets Captured 2,710 million
Total Traffic 133 GB
Contiguity No gaps whatsoever.
Snapping Method All records are 12 bytes long, containing 4 bytes of the ATM cell header.
Rotation Policy Files rotated every 30 minutes.
Anonymization No anonymization is required for ATM cell header captures.

This is a continuous 7 and a half hour GPS-synchronized ATM cell header trace captured using a DAG 3 card at the University of Auckland. As this is an ATM cell header capture, there are no IP headers and, in fact, very little information at all aside from a timestamp and most (but not all) of the ATM cell header.

The tap was installed at an OC3c link carrying various Classical-IP-over-ATM, LANE and POTS services. All cells were captured and immediately processed to extract only the timestamp and header data. All other information was discarded. We assume, but do not know for certain, details regarding the types of traffic represented by each VPI/VCI were saved, but our copies of the traces do not appear to have come with that information.

This traceset was withdrawn from NLANR's Special Traces Archive in favour of Auckland VII. We do not know the reasons for the withdrawal. Until we can ascertain that there is nothing wrong with this traceset, recommend that you use Auckland VII if you need to study an ATM cell header trace. However, Auckland V will remain part of the WITS project, even if it is for purely historical purposes.

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 contained within the trace. Traditionally, Auckland traces have set direction 0 as traffic coming into the University and direction 1 as traffic originating from the University. However, without IP headers in the trace we have not been able to confirm that this still holds for this traceset.

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.

Name Local Start Time Duration Total Packets Compressed Size
20010125-173000-0 Thu Jan 25 17:30:00 2001 0:30:00 105 million 345 MB
20010125-173000-1 Thu Jan 25 17:30:00 2001 0:30:00 90 million 291 MB
20010125-180000-0 Thu Jan 25 18:00:00 2001 0:30:00 94 million 311 MB
20010125-180000-1 Thu Jan 25 18:00:00 2001 0:30:00 86 million 277 MB
20010125-183000-0 Thu Jan 25 18:30:00 2001 0:30:00 89 million 293 MB
20010125-183000-1 Thu Jan 25 18:30:00 2001 0:30:00 85 million 274 MB
20010125-190000-0 Thu Jan 25 19:00:00 2001 0:30:00 86 million 286 MB
20010125-190000-1 Thu Jan 25 19:00:00 2001 0:30:00 84 million 268 MB
20010125-193000-0 Thu Jan 25 19:30:00 2001 0:30:00 86 million 284 MB
20010125-193000-1 Thu Jan 25 19:30:00 2001 0:30:00 84 million 269 MB
20010125-200000-0 Thu Jan 25 20:00:00 2001 0:30:00 86 million 284 MB
20010125-200000-1 Thu Jan 25 20:00:00 2001 0:30:00 85 million 272 MB
20010125-203000-0 Thu Jan 25 20:30:00 2001 0:30:00 85 million 282 MB
20010125-203000-1 Thu Jan 25 20:30:00 2001 0:30:00 85 million 274 MB
20010125-210000-0 Thu Jan 25 21:00:00 2001 0:30:00 84 million 279 MB
20010125-210000-1 Thu Jan 25 21:00:00 2001 0:30:00 86 million 275 MB
20010125-213000-0 Thu Jan 25 21:30:00 2001 0:30:00 88 million 289 MB
20010125-213000-1 Thu Jan 25 21:30:00 2001 0:30:00 85 million 272 MB
20010125-220000-0 Thu Jan 25 22:00:00 2001 0:30:00 106 million 351 MB
20010125-220000-1 Thu Jan 25 22:00:00 2001 0:30:00 87 million 282 MB
20010125-223000-0 Thu Jan 25 22:30:00 2001 0:30:00 105 million 349 MB
20010125-223000-1 Thu Jan 25 22:30:00 2001 0:30:00 90 million 289 MB
20010125-230000-0 Thu Jan 25 23:00:00 2001 0:30:00 95 million 314 MB
20010125-230000-1 Thu Jan 25 23:00:00 2001 0:30:00 94 million 303 MB
20010125-233000-0 Thu Jan 25 23:30:00 2001 0:30:00 87 million 290 MB
20010125-233000-1 Thu Jan 25 23:30:00 2001 0:30:00 91 million 291 MB
20010126-000000-0 Fri Jan 26 00:00:00 2001 0:30:00 95 million 318 MB
20010126-000000-1 Fri Jan 26 00:00:00 2001 0:30:00 90 million 288 MB
20010126-003000-0 Fri Jan 26 00:30:00 2001 0:30:00 91 million 304 MB
20010126-003000-1 Fri Jan 26 00:30:00 2001 0:30:00 92 million 292 MB