ucsd/sigcomm2001200204233200204232006-11-14ucsd/sigcomm2001SNMP and tcpdump records from 4 access points at a three-day computer-science conference.This dataset includes SNMP and tcpdump records from 4 access points at a three-day computer-science conference.The initial version2002-04-232001-08-292001-08-316789http://sysnet.ucsd.edu/pawn/sigcomm-trace/http://www.crawdad.org/wiki/pmwiki.php?n=Main.Dataset.ucsd-sigcomm2001802.11802.11bpacket traceSNMPtcpdumpUsage CharacterizationNetwork Performance Analysis802.11 infrastructureWe recorded over three days at the ACM SIGCOMM'01 conference held at U.C. San Diego in August 2001. The conference was held on two full days, a Wednesday and Thursday, and one half day, a Friday. The scheduled times of the conference on each day are as follows: 8:00-18:00 for the full days, and 8:00-14:00 on the half day.Our wireless LAN was an IEEE 802.11b network installed in a large auditorium where the conference sessions were held. The auditorium has dimensions of 110x60x27 ft and was covered by four ORiNOCO AP-1000 wireless access points, labeled NorthEast (NE), NorthWest (NW), SouthEast (SE), and SouthWest (SW), installed in the ceiling. The APs provided overlapping coverage in the auditorium and the lobby. The western APs were close to the stage. The eastern APs were at the back of the room close to the main entrances, also providing coverage to the lobby. The subnet of APs was connected to a Cisco Catalyst 2924 switch over a 100BaseT link, which connected to the venue's intranet, then the campus gigabit backbone, and finally to the Internet. The APs were operating at a data rate of 11 Mbps, on channels 1, 4, 7, and 11, and at a power of 100mW. The AP handoff algorithm was configured to use 'small' cells. The wireless user community consisted of 195 distinct users (distinct MAC addresses), roughly 40% of the total attendees. User wireless hardware was heterogeneous, as attendees used their own personal wireless cards, and the trace includes traffic from 8 different vendors.The collected data consists of two parts. The first part is a record of SNMP performance monitoring data sampled from wireless access points (APs) serving the conference. The second part is a tcpdump trace consisting of anonymized packet headers of all wireless traffic. Both parts of the trace span all three days of the conference, capturing the workload of about 300,000 flows from 195 users consuming 4.6 GB of bandwidth.We anonymized the tcpdump trace using tcpdpriv to remove all sensitive information including, packet payloads and IP addresses in packet headers.6200204052006-11-14ucsd/sigcomm2001/snmpSNMP records from 4 access points at a three-day computer-science conference.This traceset includes SNMP records from 4 access points at a three-day computer-science conference.The initial version2002-04-052001-08-292001-08-31Usage CharacterizationNetwork Performance AnalysisWe collected a continuous trace of SNMP data from each of the four APs over a period of 52 hours from the start of the conference. The SNMP data consisted of aggregate packet level statistics of all traffic through both interfaces of the APs, including information at the link, network, and transport levels. In addition, the trace also contained detailed information about the mobile users associated to each of the APs, including the MAC address, the received signal-to-noise ratio (SNR), and the effective throughput.ucsd/sigcomm200112200204052006-11-1434567ucsd/sigcomm2001/snmp/StationsSNMP records for the stations assocated with 4 access points at a three-day computer-science conference.This trace includes SNMP records for the stations associated with 4 access points at a three-day computer-science conference.The initial versionfalse2002-04-052001-08-292002-08-31This trace contains 12 trace files. Those files are named Stations_%AP_Name%_%Day%.out -- where %AP_Name% can be one of NE, NW, SE, or SW; and %Day% can be Wed, Thu, or Fri. Thus the trace file for the NE AP on Wednesday, is Stations_NE_Wed.out. The SNMP OID used to generate these trace files was .1.3.6.1.4.1, which corresponds to the MIB entry for "Associated Stations" and gives the MAC address, average received SNR, total transmitted bytes, and total transmitted packets for each mobile station associated to the AP. Each poll entry begins with a timestamp and entries from successive polls are separated by the line "End of MIB subtree".The trace-collection routine polled the APs at one minute intervals./download/ucsd/sigcomm2001/Snmp_Stations.tar.gzucsd/sigcomm2001/snmp13200204052006-11-1434567ucsd/sigcomm2001/snmp/AP_MibtreeSNMP records for 4 access points at a three-day computer-science conference.This trace includes SNMP records for 4 access points at a three-day computer-science conference.The initial versionfalse2002-04-052001-08-292001-08-31This trace contains 12 trace files. Those files are named AP_%AP_Name%_%Day%.out -- where %AP_Name% can be one of NE, NW, SE, or SW; and %Day% can be Wed, Thu, or Fri. Thus the trace file for the NE AP on Wednesday, is AP_NE_Wed.out. These files were generated using the SNMP OID .1.3.6.1.2.1, which walks the entire MIB tree. Each poll begins with a timestamp and ends with the line "End of MIB subtree". These trace files contain all information recorded at the AP at the MAC, network, transport, and application layers. For example, the number of total unicast and multicast packets (bytes) transmitted and recevied, the number of unicast and multicast MAC-level errors and retransmissions, etc.The APs are polled at one-minute intervals./download/ucsd/sigcomm2001/Snmp_AP_Mibtree.tar.gzucsd/sigcomm2001/snmp7200411092006-11-14ucsd/sigcomm2001/tcpdumpTcpdump traceset from the wireless network at a three-day computer-science conference.This traceset includes tcpdump records from the wireless network at a three-day computer-science conference.The initial version2004-11-092001-09-252004-02-28Usage CharacterizationWe recorded the networklevel headers of the packets passing through the Cisco Catalyst 2924 switch for the duration of the conference.We used tcpriv to anonymize sensitive information like sender and receiver IP addresses to protect user privacy, and discarded all packet payloads.ucsd/sigcomm200114200204232006-11-14ucsd/sigcomm2001/tcpdump/08292005Tcpdump trace from the wireless network at a three-day computer-science conference.This trace includes tcpdump records from the wireless network at a three-day computer-science conference.The initial versionfalse2002-04-232001-08-292001-08-31tcpdump formatThe trace represents a collection of all the wireless IP traffic over the entire period of the conference./download/ucsd/sigcomm2001/sigcomm01.pcap.gzucsd/sigcomm2001/tcpdump320020405ucsd/sigcomm2001/snmp/Stationsucsd/sigcomm2001/snmp/AP_Mibtree2006-11-14A command-line utility that uses the standard Win32 SNMP Management API.The snmputil tool is a command-line utility that uses the standard Win32 SNMP Management API.tools/collect/snmp/snmputil.exeNAME CHANGED to tools/collect/snmp/snmputil.exe. Also see 'old name' field.ucsd/sigcomm2001/tool/snmputil.exetools/collect/snmp/snmputil.exe2002-04-056http://www.crawdad.org/wiki/pmwiki.php?n=Main.Tool.ucsd-sigcomm2001-tool-snmputil-exe802.11SNMPSNMP files whose format is the same as those of ucsd/sigcomm2001/snmp/Stations and ucsd/sigcomm2001/snmp/AP_Mibtree.option[get|getnext|walk] node_address password snmp_oidThe usage for snmputil is: snmputil option[get|getnext|walk] node_address password snmp_oid For example, to walk the entire MIB tree at the AP, the usage is: snmputil walk AP_IP_address password .1.3.6.1.2.1The snmputil tool is a command-line utility that uses the standard Win32 SNMP Management API. The source-code consists of one source file (snmputil.c) and a makefile. If you are building snmputil.exe on your own, make sure that you have the Windows SNMP libraries, snmpapi.lib and mgmtapi.lib./download/tools/collect/snmp/snmputil.exe/snmputil.tar.gz1213420020405ucsd/sigcomm2001/snmp/Stationsucsd/sigcomm2001/snmp/AP_Mibtree2006-11-14A tool for generating data matching the pattern given by the users.This tool generates the data matching the pattern given by the users.tools/process/snmp/extract.plNAME CHANGED to tools/process/snmp/extract.pl. Also see 'old name' field.ucsd/sigcomm2001/tool/extract.pltools/process/snmp/extract.pl2002-04-056http://www.crawdad.org/wiki/pmwiki.php?n=Main.Tool.ucsd-sigcomm2001-tool-extract-pl802.11SNMPSNMP trace obtained by snmputildata matching the pattern given by the usersThe extract.pl script can be used to parse all SNMP output files in the trace to look for a certain pattern. The pattern may be a phrase representing all or part of an SNMP OID, or simply text that appears in the trace file. The script has detailed comments on how to use it. Since we collected the SNMP data using snmputil, the scripts are written specifically to parse that output. The traces contain the SNMP data collected at one-minute intervals, and extract.pl uses these timestamps in the trace file to parse the data. Since each SNMP OID has a unique entry in the trace, extract.pl can be used to extract the values of all the SNMP variables over the entire duration of the trace./download/tools/process/snmp/extract.pl/extract.pl1213520020405ucsd/sigcomm2001/snmp/Stationsucsd/sigcomm2001/snmp/AP_Mibtree2006-11-14A tool for returning number of users as a function of time.This tool returns number of users as a function of time.tools/analyze/snmp/index.plNAME CHANGED to tools/analyze/snmp/index.pl. Also see 'old name' field.ucsd/sigcomm2001/tool/index.pltools/analyze/snmp/index.pl2002-04-056http://www.crawdad.org/wiki/pmwiki.php?n=Main.Tool.ucsd-sigcomm2001-tool-index-pl802.11SNMPoutput of extract.plnumber of users as a function of timeOnce the SNMP traces have been processed using extract.pl, index.pl returns number of users as a function of time./download/tools/analyze/snmp/index.pl/index.pl620020405ucsd/sigcomm2001/snmp/Stationsucsd/sigcomm2001/snmp/AP_Mibtree2006-11-14A tool for listing time instances of occurrence of a particular mac-addresses.This tool lists time instances of occurrence of a particular mac-addresses.tools/analyze/snmp/mac_addr.plNAME CHANGED to tools/analyze/snmp/mac_addr.pl. Also see 'old name' field.ucsd/sigcomm2001/tool/mac_addr.pltools/analyze/snmp/mac_addr.pl2002-04-056http://www.crawdad.org/wiki/pmwiki.php?n=Main.Tool.ucsd-sigcomm2001-tool-mac_addr-pl802.11SNMPoutput of extract.pltime instances of occurrence of a particular mac-addressesOnce the SNMP traces have been processed using extract.pl, mac_addr.pl returns time instances of occurrence of a particular mac-addresses./download/tools/analyze/snmp/mac_addr.pl/mac_addr.pl720020405ucsd/sigcomm2001/snmp/Stationsucsd/sigcomm2001/snmp/AP_Mibtree2006-11-14A tool for listing unique mac-addresses in the trace file.This tool lists unique mac-addresses in the trace file.tools/analyze/snmp/pick_mac_addr.plNAME CHANGED to tools/analyze/snmp/pick_mac_addr.pl. Also see 'old name' field.ucsd/sigcomm2001/tool/pick_mac_addr.pltools/analyze/snmp/pick_mac_addr.pl2002-04-056http://www.crawdad.org/wiki/pmwiki.php?n=Main.Tool.ucsd-sigcomm2001-tool-pick_mac_addr-pl802.11SNMPoutput of extract.pllisting of unique mac-addresses in the trace fileOnce the SNMP traces have been processed using extract.pl, pick_mac_addr.pl returns listing of unique mac-addresses in the trace file/download/tools/analyze/snmp/pick_mac_addr.pl/pick_mac_addr.pl6ucsd/sigcomm2001tools/collect/snmp/snmputil.exetools/process/snmp/extract.pltools/analyze/snmp/index.pltools/analyze/snmp/mac_addr.pltools/analyze/snmp/pick_mac_addr.plAnand Balachandrananandba@microsoft.comMicrosoft Corporation7ucsd/sigcomm2001Geoffrey M. Voelkervoelker@cs.ucsd.eduU. C. San DiegoComputer ScienceAssociate Professor
9500 Gilman Dr. 0114 , La Jolla, CA 92093 USA
http://www.cs.ucsd.edu/~voelker
8ucsd/sigcomm2001Paramvir Bahlbahl@microsoft.comMicrosoft Research
One Microsoft Way, Redmond, WA 98052 USA
9ucsd/sigcomm2001P. Venkat Ranganvenkat@cs.ucsd.eduU. C. San DiegoComputer ScienceProfessor
9500 Gilman Dr. 0114 , La Jolla, CA 92093 USA
bahl-breathing
Paramvir (Victor) BahlMohammad T. HajiaghayiKamal JainSayyed Vahab MirrokniLili QiuAmin SaberiCell Breathing in Wireless LANs: Algorithms and EvaluationIEEE Transactions on Mobile Computing6220071536-1233164-178http://doi.ieeecomputersociety.org/10.1109/TMC.2007.20IEEE Computer Society
Los Alamitos, CA, USA
http://www.cs.utexas.edu/~lili/papers/pub/TMC2006.pdfcrawdadmeasurementwirelessdartmouth_campusucsd_sigcomm2001stanford_gatesibm_watsoncrawdaducsd/sigcomm2001
20070001
balachandran-behaviorAnand BalachandranGeoffrey M. VoelkerParamvir BahlP. Venkat RanganCharacterizing User Behavior and Network Performance in a Public Wireless LANmeasurementwirelessucsd_sigcomm2001crawdadProceedings of the 2002 ACM SIGMETRICS Conference195-205--06--2002
Marina Del Rey, CA
ACM PressACMhttp://doi.acm.org/10.1145/511334.511359wireless network, workload characterizationThis paper presents and analyzes user behavior and network performance in a public-area wireless network using a workload captured at a well-attended ACM conference. The goals of our study are: (1) to extend our understanding of wireless user behavior and wireless network performance; (2) to characterize wireless users in terms of a parameterized model for use with analytic and simulation studies involving wireless LAN traffic; and (3) to apply our workload analysis results to issues in wireless network deployment, such as capacity planning, and potential network optimizations, such as algorithms for load balancing across multiple access points (APs) in a wireless network.wireless-meas,crawdaducsd/sigcomm2001
20020601