Re: [tcpdump-workers] Possible initialization error in libpcap

2013-01-10 Thread Derek Cole
Thanks for taking some time to check that out. Can you provide a link where I can see the changes you made? I thought valgrind had a source code repo viewer for latest patches and stuff being checked in, but I couldnt find it. I'd like to take a look at what you did so I can maybe learn how to do

Re: [tcpdump-workers] Possible initialization error in libpcap

2013-01-10 Thread Guy Harris
On Jan 10, 2013, at 7:22 AM, Derek Cole derek.c...@gmail.com wrote: Can you provide a link where I can see the changes you made? The bug I filed against Valgrind: https://bugs.kde.org/show_bug.cgi?id=312989 has a patch. I thought valgrind had a source code repo viewer for latest

Re: [tcpdump-workers] PROBLEM: Software injected vlan tagged packets are unable to be identified using recent BPF modifications

2013-01-10 Thread Bill Fenner
On Mon, Jan 7, 2013 at 10:04 PM, Paul Pearce pea...@cs.berkeley.edu wrote: However, raw vlan tagged packets that are *injected* into the interface using libpcap's pcap_inject() (which is just a fancy wrapper for the send() syscall) are not identified by filters using the recent BPF

Re: [tcpdump-workers] [PATCH net 1/2] net: dev_queue_xmit_nit: fix skb-vlan_tci field value

2013-01-10 Thread Paul Pearce
My opinion as a kernel developer is that the network tap is here to have a copy of the exact frame given to the _device_. Good: as someone who spends lots of time with tcpdump doing both network and protocol diagnostics, it's really important to see exactly there. If that means turning off