Guy Harris

> This could enable us to do very specific access control like "Members of the Npcap Read domain group can do packet capture on these interfaces, but not packet injection."...

> Some issues we could resolve in a redesign: > > * [Npcap: pcap_findalldevs is very slow #61](https://github.com/nmap/npcap/issues/61) pcap_findalldevs is slow. We could leave it up to the caller to...

> Hi, I would suggest you to see, if [#259 (comment)](https://github.com/nmap/npcap/issues/259#issuecomment-841836349) helps. I.e., try installing the latest version of Npcap - currently 1.31 - from the [Npcap Web site](https://npcap.org).

Any program that panics because `pcap_open_live()` - or some library that calls `pcap_open_live()` fails has a bug. The bug is that it's assuming that `pcap_open_live()` will never fail. So where...

If that's a string in Chinese, then is it an interface *description*, rather than an interface *name*? No version of libpcap supports opening an interface by using its *description* (in...

> \xcf\xb5\xcd\xb3\xd5\xd2\xb2\xbb\xb5\xbd\xd6\xb8\xb6\xa8\xb5\xc4\xc9\xe8\xb1\xb8\xa1\xa3 That doesn't look like a valid UTF-8 representation of the name for a network interface *or* a valid UTF-16 representation of the name for a network interface. Where...

> pc = pcap.pcap(name='Realtek PCIe GBE Family Controller') That string is a *description*, not an *interface name*, and the error WinPcap/Npcap returned was probably a "no such interface" name. As...

> (Dear Microsoft: ...) See, for example, https://en.wikipedia.org/wiki/Unicode_in_Microsoft_Windows#UTF-8.

> That doesn't look like a valid UTF-8 representation of the name for a network interface or a valid UTF-16 representation of the name for a network interface. It may,...

> The interface name has not been specified in the source string *That's* an error reported by `pcap_parsesrcstr ()` for an rpcap:// URL that doesn't have an interface name. It...