To make a long story short, here's the info:
Motorola Droid 2
Droid 2.2.20
Kernel 2.6.32.9g59f0395
OpenVPN is installed using the OpenVPN installer on market place, trying launch the VPN connection via the app OpenVPN settings (also on market place). I'm using this method because the error messages on this app are more verbose than other methods.
Problem I'm having is that when trying to connect, I get an error message stating "Fatal: Unable to allocate tun/tap dev dynamically." I've done a ton of scouring on forums and others have been able to get around this problem on versions 2.1 and prior by changing the version of the tun.ko module that they use or adjusting permissions on the directories. I've tried every combination of tun.ko module out on the net with permissions, methods, and the whole shebang. Nothing I try has been able to get around this error message. Presently, the tun.ko file is located in /system/lib/modules. Running insmod tun.ko manually returns the error "insmod: init_module 'tun.ko' failed (Exec format error).
I've dug through the forums on this error as well and all remedies I've come across seem to be for 2.1 and prior (tried them anyway). Do I simply need to recompile the tun.ko module on my own? I suspect that my headache is caused by this module running in a unsupported kernel. Any help would be appreciated.
I could use some guidance. I am running stock rom on my Vibrant (2.2, FROYO.UVKB5 to be specific) and it is rooted. I am trying to run Cisco AnyConnect, but have no built-in tun/tap driver (of course). I have used tun.ko installer and it worked for about 5 days. Now, anytime I run tun.ko installer, my phone reboots. I have trashed any programs that I had installed since tun.ko installer and even uninstalled and reinstalled the installer.
I am at a loss as to even where to begin troubleshooting this issue. Would someone please help this humble novice learn more about his problem?
Thank you.
Tun.ko is a Linux kernel module. You could try changing your kernel, or running a terminal and manually installing the module via modprobe and seeing if the phone stays up long enough for you to run a dmesg to look for error messages. I don't know how you can see the panic message as the kernel crashes on a phone, but maybe there is a way. An adb shell might last a little longer than an on-phone terminal in the event of a panic.
I actually went the easy route and am trying to use the Tun.ko installed app from VPN Droid, and getting the reboot issue. It seems to be rebooting when it is doing a check to see if the Tun/Tap module is installed, which it isn't right now. I don't currently have a linux box to build a tun.ko module for my Vibrant kernel to be able to manually install it or I would do that and just forget about the tun.ko installer.
Has anyone else seen this behavior at all? It's not like I have crazy custom ware installed or anything else nuts. I'm a little more advanced than an average user and haven't even jumped past the OEM ROM with ADW launcher. Not really the Dev type, but I'm not exactly afraid to go in and do what needs to be done. I just don't know what to do off hand. XDA-Developers and Google have been my best friends when working with my phone. I've just come to a brick wall on this one.
Flashing a kernel like Bali for 2.2 roms would help. It includes a tun.ko module. More info here...
http://forum.xda-developers.com/showthread.php?t=1043947
Yeah, I think I'm going to have to suck it up and get into flashing my ROM. I've just been hesitant because even though I have Titanium backup, I know I'll have to go through some downtime to do the flash. When I upgrade, though, I'll keep this to have a device to fall back on during maintenance and flashes.
I have my server at home with a knock daemon to block all the script kiddies that tried to break into it by ssh. I was using Port Knocker on 2.3.6 with a custom ROM and it worked without any problem. When updating to ICS, it seems I'm not able to knock correctly to my server and here's what I've tested so far...
Server config doesn't seem to be the problem, since it hasn't been touched.
Router ports are still open and redirected to server's IP.
Server seems to receive the first knock (I have configured 5 ports to knock), but then it doesn't receive the rest.
I've also tried to use nc and telnet from the phone directly without any luck.
The main suspects I have about this problem are these:
Since I upgrade the phone from a custom ROM to stock ICS with root kernel (CF-Root), the ROM lacks something that its needed to be able to knock correctly.
Port Knocker app isn't working correctly on ICS (or lacks something to be able to work).
My mobile company suddenly blocks my connection so I can't knock any more... Don't really think of this one since if I do a telnet to the first port I get "Connection closed by foreign host", so I'm asuming it's reaching the server.
Right know my phone is on 4.0.3 ICS (XWLPF Kernel CF-Root) and Busybox updated to 1.20.2
Any clue what could be the problem or any hint on what could I be missing? Thanks in advance!
Hi,
Just done a factory reset and upgraded to r5 , this is a UK tablet, region changed to US and flashed. I then rooted using Root_with_Restore_by_Bin4ry_v13 . After several try I got it working, but I had to use a signed VPNfaker to accomplish this.
So now I want to use a VPN, before I used OpenVPN, this worked perfectly, now it fails to connect. I get the error - Running on Sony Tablet S (nbx03) Sony, Android API 15. Your image does not support the VPNService API, Sorry
I tried to use OpenVPN Connect , getting the error due to a know bug in this version of android it is not possible to gain permission to open a VPN Tunnel.
So last attempt using the built in L2tp/IPSec option, with this I just get a timeout error. No Connection.
So was it the rooting method damaged or changed something with VPN or is it this version US R5 ?
Anyone got VPN working on US R5 ?
OpenVPN is working fine on my tablet S with release 5. I use the apps 'OpenVPN Installer' and 'OpenVPN Settings' from Google Play...
Sent from my Sony Tablet S using xda app-developers app
walsera said:
OpenVPN is working fine on my tablet S with release 5. I use the apps 'OpenVPN Installer' and 'OpenVPN Settings' from Google Play...
Sent from my Sony Tablet S using xda app-developers app
Click to expand...
Click to collapse
That was the second option I tried. I enabled the VPN service, then selected the VPN I want to connect. It initiates the connection then stops after a second with no results in the log file. Did you try any of the other VPN apps that don't require root, OpenVPN Connect (I think US Market only) or OpenVPN for Android, this work really well on my Xperia S .
How did you root your Tablet ?
Did you do the incremental update or full install ?
I flashed the full update and basically used the same method like you. I also had to sign VpnFaker.apk for my Swiss tablet... I don't remember any issuses installing OpenVPN (OpenVPN Installerhttps://play.google.com/store/apps/details?id=de.schaeuffelhut.android.openvpn.installer, OpenVPN Settingshttps://play.google.com/store/apps/details?id=de.schaeuffelhut.android.openvpn). Interestingly, no tun.ko module is required.
I quickly tried the apps you suggested and which don't require root. But they didn't work for me in a quick test.
walsera said:
I flashed the full update and basically used the same method like you. I also had to sign VpnFaker.apk for my Swiss tablet... I don't remember any issuses installing OpenVPN (OpenVPN Installerhttps://play.google.com/store/apps/details?id=de.schaeuffelhut.android.openvpn.installer, OpenVPN Settingshttps://play.google.com/store/apps/details?id=de.schaeuffelhut.android.openvpn). Interestingly, no tun.ko module is required.
I quickly tried the apps you suggested and which don't require root. But they didn't work for me in a quick test.
Click to expand...
Click to collapse
Thanks for trying that. I will retry loading my VPN Profiles again in OpenVPN
defsix said:
Thanks for trying that. I will retry loading my VPN Profiles again in OpenVPN
Click to expand...
Click to collapse
Ok, so tried re-installing busybox, tun.ko, OpenVPN settings and OpenVPN installer however still it's not working. I am thinking the problem is deeper than this though. The built in VPN options L2TP/IPSec and PPTP are both failing to work. I just get a time out error. I have uploaded a section of the catlog if someone could have a look at it.
I am still stuck with this problem. I used AIO tool to setup boot loop protection and then re installed the full R5 on top of the old installation. I didn't do a factory reset though, I don't have the time to re install everything.
And still the problem persists.
I am unable to create any VPN
Anyone any ideas ?
ok. Factory Reset.
Factory Reset, reinstalled R5. Titanium Backup restore and still no VPN. I give up.
Sorry to hear that... for more information about the initiation process of your VPN, you could try to start the openvpn binary in a terminal as root with an increased verbosity level... just to see at which step the process actually fails
walsera said:
Sorry to hear that... for more information about the initiation process of your VPN, you could try to start the openvpn binary in a terminal as root with an increased verbosity level... just to see at which step the process actually fails
Click to expand...
Click to collapse
would that give me more or the same as a logcat ?
Could you give me a quick idea how to do this in terminal ?
Well, I am not an expert, but your logfile was just little use for me...
Steps for running openvpn in terminal:
Open terminal
Type 'su' to get root
Change to the directory with your profiles using 'cd PROFILEDIR'
Type 'openvpn' for getting all command line options
To start a connection type something like 'openvpn --config PROFILE.ovpn --verb 3 '
I couldn't test this with my connection because I haven't figured out how to pass my key for my certificate. But I think this is the way to go.
walsera said:
Well, I am not an expert, but your logfile was just little use for me...
Steps for running openvpn in terminal:
Open terminal
Type 'su' to get root
Change to the directory with your profiles using 'cd PROFILEDIR'
Type 'openvpn' for getting all command line options
To start a connection type something like 'openvpn --config PROFILE.ovpn --verb 3 '
I couldn't test this with my connection because I haven't figured out how to pass my key for my certificate. But I think this is the way to go.
Click to expand...
Click to collapse
ok, will give this a try.
I would like to patch wpa_supplicant on my Beelink W95 that is susceptible to the KRACK WPA2 WiFi exploit.
I tested the W95 with vanhoefm/krackattacks-scripts (look on github, can't post links) and it failed the first test. I would like to patch wpa_supplicant so I can proceed with the other tests.. Except I'm not sure how to do this.
I've compiled programs for Linux and I've used Android studio. I'm really not sure how to cross compile from Linux to android and I don't think I need the full blown Android studio experience.
Are there any good guides to compiling just individual command line programs. I know I'd have to get the source, then do .configure then make, what I'd like some clarity on is if I need specific source from the device manufacturer or can I just use vanilla android code. Further, what options does make take, and basically what do I need to know so I can just compile wpa_supplicant with the patches I need to apply.
Thank you
Progress...
I decided that the first step should be to compile a generic wpa_supplicant and not worry about patches or security updates or anything like that. In order to do that, I had to compile openssl and libnl libraries. I went through a lot of versions of all three because I would always run into some problem or another. After a lot of trial and error (and some learning) I managed to successfully compile wpa_supplicant for the W95 box.
Yet I'm stuck. I can run wpa_supplicant from adb shell but I have not been able to successfully associate with an access point. I figured this might be some sort of conflict with Network or WiFi manager and two wpa_supplicants running at the same time. I wanted to successfully associate before I continued on to try and replace the wpa_supplicant on the Android box with my compiled version. My problem here was that I could not figure out how to enable wlan0 without network manager. In any case I got desperate and punted. I went ahead and tried to replace the original wpa_supplicant with the one that I compiled. Now everything's a mess.
Now that I think about it, I could probably enable the ssv6051 wifi driver module and bring up wlan0 with ifconfig or ip but did I know that back then? No.
Since I did already try and replace wpa_supplicant with my compilation I figured all bets were off. In any case, I could always copy back the original wpa_supplicant right? Well, not exactly. At this time, neither one works and I'm racking my brains just trying to get things back to square one. I get a vague error about not being able to start HAL. I read some about HAL and a possible culprit, selinux (although this is unlikely due to the w95 box being in Permissive mode by default) but I still am not anywhere closer to fixing my wifi. The button moves on temporarily, the driver modules load, but the HAL error occurs and it does not list any wifi networks.
I think I messed up when I edited one of the wpa_supplicant.conf files. Or it could have something to do with the wifi vendor. I don't know, but I'm close to getting this working. Then I can patch wpa_supplicant and it will no longer be vulnerable to the KRACK attack. At the very least I can continue the other tests.
Thank you for reading. Your input is appreciated.