-
Notifications
You must be signed in to change notification settings - Fork 945
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
build on macbook m1 #867
Comments
I think this duplicates #773. So far, no answer has been found. |
I successfully ran it on the m1 pro chip. I tried installing tuntap with homebrew, but it failed and there is nothing showing on the system preference panel. So instead I installed Tunnelblick 3.8.7beta02. I didn't change the config. After installing it, you'll find the TunnelBlink icon in the systray at the top right corner. Right-click it and you'll see a menu item about installing kernel extension. Install it (this requires you to restart your macOS into recovery mode and reduce the security policy). Then back to n2n, compile it using the normal Linux commands then it should work (one minor thing, it's better to make sure that the server node and client node use the same version, otherwise it may fail). Hope it helps:) |
@zhaogang92 Did you really succeed ? I installed Tunnelblick 3.8.7beta02 and the kernel extension. Here's the output when I ran edge:
It looks like it failed because it cannot open tap device. |
@Oliver0624 Yeah I use it to connect to my home desktop since yesterday. From your output, I can think of two things:
|
@Oliver0624 Oh I forgot to add, did you enter MacOS recovery mode to reduce the security policy? |
@zhaogang92 I've found the problem. And my n2n version is 3.1. |
@Oliver0624 That's interesting. Actually, I only enabled one.. Probably it's caused by the difference between 3.1 and 2.8. |
@zhaogang92 |
@Oliver0624 I haven't rebooted yet. But it seems very annoying. Hope Tunnelblick can get updated soon. BTW, I'm wondering if it's good to update the doc a little bit to include info for M1 chip? There are already a few issues posted on it. |
@zhaogang92 I've been reading along with interest - I'm not a Mac user, but it almost sounds like the process for M1 matches what I have heard might be the planned process for the x86_64 systems as well (which is even more reason to get it documented better) Are you able to summarise your process? If you post a summary, I can make a Pull Request out of it (Or you could make the Pull Request yourself) |
@hamishcoleman Sorry forgot to respond.. Yeah, I'll write a summary in this thread probably tomorrow (then you can make a PR). Hope it could help other mac m1 users :) And now I can confirm the problem mentioned by @Oliver0624 above, after a few days using the new mac. Now every time after reboot, we need to re-install the TunnelBlick extension (but somehow I feel this is either an intentional design or limited by MacOS itself). It's not a big problem though as we don't need to reboot very often. |
I don't know if I can't do it, or is it different from what you said? |
Hi, I was running n2n latest version and following the steps posted above, but when running edge on my mac, it stuck at |
how to build on macbook m1?
The text was updated successfully, but these errors were encountered: