-
Notifications
You must be signed in to change notification settings - Fork 499
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
Big Sur "No tun devices found, trying utun. segmentation fault" #48
Comments
I was able to get this to work with specifying |
Since a904570 it is supposed to try utun automatically. Can you try running it inside gdb and try to get a stack trace or core dump? Try this:
then a stack trace can be shown by typing |
Result:
|
Thanks, I spotted an error causing NULL to be passed to the utun setup. Can you try again with the latest code? It will probably work better now but might log a bit while testing devices in use. |
LGTM, works great now:
|
Thanks for the quick test! |
I'm trying to run iodine as follows:
However, I get:
This happens regardless of specifying
-d=utun0
(all the way throughutun7
, onlyutun0
throughutun6
are shown on myifconfig
). There aren't any/dev/tunX
or/dev/utunX
devices showing in/dev
, though I am not sure whether they should be or not.This is using the latest
master
commit as of May 12th 2021 on Mac OS X Big Sur 11.3.Tunnelblick seems to be able to create a new
utun7
no problem when it creates an OVPN connection.The text was updated successfully, but these errors were encountered: