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
t
On Jan 10, 2013, at 7:22 AM, Derek Cole 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 patches and stuff
>
On Mon, Jan 7, 2013 at 10:04 PM, Paul Pearce 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 modifications.
>
> The bug man
>> 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
