Hey, I have been looking forward to the 2.1 update for our Heros because I thought it was going to finally give us simple VPN access... *to Cisco concentrators*. Unfortunately, it only gives us IPSec/L2TP PSK or CRT... whereas I need a pure IPSec client that supports Group Authentication in order to connect to my corporate VPN.
So, I, and I am sure many others, need to revert back to the Get-A-Robot-VPNC client to connect to our corporate networks, but apparently do not have a correct tun.ko module. Trying to insmod a tun.ko module, I get "invalid format" or "failed executable" - So, can someone provide a tun.ko that we can use, or explain how to get one installed in these new 2.1 ROMs?
I am currently using the ZenHero 2.1 ROM
Thanks! Once I get VPN access again, the Hero will really be something pretty damn awesome again.
Or, does anyone know of any VPN clients coming down the pipe for Android? or any other projects in development?
I heard Shew Soft was coming out with a mobile variant... not sure if it'll be on Android though..
I have no use for it or way to try it, but I did find vpn connections in the market when searching for something else and remembered this thread. It said on the comments though to go to the site for the latest version. http://code.google.com/p/get-a-robot-vpnc/
actually, a search for vpn in the market turned up a few options. Take a look, I don't know exactly what you need.
I have been trying multiple ways. I even tried the tun.ko. I have not been successful but I would like to hear if anyone is successful.
danaff37 said:
actually, a search for vpn in the market turned up a few options. Take a look, I don't know exactly what you need.
Click to expand...
Click to collapse
Unfortunately, none support, what I think to be the most popular VPN type, from a corporate stand-point: pure IPSec that supports Group Authentication. Most in the market are just for VPNC.
Thanks for your post though.
Yes the android app is lacking.
I have a Cisco concentrator working with MY phone. I just dumped all Group based auth. We wanted a device that would work with 99.999% of devices on the market and our little Asa-5505 does the trick.
You should be able to configure policies on the cisco to handle either clients, that is really your or your admins choice.
Otherwise the stock android vpn client MY only complaint is it will NOT let me vpn over mobile network.. only wifi. Kinda pointless if I have wifi I would use my laptop to vpn to work. WTF?
Sprint is the problem
kkruse said:
Yes the android app is lacking.
I have a Cisco concentrator working with MY phone. I just dumped all Group based auth. We wanted a device that would work with 99.999% of devices on the market and our little Asa-5505 does the trick.
You should be able to configure policies on the cisco to handle either clients, that is really your or your admins choice.
Otherwise the stock android vpn client MY only complaint is it will NOT let me vpn over mobile network.. only wifi. Kinda pointless if I have wifi I would use my laptop to vpn to work. WTF?
Click to expand...
Click to collapse
I realize this post has been sitting here for a while, but I thought this might help some others who may run into similar issues. At my work, we have all Cisco equipment and have a Cisco ASA configured with PSK mobile VPN. We are having basically no luck getting in using Sprint-connected devices (Sprint EVO 4G) on anything but Wifi. I CAN, however, connect just fine on my Samsung Captivate over AT&T 3G signal using the same built-in android VPN client. We've gone the rounds with the Sprint Engineers on this and they have nothing they can pinpoint that is causing this outage. I would really like for either Cisco or Sprint to come up with a good explanation as it shouldn't matter if you're on Wifi or 3G, it should work either way. The point is that it works on AT&T for us, but not Sprint, as far as 3G/4G data connection is concerned.
Related
I've had the captivate about 24 hours now and dig it. I've rooted it and remove the att bloatware (per titanium backup), I've also performed a backup using Rom Manager.
I'm having trouble getting it up and running on an enterprise wireless what uses 802.1x PEAP authentication. I can get through all the auth. steps, and the device is assigned an IP, but I am unable to do anything that requires an internet connection; browser, market, etc.
Has anyone else ran into this issue?
*****EDIT*****
sigh i just realized that this is in the wrong area, it should have been over in development...i'm an idiot
I had a similar problem on a WEP-encrypted network, which I fixed by setting a static IP on the phone and then setting it back to DHCP (the correct setting). However, your problem could be entirely different than mine (not that I even am sure what my problem was, just that I fixed it!)
Best of luck!
Having the same problem on enterprise access points regardless of encryption. Home wifi netwroks work great (open and WPA2). Enterprise APs (open and WEP) connect and give me an IP, but will not transfer data. Think its a driver issue with the Wifi, it happens on every captivate ive tested, and seems to be more widespread than the GPS issue.
I have had the same issue with my work at work. I can get it to connect and get a ip but can not pass any data.
Sent from my SAMSUNG-SGH-I897 using XDA App
Had the same problem at work. Luckily I'm an admin and figured mine out. Our monowall portal was the issue. I can give a detailed answer for my problem tomorrow when I get to work.
I actually had the cap wiped to go back, then I literally figured out the problem. Thanks go out to my team mate for helping me talk through this.
Sent from my SAMSUNG-SGH-I897 using XDA App
can't wait to hear what your fix was!
Sent from my SAMSUNG-SGH-I897 using XDA App
This sounds more like your network not being allowing your device rather then the device having an issue.
it's been frustrating as I know two other guys with android devices that didn't have an issue. one is a droid eris running 2.1 and the other is a nexus one running 2.2.
Sent from my SAMSUNG-SGH-I897 using XDA App
designgears said:
This sounds more like your network not being allowing your device rather then the device having an issue.
Click to expand...
Click to collapse
Worked closely with my highly experienced network admin in my dept. for an afternoon (we had some time to kill). He checked the firewall and dhcp servers, ran packet traces, etc.
With what I'm experiencing, its the device. These wifi networks we use with Cisco APs are completely wide-open. All other phones and mobile devices have always worked great for years. We rely on this network for many custom applications and mobile tools.
Once the dhcp server leases an address, it seems like the radio stack hangs, and the device ceases communication. Here's an older thread on the exact issue over at androidfouroms: http://androidforums.com/samsung-captivate/130403-wifi-terrible.html
I have tested multiple new unmodified captivates and the issue is identical accross the board.
Now that I am at work, and have coffee in me and not beer, I will go through the problem I had with miCap and works wireless. Due to my skeptical ways, I will be semi vague for security purposes. On with it.
When I originally got miCap (pet name for it) I was able to access our public wifi. It allowed me into the public portal to agree to terms. I played a little bit on it, but wanted to see if I could access our private wifi. I got in the private no problem. But after that I never was able to get back on to our public. It did the same thing as I've read. It got an ip no problem (via dhcp) and acted like all was well. No browser, or ap could get a connection. The phone would not switch over to 3g to get info.
Armed with ip and mac address, my co-worker and I started to did through our monowall. ( He also has a cap that had no issues on public or private). We try tried reserving the ip for miCap, didn't work. We tried static ip, didn't work. I spent the morning completely wiping miCap to get it back to return worthy.
This was when I decided on last ditch effort.
Our ap's are cisco's that connect into monowall. I got into monowall and dug around. I found that with in the captive portal (how fitting) that the ip/mac associated with my phone hadn't checked in for 8 days. Even though I tried everyday. I deleted the entry to the phone there and suddenly my phone was getting access again.
Now I understand that this may not help everyone, because setups vary from place to place. But digging deeper into configurations at the access points may be what is needed. Do I think the phone had nothing to do with it? No, I think it helped aggravate the problem.
We have had problems with the Intel 3945abg chipsets with the same exact setup. That problem was fixed with driver updates on the laptops.
sorry for the long winded reply.
So in a nut shell you deleted the DNS entry for that ip/mac in the firewall and you are working.
Pmac25 said:
So in a nut shell you deleted the DNS entry for that ip/mac in the firewall and you are working.
Click to expand...
Click to collapse
Essentially yes. But it is not listed like that in the portal. Hmmm. I wonder about the combo of dhcp/dns being the culprit.
I was able to resolve this issue by changing my connection settings from DHCP to static for the Cisco APs.
Installing WiFi Buddy from the market allowed me to access these connection settings.
I just used an address from our static IP pool.
Manually set IP, subnet, gateway, and DNS, and now im finally rolling on our enterprise wifi network
I sent a help ticket into samsung; maybe if enough folks do we can get it on their radar.
jhannaman82 said:
I was able to resolve this issue by changing my connection settings from DHCP to static for the Cisco APs.
Installing WiFi Buddy from the market allowed me to access these connection settings.
I just used an address from our static IP pool.
Manually set IP, subnet, gateway, and DNS, and now im finally rolling on our enterprise wifi network
Click to expand...
Click to collapse
you can set the ip manually with out an app. When on the wifi screen, hit menu-advanced. This is a good time to set the wi-fi sleep policy also.
phlunkie said:
you can set the ip manually with out an app. When on the wifi screen, hit menu-advanced. This is a good time to set the wi-fi sleep policy also.
Click to expand...
Click to collapse
Thanks for that, i figured the menu was built in somewhere just never found it.
:thumbsup:
UPDATE
So I flashed the i9000 Eclair rom last night, and when I got into work today I can connect and use the wifi here. So looks like something AT&T buggered up, big surprise there, when they "customized" the captivate.
As much as I normally love blaming AT&T for problems, that can't be done here. My Captivate (running Stock Firmware) connects just fine to my work network. We use 802.1x with PEAP/MSCHAPv2 for authentication.
Anyone been able to connect at over 802.11b speeds while connected to an 802.1x network? I show connections at G and N speeds on my WPA2 network but nothing over 11Mbps on 802.1x.
Sent from my SAMSUNG-SGH-I897 using XDA App
Hi,
I am also having problems with my work wifi network.
It is 802.1x, on TTLS/PAP it also requires a thawte premium server ca certificate insalled.
Is there any way to connect this kind of networks?
With my previous iphone 3g it was taking only 4-5 seconds.
My Xoom usually disconnects the VPN immediately after opening any file from an SMB Share using ES File Explorer. I preferred Astro but the SMB addon doesn't work with Honeycomb yet. A variation of different vpn clients all do the same, as soon as data is done being transferred from a single download, the VPN will disconnect.
Is there a workaround for this? It would be great to only have the VPN connect when resources on the network were accessed or written.
I haven't found a workaround or solution to keep the VPN up and stable.
(btw, this is a typical MS 2008 PPTP on a Windows Domain)
At the moment, I'm having to reconnect after every file transfer- again, the wireless network doesn't seem to make a difference (although the 3g connection is obviously poor)
I've done a little troubleshooting on this in the last few days using the magic of wireshark. MS PPTP Server, makes the connection and then drops after SMB traffic is attempted, as well any website will not load, and no email / communication will work.
I believe this fully involves a Default Gateway setting on the Xoom, being it's a client-side setting and the Xoom doesn't appear allow that option to be changed (silly that it's missing, imo).
When I make a connection, Verizon's firewall policies see a foreign IP return traffic at some point on their network and blocks the transmission completely, eventually causing PPTP to timeout.
Here's a good read on how to get around the restriction:
http://jbenisek.wordpress.com/2010/10/05/android-2-1-and-2-2-vpn-pptp-over-verizon/
I myself have been on the phone this morning regarding this issue, I'm up to about a 3rd level of tech support and he is trying to tell me 'nothing is blocked at all on the Verizon network'...
I'm awaiting a call back now... at which I'll try to show him the above site/resource and maybe he'll move me to an unrestricted IP block. We bought 3 Xooms with the intention of working remotely in the field using PPTP- 4 more coming soon---
At this point, I'm still tempted to go back to Sprint and just wait on their Xoom release.
*btw, you can verify the above by tethering to the Xoom and changing your default gateway on a laptop/pc, the connection will work fine.
edit:
AH-HAH!
And more info;
http://code.google.com/p/android/issues/detail?id=4706
Apparently this is a known issue.
Encrypted PPTP is broken on Android: http://code.google.com/p/android/issues/detail?id=4706
I've posted about this problem in this thread:
http://forum.xda-developers.com/showthread.php?t=992876
I've tried it on every version of Android since 2.1. I tried it with my Xoom on 3.0 and the problem remains. It appears to be a pretty low priority for Google.
sangreal06 said:
Encrypted PPTP is broken on Android: http://code.google.com/p/android/issues/detail?id=4706
Click to expand...
Click to collapse
Turned off encryption on the server and all was well. I can't believe google let that slide... !?
I guess I'll transition to a L2TP VPN...
I am trying to use PPTP VPN with MPPE encryption enabled to connect to a network with a WRT54GL running dd-wrt-vpn running the vpn server. I know I have the server setup right, and I have added scripts to the server pptpd options file to require encryption "MPPE required" and disable compression "nodeflate". Using a rooted EVO 4G with stock 2.2 Froyo, I am able to connect successfully over 3G or 4G, however traffic only works for about 20 seconds, after that, no web pages will load, no ping, nothing, but the vpn stays connected and never disconnects. I know this has been an issue with Android since 1.6, and you can see the post on code.google, issue 4067, it's been there since november 2009, and has still not been fixed. I'm not asking a question about "what's causing the issue", so please don't tell me to use search just yet , what is strange to me is that if I use my Samsung Galaxy Tab 10.1 running Android 3.1 to tether to my Evo with wireless tether, then I can use the PPTP VPN client in 3.1, and it connects and creates a stable pptp tunnel, and I was able to have stable traffic for hours without anything going wrong (except for the Evo battery temp reaching 100F after some time ). They had reported on that issue 4067 that even the later versions of android don't have a working pptp and ppp0 client, so that's obviously not correct.
Anyway, I read a post here (in the Samsung Epic 4G forum) by member "drunix" from september of last year that said he was going to try to recompile the client with MPPE encryption enabled (assuming that is the issue in 2.2) if no one else has done it yet or tried to fix this yet. I don't think it's just the encryption that is the issue, because even with encryption disabled both on the server and client, traffic dies again after about 20 seconds.
So judging from what that member wrote, even though SO many android phone owners have complained so far about the pptp vpn client not working properly in Android versions 1.x and 2.x, no one has so far successfully fixed this issue yet, no one has even acknowledged or attempted to look at this issue yet so far other than that one member, not even the OS manufacturer. I have a hard time believing that the independent developers here and everywhere else make all these custom roms and kernels and other very impressive things from scratch, but no one has even touched this issue when functional pptp and ppp0 already exists almost on all other computer OS's and other platforms, and iPhone, WinMo and linux ALL have functional clients. All apple users say that they can successfully use the phone to connect to a pptp vpn. I guess this must not be important enough to catch the attention of any devs not only from google, but not even here. Is there any way some of the very knowledgable devs here, who can so easily root any new android version that comes out, take a look at this to see if they can fix it so android can be fully functional in all its included features like apple? I think this is the only major issue where android does not function as well as iOS, otherwise it is ahead of the iphone in every other aspect, so why not try to fix this for those who have the knowledge and fix things that are way more complicated than this?
Thanks
Are you referring specifically to 2.2 versions? If so I cannot answer since I am running 2.3.4 modified stock sense 3.0
Also I have successfully used at least three of the available VPN clients to support a IP/Sec connection to both secured servers and routers (mostly routers) with no drops, lock ups or related.
For me, the VPN clients work and have worked but maybe you are referring to something specifically different.
Hope that helps
Hey, I was hoping I could get some help with this. I must be doing something wrong because I've spent a ridiculous amount of time on this project and have nothing to show for it.
I want to run a mobile hotspot on my phone, but not nearly enough to justify paying Verizon an extra $30/month for tethering. I'd only use it a few times a month and wouldn't push a lot of data thru, plus I'm paying them for an "unlimited" data plan - I won't get into that, you know where I'm coming from. I know they probably won't do anything about it since I'm using it so little, but I want to add an extra layer of security via an SSH tunnel or a VPN. I'm sure they just have to run a very basic report on their system to catch somebody who's tethering, and who knows when some manager will tell them to run it on every user vs just the high bandwidth ones? They could force me onto a more expensive plan, disable my account, throttle my connection, or just block any port an Android phone doesn't normally use, and they could do all that automatically pretty easily. If all my tethering data is encrypted they'd have to do some actual work to prove I'm tethering and probably won't think it's worth their time.
I installed OpenSSH on my home PC, forwarded some ports, and put the SSHTunnel app on my phone and it works great. It seamlessly moves all traffic over my SSH tunnel, except for the mobile hotspot. Which was kind of the point of the whole exercise! I looked all over the place but could not find a way to resolve this.
Next I looked at setting up a VPN so I loaded TomatoVPN on my router. The default VPN (OpenVPN) option for that firmware is IPSec with a CA certificate, so I went about setting that up. Apparently the default Android VPN client doesn't work well with IPSec because I can't get it to work - it keeps prompting me for a username and password, but it won't accept my router's admin credentials. None of the tutorials mention that prompt and I can't get around it. I messed around with an IPSec PSK VPN but couldn't get Android to connect to that either.
I looked into PPTP a bit but they say it's not supported by Linksys or OpenWRT, and from my experience Tomato doesn't appear to work with it either. I was going to put a PPTP server on my PC but saw somewhere that many routers can't forward PPTP requests from a WAN into the LAN.
So I went back to the IPSec approach, figuring the problem is with the Android client. I tried putting OpenVPN on my phone, but got stuck where I have to register a tun.ko file using the terminal. I don't even know if I found the right tun.ko. Then I realized I was trying to install an app to configure an app that installs another app and maybe I wasn't going about this the right way.
Does anybody have any advice? How should I approach this?
Here's what I'm using
Phone: Rooted HTC Thunderbolt
Carrier: Verizon
Ugh, looks like Verizon is 1 step ahead of me:
jbenisek.wordpress.com/2010/10/05/android-2-1-and-2-2-vpn-pptp-over-verizon/
Well, that sucks.
One thing I've been enjoying greatly (and use VERY frequently) is the Cisco IPSec client that has been standard in iOS.
Since getting my iPhone in 2009, I've been able to connect to my work systems and get a lot of stuff done that would have otherwise required a trip to my desk.
I haven't seen any Cisco IPSec support in the native AOSP or CyanogenMod builds. Is this even possible with Android?
With more and more Android devices comes out (and I have three now), it would be nice to have more options other than always going to iOS.
I saw Cisco AnyConnect in the Market. That (unfortunately) requires Root, something that may not always be possible. There was nothing for Cisco IPSec connectivity.
I had a friend tell me that it is an issue with the linux kernel that is being used not the rom. Doubtful that cisco ipsec vpn will be available on android anytime soon.
Currently it has been done for Samsung devices: https://market.android.com/details?id=com.cisco.anyconnect.vpn.android
And 4.0 is supposed to introduce a new VPN API, meaning that once ICS is ported to this device, you should have what you're looking for.
you can try the cisco anyconnect for rooted phones- for whatever reason it works on my rooted epic 4g but refuses to connect on my nook color. The other option which works is vpnconnections