Windows creates a new network connection/interface on every connect

Open
#37 3 comments 0 reactions 1 assignee View on GitHub

Maintainers usually reply within 1 day

@oschwartz10612 is already working on this.

Since Apr 28, 2026.

Assessment

This issue has not been assessed yet.

Description

bug
Describe the Bug

Previously opened this as a feature request (https://github.com/orgs/fosrl/discussions/2772), but this a bug rather than a feature request.

When connecting to a Pangolin instance on Windows, either through OLM or the GUI client, a new virtual network connection and registry entry is created on every connection in the following locations:

Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsNT\CurrentVersion\NetworkList\Signatures\Unmanaged
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\NetworkList\Profiles

Below is a link to the pull request that another project used to solve the issue. Started looking into the solution, and it seems like the solution here will be similar:
https://github.com/netbirdio/netbird/pull/2479

Environment
  • OS Type & Version: Windows 11
  • Pangolin Version: 0.9.0
  • Gerbil Version: N/A
  • Traefik Version: N/A
  • Newt Version: N/A
  • Olm Version: 1.4.4
To Reproduce

Install Pangolin on Windows. Connect to a network. Disconnect and reconnect. New entries will be visible below and the interface will be named something like olm2 or Pangolin2

Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsNT\CurrentVersion\NetworkList\Signatures\Unmanaged

and

Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\NetworkList\Profiles

Expected Behavior

Install Pangolin on Windows. Connect to a network. Disconnect and reconnect. The interface name should remain the same and new entries should not be created in the registry.

Dominant language
Go
Stars
26
Forks
10
Avg merge
5h 49m
Merged PRs (30d)
12

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from fosrl/windows-linux

All issues in fosrl/windows-linux

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.