Related
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.
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 just got my A7 a few days ago. I did the elocity firmware, the latest dexter mod and the adhoc fix.
1. I cannot get the vpn to work. I am trying to get it to connect to my Cisco ASA at work and no matter if I try ip or dns name, it fails immediately. The connection never leaves the A7.
2. I rooted my Motorola Droid and put Barnacle on it. My laptop can wifi tether to the adhoc network off the phone with no problems. My A7 can see the adhoc, tries to obtain ip address over and over and just doesn't connect. It doesn't matter if I use proper wep or non matching wep key, same results. This is frustrating.
I have re wiped, re firmwared, re dextered several times. Out of ideas. Going on vacation i a few weeks and need to be able to tether.
Help!!!!
hi I had to do this to my samsung intercept running barnacle to make it connect. mabey it will help you.
http://androidforums.com/samsung-intercept-sprint/194068-barnacle-wont-run.html
I use the legacy version of barnacle. I think its available on authors site if not on market
scroll down page a little to see instructions for the fix in the link
Try installing googles wifi tether and run it without wep or wpa and see if you can connect that way.If you can connect then enable the Access control and set a ringtone to let you know when there is a connection,that way you can set it up to where you are the only one that can use it and know if there are any other connections besides you. Go to the link below to get the latest download and be sure to read up on it.This is what I use all the time with 0 problems.If you have any problems with it pm me and I will try to help you with it as much as I can.
http://code.google.com/p/android-wifi-tether/downloads/list
Update
I did as suggested with both Barnacle and Google Wifi Tethering with wep turned off. And it works. Why is that? If I create a wep key in either Barnacle as ascii or hex, it doesn't work whether I use ascii or hex equivalent on the eLocity. With the Wifi Tethering app, it only has ascii option and still no luck. Until a new Dexter comes out that may fix this problem (at least for me), I will probably just use Barnacle with max 3 connections and by default new clients gets no nat. I will manually allow nat from the phone to control access.
What sucks is I cannot use my buddy's jail broken iphone for wifi tethering either. My velocity has the same problem passing passwords to ad-hoc networks.
As far as Ive read and been told Android will not connect with wep but what you said you were going to do will work just fine,that's basically what I do,but when Im going to be in one place for a while I will use Google's wired usb connection (link below) to connect to my laptop and then just share its internet connection with other laptops,phones, game systems etc.Either way I think its a good idea to have both the wireless and wired installed just in case and there free so what the hell.
I hope some of this will help you out. Good luck and have a good vacation.
http://code.google.com/p/android-wired-tether/
Last Thursday I installed the 4.010.11 update from Acer and my wifi connection at work worked perfectly for one day. After the first day it switches very slowly back and forth between "Connecting" and "Scanning" but never actually connects. Looking at the active connections on the WAP we can see the MAC address of the tablet trying to connect but it won't do it.
We are using:
EAP method: PEAP
Phase 2: none
CA cert: unspecified
User cert: unspecified
Identity: my username
Anonymous identity:
Password: my password
My co-worker has a Xoom and it connects fine and both of our Android phones connect too.
We did not make any changes to the wireless configuration. The WAP I'm trying to connect to is an HP ProCurve MSM422 AP.
Today I backed everything up and did a factory reset and the A500 still won't connect. The unit connects just fine to all non 802.1x WAPs.
I have not installed the Acer wifi fix since my understanding is that it is rolled into the 4.010.11 update.
I've become pretty reliant on my tablet at work so this is driving me nuts. Anyone have any ideas?
Thanks,
Matt
same scenario for me, it appeared on the .08 update and I had hoped the .11 update would take care of this issue. However it didn't.
My Nexus One connects fine to the 802.1x connection. My A500 connects to wpa or open networks without trouble.
I don't use my A500 at work but I wish I could if I wanted to.
There is a fix for this well known issue on the Acer support site. Download the zip indicated (it's very easy to find), unzip it to your PC, and follow the instructions within.
There are also several threads on this topic that contain other ways to fix the issue, at least temporarily, but the Acer fix is meant to be a permanent one.
I ran into the same problem after trying to connect to a network that I hadn't yet properly set up. For me a factory restore solved the problem and it hasn't returned so far.
Sent from my A500 using XDA Premium App
FloatingFatMan said:
There is a fix for this well known issue on the Acer support site. Download the zip indicated (it's very easy to find), unzip it to your PC, and follow the instructions within.
There are also several threads on this topic that contain other ways to fix the issue, at least temporarily, but the Acer fix is meant to be a permanent one.
Click to expand...
Click to collapse
The threads on here don't mention 802.1x and my tablet works fine with all the other wireless protocols. The other threads also reported that it would connected and disconnect quickly. My tablet takes several minutes before it switches from "Connecting" to "Scanning" and vice verse.
I have done all the other fixes (double reset, system restore, deleting the DHCP cache (was never there to delete on mine), using static instead of DHCP, etc) and they do not help, not even temporarily. I have not flashed the fix from Acer since the PDF in the patch.zip does not list my newer version as being affected. My understanding, after reading all those other threads, is that the patch is rolled into the .11 update.
dude64 said:
I ran into the same problem after trying to connect to a network that I hadn't yet properly set up. For me a factory restore solved the problem and it hasn't returned so far.
Click to expand...
Click to collapse
I've done a factory restore and it did not help. First thing after restoring I went into my wireless settings and it would not connect. I figured since it worked for a day after doing the .11 update it would at least work temporarily after a restore but no dice.
-
Thanks to the both of you for your suggestions. I may try the Acer patch later today if I have time, I'm stuck in meetings most the day, and will report back. If anyone else has any other ideas I would be very grateful.
I might be a channel related issue. However, what EXACTLY do you mean by 802.1x? Do you refer to 802.11 a/b/g/n? Which one does your router support? IIRC, the A500 supports a/g/n variants only. Not at my tablet right now to check.
Wilda said:
Thanks to the both of you for your suggestions. I may try the Acer patch later today if I have time, I'm stuck in meetings most the day, and will report back. If anyone else has any other ideas I would be very grateful.
Click to expand...
Click to collapse
Just got done trying the patch (after all the other resets suggested on the Acer website) and it didn't work. According to the documentation with the patch, it is only for versions .07-.09.
I'd also like to add that I use WEP on my home network and I connected without a problem this morning. We also use PEAP here at work, so maybe that's the issue.
FloatingFatMan said:
I might be a channel related issue. However, what EXACTLY do you mean by 802.1x? Do you refer to 802.11 a/b/g/n? Which one does your router support? IIRC, the A500 supports a/g/n variants only. Not at my tablet right now to check.
Click to expand...
Click to collapse
802.1X is an authentication protocol originally used on wired LAN's for port authentication that is now also often deployed in corporate wifi networks to authenticate wireless client access to the network.
It should not be confused with 802.11 specs for the RF layer.
rvholland said:
802.1X is an authentication protocol originally used on wired LAN's for port authentication that is now also often deployed in corporate wifi networks to authenticate wireless client access to the network.
It should not be confused with 802.11 specs for the RF layer.
Click to expand...
Click to collapse
OK, I see what you're talking about now. The A500 only supports 802.11 b/g/n. Not sure what you connected to on the first day, but there is no listed support for 802.1X.
I'm not sure you've got a handle on the difference yet. 802.11 b/g/n is the wireless LAN spec, 802.1X is an authentication protocol used on top of the 802.11 layer instead of WEP or WPA2/WPA.
My A500, like the OP's, when running 3.0 worked fine on the network with 802.1X EAP authentication. If you are in the presence of a network running 802.1X and attempt to connect you are presented with a menu for information such as the info in the OP's first post. This info may still be entered in 3.1 for the 802.1X EAP network but it is not authenticating in 3.1 like it used to do in 3.0.
I suspect that the A500 is not presenting its entered credentials correctly such that the authentication process can complete.
I can confirm the Acer offical patch works for .11 (even though it says US .07-.09) - before I couldn't connect at work (PEAP/MSCHAPv2) but WPA and WEP worked fine - after patch 802.1x EAP worked great.
Tested on US 32gb 4.010.11_COM_GEN2
well I installed the patch and will report tomorrow on the results...
Well the wififix patch is not effective in correcting the issue I have at work with 802.1x networks. Patch installed last night and this morning the a500 will not connect.
Guess this is another issue Acer is deficient in testing.
I also tried the double reset just to make sure that it wouldn't by chance have any effect. No connect results.
To answer FloatingFatMan the WAP has two antennas which can be set independently. Right now one is set for b/g and the other for n. As was previously stated 802.1x is an authentication protocol and has nothing to do with speed. In our case it allows wireless users to be authenticated through Active Directory instead of using a password like WEP or WPA.
I'll try the Acer patch today and see if I have any better luck than rvholland.
pfc.joker said:
I can confirm the Acer offical patch works for .11 (even though it says US .07-.09) - before I couldn't connect at work (PEAP/MSCHAPv2) but WPA and WEP worked fine - after patch 802.1x EAP worked great.
Tested on US 32gb 4.010.11_COM_GEN2
Click to expand...
Click to collapse
rvholland said:
Well the wififix patch is not effective in correcting the issue I have at work with 802.1x networks. Patch installed last night and this morning the a500 will not connect.
Guess this is another issue Acer is deficient in testing.
I also tried the double reset just to make sure that it wouldn't by chance have any effect. No connect results.
Click to expand...
Click to collapse
I have the same version as pfc.joker (just the 16GB model), but I got the same results as rvholland. Went home and worked fine but at work it's borked. I haven't been able to find anything useful on the web regarding this. Anyone talked to Acer about it? I'm afraid they are going to charge me $100 for the call.
4.010.13 doesn't help
My a500 updated late yesterday to 4.010.13 and even though there was reference to some wifi tweaks it does not improve the situation I'm having on 802.1X authenticated wifi.
Retried this morning at work and the same results of scanning-connecting-disconnected and then followed by simply staying at scanning for a long time.
There is never any mention of 'obtaining ip address'. I doubt its ever connecting far enough to communicate with the dhcp server.
I received the 4.010.13 update last night and hoped it would fix the issue but like rvholland I too still cannot connect to the wireless at work. Hopefully a fix is found soon.
rvholland said:
There is never any mention of 'obtaining ip address'. I doubt its ever connecting far enough to communicate with the dhcp server.
Click to expand...
Click to collapse
Same thing here. Watching the connections on the WAP it looks like the A500 tries to connect but hangs on the authentication and therefore never gets to the point where the DHCP server can assign an IP.
My first query via online support from Acer was not helpful. They suggested the same old "use 4.010.10" update about wifi issues or "use the patch" answer.
Perhaps the second round will get someone to read the actual explanation of steps already taken before replying with the steps for a different problem.
rvholland said:
My first query via online support from Acer was not helpful. They suggested the same old "use 4.010.10" update about wifi issues or "use the patch" answer.
Perhaps the second round will get someone to read the actual explanation of steps already taken before replying with the steps for a different problem.
Click to expand...
Click to collapse
Thanks for taking the time to check in with Acer. We only have a few weeks before school starts and have a lot of projects that need to be done before the students come back so I have very little time to look into this right now. I sure hope you can get a hold of someone that actually realizes this is a separate wireless issue and is not fixed with .10 or the wifi patch on their website.