SVI/netbird
1
0
Fork 0
mirror of https://github.com/netbirdio/netbird.git synced 2026-05-15 20:51:57 -04:00
Code Issues 3.0k Packages Projects Releases 10 Wiki Activity

Ubuntu Desktop does not track Network Manager status conflict with Netbird Daemon #1386

New Issue
Open
opened 2025-11-20 05:29:24 -05:00 by saavagebueno · 3 comments
saavagebueno commented 2025-11-20 05:29:24 -05:00
Owner
Copy Link

Originally created by @JonTheNiceGuy on GitHub (Oct 30, 2024).

Describe the problem

In Ubuntu Desktop, when you establish a connection to the Netbird Mesh it shows "wt0" in the VPN Quick Settings. Clicking on that will disconnect the node from the mesh, but the connection in the Netbird Daemon shows as still connected, and the wt0 interface is still present when you execute ip -br a

To Reproduce

Steps to reproduce the behavior:

  1. Perform fresh install of Ubuntu 24.04 (other version may work as well)
  2. Setup netbird using curl -fsSL https://pkgs.netbird.io/install.sh | sh && netbird up --admin-url https://example.org:443 --management-url https://api.example.org:443 --setup-key $SETUPKEY
  3. Confirm the mesh is up with netbird status (looking for Management: Connected and Signal: Connected) and ip -br a (looking for wt0 UNKNOWN 100.64.0.0/16)
  4. Confirm that Network Manager believes the mesh is up with nmcli con show (looking for wt0)
  5. Run nmcli con down wt0
  6. Confirm the mesh is still considered "up" with netbird status (looking for Management: Connected and Signal: Connected) and ip -br a (looking for wt0 UNKNOWN - note that the IP address has disappeared)
  7. Note that Network Manager believes the mesh is down with nmcli con down (wt0 has disappeared)
  8. Run netbird down
  9. Confirm the mesh is considered "down" with netbird status (looking for Management: Disconnected and Signal: Disconnected) and ip -br a (wt0 has disappeared)
  10. Run netbird up
  11. Confirm the mesh is up with netbird status (looking for Management: Connected and Signal: Connected) and ip -br a (looking for wt0 UNKNOWN 100.64.0.0/16)
  12. Confirm that Network Manager believes the mesh is up with nmcli con show (looking for wt0)

Expected behavior

If nmcli or the quick settings tile change the state of the connection in Network Manager, reflect the change of state in the Netbird daemon

Are you using NetBird Cloud?

Self hosted

NetBird version

netbird version: 0.30.3

NetBird status -dA output:

Omitted, happy to provide if further diagnosis suggests it is needed.

Do you face any (non-mobile) client issues?

Omitted, happy to provide if further diagnosis suggests it is needed.

Screenshots

Screencast from 2024-10-30 22-27-12.webm

Additional context

Initially raised in Slack - recommended to raise here.

