Next | Query returned 57 messages, browsing 51 to 60 | previous

History of commit frequency

CVS Commit History:


   2005-04-11 23:48:17 by Todd Vierling | Files touched by this commit (3539)
Log message:
Remove USE_BUILDLINK3 and NO_BUILDLINK; these are no longer used.
   2004-12-29 12:51:39 by Adrian Portelli | Files touched by this commit (3)
Log message:
- Update to 0.21
- Security fix (http://www.atstake.com/research/advisories/2003/a080703-2.txt)
- PPP interfaces supported
   2004-08-25 09:56:18 by Curt Sampson | Files touched by this commit (2)
Log message:
Rather than saying "family = family;", say nothing at all. This does not
change the way the program works, so the package version has not been changed.
   2004-08-20 09:10:53 by Curt Sampson | Files touched by this commit (3)
Log message:
Add a patch: the address family coming back from the loopback interface is
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-18 09:33:30 by Soren Jacobsen | Files touched by this commit (1)
Log message:
Convert to buildlink3.
   2003-05-06 19:43:16 by Julio Merino | Files touched by this commit (726)
Log message:
Drop trailing whitespace.  Ok'ed by wiz.
   2003-04-10 19:08:14 by Thomas Klausner | Files touched by this commit (4) | Imported package
Log message:
Initial import of tcpflow-0.20, provided by Adrian Portelli via pkgsrc-wip.

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.


Next | Query returned 57 messages, browsing 51 to 60 | previous