I have some programs that suffered terrible performance degradation when
moving from Ubuntu 12.04 to Ubuntu 14.04. Originally I blamed Ubuntu
14.04 for the performance hit and simply stuck with 12.04, however when I
updated libpcap to support hardware timestamps, the performance degraded
again
On Fri, 14 Nov 2014, Guy Harris wrote:
On Nov 14, 2014, at 1:17 PM, Steve Bourland wrote:
I have some programs that suffered terrible performance degradation
when moving from Ubuntu 12.04 to Ubuntu 14.04.
Are those programs capturing and processing network traffic, are they
sending
On Fri, 14 Nov 2014, Guy Harris wrote:
On Nov 14, 2014, at 2:08 PM, Steve Bourland wrote:
On Fri, 14 Nov 2014, Guy Harris wrote:
On Nov 14, 2014, at 1:17 PM, Steve Bourland wrote:
I have some programs that suffered terrible performance degradation
when moving from Ubuntu 12.04 to
If you have the server's certificate, wireshark has the capability to
decrypt SSL traffic captured with tcpdump, but you must have the
certificate and the start of the tcp session.
On Sun, 8 Jul 2018, tcpdump-workers-requ...@lists.tcpdump.org wrote:
Send tcpdump-workers mailing list submissio
I am expecting this is a change outside of libpcap given the lack of a
note in the change log, but we are moving from Ubuntu 16.04 (well, really
12.04) to 18.04 and have starting having packets flagged for Frame Check
Sequence errors when captured and analyzed in Wireshark. I have a simple
ARP
On Tue, 11 Sep 2018, Michael Richardson wrote:
Steve Bourland wrote:
> are captured, if called with size argument 60, 74 are captured). On
> matching hardware under Ubuntu 16.04 (libpcap 1.7.4), pcap_inject with
> size 50 results in 60 bytes on the wire (expected minimum pa
On Tue, 11 Sep 2018, Michael Richardson wrote:
Steve Bourland wrote:
> are captured, if called with size argument 60, 74 are captured). On
> matching hardware under Ubuntu 16.04 (libpcap 1.7.4), pcap_inject with
> size 50 results in 60 bytes on the wire (expected minimum pa
On Tue, 11 Sep 2018, Michael Richardson wrote:
Steve Bourland wrote:
> I'm a little confused, why would the capture mechanism matter for the
> pcap_inject call? I am capturing both senders packets on the same
> machine (a single tcpdump call). I was thinking my next
