[tcpdump-workers] tcpdump and libpcap releases, and future thoughts

2014-09-03 Thread Michael Richardson
I pushed the button on libpcap 1.6.2 early last night. This includes patches that Guy asked for. It seems that we might need more patches to better select Linux memory mapped packet choices? I pushed the button on tcpdump 4.6.2 later that night. I was trying to use libnetdissect in another proje

Re: [tcpdump-workers] tcpdump and libpcap releases, and future thoughts

2014-09-03 Thread Guy Harris
On Sep 3, 2014, at 12:34 PM, Michael Richardson wrote: > It seems that we might need more patches to better select Linux memory mapped > packet choices? I'd prefer a patch that reduces or the removes the *need* to do so, such as this patch, which I'm in the process of testing (yes, I already

Re: [tcpdump-workers] tcpdump and libpcap releases, and future thoughts

2014-09-03 Thread Michael Richardson
Guy Harris wrote: > On Sep 3, 2014, at 12:34 PM, Michael Richardson > wrote: >> It seems that we might need more patches to better select Linux memory >> mapped packet choices? > I'd prefer a patch that reduces or the removes the *need* to do so, > such as this patch, w

Re: [tcpdump-workers] tcpdump and libpcap releases, and future thoughts

2014-09-03 Thread Guy Harris
On Sep 3, 2014, at 4:44 PM, Michael Richardson wrote: > My logic is that if we have the switch/env-var to force libpcap to use a > particular method, that permits not only benchmarking, but also isolation of > bugs easier. OK, I'd vote for an environment variable, so as not to 1) add a