On Thursday 24 March 2005 17:43, Guy Harris wrote: > On Mar 24, 2005, at 3:18 PM, Tom Brown wrote: > > Thanks for your feedback. It made me inspect my application a > > little closer. I > > think I found the source of my problem. I was checking caplen for a > > minimum > > value. If it was less than a certain value I would ignore the > > packet. When I > > logged the value of caplen I found it was either a very large value > > or a > > negative value. So I was missing packets everytime it showed up > > negative. So > > I changed the application to ignore caplen and it has been working as > > expected for about two hours. Do you know why caplen contains a > > bogus value? > > It looks like the entire pcap_pkthdr structure returned from > > pcap_next_ex() > > contains bogus information. > > Was this before, or after, you fixed your callback function to have a > C calling sequence?
I found the problem. I was passing the address of a pcap_pkthdr structure and not a pointer to the address of pcap_pkthdr structure. Thanks, Tom ================================================================== This is the WinPcap users list. It is archived at http://www.mail-archive.com/[email protected]/ To unsubscribe use mailto: [EMAIL PROTECTED] ==================================================================
