What version(s) of tcpdump have you seen this happen with? Hopefully it was not 3.5. If the problem happens again, check and see if the sniffer is based upon libpcap, and if so, then the problem may lie there. I checked the changelog on tcpdump.org, but didn't see anything that described the problem. Thanks, -- Joseph On Wed, 13 Dec 2000, Dave Goldsmith wrote: > Check the receiving system/application or try using a different sniffer. I > have seen tcpdump give back excess data before. - This is the TCPDUMP workers list. It is archived at http://www.tcpdump.org/lists/workers/index.html To unsubscribe use mailto:[EMAIL PROTECTED]?body=unsubscribe
