 | 1 | initial version |
why??
Possibly because the point at which the WinPcap or Npcap driver plugs into the networking stack is a point at which that traffic isn't visible.
The Wireshark developers don't maintain the WinPcap driver (nobody is maintaining WinPcap any more) and don't maintain the Npcap driver; if Wireshark is using Npcap (go to Help > About to see whether it's running with WinPcap or Npcap), the best place to report this issue is the Nmap issue database (Npcap currently doesn't have its own issue database).
| | 2 | No.2 Revision |
why??
Possibly because the point at which the WinPcap or Npcap driver plugs into the networking stack is a point at which that traffic isn't visible.
The Wireshark developers don't maintain the WinPcap driver (nobody is maintaining WinPcap any more) and don't maintain the Npcap driver; if Wireshark is using Npcap (go to Help > About to see whether it's running with WinPcap or Npcap), the best place to report this issue is the Nmap Npcap issue database (Npcap currently doesn't have its own issue database)..
