[Yang Luo <hsluoyb@xxxxxxxxx>]

Hi list,

In latest 0.04 r6 version, I have used 0x02, 0x00, 0x00, 0x00 for an IPv4 packet and 0x18, 0x00, 0x00, 0x00 for an IPv6 packet (tell me if you have better value for IPv6). The driver can return NdisMediumNull now for loopback interface. Wireshark seems to work now, one little issue is that in the "Characteristics" tab in loopback interface's "Interface Details", "Media supported" and "Medium in use" shows (0xffffffff) instead of a understandable string, this is because that the source code lacks the -1 to string mapping.

Latest installer is at:

https://svn.nmap.org/nmap-exp/yang/NPcap-LWF/npcap-nmap-0.04-r6.exe

Cheers,

Yang

On Sun, Aug 23, 2015 at 7:17 PM, Guy Harris <guy@xxxxxxxxxxxx> wrote:

On Aug 23, 2015, at 2:55 AM, Graham Bloice <graham.bloice@xxxxxxxxxxxxx> wrote:

> As AF_INET6 is defined as 23 on the Windows platform:
> ws2def.h(109): #define AF_INET6        23              // Internetwork Version 6
>  Shouldn't code running on that platform, i.e. Wireshark use the appropriate value rather than faking that of another OS?

Only if we want to have to modify tcpdump/WinDump and Wireshark to handle that value.  It currently doesn't, as no platform that supports DLT_NULL uses it.

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