linuxdcpp-team team mailing list archive

[eMTee <2116965@xxxxxxxxxxxxxxxxxx>]

tl;dr of research : it is common for VPN virtual network drivers not to
set the adapter category. Now to check why do we ignore these adapters,
even though in theory it's ok that we do not list what we know nothing
about...

--------------

Detailed information from combnied prompt :

In the output of Windows' ipconfig, there is an "unknown" adapter
listed. It is a virtual adapter for a VPN service. Is it common for VPN
drivers not to set the category? If so, then why?

ChatGPT said:

Yes, it's relatively common for VPN services to have virtual adapters
that appear as "Unknown Adapter" in the output of ipconfig on Windows.
This typically happens because the VPN's virtual network driver does not
specify a network adapter category that Windows recognizes.

Why this happens:

    Lack of Category Setting in the INF File
    When a virtual network adapter is installed, its driver installation (via an .inf file) can specify a Device Class and Category. If these are omitted or set to values that are non-standard or unrecognized, Windows will default to displaying them as "Unknown adapter" in tools like ipconfig.

    Custom Virtual Network Stack
    Many VPNs (like OpenVPN, WireGuard, or proprietary VPNs) create custom virtual adapters that don’t map directly to traditional Ethernet or Wi-Fi classes. They may use NDIS (Network Driver Interface Specification) to create a TAP or TUN-style adapter, and may not set the same metadata that a physical network interface does.

    Driver Simplification or Privacy
    Some VPN vendors don’t bother categorizing the adapter properly because:

    It doesn’t impact the VPN’s core functionality.

    The adapter is managed internally by the VPN software and not
intended for end-user interaction.

    Some developers simply skip setting the category due to oversight or
lack of incentive.

    Windows UI and ipconfig Behavior
    The "Unknown adapter" label is more of a UI presentation issue in Windows' networking tools. The OS can still functionally use the adapter for routing, DNS, etc., but tools like ipconfig and Network and Sharing Center may not show friendly names or types if metadata is missing.

Should VPN Vendors Set the Category?

Ideally, yes—setting the correct category (e.g., "Tunnel", "VPN", or
"Virtual") helps with:

    Clearer diagnostics and network administration.

    Easier identification of adapters in ipconfig, PowerShell, or Device
Manager.

    Better integration with Windows networking policies.

But since there’s no functional penalty, many developers skip
it—especially in open-source VPN tools.

Conclusion:

Yes, it's common for VPN adapters to appear as "Unknown" in ipconfig due
to missing or non-standard metadata. While not ideal, it's usually
benign and doesn't affect functionality. For clarity and
professionalism, though, better VPN solutions do set these values
correctly.

-- 
You received this bug notification because you are a member of
Dcplusplus-team, which is subscribed to DC++.
https://bugs.launchpad.net/bugs/2116965

Title:
  ProtonVPN's "unknown" virtual ethernet adapter is not listed in the
  selectable bind address dropdown

Status in DC++:
  Confirmed

Bug description:
  Converted from Question
  https://answers.launchpad.net/dcplusplus/+question/822122

  --------------------------------------------------

  Hello, how should i configure DC++ to work in active mode with a VPN ?

  I selected Active Mode (no router or manual configuration), I paste
  the VPN port number to both TC and UDP.

  What should i select in preferred port mapping interface ?
  As i know from other p2p clients that UPnP must be disabled but here i have 3 options but it seems can't be disabled.

  Should i select "Don't allow hub/UPnP to override" ?

  By the way i have already tried many variations and it does not work.
  Only in automatic mode it connects, but not in active.

  I have already read both:
  https://dcplusplus.sourceforge.io/webhelp/settings_connectivity_manual.html
  https://dcplusplus.sourceforge.io/webhelp/faq_portforward.html
  There is no VPN reference in them.

  Please help!

To manage notifications about this bug go to:
https://bugs.launchpad.net/dcplusplus/+bug/2116965/+subscriptions