Wireshark-dev: Re: [Wireshark-dev] The IPv6 value "24" in DLT_NULL causes Npcap's BPF filter no
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: Yang Luo <hsluoyb@xxxxxxxxx>
Date: Thu, 15 Sep 2016 16:47:05 +0800
I have released Npcap 0.09 r12 which has this issue fixed. Please try it at:

Thanks!


Cheers,
Yang


On Thu, Sep 15, 2016 at 11:59 AM, Guy Harris <guy@xxxxxxxxxxxx> wrote:
On Sep 14, 2016, at 8:20 PM, Guy Harris <guy@xxxxxxxxxxxx> wrote:

> I'll fix this up; for now, just keep using 24 - it's not as if any code that wants to read an AF_NULL pcap file can rely on its OS's AF_INET6 being the packet type value *anyway*, it has to check for all platform values (which both tcpdump and Wireshark do).

I've checked the fix in as change 92fddb84d54cc1bdfa245cde74385b76cabb5a70 to libpcap.  It checks for 24 on Windows live captures.

tcpdump and Wireshark already handle 24 as meaning IPv6 (they also check for 28, which is the FreeBSD value, and 30, which is the Darwin - macOS, iOS, tvOS, watchOS, etc. - value).

___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev@xxxxxxxxxxxxx>
Archives:    https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
             mailto:wireshark-dev-request@wireshark.org?subject=unsubscribe