-
Notifications
You must be signed in to change notification settings - Fork 497
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Infinite connect on Mac M3 | error creating tun device: Interface name must be utun[0-9]* #2741
Comments
I have the same issue, changing the name of the interface does not fix the issue for me. |
Hello @alex-ritter and @DyllasDek by default the macOS client uses the correct interface name prefix. Can you clarify if you are getting the wrong name after just installing the client? |
Hi @mlsmaycon Netbird I believe is selecting the right interface name (utun5) and used to work on my Mac. After updating to the new relay system all agents other then my mac fails to connect to netbird. Netbird fails on my mac because it says that the interface is currently in use (utun5). Changing the name of the interface doesn't fix the issue. I'm tempted just to reinstall macos but this seems like a netbird issue. |
HI! I get wrong name on fresh install. I can't reproduce error because now it stores cache. From logs I found my init interface name: |
I found that it turns out that during the initial setup, I accidentally changed the name of the interface. This is my mistake, however, it seems to me that then there should be validation in the application for the interface name. |
Yeah Danila-Mac seems like it's a custom interface name... That should give an error 'Interface name must be utun[0-9]*'. Seems like utun100 works for me after a fresh install of Mac OS and Netbird. Netbird on my last install started being unstable after removing the log file and config files to try to reinstall netbird during a different issue. When I removed the log file and config files before, logs stop generating, it somehow still used the old configuration, and Netbird became extremely unstable afterwords with reinstalls not fixing either of those issues. This time i'm not touching those files because I don't want any issues lol |
Describe the problem
Trying to connect to vpn from Mac M3 but encounter error:
/var/log/netbird/client.log
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Connection established
Are you using NetBird Cloud?
Self hosted Netbird
NetBird version
0.30.1
both on client and server sideScreenshots
Additional context
I know that for now Netbird doesn't support M3, but hope this issue will help to determine issue and add support for M3.
The text was updated successfully, but these errors were encountered: