Related
hi,
did anyone find a way to use openvpn on htc hero?
Catscrash said:
hi,
did anyone find a way to use openvpn on htc hero?
Click to expand...
Click to collapse
Not yet, but I am using the CyanogenMod 4.0.1 on my Dream and I have seen Donut on the HTC Click -- in both cases, Settings --> Wireless Controls is showing an option for VPN Settings, so I'm guessing that it would be a matter of time before this is available on the Hero and Magic firmware
Be patient, or wait for someone to cook a ROM with this feature
VPN wil be in Donut.
For now, it seems possible to implement it.
For the program GUI, it should good to extand that program to support openvpn and pptp vpn.
First of all tun driver is needed, you'll find it here.
Install and, as root, type:
# insmod /system/lib/modules/tun.ko
lsmod command should give you:
tun 11300 0 - Live 0xbf000000
That should load the tun kernel module.
I think we should then have to compile openvpn using android ndk.
A guy did it for the dream. Worth trying it. Maybe someone else could tell if binaries compiled for Dream can work on Hero
OpenVPN ist working on hero. I used the binaries for the G1. But the CIPHER is different: AES-256-CBC. I'm now testing it and if it's stable, perhaps I'm gonna compile openvpn with complete static openssl, so all functions should work.
If someone is interested, I can post my scripts and settings.
gogh57 said:
OpenVPN ist working on hero. I used the binaries for the G1. But the CIPHER is different: AES-256-CBC. I'm now testing it and if it's stable, perhaps I'm gonna compile openvpn with complete static openssl, so all functions should work.
If someone is interested, I can post my scripts and settings.
Click to expand...
Click to collapse
I am REALLY interested to now how you compiled it.
Hi!
I haven't compiled openvpn until now. I used this one:
https://www.digital-bit.ch/wiki/OpenVPN_auf_dem_G1
Just tried, may work. But i can't connect to my astaro because the key needs auth wit user and pw.
This Version hasnt been compiled with --auth-ask-pass. And reading from commandline doesn't work either..
I did compile it on my G1 with CyanogenMod ROM.
As far as I can see, it is working perfectly: I'm using it with certificates for 3 different VPNs.
Only issue: I wasn't able to complile a shared version of liblzo, so the binary is statically linked against liblzo.a (751 KB... )
Ah, yes, of course no GUI interface, shell only...
Hi!
Cool, could you post the binary? Could you give me a hint how you did it? I had several problems.
Would be perfect if someone could compile openvpn with " --enable-password-save"
Please post it, when a OpenVPN GUI for the HTC Hero / Magic is available.
Thans alot
wolfiedk said:
Please post it, when a OpenVPN GUI for the HTC Hero / Magic is available.
Thans alot
Click to expand...
Click to collapse
The great spam protection measures in this forum deny posting links for new users, so you have to manually follow them.
See: github.com/fries/android-external-openvpn
There is also an app and a statically linked openvpn binary at github.com/fries/android-external-openvpn/downloads
The openvpn binary has the following features:
* --enable-password-save
* statically linked against a blowfish enabled openssl
* statically linked against liblzo
Build:
* openvpn-static.bz2 was build on a donut-tree (1.6) for htc-magic
* openvpn-android-2.1.tar.bz2 was build on a cupcake (1.5) tree for htc-magic
* should run on a verity of (rooted) phones, please try it an give feedback.
A dynamically linked version is also available. The above git repo integrates seamless into the android build system. Some instructions may be found here: wiki.github.com/fries/android-external-openvpn/
Any feedback is welcome. Enjoy.
read this first -> http://sourceforge.net/projects/tunneldroid/files/README/download
First make sure kernel is compile with tun module
install tunneldroid from market
binary download -> http://sourceforge.net/projects/tunneldroid/files/openvpn-binary.zip/download
The newest version of my 'OpenVPN Settings' app is available at github.com/fries/android-external-openvpn/downloads
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.
This topics if only for Cyanogenmod, any off topic will be reported.
Next milestones:
Fix microphone bugs
Correct camera orientation
Repair Tethering
My git:
http://github.com/WillingMagic
Project mailing list:
http://groups.google.com/group/samsung-galaxy-551
Second Beta (THIS BUILD IS WORKS ONLY WITH GINGERBREAD RADIO/AMMS)
Current Status:
USB/WIFI Tethering Working with alternative apps
RIL Working
Sound Microphone stop working after screen dims
Headset Working
Touchscreen Working
HW/3D Working
Screen Working
ADB Working
SDCard Working
Vibration Working
Sensors Working
WiFi Working
3G Working
Bluetooth Working
GPS Working
Keyboard Working
Camera Wrong orientation
How to install:
Backup your config and apps.
Download ODIN with callisto.ops and CWM recovery.tar.
Press Q+Power to activate Download mode
Flash using Odin CWM_recovery.tar as PDA.
Download latest cyanogenmod 7.2 for samsung callisto and gapps for gingerbread.
Press T+Power to activate Recovery mode
Wipe data/factory reset
Use install zip from sdcard to install cyanogenmod and gapps
Reboot system
Configure your phone
You have working Cyanogenmod 7
PLEASE SEND ANONYMOUSE STATISTICS.
If 2g/3g not working check APN settings.
Mirror:
Spideroak
IF YOU WANT USE OTHER SAMSUNG ROMS, PLEASE WIPE DATA AND CACHE AFTER FLASHING.
Hey,
Some information that may be useful:
It appears that you already have the Gingerbread source. I checked the official Gingerbread Callisto kernel's .config, and it has some new definitions for targets that appear in the Gio source code. Therefore I'm pretty sure that this archive from Samsung's OS site contains the source you need: GT-S5660M_BMC_Opensource.zip
I recommend you use that source unmodified in combination with the newer Gingerbread bootloader (i.e., don't use any of my patches for the G5).
One more thing: I discovered that later AR6000 drivers actually support WEXT in the supplicant. Therefore, I recommend that you change the supplicant from AWEXT to WEXT in BoardConfig.mk, and -Dawext -> -Dwext in init.gt-i5510.rc. You may want to try the v6 supplicant, but try v5 as well.
Hey willing,
Don't need wait for samsung release kernel source.
We are working in it, make a fork.
It's 100% working.
github.com/arkas/Callisto_kernel_2.6.35
We are pinkflozd and smoke87 from enigma.
galaxy551.wordpress.com
Link?
Kernel download is down. I want this thing badly. Also, do i need to be on froyo or on gb? Thanks in advance!
race55 said:
Kernel download is down. I want this thing badly. Also, do i need to be on froyo or on gb? Thanks in advance!
Click to expand...
Click to collapse
My fault, logged in with my megaupload acount and now im running cyanogen! Had some difficulties with adb, but i found you can copy and paste it so, its awesome. BTW, multitouch is not working in web browser.
smoke87 said:
Hey willing,
Don't need wait for samsung release kernel source.
We are working in it, make a fork.
It's 100% working.
github.com/arkas/Callisto_kernel_2.6.35
We are pinkflozd and smoke87 from enigma.
galaxy551.wordpress.com
Click to expand...
Click to collapse
Already test this kernel with .config.pinkflozd, yeah it's 100% work hope the beta version will release with this new kernel.
Not AZERTY, but in case anyone needs it, I've created a layout file for QWERTZ (German) hardware keyboard:
http://forum.xda-developers.com/showthread.php?p=17964386#post17964386
Proximity on Second Alpha
I try to compare the init.rc & init.gt-i5510.rc to stock GB 2.3.4 init.rc I found that proximity device setting didn't exist in 2nd Alpha config. Can I enabling that device only by adding the missing lines or must have the drivers too to make it works?
Stock init.rc:
# change the permission sensor chips
chown root system /dev/mmc31xx
chown root system /dev/bma_accel
chown root system /dev/kr3dm_accel
chown root system /dev/ecompass_ctrl
chown root system /dev/proximity
chown root system /dev/ledflash
chown system radio /sys/devices/virtual/accelerometer/accelerometer/calibrate
chmod 0660 /dev/mmc31xx
chmod 0660 /dev/bma_accel
chmod 0660 /dev/kr3dm_accel
chmod 0660 /dev/ecompass_ctrl
chmod 0660 /dev/proximity
chmod 0660 /data/misc/sensors/ecs_nvm
chmod 0660 /data/misc/sensors/accel_offset
chmod 0664 /sys/devices/virtual/accelerometer/accelerometer/calibrate
chown system radio /sys/devices/virtual/touch/firmware/firmware
chmod 0664 /sys/devices/virtual/touch/firmware/firmware
chown system radio /sys/devices/virtual/touch/firmware/firmware_ret
Click to expand...
Click to collapse
Second Alpha init.gt-i5510.rc:
# For sensors
mkdir /data/misc/sensors 0777 system misc
chmod 0666 /data/misc/sensors/ecs_nvm
chmod 0666 /data/misc/sensors/accel_offset
Click to expand...
Click to collapse
info: GT-I5510_OpenSource_GB_update.zip
WillingMagic said:
This topics if only for Cyanogenmod, any off topic will be reported.
We got released official gingerbread, day after I released Second Alpha.
I`m still waiting for kernel 2.6.35.7 source.
Next milestones:
Support new bootloader.
Build kernel 2.6.35.7
Fix wifi
Remove other buggs
Onenand driver and bml over mtd
Released clockwork recovery
Start porting of newer kernel (3.0?)
My git:
http://github.com/WillingMagic
Project mailing list:
http://groups.google.com/group/samsung-galaxy-551
Click to expand...
Click to collapse
Please check opensource.samsung.com
GT-I5510_OpenSource_GB_update.zip is coming
didhiy said:
Please check opensource.samsung.com
GT-I5510_OpenSource_GB_update.zip is coming
Click to expand...
Click to collapse
It's already up.
https://opensource.samsung.com/reception/reception_main.do?method=reception_list&menu_item=mobile
Does that mean Gingerbread update would be soon available via KIES from Samsung for GT I5510 ?
rakeshishere said:
Does that mean Gingerbread update would be soon available via KIES from Samsung for GT I5510 ?
Click to expand...
Click to collapse
Samsung has released the official Gingerbread update only to one baseband and that baseband is from EU.
If your baseband is the same baseband as the update, you can update via Kies. Otherwise you can't. You're gonna have to do it via Odin if you're really up to it.
dgenx210 said:
Samsung has released the official Gingerbread update only to one baseband and that baseband is from EU.
If your baseband is the same baseband as the update, you can update via Kies. Otherwise you can't. You're gonna have to do it via Odin if you're really up to it.
Click to expand...
Click to collapse
I'm currently located in India and desperate to update to Gingerbread
i saw that update is available for European users but was curious to know if update is coming in wave form or something officially may be in coming months ?
EDIT:
Installed Gingerbread via Odin and felt like phone got a new life. Thanks a lot
New build comming in this week.
Fixed keyboard
Added tun.ko driver
Easy install, aka flash and forgot.
Wifi fix.
Sent from my GT-I5510 using xda premium
Really looking forward to this
WillingMagic said:
New build comming in this week.
Fixed keyboard
Added tun.ko driver
Easy install, aka flash and forgot.
Wifi fix.
Sent from my GT-I5510 using xda premium
Click to expand...
Click to collapse
Me too waiting for your new built....
WillingMagic said:
New build comming in this week.
Fixed keyboard
Added tun.ko driver
Easy install, aka flash and forgot.
Wifi fix.
Sent from my GT-I5510 using xda premium
Click to expand...
Click to collapse
Im waiting new biuld to)
is it cyanogen mod?
nbnikhilrock9 said:
is it cyanogen mod?
Click to expand...
Click to collapse
this is unofficial cyanogenmod
I was wondering if the Galaxy Nexus stock ROM had OpenVPN support in kernel and if someone was contemplating compiling tun.ko for the less tech savy users
Would also like to know if it's possible to use OpenVPN on the GN.
If it is not in there stock, I am sure one of the many kernel devs will add it for us.
Apparently...
"It should now be possible to write a OpenVPN client for Android."
According to:
https://code.google.com/p/android/issues/detail?id=3635#c87
So it's just a waiting game now for an app it looks like.
openVPN works
Hi,
Just wanted to let you know I got openVPN working. (pic below)
I have Revolution 1.3.0 ROM and Franco's kernel installed, both excellent I must add.
I didn't need a tun.ko, did on my sgs2.
There are 2 programs you need on the market, openVPN installer and openVPN setting. Run those and you should be good to go. The only thing I had to do was create a /system/xbin/bb folder and copy ifconfig into it. This may have been something to do with the way I installed busybox.
I use the last MCK kernel compatible with Android Revolution HD.
Will check if the kernel have support.
I can't wait to be able to watch Netflix from the USA again.
Unfortunately, stock ICS on the GN has no tun support. We still need a tun.ko. So far I didn't find one, so I guess I need to compile it myself...
I believe it stock ROM does have tun support. See this thread:
http://android.modaco.com/topic/349642-tunko-for-openvpn/
Steps are here for anyone else looking to get it working (which I gleaned from here http://forum.xda-developers.com/showpost.php?p=17233744&postcount=9):
Install Busybox from Market
Install OpenVPN Installer from Market and install to:
binaries: /system/xbin
route/ifconfig: /system/xbin/bb
Create /system/xbin/bb with Root Explorer or from shell
Create link to busybox for ifconfig and route
ln -s /system/xbin/busybox /system/xbin/bb/route
ln -s /system/xbin/busybox /system/xbin/bb/ifconfig
taylormadearmy said:
I believe it stock ROM does have tun support.
Click to expand...
Click to collapse
Indeed, you're right. Although my OpenVPN installer indicated my kernel was lacking a tun module, I justed ignored it and now I'm running OpenVPN on rooted/unlocked ICS. Great!
Mark
I would ideally like this to work without rooting. Hopefully a proper app gets made!
Great News though!
Indeed, I thought that I needed Franco's kernel to get openVPN to work, but when I flashed back to stock kernel (I had some battery issues) the openVPN still worked.
Everything worked fine, I can now connect on my VPN servers through OpenVPN Settings (On the Android Market) : D. Awesome ! Many thanks
nvm
10 characters
Just in case you haven't heard yet: The official Cisco AnyConnect VPN Beta has been released in the market a week or two ago. It supports all ICS devices (tested it on my Asus TF101 with stock 4.0.3). Works great on my unrooted GN!
Gesendet von meinem Galaxy Nexus mit Tapatalk
Help with OpenVPN setup
Hello,
I followed all the instructions on this post regarding install and reconfiguration of folder permissions. I'm running AOKP Milestone 3 and Franco kernel Milestone 2. My phone connects to openVPN but it's clear that data isn't flowing through it (i.e., I'm in China and still can't use Facebook or Youtube apps)
Any suggestions? OpenVPN app connects to the server very quickly but when visiting Facebook.com, I can see very easily that the download rate is 0.0kbps, then the page times out.
Any help would be appreciated!
romerjon said:
Just in case you haven't heard yet: The official Cisco AnyConnect VPN Beta has been released in the market a week or two ago. It supports all ICS devices (tested it on my Asus TF101 with stock 4.0.3). Works great on my unrooted GN!
Gesendet von meinem Galaxy Nexus mit Tapatalk
Click to expand...
Click to collapse
Does this work with open vpn? Sorry if this is a dumb question, I am a new user to open vpn. I am about to setup an open vpn server on my dd-wrt router.
does anyone know where the tun.ko module is located on stock rom?
i can't find it no matter how i search for it. will it be possible for someone to upload it and give us the link?
thank you...
Hi!
Have someone compiled a running openvpn binary with needed tun.ko for the stock firmware (1.28) ?
I would like to use openvpn with my one x.
prodigy7
One ROM says it's openvpn compatible. I can't post a link, so this is the thread title/rom name:
[ROM] Android Revolution HD 3.0.0 | ICS | High Quality & Performance | 1.28.401.9
Lemme know how it works
Hmm k ... i wait for final s-off and try to compile openvpn, if no one hasn't done at this time or try to get the files from this ROM.
prodigy7 said:
Hi!
Have someone compiled a running openvpn binary with needed tun.ko for the stock firmware (1.28) ?
I would like to use openvpn with my one x.
prodigy7
Click to expand...
Click to collapse
Just download OpenVPN Installer and OpenVPN Settings
and install busybox
No need for tun.ko (CONFIG_TUN=y in the kernel)
of course you need a rooted phone.
richardtrip said:
Just download OpenVPN Installer and OpenVPN Settings
and install busybox
No need for tun.ko (CONFIG_TUN=y in the kernel)
of course you need a rooted phone.
Click to expand...
Click to collapse
Really cool!!!!!!!!! Thank you very much for this hint. I'll try it next time
Definitely will try this..I can see it have a good rating (more than 4.0)..