I'm trying to run iodine as follows: <div class="snippet-clipboard-content notrans

Since <a class="commit-link" data-hovercard-type="commit" data-hovercard-url="https://

Result: <div class="snippet-clipboard-content notranslate position-relative overfl

LGTM, works great now: <div class="snippet-clipboard-content notranslate position-

Big Sur "No tun devices found, trying utun. segmentation fault" about iodine HOT 6 CLOSED

yarrick commented on May 17, 2024

Big Sur "No tun devices found, trying utun. segmentation fault"

from iodine.

Comments (6)

andrewmunsell commented on May 17, 2024

I was able to get this to work with specifying -d utun7, without the equals

from iodine.

yarrick commented on May 17, 2024

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:

$ sudo gdb ./iodine
(gdb) r -f -P password t1.mydomain.com

then a stack trace can be shown by typing where once it stops on the segfault. It is probably some missing error handling in open_utun() if I have to guess.

from iodine.

andrewmunsell commented on May 17, 2024

Result:

➜  bin sudo gdb ./iodine
Password:
GNU gdb (GDB) 10.2
...
Reading symbols from ./iodine...
(gdb) r -f -P password t1.mydomain.com
Starting program: /Users/andrew/Downloads/iodine-master/bin/iodine -f -P password t1.mydomainc.om
[New Thread 0x2003 of process 13668]
[New Thread 0x2503 of process 13668]
warning: unhandled dyld version (17)
No tun devices found, trying utun

Thread 2 received signal SIGSEGV, Segmentation fault.
0x0000000100003241 in utun_unit (dev=0x0) at tun.c:344
344		while (*unit_str != '\0' && !isdigit(*unit_str))

from iodine.

yarrick commented on May 17, 2024

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.

from iodine.

andrewmunsell commented on May 17, 2024

LGTM, works great now:

➜  bin sudo ./iodine -f -P password t1.mydomain.com
No tun devices found, trying utun
iodine: open_utun: connect: Resource busy
iodine: open_utun: connect: Resource busy
iodine: open_utun: connect: Resource busy
iodine: open_utun: connect: Resource busy
iodine: open_utun: connect: Resource busy
iodine: open_utun: connect: Resource busy
iodine: open_utun: connect: Resource busy
Opened utun7
Opened IPv4 UDP socket
...

from iodine.

yarrick commented on May 17, 2024

Thanks for the quick test!

from iodine.

Related Issues (20)

Recommend Projects