tunnelblick crashes

[sathio]

Hi, I've read about the foo.tun module, but unluckily I cannot unload
it

I get this error:

# kextunload -b foo.tun
(kernel) Kext foo.tun did not stop (return code 0x5).
(kernel) Kext foo.tun can't unload - module stop returned 0xdc008017.
Failed to unload foo.tun - (libkern/kext) kext (kmod) start/stop
routine failed.


is it because I run an openvpn2 server on the same machine as well?

any help would be greatly appreciated.

best regards

[jkbull...gmail.com]

If the foo.tun is being used by another process (for example, another OpenVPN server), that would prevent it from being unloaded.

If you're trying to unload it with the command line (it isn't clear where your "error" came from), you need to prefix it with sudo:

sudo kextunload -b foo.tun

You can control Tunnelblick's tun/tap load/unload with preferences. I'd give you a link but Google Code's servers are having problems at the moment - I'm getting a "500 Server Error" when I try to access the wiki. Here's a link to the Documentation page, though:

http://code.google.com/p/tunnelblick/wiki/Documentation?tm=6

Click on any 3.1 (or 3.0, if that's what you're using) document. In the sidebar of the resulting page, you'll see (toward the bottom) a link to the writeup on preferences.

[jkbull...gmail.com]

Oh, and by "crashes", do you mean it actually dies, or does it just not connect?

[sathio]

>> where your "error" came from), you need to prefix it with sudo:

I don't use sudo, I was logged with root on the terminal when I
entered that command.
the other module was able to unload (if I recall correctly it was
foo.tap)

I guess it's indeed the openvpn2 server that I'm running preventing
the module to be unloaded.
I tried to kill the process but since it's in some sort of automagic
respawn it just won't let go!

I didn't find any option on the tunnelblick application, where are
they?
on the server I'm having the problem the voice option is grayed out.

I'm having the same 500 Server Error message on google as well., I'll
check those later.

On Dec 8, 6:31 pm, "jkbull...gmail.com" <jkbull...@gmail.com> wrote:
> Oh, and by "crashes", do you mean it actually dies, or does it just not
> connect?

this is the crash I get while trying to connect

2010-12-08 18:32:56 *Tunnelblick: OS X 10.6.5; Tunnelblick 3.1 (build
2190); OpenVPN 2.1.4
2010-12-08 18:32:56 *Tunnelblick: Attempting connection with xxx; Set
nameserver = 3; monitoring connection
2010-12-08 18:32:56 *Tunnelblick: /Applications/Tunnelblick.app/
Contents/Resources/openvpnstart start xxx.ovpn 1337 3 0 0 0 49
2010-12-08 18:32:58 *Tunnelblick: openvpnstart status #5: /
Applications/Tunnelblick.app/Contents/Resources/tun.kext failed to
load - (libkern/kext) kext (kmod) start/stop routine failed; check the
system/kernel logs for errors or try kextutil(8).
2010-12-08 18:32:57.573 openvpnstart[1758:903] *** Terminating app due
to uncaught exception 'NSInvalidArgumentException', reason: 'task
already launched'
*** Call stack at first throw:
(
0 CoreFoundation 0x95b5e6ba
__raiseError + 410
1 libobjc.A.dylib 0x99214509
objc_exception_throw + 56
2 CoreFoundation 0x95b5e3e8 +
[NSException raise:format:arguments:] + 136
3 CoreFoundation 0x95b5e35a +
[NSException raise:format:] + 58
4 Foundation 0x940c5ad6 -
[NSConcreteTask launchWithDictionary:] + 128
5 Foundation 0x940c5a50 -
[NSConcreteTask launch] + 41
6 openvpnstart 0x0000298e loadKexts +
303
7 openvpnstart 0x00005029 startVPN +
5314
8 openvpnstart 0x000057c1 main + 1677
9 openvpnstart 0x00002282 _start +
216
10 openvpnstart 0x000021a9 start + 41
)


thanks for your help!

[jkbull...gmail.com]

I have a local copy of the docs:

  * -doNotLoadTapKext (Boolean): If set, the standard tap kext will not be loaded.

  * doNotLoadTunKext (Boolean): If set, the standard tun kext will not be loaded.

  * *-loadTapKext (Boolean): If set, the standard tap kext will be loaded.

  * -loadTunKext (Boolean): If set, the standard tun kext will be loaded.

They are per-configuration preferences. For a configuration named abcde.conf (or abcde.ovpn), for example, the prefs would be "abcde-doNotLoadTapKext". They are boolean preferences. You can set them via the defaults command, e.g.

defaults    write    com.openvpn.tunnelblick   abcde-doNotLoadTapKext  -bool    yes

Thanks for the crash info. I assume I will be able to make it happen and debug itf. Tunnelblick should complain, but not crash!

[sathio]

On Dec 8, 6:50 pm, "jkbull...gmail.com" <jkbull...@gmail.com> wrote:

> They are per-configuration preferences. For a configuration named
> abcde.conf (or abcde.ovpn), for example, the prefs would
> be "abcde-doNotLoadTapKext". They are boolean preferences. You can set
> them via the defaults command, e.g.
>
> defaults write com.openvpn.tunnelblick abcde-doNotLoadTapKext -bool yes

Hi, thanks for the help, but apparently it still doesn't work

server:Configurations sathia$ defaults write com.openvpn.tunnelblick
myvpn-doNotLoadTapKext -bool yes
server:Configurations sathia$ defaults write com.openvpn.tunnelblick
myvpn-doNotLoadTunKext -bool yes

[jkbull...gmail.com]

foo.tun cannot be loaded when Tunnelblick 3.1 attempts to make a tun connection. This because foo.tun conflicts with Tunnelblick 3.1's net.tunnelblick.tun, which is an upgraded, 64-bit version. (foo.tap and net.tunnelblick.tap conflict similarly.)

So Tunnelblick 3.1 tries to unload foo.tun before it tries to load net.tunnelblick.tun. But if it isn't going to try to load net.tunnelblick.tun, it shouldn't be trying to unload foo.tun.

Whether Tunnelblick 3.1 can operate with foo.tun is a different matter. If 3.0 did, then 3.1 should.

> ... it still doesn't work 

Are you seeing an error when Tunnelblick 3.1 tries to unload foo.tun, even though you have the "myvpn-doNotLoadTunKext" preference set? Or is Tunnelblick still trying to load net.tunnelblick.tun? Or is it an error trying to connect (with the foo.tun, which is already loaded)? If so, what error is it getting?

[sathio]

I'm not sure how to check these questions that you made me.
I'm trying to connect via UI but it still throws that same error when
it tries to connect

[Jonathan K. Bullard]

Sorry, I got carried away.

The bottom line is that if your OpenVPN2 server is running, and using foo.tun, Tunnelblick will not be able to unload it, and Tunnelblick 3.1 will not be able to connect.

If you can't stop your OpenVPN2 server, you can try using older versions of Tunnelblick (which use the older foo.tun) to see if they will work while OpenVPN2 is running. The new tun/tap kexts were introduced in Tunnelblick 3.0b22, so you should use a version before 3.0b22.

I suggest you try Tunnelblick version 3.0b10. All versions of Tunnelblick are available from the Downloads page at

http://code.google.com/p/tunnelblick/wiki/DownloadsEntry?tm=2

--
You received this message because you are subscribed to the Google Groups "tunnelblick-discuss" group.
To post to this group, send email to tunnelbli...@googlegroups.com.
To unsubscribe from this group, send email to tunnelblick-dis...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/tunnelblick-discuss?hl=en.

[sathio]

Oh, I finally got it.
I've managed to connect to the desired vpn by killing the previous
daemon (my problem was that launchctl would bring up the other vpn
immediately)
I'll try the beta release asap and let you know.
thanks for the kind help.

regards

On Dec 13, 2:04 pm, "Jonathan K. Bullard" <jkbull...@gmail.com> wrote:
> Sorry, I got carried away.
>
> The bottom line is that if your OpenVPN2 server is running, and using
> foo.tun, Tunnelblick will not be able to unload it, and Tunnelblick 3.1 will
> not be able to connect.
>
> If you can't stop your OpenVPN2 server, you can try using older versions of
> Tunnelblick (which use the older foo.tun) to see if they will work while
> OpenVPN2 is running. The new tun/tap kexts were introduced in Tunnelblick
> 3.0b22, so you should use a version before 3.0b22.
>
> I suggest you try Tunnelblick version 3.0b10. All versions of Tunnelblick

> are available from the Downloads page athttp://code.google.com/p/tunnelblick/wiki/DownloadsEntry?tm=2

> > tunnelblick-dis...@googlegroups.com<tunnelblick-discuss%2Bunsu bsc...@googlegroups.com>
> > .