PcapWT: An efficient packet extraction tool for large volume network traces
Author
dc.contributor.author
Kim, Young-Hwan
Author
dc.contributor.author
Konow, Roberto
Author
dc.contributor.author
Dujovne, Diego
Author
dc.contributor.author
Turletti, Thierry
Author
dc.contributor.author
Dabbous, Walid
Author
dc.contributor.author
Navarro, Gonzalo
Admission date
dc.date.accessioned
2015-07-15T13:24:23Z
Available date
dc.date.available
2015-07-15T13:24:23Z
Publication date
dc.date.issued
2015
Cita de ítem
dc.identifier.citation
Computer Networks 79 (2015) 91–102
en_US
Identifier
dc.identifier.uri
https://repositorio.uchile.cl/handle/2250/131975
Abstract
dc.description.abstract
Network packet tracing has been used for many different purposes during the last few decades,
such as network software debugging, networking performance analysis, forensic
investigation, and so on. Meanwhile, the size of packet traces becomes larger, as the speed
of network rapidly increases. Thus, to handle huge amounts of traces, we need not only
more hardware resources, but also efficient software tools. However, traditional tools are
inefficient at dealing with such big packet traces. In this paper, we propose pcapWT, an
efficient packet extraction tool for large traces. PcapWT provides fast packet lookup by
indexing an original trace using a wavelet tree structure. In addition, pcapWT supports
multi-threading for avoiding synchronous I/O and blocking system calls used for file
processing, and is particularly efficient on machines with SSD. PcapWT shows remarkable
performance enhancements in comparison with traditional tools such as tcpdump and most
recent tools such as pcapIndex in terms of index data size and packet extraction time. Our
benchmark using large and complex traces shows that pcapWT reduces the index data size
down below 1% of the volume of the original traces. Moreover, packet extraction performance
is 20% better than with pcapIndex. Furthermore, when a small amount of packets
are retrieved, pcapWT is hundreds of times faster than tcpdump.