Originally created by @JonTheNiceGuy on GitHub (Oct 30, 2024). **Describe the problem** In Ubuntu Desktop, when you establish a connection to the Netbird Mesh it shows "`wt0`" in the VPN Quick Settings. Clicking on that will disconnect the node from the mesh, but the connection in the Netbird Daemon shows as still connected, and the `wt0` interface is still present when you execute `ip -br a` **To Reproduce** Steps to reproduce the behavior: 1. Perform fresh install of Ubuntu 24.04 (other version may work as well) 2. Setup netbird using `curl -fsSL https://pkgs.netbird.io/install.sh | sh && netbird up --admin-url https://example.org:443 --management-url https://api.example.org:443 --setup-key $SETUPKEY` 3. Confirm the mesh is up with `netbird status` (looking for `Management: Connected` and `Signal: Connected`) and `ip -br a` (looking for `wt0 UNKNOWN 100.64.0.0/16`) 4. Confirm that Network Manager believes the mesh is up with `nmcli con show` (looking for `wt0`) 5. Run `nmcli con down wt0` 6. Confirm the mesh is still considered "up" with `netbird status` (looking for `Management: Connected` and `Signal: Connected`) and `ip -br a` (looking for `wt0 UNKNOWN` - note that the IP address has disappeared) 7. Note that Network Manager believes the mesh is down with `nmcli con down` (`wt0` has disappeared) 8. Run `netbird down` 9. Confirm the mesh is considered "down" with `netbird status` (looking for `Management: Disconnected` and `Signal: Disconnected`) and `ip -br a` (`wt0` has disappeared) 10. Run `netbird up` 11. Confirm the mesh is up with `netbird status` (looking for `Management: Connected` and `Signal: Connected`) and `ip -br a` (looking for `wt0 UNKNOWN 100.64.0.0/16`) 12. Confirm that Network Manager believes the mesh is up with `nmcli con show` (looking for `wt0`) **Expected behavior** If `nmcli` or the quick settings tile change the state of the connection in Network Manager, reflect the change of state in the Netbird daemon **Are you using NetBird Cloud?** Self hosted **NetBird version** `netbird version`: `0.30.3` **NetBird status -dA output:** Omitted, happy to provide if further diagnosis suggests it is needed. **Do you face any (non-mobile) client issues?** Omitted, happy to provide if further diagnosis suggests it is needed. **Screenshots** [Screencast from 2024-10-30 22-27-12.webm](https://github.com/user-attachments/assets/14f829ab-9e3f-41f1-93a5-d884672196df) **Additional context** Initially raised in [Slack](https://netbirdio.slack.com/archives/C02KHAE8VLZ/p1730315889081849) - recommended to raise here.
saavagebueno added the clientwaiting-feedbackclient-uilinux labels 2025-11-20 05:29:24 -05:00
saavagebueno commented 2025-11-20 05:29:25 -05:00
Author
Owner
Copy Link

@mgarces commented on GitHub (Oct 31, 2024):

hi @JonTheNiceGuy thank you for reporting this; let me try to replicate it on my side

@mgarces commented on GitHub (Oct 31, 2024): hi @JonTheNiceGuy thank you for reporting this; let me try to replicate it on my side
saavagebueno commented 2025-11-20 05:29:25 -05:00
Author
Owner
Copy Link

@nazarewk commented on GitHub (Apr 28, 2025):

Hello @JonTheNiceGuy,

We're currently reviewing our open issues and would like to verify if this problem still exists in the latest NetBird version.

Could you please confirm if the issue is still there?

We may close this issue temporarily if we don't hear back from you within 2 weeks, but feel free to reopen it with updated information.

Thanks for your contribution to improving the project!

@nazarewk commented on GitHub (Apr 28, 2025): Hello @JonTheNiceGuy, We're currently reviewing our open issues and would like to verify if this problem still exists in the [latest NetBird version](https://github.com/netbirdio/netbird/releases). Could you please confirm if the issue is still there? We may close this issue temporarily if we don't hear back from you within **2 weeks**, but feel free to reopen it with updated information. Thanks for your contribution to improving the project!
saavagebueno commented 2025-11-20 05:29:25 -05:00
Author
Owner
Copy Link

@JonTheNiceGuy commented on GitHub (Apr 30, 2025):

$ dpkg -l | grep netbird
ii  netbird                                        0.43.0                                   amd64        Netbird client.
ii  netbird-ui                                     0.43.0                                   amd64        Netbird client UI.

Confirmed still an issue, tested this morning.

@JonTheNiceGuy commented on GitHub (Apr 30, 2025): ``` $ dpkg -l | grep netbird ii netbird 0.43.0 amd64 Netbird client. ii netbird-ui 0.43.0 amd64 Netbird client UI. ``` Confirmed still an issue, tested this morning.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
2021 Q4
2022 Q1
2022 Q1
accessibility
acl
agent
agent
Android
Android
api
authentik
automation
azure
battery-usage
bug
cache
client
client-ui
cloud
cloud-only
cloudflare
community
compatibility
config-idp
config-issue
connection
contribution
coturn
cross-vpn
dashboard
data-usage
distribution
dns
docker
documentation
duplicate
enhancement
enhancement
event-stream
feature-request
freebsd
getting-started
go
good first issue
gui
help wanted
home-assistant
idp
inconsistency
integration
integrations
ios
ipv6
jwt
k8s
keycloak
linux
login
macos
management-service
missing-docs
mobile
moved-internal
needs-review
netbird-ui
networking
new-platform
nginx
notification
okta
openwrt
packaging
peer-management
peer-management
peer-management
performance
postgres
posture-checks
psk
pull-request
Mirrored from GitHub Pull Request
 question
refactor
relay
release
rfc
routes
security
security-related
self-hosting
server
signal
sleep-issue
ssh
ssl
status
store
synology
system-compatibility-issue
test-suite
third-party-integration
triage
triage-needed
troubleshooting
UX
waiting-feedback
windows
wontfix
zitadel
No Label client client-ui linux waiting-feedback
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
saavagebueno
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: SVI/netbird#1386
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?