search

Jdesk / tunnelblick

Automatically exported from code.google.com/p/tunnelblick
0 stars 0 forks source link

Cannot allocate TUN/TAP dev dynamically -cvs build #117

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. check out source from svn
2. build .dmg using xcode
3. Install Tunnelblick.dmg, mount and then copy Tunnelblick to Applications
folder.  

Expected output is being able to connect to openvpn server, instead
everything works except it disconnects because of the "Cannot allocate error.  

---snip---
2009-10-07 19:11:49 OPTIONS IMPORT: timers and/or timeouts modified
2009-10-07 19:11:49 OPTIONS IMPORT: --ifconfig/up options modified
2009-10-07 19:11:49 OPTIONS IMPORT: route options modified
2009-10-07 19:11:49 OPTIONS IMPORT: --ip-win32 and/or --dhcp-option options
modified
2009-10-07 19:11:49 ROUTE default_gateway=192.168.0.1
2009-10-07 19:11:49 Cannot allocate TUN/TAP dev dynamically

This is from SVN checked out today 
Checked out revision 201.

I did some research and found that tun.kext and tap.kext are missing.  They
are available in the compiled version located under Downloads.

Original issue reported on code.google.com by storagen...@gmail.com on 7 Oct 2009 at 9:57

GoogleCodeExporter commented 9 years ago 
This works for me.

Are you using the directions in the "BuildingFromSource" wiki? Compiling on 
Leopard (not Snow Leopard or 
Tiger)? There should be no errors or warnings from the build.

Are you looking for tun.kext and tap.kext in the proper location? They should 
be located in
Tunnelblick.app/Contents/Resources.

Original comment by jkbull...@gmail.com on 8 Oct 2009 at 12:10

GoogleCodeExporter commented 9 years ago 
I am quite sure I am doing it correctly

1. check out "svn checkout http://tunnelblick.googlecode.com/svn/trunk/
tunnelblick-read-only "

2. open Tunnleblick.xcodeproj  with xcode, set to Release, hit "Build and Go"

3. As you can see from the attached screen shot
Also you can see the tun.kext and tap.kext are showing up in read.  It appears 
that
the two errors are because of those two files the tun.kext and tap.kext.  
It appears that they show up read because the files are not actually in the svn.

Original comment by storagen...@gmail.com on 8 Oct 2009 at 3:34

Attachments:

GoogleCodeExporter commented 9 years ago 
I'm sorry you're having so much trouble.

Don't hit "Build and Go". Instead, click "Build Results" on the "Build" menu, 
then click the "Build" button (or 
click "Build" on the "Build" menu) and wait for the build to complete. Make 
sure there are no warnings or 
errors.

Then, double-click tunnelblick-read-only/build/Release/Tunnelblick.dmg, drag 
the Tunnelblick.app that 
appears in the new window to the shortcut to Applications so Tunnelblick.app is 
copied to /Applications, and 
run Tunnelblick from /Applications.

2. The screenshot shows tun.kext and tap.kext in red, indicating they don't 
exist. That is normal before a 
build is made because the build process includes building tun.kext and 
tap.kext. After a successful build 
(with no errors), they should be in black instead of red.

Original comment by jkbull...@gmail.com on 8 Oct 2009 at 11:39

GoogleCodeExporter commented 9 years ago 
I attached a screen capture.  I did just like you said, but there are still 
errors. 
I started cleanly, I checked out a from svn, and then tried to compile with out
modifying it at all.

Original comment by roadwarr...@gmail.com on 8 Oct 2009 at 1:53

Attachments:

GoogleCodeExporter commented 9 years ago 
You should not be getting _any_ of those error messages, much less 524 of them!

What version of Xcode are you using?

Original comment by jkbull...@gmail.com on 8 Oct 2009 at 2:06

GoogleCodeExporter commented 9 years ago 
Xcode 3.1.3
Mac OS X 10.5.8

Original comment by roadwarr...@gmail.com on 8 Oct 2009 at 2:10

GoogleCodeExporter commented 9 years ago 
That is what I use to build successfully (with no errors).

From the errors I can see, it looks like many common system definitions are 
missing. Maybe re-installing Xcode 
would help.

Original comment by jkbull...@gmail.com on 8 Oct 2009 at 2:45

GoogleCodeExporter commented 9 years ago 
Or maybe just trashing the Xcode preferences, 
~/Library/Preferences/com.apple.Xcode.plist (the ~ indicates your 
home folder).

Original comment by jkbull...@gmail.com on 8 Oct 2009 at 2:49

GoogleCodeExporter commented 9 years ago 
Wow, for some reason it appears that it was necessary to reinstall xcode.  
After that
was done I was able to compile successfully.  Thanks for the help.

Original comment by roadwarr...@gmail.com on 8 Oct 2009 at 9:34

GoogleCodeExporter commented 9 years ago 
You're welcome. Marked as "Invalid" because it is not a Tunnelblick issue. 
(Please don't take it personally!)

Original comment by jkbull...@gmail.com on 8 Oct 2009 at 11:38