On Wed, 2007-05-23 at 13:30 -0400, Steve Dickson wrote: > > Oh yeah... I've had a long and sorted history with > tcpdump.. The main problem is if you don't specify the > correct arguments, the binary trace it produces is useless > because it does not capture enough of the packet... > and lets not even start to talk about what protocols > it does *not* support... :-) I didn't think that the packet dissection code in tcpdump had anything to do with writing out a packet capture file. What packets does "tcpdump -s 0 -w packets.cap eth0" fail to write to the file? Jeff
Attachment:
signature.asc
Description: This is a digitally signed message part
-- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
