summaryrefslogtreecommitdiff
path: root/net/tcpflow
AgeCommit message (Collapse)AuthorFilesLines
2009-07-17Give up MAINTAINERadrianp1-2/+2
2008-06-20Add DESTDIR support.joerg1-1/+3
2007-02-22Whitespace cleanup, courtesy of pkglint.wiz1-2/+2
Patch provided by Sergey Svishchev in private mail.
2006-01-02Include a set of patches from Jukka Salmi in PR# 30805adrianp6-2/+201
The patches are a modified version of some enhancements to tcpflow from Debian Adds the following options: -e When outputting to the console each flow will be output in alternating colours. -C Console print without the packet source and destination details being printed. Print the contents of packets to stdout as they are received, without storing any captured data to files (implies -s).
2005-04-11Remove USE_BUILDLINK3 and NO_BUILDLINK; these are no longer used.tv1-2/+1
2005-02-24Add RMD160 digests.agc1-1/+2
2004-12-29- Update to 0.21adrianp3-11/+10
- Security fix (http://www.atstake.com/research/advisories/2003/a080703-2.txt) - PPP interfaces supported
2004-08-25Rather than saying "family = family;", say nothing at all. This does notcjs2-5/+4
change the way the program works, so the package version has not been changed.
2004-08-20Add a patch: the address family coming back from the loopback interface iscjs3-2/+17
in host, not network format. At least, this is the case for NetBSD. I don't know what systems out there exist where this is not the case, but Linux is one possibility.
2004-04-18Convert to buildlink3.snj1-3/+3
2003-05-06Drop trailing whitespace. Ok'ed by wiz.jmmv1-12/+12
2003-04-10Initial import of tcpflow-0.20, provided by Adrian Portelli via pkgsrc-wip.wiz4-0/+38
tcpflow is a program that captures data transmitted as part of TCP connections (flows), and stores the data in a way that is convenient for protocol analysis or debugging. A program like 'tcpdump' shows a summary of packets seen on the wire, but usually doesn't store the data that's actually being transmitted. In contrast, tcpflow reconstructs the actual data streams and stores each flow in a separate file for later analysis. tcpflow understands sequence numbers and will correctly reconstruct data streams regardless of retransmissions or out-of-order delivery. However, it currently does not understand IP fragments; flows containing IP fragments will not be recorded properly. tcpflow is based on the LBL Packet Capture Library (available from LBL) and therefore supports the same rich filtering expressions that programs like 'tcpdump' support.