[GH-ISSUE #5555] Hide wt0 from NetworkManager #11458

Open
opened 2026-08-05 01:29:45 -04:00 by saavagebueno · 7 comments
Owner

Originally created by @WRZOOZ on GitHub (Mar 9, 2026).
Original GitHub issue: https://github.com/netbirdio/netbird/issues/5555

Could we hide wt0 interface in NetworkManager, so users do not disconnect tunnel leaving Netbird DNS and thus breaking their internet access?
It happens a lot when transitioning from old legacy VPN managed by NetowkManager and disabling NetworkManager management over that interface seems to fix that problem entirely.

I am doing so by placing following content in /etc/NetworkManager/conf.d/netbird.conf

[keyfile]
unmanaged-devices=interface-name:wt0

Maybe you could place that file there on installation?

Originally created by @WRZOOZ on GitHub (Mar 9, 2026). Original GitHub issue: https://github.com/netbirdio/netbird/issues/5555 Could we hide wt0 interface in NetworkManager, so users do not disconnect tunnel leaving Netbird DNS and thus breaking their internet access? It happens a lot when transitioning from old legacy VPN managed by NetowkManager and disabling NetworkManager management over that interface seems to fix that problem entirely. I am doing so by placing following content in `/etc/NetworkManager/conf.d/netbird.conf` ``` [keyfile] unmanaged-devices=interface-name:wt0 ``` Maybe you could place that file there on installation?
saavagebueno added the feature-request label 2026-08-05 01:29:45 -04:00
Author
Owner

@p3lim commented on GitHub (May 18, 2026):

Similar issue with networkd, solved with writing the following to /etc/systemd/network/10-netbird.conf

[Match]
Name=wt0

[Network]
KeepConfiguration=yes
<!-- gh-comment-id:4479215295 --> @p3lim commented on GitHub (May 18, 2026): Similar issue with networkd, solved with writing the following to `/etc/systemd/network/10-netbird.conf` ``` [Match] Name=wt0 [Network] KeepConfiguration=yes ```
Author
Owner

@t-animal commented on GitHub (Jun 12, 2026):

Fair word of warning: it is super annoying that disabling wt0 via NetworkManager breaks DNS, alright.

However, applying the first suggestion (/etc/NetworkManager/conf.d/netbird.conf) hides wt0 from NetworkManager completely, thus also disabling the lock-icon in the GUI that indicates VPN is enabled!

<!-- gh-comment-id:4690619469 --> @t-animal commented on GitHub (Jun 12, 2026): Fair word of warning: it is super annoying that disabling wt0 via NetworkManager breaks DNS, alright. However, applying the first suggestion (/etc/NetworkManager/conf.d/netbird.conf) hides wt0 from NetworkManager completely, thus also disabling the lock-icon in the GUI that indicates VPN is enabled!
Author
Owner

@p3lim commented on GitHub (Jun 22, 2026):

thus also disabling the lock-icon in the GUI that indicates VPN is enabled!

Netbird has their own applet, so I consider this a reduction in wasted space and a win.

<!-- gh-comment-id:4766425929 --> @p3lim commented on GitHub (Jun 22, 2026): > thus also disabling the lock-icon in the GUI that indicates VPN is enabled! Netbird has their own applet, so I consider this a reduction in wasted space and a win.
Author
Owner

@WRZOOZ commented on GitHub (Jun 22, 2026):

Honestly, in most cases, Netbird works as a split VPN and thus provides only specified services, so the system icon could be misleading for users (as it does not provide any additional security over the broader internet). Also, there is a Netbird applet as mentioned before, so there is no point in showing that system icon.

<!-- gh-comment-id:4766771085 --> @WRZOOZ commented on GitHub (Jun 22, 2026): Honestly, in most cases, Netbird works as a split VPN and thus provides only specified services, so the system icon could be misleading for users (as it does not provide any additional security over the broader internet). Also, there is a Netbird applet as mentioned before, so there is no point in showing that system icon.
Author
Owner

@t-animal commented on GitHub (Jun 22, 2026):

This is only true if you actually use the UI at all. I for one don't and instead use the CLI.

Plus, at least in my setup for some reason I have not yet looked into, whenever I the netbird daemon restarts, e.g. after an update, it reconnects and thus the VPN is active suddenly.

Whether netbird is a split VPN or not entirely depends on your config. I have a split-by-default profile and a fulltunnel-by-default profile.

<!-- gh-comment-id:4766790393 --> @t-animal commented on GitHub (Jun 22, 2026): This is only true if you actually use the UI at all. I for one don't and instead use the CLI. Plus, at least in my setup for some reason I have not yet looked into, whenever I the netbird daemon restarts, e.g. after an update, it reconnects and thus the VPN is active suddenly. Whether netbird is a split VPN or not entirely depends on your config. I have a split-by-default profile and a fulltunnel-by-default profile.
Author
Owner

@t-animal commented on GitHub (Jun 22, 2026):

Additionally, I would suggest to at least prefix the tunnel name with something like "netbird" or so if the file were distributed with netbird. wt0 may be easily used by other wireguard configs (mine are all called wg-N, but that's merely conventional)

<!-- gh-comment-id:4766908424 --> @t-animal commented on GitHub (Jun 22, 2026): Additionally, I would suggest to at least prefix the tunnel name with something like "netbird" or so if the file were distributed with netbird. `wt0` may be easily used by other wireguard configs (mine are all called wg-N, but that's merely conventional)
Author
Owner

@p3lim commented on GitHub (Jun 22, 2026):

"wt" is from "WireTrustee", NetBird's previous name.

<!-- gh-comment-id:4766930796 --> @p3lim commented on GitHub (Jun 22, 2026): "wt" is from "WireTrustee", NetBird's previous name.
Sign in to join this conversation.
No Label feature-request
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: DYNR/netbird#11458