Skip to content

Add [DWORD]*NdisDeviceType=1 to Npcap Loopback Adapter #437

Closed

Description

@segevfiner

Setting [DWORD]*NdisDeviceType=1 in the registry for the "Npcap Loopback Adapter" will remove it from various places in the Windows GUI and will stop Network Location Awareness from considering it.

This was done, for example, in VirtualBox: https://www.virtualbox.org/ticket/9688

And also in VMware products. For the reasons I mentioned previously.

See: https://msdn.microsoft.com/en-us/windows/hardware/drivers/network/keywords-not-displayed-in-the-user-interface

Activity

  1. Varunram commented on Jan 18, 2017

    @Varunram

    @segevfiner Assuming I read your question correctly, by setting NdisDeviceType to 1 in the registry, we are telling the system to identify the network interface (modem/router/hotspot) as an endpoint device (like a smartphone/tablet). So its no surprise that Windows GUI does not show it among the list of networks because windows only scans for the list of networking interfaces (i.e. devices which can communicate with an external network and not just a local computer/network) nearby.

  2. hsluoyz commented on Jan 18, 2017

    @hsluoyz
    Member

    I just don't know why you would set NdisDeviceType to 1 for Npcap Loopback Adapter? I didn't remember that I said Npcap Loopback Adapter has anything to do with that parameter?

  3. segevfiner commented on Jan 18, 2017

    @segevfiner
    Author
  4. dmiller-nmap commented on Jan 18, 2017

    @dmiller-nmap
    Contributor

    I concur this looks like a good thing to do. References:

    • MSDN: "Set *NdisDeviceType to NDIS_DEVICE_TYPE_ENDPOINT (1) if this device is an endpoint device and is not a true network interface that connects to a network."
    • Blog "Fix: VirtualBox causes 'Unidentified' network on Vista and Windows 7": 'while this “unidentified” network is present the windows firewall settings will stay on “Public”. This behavior is undesirable because you want to be able to switch your firewall settings based on your location (home/work/public).'

    I would not be surprised if this is related to nmap/nmap#373 in cases where the windows firewall settings are very restrictive. I'm checking on a fix.

  5. changed the title [-]Add [DWORD]NdisDeviceType=1 to Npcap Loopback Adapter[/-] [+]Add [DWORD]*NdisDeviceType=1 to Npcap Loopback Adapter[/+] on Jan 18, 2017
  6. segevfiner commented on Jan 18, 2017

    @segevfiner
    Author

    I noticed that the key has an asterisk in front of it, so it's "*NdisDeviceType". I updated the issue accordingly.

  7. dmiller-nmap commented on Jan 19, 2017

    @dmiller-nmap
    Contributor

    Did this in a9b7f9e

  8. CollinChaffin commented on Apr 16, 2017

    @CollinChaffin

    How often does the windows installer get rebuilt? I ask because I cannot find any nightlies or beta builds for windows.

    These issues that involve killing of wifi, missing ndis keys (this issue) are actually 100% specific to Windows users and they are pretty serious, yet the latest installer I find is still approaching a half year old from December and still does not incorporate the required fixes.

    If they don't exist and it is needed, I would even volunteer to help run some builds if there are some detailed docs on the build process through to the windows installer package.

  9. gvanem commented on Apr 16, 2017

    @gvanem

    These issues that involve killing of wifi, missing ndis keys (this issue) are actually 100% specific
    to Windows users and they are pretty serious,

    Yes, they are. That's why I'm sitting on the fence until Npcap bugs are fixed. I'm really happy with the old WinPcap (npf.sys); I'm in no need to use loopback adapter or anything fancy. I'm not sure why/if people think Npcap is so much faster or it's purported features are so nice that they risk a Blue Screen now and again. I don't.

  10. Varunram commented on Apr 16, 2017

    @Varunram

    @CollinChaffin Npcap doesn't do nightlies or beta builds currently, but you can download the latest version of the Windows installer here or view the list of available installers here .

  11. transferred this issue fromnmap/nmapon May 5, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions