Guy Harris

> Report diagnostic info directly in the packet stream, such as changes to the adapter reported via Status Indications That would require adding blocks to provide network-layer indications, which might...

(And, yes, a pcapng-capable capture/read/write API is something I've been working on.)

> I determined that the binary library files in WinPcap 4.1.2 Developer's Pack do not export symbols used in pypcap-1.2.3. WinPcap bug - unlikely ever to be fixed, as WinPcap...

> I am also experiencing this with Python 3.7 (x64) using Build Tools for Visual Studio 2019 on Windows 10 (version 1803, build 17143.950). I have pypcap-1.2.3 and the WinPcap...

> Perhaps we want to make the suggestion of not using WinPcap and favouring Npcap in the Readme even stronger and link to some of the issues (like this one)...

@fyodor This isn't exactly a duplicate, as I read this bug and nmap/npcap#74. Remote capture support in libpcap includes both client and server code; both autotools and CMake have an...

It appears that Npcap *is* shipping remote capture *client* code; however, that code is buggy. See nmap/nmap#1506.

Npcap should now be shipping non-buggy remote capture client code, as of 0.9983.

Actually, _if_ you've opened a regular network interface, on most platforms, the descriptor returned by `pcap_fileno()` is the same as the descriptor returned by `pcap_get_selectable_fd()`. But it's still best to...

> you seem to know quite a bit about his Being a core libpcap developer for many years helps. :-) > is there a feature request here? I would say...