I propose to release a libpcap 1.5.3 this week with the following changes:
1) if PCAP_LINUX_TPACKET="v3" or ="v2" then the specific method will be used chosen, unless: 2) a new pcap_linux_tpacket(enum method) has been called by the application (which having a GUI, I presume) can let the user pick the right answer. 3) failing this, the default will be *v2* for now. >From the thread on this github issue, my impression is that there might be a logic error (either a mis-understanding, or a bug) in pcap compared to the kernel, or it may be that some applications have been doing something slightly wrong, but up to now, it hasn't mattered. Having the above controls would let people move forward, and let us gather enough data to figure out what is up, and fix it. -- ] Never tell me the odds! | ipv6 mesh networks [ ] Michael Richardson, Sandelman Software Works | network architect [ ] m...@sandelman.ca http://www.sandelman.ca/ | ruby on rails [ _______________________________________________ tcpdump-workers mailing list tcpdump-workers@lists.tcpdump.org https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers
