Related
I am attempting to get vpnc (for cisco vpn) working on my evo but I have looked everywhere and not been able to find the tun.ko module for my kernel.
There is a post here by sjakub: http://forum.xda-developers.com/showpost.php?p=5692491&postcount=12 which describes how to compile it, but I do not have access to linux currently.
Would anyone be kind enough to compile the proper file for me please? Thank you very much!
Bump
Looking for the same thing using DC 3.5
Help?
Is anyone able to help with this? Or offer any other suggestions? Thank you.
-David
I'm using netarchy's 4.0.* kernels (with tun.ko already loaded) but I'm still unable to VPN to my Cisco concentrator through VPN Connections
Have either of you tried netarchy's 4.0 kernel?
I'm running Fresh 3.1 with netarchy 4.0.3 kernel, VPN Connections says I'm connected, but when I try to access anything internal... no dice.
My company uses OpenVPN and I had it working with the tun.ko on the 2.1 roms. Also looking for a recompiled version for 2.2 kernels.
also interested in this one
Need this too
My kernel is also 2.6.32.15-g746f4f0 and I need the tun.ko file for this. How can I look/compile this? Is it safe to install another kernel? Very new to this, but I was able to successfully install 3.26.651.6 Froyo DeOdexed RevE.1, but don't know how to update a kernel that will work with VPN Connections.
Thanks very much in advance!
I had the same problem, until I switched to CM6 -- It's become a solid ROM and I've learned to live without sense, every time I kick my VPN in and fix a server issue I miss sense less and less. IMHO every ROM should look to integrate this feature.
Kernel
I am using AVA V5 and the Netarchy Kernel caused me problems, so I am using stock. I may try it again shortly if there is not anyone out there who can compile tun.ko for it.
drizkol said:
I'm using netarchy's 4.0.* kernels (with tun.ko already loaded) but I'm still unable to VPN to my Cisco concentrator through VPN Connections
Have either of you tried netarchy's 4.0 kernel?
I'm running Fresh 3.1 with netarchy 4.0.3 kernel, VPN Connections says I'm connected, but when I try to access anything internal... no dice.
Click to expand...
Click to collapse
I installed Netarchy 4.1.8 today and my VPN no longer force closes. However now it says connected, but I cannot access anything inside my work network same as you. Did you find a solution to this?
I have TUN vermagic=2.6.32.15-g746f4f0
I compiled TUN using the HTC sources see my post below
FYI, looks like tun.ko creates the /dev/tun device, but vpnc is looking for /dev/net/tun
will be looking into this next but tun.zip is attached to the post below
http://forum.xda-developers.com/showthread.php?p=7913695#post7913695
btedeski said:
I compiled TUN using the HTC sources see my post below
FYI, looks like tun.ko creates the /dev/tun device, but vpnc is looking for /dev/net/tun
will be looking into this next but tun.zip is attached to the post below
http://forum.xda-developers.com/showthread.php?p=7913695#post7913695
Click to expand...
Click to collapse
sweet, let me know if you get anywhere with this..
Symlink /dev/net/tun to /dev/tun
>> Symlink /dev/net/tun to /dev/tun
yes that is on the top of the list to try,
unfortunately my work is getting in the way of finding time to relax and play with my phone (as the girl friend calls it)
Bill
Will someone please make a tun.ko for the new released kernel or send links on how to and the tools needed? Thanks in advanced.
until HTC releases the source for kernel 2.6.32.15-ge2fb08e
we can not compile a "Real" tun.ko
I modified the version string on the current released code 2.6.32.15-g746f4f0 to ge2fb08e and am compiling it right now.
This will allow it to load and as long as there are no major changes in the kernel it could work for you. It will at least load so you can test it.
I will up load it as soon as it is done compiling
Bill Tedeski
dwertz said:
Will someone please make a tun.ko for the new released kernel or send links on how to and the tools needed? Thanks in advanced.
Click to expand...
Click to collapse
That would be great. Thank you
btedeski said:
until HTC releases the source for kernel 2.6.32.15-ge2fb08e
we can not compile a "Real" tun.ko
I modified the version string on the current released code 2.6.32.15-g746f4f0 to ge2fb08e and am compiling it right now.
This will allow it to load and as long as there are no major changes in the kernel it could work for you. It will at least load so you can test it.
I will up load it as soon as it is done compiling
Bill Tedeski
Click to expand...
Click to collapse
to build it yourself
you can get instructions for an android build system here
http://source.android.com/source/download.html
download the source from HTC http://developer.htc.com/
you will need a .config file should be /proc/config.gz on your phone, uncompress and rename to .config
http://code.google.com/p/android/issues/detail?id=3803
you will need to setup your path to include the build environment you download from source.android.com I will put mine at the end of this
edit the Makefile and change EXTRAVERSION = .15-ge2fb08e to contain version string you need
do a make modules
as long as the kernel has not changed to much from the base source HTC has provided it should work.....
I added the folllowing path statements to my .bash_profile
PATH=$PATH:$HOME/bin
PATH=$PATH:/opt/mydroid/prebuilt/linux-x86/
PATH=$PATH:/opt/mydroid/prebuilt/linux-x86/toolchain/arm-eabi-4.4.0/
PATH=$PATH:/opt/mydroid/prebuilt/linux-x86/toolchain/arm-eabi-4.4.0/arm-eabi/bin/
PATH=$PATH:/opt/mydroid/prebuilt/linux-x86/toolchain/arm-eabi-4.4.0/arm-eabi/lib/
PATH=$PATH:/opt/mydroid/prebuilt/linux-x86/toolchain/arm-eabi-4.4.0/bin/
PATH=$PATH:/opt/mydroid/prebuilt/linux-x86/toolchain/arm-eabi-4.4.0/lib/
PATH=$PATH:/opt/mydroid/prebuilt/linux-x86/toolchain/arm-eabi-4.4.0/lib32/
PATH=$PATH:/opt/mydroid/prebuilt/linux-x86/toolchain/arm-eabi-4.4.0/libexec/
PATH=$PATH:/opt/mydroid/prebuilt/linux-x86/toolchain/arm-eabi-4.4.0/share/
PATH=$PATH:/user/lib/gcc/i686-redhat-linux/4.4.4./libgcc.a
dwertz said:
Will someone please make a tun.ko for the new released kernel or send links on how to and the tools needed? Thanks in advanced.
Click to expand...
Click to collapse
Tun.ko vermagic=2.6.32.15-ge2fb08e
the attached tun.ko is build from the released HTC source with the version string changed to ge2fb08e
as long as the kernel has not changed much on the leaked kernels this should load and work
[[email protected] net]$ strings tun.ko | grep magic
vermagic=2.6.32.15-ge2fb08e preempt mod_unload ARMv7
You are awesome. Thanks
update - The tun.ko does work so it looks like the leaked kernel did not change much.
I will try and learn how to make one. I have ubuntu in vmware to use. Does this have to be a linux box or can it be done on a MacOSX?
Do you have the cifs.ko and nls_utf8.ko for 2.6.32.15-ge2fb08e?
I am trying to get cifs working on my evo.
Never mind. Thanks for everyone's help.
Here is what I did to get the cifs.ko and nls_utf8.ko (from here http://forum.xda-developers.com/showthread.php?t=754793) to work for my kernel.
I took the cifs.ko and nls_utf8.ko created by "snq-" and used a hex editor to edit the kernel number to match mine.
That was all, no re-compile needed. then I followed the rest of the steps laid out by snq- to install the files and test them.
Lastly I installed CifsManager which is available on Market and everything worked.
I am able to connect to my network only locally. Comcast seems to be blocking ports so I cannot access smb from outside my network.
please post link for cifs.ko
If you have a working cifs.ko for this kernel, please post a link!
Thanks!
Any Suggestions
Any where else to go for a tun.ko for ge2fb08e? I've almost exhausted my searching. Thanks!
i am trying to set up OpenVPN on my Evo with the same ge2fb08e kernel version. i installed the pre-requisites, but do not have the tun driver. can you send me a copy of the tun.ko zip? TheEdge88
SR, You can download the tun.ko file in the previous post, but you need to post 9 more times before you can access it. It worked for me and now I can connect to the OpenVPN server. I think I still have a problem with routing though.
NOTE: there is no guarantee this will work, because without access to the corresponding kernel source I can't be sure. It may wipe out your device if there's memory corruption! You're warned, use it only at your risk!!
Over the last weekend I wanted to familiarize with the arm assembly, buildsystem, SDK so I created a tun.ko module for kernel running in the JPK ROM. But lots of the time was also wasted trying to guess their config (things like disabled DMABOUNCE and removal of the dummy they added in 2.6.29 from struct net_device, I hope I got it all right).
I encourage to release the kernel source along with the ROM images in the future (it'd be much simpler if there was a git tree that they can just tag with the name of the ROM), and to include the tun device into the modules/tun/tun.c (as in the tarball) so that it is included by default in the future. I won't be doing this process again.
I had to install openvpn with the openvpn installer a second time with openvpn in xbin, busybox in xbin/bb and I created the bb directory and two symlinks from xbin/bb/{ifconfig,route} to xbin/busybox (after mounting /system rw). The DNS to change during VPN must be set by long pressing on the left of the openvpn config slot in the OpenVPN settings GUI.
The tun.ko I keep it in /sdcard/openvpn/tun.ko and the path has to be configured in the openvpn settings advanced settings menu and I choose to load it with insmod.
This JPK rom works great for me, so I'll likely keep using it for a long while now that I've got openvpn running fine.
252ae6e655fa08774f32f67dd76dad3a tun.ko
EDIT: the same tun.ko module works for JPM too
Great job!!!
I use vpnc daily, so I couldn't even think to upgrade to JPK without an available tun module.. now I can!
Would you share your .config, so other devs can use it? Maybe we can hope in a Froyo-voodoo in a short time..
I'm confirming that it works.
Here is how I did it (I garantee that THIS IS NOT THE MOST ELEGANT WAY to make it work)
Install Openvpn from Openvpn Installer
openvpn in /system/xbin
route and ifconfig in /system/bin
At this point, Openvpn could connect and create a tun device, but route are not pushed so it's not very usefull
So, I downloaded this version of Openvpn
http://github.com/downloads/fries/android-external-openvpn/openvpn-static-2.1.1.bz2
As superuser
Code:
su
I remounted in rw /system
Code:
mount -o remount,rw /system
I renamed /system/xbin/openvpn into openvpn_old
Code:
mv /system/xbin/openvpn /system/xbin/openvpn_old
I put that new openvpn binary in /system/xbin
I created symlinks from /system/bin/route and ifconfig to /system/xbin
Code:
ln -s /system/bin/route /system/xbin/route
ln -s /system/bin/ifconfig /system/xbin/ifconfig
I also created a symlink os /system/xbin to /system/xbin/bb, just in case
Code:
ln -s /system/xbin /system/xbin/bb
Here we go
captive said:
Would you share your .config, so other devs can use it?
Click to expand...
Click to collapse
+1
i tried to complie cifs.ko and tun.ko for the JPC kernel and couldnt get it to work. i ultimately went back to eclair because of this so would like to be able to compile modules and other filesystem support.
thanks.
kanemari said:
+1
i tried to complie cifs.ko and tun.ko for the JPC kernel and couldnt get it to work. i ultimately went back to eclair because of this so would like to be able to compile modules and other filesystem support.
thanks.
Click to expand...
Click to collapse
config attached, but the config is not enough and it may not be fully correct (it is enough as far as the data structures used by tun.ko are concerned, I checked them all against the zImage assembly). The diff of the v2.1 image, has to be applied too but with DMABOUNCE removed from Kconfig of the subarch of the galaxy as far as I can tell and the placeholder added to struct net_device in their v2.1 diff, has to be removed too. cifs.ko may be more complicated than tun, good luck. Unless you've personal interest to familiarize with the enviroment and the arm assmbly like I had, I would wait the source to released, it has to be released eventually to comply with the GPLv2.
Thankyou Newmail!!
I've tryed VPNC 0.99 and works great!!
You have only to type from terminal: insmod /system/folder/tun.ko
After that you can use VPNC...
I've found an issue with the FQDN of the VPN gateway... solved setting the IP address
Just a question:
when I'll update my JPK.. what I have to do to recompile the tun.ko?
Can you write here the procedure?
Cheers
Paolo
newmail said:
config attached, but the config is not enough and it may not be fully correct (it is enough as far as the data structures used by tun.ko are concerned, I checked them all against the zImage assembly). The diff of the v2.1 image, has to be applied too but with DMABOUNCE removed from Kconfig of the subarch of the galaxy as far as I can tell and the placeholder added to struct net_device in their v2.1 diff, has to be removed too. cifs.ko may be more complicated than tun, good luck. Unless you've personal interest to familiarize with the enviroment and the arm assmbly like I had, I would wait the source to released, it has to be released eventually to comply with the GPLv2.
Click to expand...
Click to collapse
OK, but is the placeholder field at the end of the net_device struct?
If so it shouldn't matter and a module cross compiled from the 2.6.29 source should be OK. The absence of DMABOUNCE shouldn't matter for tun.ko either.
In theory you should be able to clone the AOSP git kernel repo and use that kernel for building a module, as long as the module itself doesn't actually use changes that have been made by Samsung (unlikely).
The .config used probably does deserve some attention though, as you have done.
foloap said:
Thankyou Newmail!!
I've tryed VPNC 0.99 and works great!!
You have only to type from terminal: insmod /system/folder/tun.ko
After that you can use VPNC...
I've found an issue with the FQDN of the VPN gateway... solved setting the IP address
Just a question:
when I'll update my JPK.. what I have to do to recompile the tun.ko?
Can you write here the procedure?
Cheers
Paolo
Click to expand...
Click to collapse
Glad it works great for you too. So the tun.ko has to be recompiled if they alter .config. It may work but it's not guaranteed. The procedure is nasty and hard to document and I don't have enough time for that sorry. But I'm sure we'll get the source when there will be an official Froyo release that is shipped to all phones so I wouldn't worry.
raven-au said:
OK, but is the placeholder field at the end of the net_device struct?
If so it shouldn't matter and a module cross compiled from the 2.6.29 source should be OK. The absence of DMABOUNCE shouldn't matter for tun.ko either.
In theory you should be able to clone the AOSP git kernel repo and use that kernel for building a module, as long as the module itself doesn't actually use changes that have been made by Samsung (unlikely).
The .config used probably does deserve some attention though, as you have done.
Click to expand...
Click to collapse
The .config is the fundamental part, and it may be enough I'm not sure. There was a placeholder was a samsung customization done in the middle of net_device and that was removed in the Froyo ROM (initially I applied it). the DMABOUNCE removal affects the struct device that is part of net_device so a lot of stuff goes off by 4 bytes by tweaking that arch config option. That gets set in some Kconfig patched in by samsung. You're right that probably tun isn't affected by the DMABOUNCE but I tried to get the net_device size right (just in case) and it may affect other net modules.
Hi newmail, thanks so much for the tun.ko file, this is the first time I've managed to get VPNC working on my SGS!! One question though, I find I'm having to run insmod everytime I reboot the phone to make tun.ko available again, does anyone know if there's a way around this please so it stays permanently available? Many thanks!!
@bdl1969
I made a subdir in /system/lib called "modules" and placed my tun.ko there.
Now it's insmodded automagically..
newmail said:
The .config is the fundamental part, and it may be enough I'm not sure. There was a placeholder was a samsung customization done in the middle of net_device and that was removed in the Froyo ROM (initially I applied it). the DMABOUNCE removal affects the struct device that is part of net_device so a lot of stuff goes off by 4 bytes by tweaking that arch config option. That gets set in some Kconfig patched in by samsung. You're right that probably tun isn't affected by the DMABOUNCE but I tried to get the net_device size right (just in case) and it may affect other net modules.
Click to expand...
Click to collapse
Oh crap, that is bad news.
Then both the DMABOUNCE and the net_device are likely a problem.
That's a stupid way of doing things.
raven-au said:
Oh crap, that is bad news.
Then both the DMABOUNCE and the net_device are likely a problem.
That's a stupid way of doing things.
Click to expand...
Click to collapse
The smart way of doing things I already mentioned in the first post (public git tree tagged at every ROM release .
captive said:
@bdl1969
I made a subdir in /system/lib called "modules" and placed my tun.ko there.
Now it's insmodded automagically..
Click to expand...
Click to collapse
hmm I tried and it didn't work for me... are you sure? openvpn GUI runs insmod for me so it's no big deal.
That worked great for me, thanks for the suggestion! The only problem I found was that it caused my Good for Enterprise app to crash so I uninstalled and reinstalled it and then it was all fine. Only problem I'm left with now is when using VPNC, I make the VPN connection fine but I can't disconnect via the app, I have to bounce the network connection (eg. toggle WiFi) to drop the tunnel!
I compiled tun.ko using the 2.6.32 kernel from android git and your .config, but it won't load with dmesg saying "Unknown symbol mem_map". May I ask which kernel version did you use, and what arm toolchain are you using?
sztupy said:
I compiled tun.ko using the 2.6.32 kernel from android git and your .config, but it won't load with dmesg saying "Unknown symbol mem_map". May I ask which kernel version did you use, and what arm toolchain are you using?
Click to expand...
Click to collapse
Probably you have discontigmem off in the .config. The platform of the galaxy isn't in the android kernel, it's in arch/arm/plat-s5pc11x (it's the thing that sets DMABOUNCE in v2.1 roms and I guess it doesn't on the JPK kernel).
You need to make a diff between android 2.6.29 and their tree, and apply it to the 2.6.32 kernel, then you need to solve enough rejects so that it can build external module. I didn't port the whole diff of course, just enough so make can start with the headers and .config all right. Then I built the module externally (adding the tun/ directory to their modules/ directory) but it should also work with just make modules setting CONFIG_TUN=m if you want to build it in-tree.
It's a bit tricky.. If you really need I can give you the broken diff to apply to the 2.6.32.9 android kernel. That is enough to build some module including tun.ko
newmail said:
Probably you have discontigmem off in the .config. The platform of the galaxy isn't in the android kernel, it's in arch/arm/plat-s5pc11x (it's the thing that sets DMABOUNCE in v2.1 roms and I guess it doesn't on the JPK kernel).
You need to make a diff between android 2.6.29 and their tree, and apply it to the 2.6.32 kernel, then you need to solve enough rejects so that it can build external module. I didn't port the whole diff of course, just enough so make can start with the headers and .config all right. Then I built the module externally (adding the tun/ directory to their modules/ directory) but it should also work with just make modules setting CONFIG_TUN=m if you want to build it in-tree.
It's a bit tricky.. If you really need I can give you the broken diff to apply to the 2.6.32.9 android kernel. That is enough to build some module including tun.ko
Click to expand...
Click to collapse
It'd be great. I've already tried to do the patching. It compiles, but crashes the phone when loaded. Maybe your version is a bit better.
sztupy said:
It'd be great. I've already tried to do the patching. It compiles, but crashes the phone when loaded. Maybe your version is a bit better.
Click to expand...
Click to collapse
Did you find the source now that JPM has been released officially with Kies? I upgraded to JPM now, in the hope we get the source....
BTW, my tun.ko and my rfs_async.ko also works fine on JPM. I don't know about my ext4 build but I assume that will work too.
I used one CSC of this thread http://forum.xda-developers.com/showthread.php?t=802909 and I deleted the KOR /efs/nv_data* created by the JPK ROM (leaving the .nv_data.bak*). So with this combination of CSC from that thread, and MODEM and PDA from the JPM rar, I apparently restored the original product_id (SGSToolbox also says I'm back to the original product_id). Not that product_id matters but I thought I'd try that next time I flashed and apparently it worked fine...
newmail said:
Did you find the source now that JPM has been released officially with Kies? I upgraded to JPM now, in the hope we get the source....
BTW, my tun.ko and my rfs_async.ko also works fine on JPM. I don't know about my ext4 build but I assume that will work too.
I used one CSC of this thread http://forum.xda-developers.com/showthread.php?t=802909 and I deleted the KOR /efs/nv_data* created by the JPK ROM (leaving the .nv_data.bak*). So with this combination of CSC from that thread, and MODEM and PDA from the JPM rar, I apparently restored the original product_id (SGSToolbox also says I'm back to the original product_id). Not that product_id matters but I thought I'd try that next time I flashed and apparently it worked fine...
Click to expand...
Click to collapse
The JPM source was avialable for a few hours on the samsung's site, did grap it. You can find it on megaupload somewhere. I couldn't manage to compile a working module from that source either (it now loads fine, but does a kernel panic when I try to mount a loop device formatted with ext4), but I'm sure that's my fault.
Hey,
Not sure if this is the right forum or not. But I have tried a few places and ended up with no reply or a dead end so I'm hoping I will actually get some where here.
But is there any way that makes it possible to get tun.ko working on a stock HTC Desire rom?. I have been searching for god know hows long to find any help or instructions on the matter without much help being offered :/
Its because I want to run VPNC on my Desire and I got all the stuff bar tun.ko, so that is the only thing stopping me from going any further and any and all help will be appreciated.
Kind regards.
Yes, you can download the desire kernel from http://developer.htc.com/
You also need the build toolchain for arm processors, find it on http://developer.android.com/sdk/index.html
You need to root your desire, so you can copy files to the system partition. http://unrevoked.com/
The kernel .config file for making oldconfig is , as far as I remember, delivered with the kernel package by htc. If not you can get it from your phone.
Build tun as module, and copy it on yor device.
Hope thats a good quick start for you.
malachay.
It helped somewhat, althought I am not sure how I actually build something as a module etc considering I dont really have much in the way of linux/unix experience.
But my phone is both rooted and S-OFF.
So considering my lack of experience with these things a more elaborate/comprehensive guide or just the steps I need to reproduce to actually build the file as a module, would be greatly appreciated.
MeX_DK said:
It helped somewhat, althought I am not sure how I actually build something as a module etc considering I dont really have much in the way of linux/unix experience.
But my phone is both rooted and S-OFF.
So considering my lack of experience with these things a more elaborate/comprehensive guide or just the steps I need to reproduce to actually build the file as a module, would be greatly appreciated.
Click to expand...
Click to collapse
You don't have to build one per say, you just need to find the Tun module (Tun.ko) for your specific kernel.
If you go to the "About phone" -> "Software Information" section, you'll see a Kernel version.
For example, the phone I have is using Kernel 2.6.32.15-gf5a401c - so I have a tun.ko that loads for that kernel.
There's quite a few TUN modules posted on this forum for various versions of the HTC kernels.
If you don't find a module that fits your kernel version , I can build it for you if you want.
Sent from my HTC Desire using XDA App
Mekrel said:
For example, the phone I have is using Kernel 2.6.32.15-gf5a401c - so I have a tun.ko that loads for that kernel.
Click to expand...
Click to collapse
My kernel seems to be the same, so would you mind sharing your tun.ko and possibly any instructions on how to get it on my phone and working ?
But my kernel version says: 2.6.32.15-gf5a401c
[email protected] #1
MeX_DK said:
My kernel seems to be the same, so would you mind sharing your tun.ko and possibly any instructions on how to get it on my phone and working ?
But my kernel version says: 2.6.32.15-gf5a401c
[email protected] #1
Click to expand...
Click to collapse
Here's the tun.ko I made for my ROM:
Tun.ko for 2.6.32.15-gf5a401c
It's not a flashable zip though, you need to push it to your phone using ADB (or use QtADB if you want a UI program to help you).
You need to put it in /system/lib/modules/
To load it, run terminal emulator on your device (it's free on the market) and run the command:
Code:
insmod /system/lib/modules/tun.ko
Although, if you're using a VPN application on your phone, the application might have an option to load the TUN module for you - so the insmod command might not be needed.
Mekrel,
Do you have the "exact" ADB command on hand?. Because I know how what ADB is for, but doesn't know the commands etc by heart
This is the error I get when I try :/
D:\Test\android-sdk-windows\platform-tools>adb push D:/tun.ko /system/lib/module
s
failed to copy 'D:/tun.ko' to '/system/lib/modules/tun.ko': Read-only file syste
m
Hi!
Seems like there is the same problem on all Android devices. OpenVPN requires the tun.ko kernel module that is hard to get. And it also seems like it must be compiled more or less exactly to much your rom version :-( .
I have a HTC Desire HD running stock rom kernel version 2.6.32.21-gf3f553d [email protected] #1
I have tried various tun.ko modules I have found, but none is comaptible; insmod tun.ko fails.
Questions:
#1 Where can the right version of this magical module tun.ko be found?
#2 Is it hard to compile it for the correct ROM?
#3 How? Isthere any good step-by-step guides.
This could also be a good way to get introduced to compiling kernel modules fro Android devices.
br akeso
Hey all,
Anyone has got the tun.ko module for this kernel? Or anyone could compile one? Thanks!
Hi,
I tried to compile a matching tun.ko module. However, I have currently no possibility to test if it works. If someone wants to try it, I would be glad to hear, if it works or not. (As always, don't blame me, if it breaks anything.)
[Edit: OK. I removed this version, as it obviously did not work. A working tun.ko can now be found in post #8]
it loaded successfully but then i get FCs in settings ever since
it indeed does not work
I tried to use it in console
it loads OK, but when creating a tunnel interface the phone reboots unexpectedly
has anybody succeeded in building tun.ko against this 2.6.35.10-g0956377 kernel version?
thank you very much in advance
OK
since HTC has not release 2.6.35.10 kernel sources for DHD I was not able to build tun.ko against DHD kernel
I grabbed the only 2 kernel sources with this version that are available on developer.htc.com and tried to build tun.ko agains them
the one from HTC Desire S works fine on my phone
I will recompile it against DHD kernel once it gets released
so far you can try the one attached and report if it works or not
if was build with magic version number g0956377
just unpack
rename to tun.ko
insmod
and report if it works
Have a nice day
Martin
have not use
<s>Would you please build it against desire s's own g13f6602 ?</s>
thank you for the common idea
The official kernel sources for the 2.6.35.10-g0956377 kernel used in the 2.36.405.8 software for the DHD are now available. I have therefore compiled the tun.ko module again from these sources. This module works now also on my phone. You find it attached below.
Hi can anyone help me get a tun.ko for my HTC DHD, kernel is 2.6.32.21-gbe90714 ... Thanks
Can somebody please build tun module against 2.6.35.10-g13f6602 kernel?
Someone has already done this for this version of kernel (2.6.35.10-g13f6602), so tun module and everything else is in the archive.
openvpn got working
Posted by Karthik on May 8, 2011 in Android Support, Rooting and Mods | 0 comments
For those who have already rooted their phones and need ovpn, i’ve compiled tun.ko module, which suites stock ROM (2.6.35.10-g13f6602)
All you need is to put it into /system/lib/modules/ from the archive attached.
Also, you can find there working binary (and lib) from cm7.
Just place the binary into /system/xbin/ and lib to /system/lib/
Enjoy!
Click to expand...
Click to collapse
Hi
Has anyone got the tun.ko for 2.6.35.10-gd2564fb?
Thanks!