Until yesterday I have been successful in connecting to various WiFi hot spots, now I have to use a static IP to connect to the very same two WiFi hot spots. Using dynamic addressing my tablet cycles "authenticating, obtaining IP address etc." and never successfully connects. When I use static IP, the connection is instanteneous. I have tried recycled power to one of the WiFi hotspots without any change. Also, I have been successful in connecting another device to the WiFi router successfully suggesting the problem is with my tablet. The table otherwise works fine.
Has anyone else encountered this?
Lost DHCP over WiFi
I just found the following (timely) posting forum.cyanogenmod.com/topic/18708-dhcp-timeout-over-wifi and will investigate whether that would be cause of my recent problem since I had just downloaded another version of busybox.
I have the same issue but from makin my laptop the hotspot n connecting tab to that, but I use Connectify for the hotspot and itworks with connecting, just not all the time.
When it doesn't, have to forget the connection then re-connect, usually fixes it. I don't think its ur tablet though, ive experienced this with every rom I've tried(tnt stock, tntlite 4.25, vegan froyo and ginger experimental)
Hope this helps
No it does not help since your problem does not resemble mine.
Problem solved after updating busybox to working version. Apparently a version of busybox lacked certain programs needed by the DHCP client.
More info on updating busybox please?
hga89 said:
Problem solved after updating busybox to working version. Apparently a version of busybox lacked certain programs needed by the DHCP client.
Click to expand...
Click to collapse
Related
Hey guys,
I have been keeping my eyes out for the tun.ko module to come out in one of the kernels, and it finally did in the 1.76 GHz kernel. I had to reinstall VPN connections after flashing the kernel, and then VPN connections would tell me that my VPN was connected properly. However, I can't get data to pass through the VPN. No pings to the remote end, no RDP, nothing.
Anybody else get this working?
Thanks,
Seth
I thought I set up my VPN wrong >_> Well that explains it! Thanks! Same issue. I have however been able to see my phone in my router, though I can't do anything with it there in or out.
This sounds like the same issue I was having with openvpn (I assume that's what you're referring to since you're talking about the tun module). I'm running Das BAMF 1.3.2, and tun is already built into the kernel. I'm having the same problem. The VPN connects, no errors at all, even ran it in the terminal so I could see all of OpenVPN's connection output. But data is not routed through the tunnel. WhatIsMyIP still reports my Verizon IP address.
Now, on two occasions I have had success. I was able to connect and disconnect my VPN all I wanted and everything worked. However this only lasted for the current phone 'life cycle', ie it failed again after the next reboot. I can't find a pattern or anything, it seems that it will randomly work after a reboot, but not that often... 1 out of 10 maybe? I didn't waste my time trying to nail down a ghost.
I think I solved the OpenVPN problem. There's an option in OpenVPN settings called 'Fix HTC Routes'. If you check it, you can get the link to view the issue tracker. Essentially it deletes a few routing tables after OpenVPN starts up. For some reason, it doesn't seem to work on the Thunderbolt. Perhaps that option is using a deprecated script command (ip ru del route)? Whatever the reason, the fix is simple. After connecting to OpenVPN, open a terminal and issue the following commands:
Code:
ip ru del table gprs
ip ru del table wifi
Ignore any errors you might get if the routing table doesn't exist. I don't think you need SU, and you can use GScript Lite to make the process easier on you.
I'll give this a shot with VPN Connections when I get a chance and report back. If anybody else has any success, please post here.
I have had better success, but it's not right yet for me. I am able to get some data to flow using RDP, Telnet, etc., but nothing actually works completely right.
When telnetting into routers, I am not able to actually authenticate. however, I CAN finally see the prompts.
When using RDP, it doesn't time out any more, but I don't get any video data back to my phone's screen. No login page, etc.
Those two commands also seem to time out eventually. I need to reenter them to get the data flowing again, it seems.
Anybody else have better results?
Seth
Well, without knowing which VPN you're using, I can't say. But it does seem to work with openvpn and the OpenVPN Settings market app (I have my own install of openvpn, so I don't use the related OpenVPN Installer app).
The routing tables gprs/wifi are automatically recreated when those connections are re-established. Meaning, if you are on VPN via wifi, and wifi disconnects/reconnects, then the wifi routing table is recreated. The same goes for gprs if you lose connection and it is reestablished. I don't know what the system might try to do using the built in VPN connections.
Sorry about that, the lack of info wasn't very helpful.
I'm trying to connect to my Cisco VPN. We are using group authentication as well as user authentication. The outside device is a 2811 router, and if there are any other specifics that might help, I'd be happy to provide it.
Thanks,
Seth
I'm currently using the new 2.3.4 leaked moto rom from Kenneth Penn's post. I also use Barnacle quite regularly for tethering. When attempting to connect directly from the phone to our PPTP VPN, I successfully connect, but a bunch of protocols are rejected and the connection is pretty much useless.
However, when I tether and connect to the VPN via wifi, I'm not even able to connect. Is this a known issue with Barnacle/Android or the Atrix specifically? Are there other apps that people have found that circumvent these issues?
I've seen some posts that explain you can modify the ppp0 routing tables and some people are using the Android Tether app. But before I dig too deep into those ventures, I'm curious if someone else has already found a decent solution.
Thanks!!
I'm having the same issue with the wired tether app. It worked just fine on froyo but now it doesn't on GB. My computer recognizes the connection to the device but my phone doesn't seem to recognize my computer. Therefore I get no connection between my phone and the computer for the usb tethering to occur.
The issue I posted originally is specific to a PPTP VPN connection. Are you connecting to a VPN? If not, you may be better off creating a new topic as your issue may be replied to more quickly.
shaunole said:
The issue I posted originally is specific to a PPTP VPN connection. Are you connecting to a VPN? If not, you may be better off creating a new topic as your issue may be replied to more quickly.
Click to expand...
Click to collapse
Oh I see. Thanks
Hello
I have installed OpenVPN and its logging on to the vpn and is visible on the network list BUT I dont get any connection to another client in the vpn. I tried to ping another client from my SGS2 and from a client to the SGS2 but its always a timeout. I tried it with the phone and serveral wireless networks.
So I think it could be a routing issue but I dont have a clue how to see if thats really the problem and if its true how to fix it. I read some other posts and maybe it could also be a tun.ko problem but the SGS2 with 2.3.3 should already have installed it on the software, so I'm not sure how to see if thats ok. The Busybox is installed at /system/xbin. So does anybody have an idea how to find out whats actually the problem and how to fix this?
Thanks for your help!
Manolo
It's not clear to me if you tried connecting through your mobile data plan. Did you also tried that?
What is the IP that you are getting when your are connected to the VPN?
If it something like 192.168.1.* Then that's could be your problem. If the WIFI your are on, also gives you an ip adress as 192.168.1.* then that causes the problem. Either change the ip range of your network to 192.168.10* (just an example) or the ip range of you VPN.
ps can you post your VPN server settings?
Do you mean my own ip or the ip that i have in the vpn?
my own edge telekom ip is 10.219.127.35 and my internal vpn ip is 10.10.0.22
I can't post my vpn server settings because i got some key files for the vpn.
If you have installed installed this .zip
http://forum.xda-developers.com/showthread.php?p=16182571#post16182571
Then all you need to do is download openvpn settings from the market. And run in.
If you already did these steps, then the problem lies probably with your server and I need the server config. I don't need the keys of course
Thx!
How does this update work? I see no instructions on the post. Is it just to copy on the root folder?
Ah yes... I found how it goes and its working perfectly!
Thx a lot!
Router information: Linksys Wireless-N WRT120N
I have done everything that i could think of to get this working. i have done several google searches and they all say to do specific things.
For example:
-Reset router
-Enable B/G only or G only set at channel 11
-turn off router firewall settings
-and a bunch of other random sh*t
i have done all of the above then some and i still cant get it to connect. all i get is *scanning* then *disconnected* thats the only two things it says. except right after i reset the router. every time i reset the router i get * obtaining IP yadadada* then goes to *disconnected* then back to the "scanning, disconnected" loop.
there have been some people that have said flashing a custom firmware on the router would fix the issue with mobile connectivity on Wireless-N routers.
please someone be helpful with this and please dont tell me i need to reset my router. i have asked this same question on several forums and the only replies i get are "if you reset the router and turn off security it WILL work fine" thats bull****. im not an idiot. thats the first step any computer literate person would take before asking questions.
**Update: same as from General thread. i had to repost because it was closed for some reason there. also here are the answers to the other two guys to responded.
"not standing close enough" -i have been standing next to it. i have yet to test it more than 10 feet away lol so it cant be there
"flash another rom or reflash current rom" -it has nothing to do with my rom, kernal, or radio. this issue is also happening on my girlfriends xperia running Wolfxperia and mine is the blackeditionHDv2. its also an issue with her sisters xperia. hers is still stock 2.2(i think). their stepdad has an iphone and it wont connect with that either. from what ive gathered... its a mobile issue. i know all these phones say (b or g only) but even setting the router to broadcast in b/g it still wont connect. it notices the routers name with full strength on all devices. also i might add that their laptop is an older laptop. does not support N but still can connect to the router and have internet.
Same here. Xperia mini x10 pro. When on it says connecting even thought I nothing appear visible.
Sent from my DesireS to your screen
Has it ever worked or it just not Working now? It happened to me before I reverted to stock and it worked
Sent from my X10S using XDA
*sorry for hijacking your post ts*
as for me it just started, before that when i was at col i was able to watsapp as usual, the phone is currently not with me but when i get i will post some ss for you to see.
-------------------------------
Here are the ss
any idea on how i can solve this?
I'm guessing this is an ip issue. The mobile devices are not able to get one. This usually happens to me on a public network and I even get a " limited or no connectivity".
The work around I do is to assign a static ip on my phone. Its very simple to do and if you need help doing it, let me know.
There's no clear explanation I can tell you, but it seems some mobile devices have a hard time pulling ip's from different types of routers. Hope this helps.
Sent from my X10 using Tapatalk
daniel.b said:
I'm guessing this is an ip issue. The mobile devices are not able to get one. This usually happens to me on a public network and I even get a " limited or no connectivity".
The work around I do is to assign a static ip on my phone. Its very simple to do and if you need help doing it, let me know.
There's no clear explanation I can tell you, but it seems some mobile devices have a hard time pulling ip's from different types of routers. Hope this helps.
Sent from my X10 using Tapatalk
Click to expand...
Click to collapse
Will ask my gf to give it a try. It happened so abruptly, it was working fine when she was at col then when she came back it won't detect any wifi, whether it's her house or mine, and now that she is back at her col she still can't connect.
I know how you feel.
I have had this issue ever since I first upgraded to Stock 2.3.3 last July. On 1.6 and 2.1 (both stock also) I never had issues.
Basically, in my case, resetting the router DOES solve the problem, but only for a limited time. This limited time is random, as sometimes it will work for a few days, and then sometimes it will cut out a few hours again after I have reset my router. I am also using the static IP method (and an app called WiFi Stat which I initially thought had solved the problem, but it hasn't) I'm not sure what triggers the WiFi connection to be lost, but there must be a trigger. Like I said, I never had this issue in my previous old Android versions.
I had hoped (somewhat naively) that moving to a custom ROM would solve the issue, but after installing Wolf's latest ROM, I still have this issue.
Have you tried anything based on 2.3.4 or above, to see if this is an Android 2.3.3 issue? Are there any good ROMs people could recommend that are based on higher versions than 2.3.3?
WEP/WPA key issue?
If its not the kernel/ROM/version of the phone, it could have something to do with the way the security is set up for your router. I had the most frustrating time logging into my university's wireless (think it was encrypted with 802.1x EAP) which required username and password. Though most home-owned router are equipped with WPA/WPA2 PSK or WEP, you can try the steps below:
1. Go to Settings ->Wi-Fi Settings -> Add Wi-Fi network
2. Type in the network SSID (yeah this is the manual part)
3. Open the "Security" drop-down box and set the following:
Security: 802.1x EAP
EAP method: PEAP (default)
Phase 2 auth.: MSCHAPV2
CA cert.: leave unchanged
User cert.: leave unchanged
4. Type in username (if any) and password.
Once again, this would work 99% for 802.1x...not sure about WPA/WEP. Good luck!
Try Channel 6 in router option and hope it works.
Solve
setting a static ip doesnt seem to work.. any idea? i wish not to re-flash as i dun think that would be a permanent solution.
again i dun think it has anything to do with my router as other gadgets are able to connect with it and i didnt fiddle with the security.
It is unable to detect any router as i have tried it different hotspots.
Hope to get some help.
------------------------------------
I wipe clear the settings and it worked again.. hope the problem doesn't persist again.
Has anyone gotten their Tablet S to connect to WiFi via an ad hoc connection? I found this in the Market ZT-180 Adhoc Switcher but don't know if it works with our Murata WiFi module.
I did try the wpa_supplicant hack, but afterward I was only able to see ad hoc connections. Actually connecting to them failed each time.
I tried wifiAdHocEnabler from the market, same result, i can see the adhoc networks now but it keeps on obtaining IP address on Sony tab S when I try to connect
I tried it on my desire hd, it worked (connected to the adhoc) but no internet, I am still trying to figure out how to solve it
Hi,
This was already discuss here:
http://forum.xda-developers.com/showthread.php?t=1290313&highlight=ad+hoc
I was able to connect my tablet to my android phone internet
Thanks rimsilva for pointing out that post
the issue is still there, I can see the adhoc and the tab keeps trying to obtain IP address
I can use my iphone hotspot to connect my tablet to internet, simple and easy
SudaDreamS said:
Thanks rimsilva for pointing out that post
the issue is still there, I can see the adhoc and the tab keeps trying to obtain IP address
Click to expand...
Click to collapse
Have you tried busibox and wifiadhocenabler in the tablet.
I had the same issue with a specific rom in my android phone, the wifi tether was running but my laptop was always obtaining IP address.
In your phone you are using native tether or external application? Please try wireless tether or wifi tether beta (look in Google)
I am using htc P3600 WM6 (Trinity) as wifi hotspot with WMWifiRouter
I can detect it using other windows mobile 6 device and I can surf internet on other WM6 easily. This is why I guess the issue is in android (Sony S & htc Desire HD 2.3.3 Leedroid)
& yes I tried the wifiadhoc enabler and after trying it only i was able to detect the hotspot but I couldn't connect (obtaining IP)
I tried the adb method, root explorer method, Xoom files, Nook files all are giving same result (obtaining IP)
Sorry guys, I'm confused as to why it sounds so complicated.
I have no problem connecting my new unrooted tablet s to wifi using my iphone hotspot or connecting to wifi at Mcdonald, Starbuck or other government building or libraries.
I don't need any app at all.
Kermit33 said:
Sorry guys, I'm confused as to why it sounds so complicated.
I have no problem connecting my new unrooted tablet s to wifi using my iphone hotspot or connecting to wifi at Mcdonald, Starbuck or other government building or libraries.
I don't need any app at all.
Click to expand...
Click to collapse
Look that we're talking about different things, that may cause the connection problem.
My experience is with Android --> Android connection. I had no success with MIUI .35 Kernel in my Ideos, but with CM7 and now Aurora ICS works perfect.
I thought SudaDreamS was trying the same but no, he is on WM6 and maybe is limitation between both systems.
Now you are talking about iOS and routers....
SudaDreamS look at this thread:
http://forum.xda-developers.com/showthread.php?t=1192961
http://android.stackexchange.com/questions/17190/tethering-hc3-2-with-windows-mobile
PS: your tablet is rooted right?
rimsilva said:
Look that we're talking about different things, that may cause the connection problem.
My experience is with Android --> Android connection. I had no success with MIUI .35 Kernel in my Ideos, but with CM7 and now Aurora ICS works perfect.
I thought SudaDreamS was trying the same but no, he is on WM6 and maybe is limitation between both systems.
Now you are talking about iOS and routers....
SudaDreamS look at this thread:
http://forum.xda-developers.com/showthread.php?t=1192961
http://android.stackexchange.com/questions/17190/tethering-hc3-2-with-windows-mobile
PS: your tablet is rooted right?
Click to expand...
Click to collapse
My tablet is not rooted.
Thanks again rimsilva,
well both links didn't help much
I tried to use a static IP to overcome (obtaining IP address issue)
The great news is .. I was able to connect but no internet surfing on the tab yet and on the other wm6 as well, there was no surfing
anyhow, I'm still trying
hope some1 will suggest some solution or help by thinking with me
---------- Post added at 05:08 PM ---------- Previous post was at 05:05 PM ----------
Kermit33 said:
My tablet is not rooted.
Click to expand...
Click to collapse
You can't tether to ad-hoc then, anyhow you might tether to access points
I managed to connect by removing the security of the network, speed is fine, it works perfectly now, since I'll be using it on the go, I wont need the security that much + the WMWifirouter shows how many devices are connected, so it's gives partial sense of security
Thanks to rimsilva for trying to help
SudaDreamS said:
I managed to connect by removing the security of the network, speed is fine, it works perfectly now, since I'll be using it on the go, I wont need the security that much + the WMWifirouter shows how many devices are connected, so it's gives partial sense of security
Thanks to rimsilva for trying to help
Click to expand...
Click to collapse
Holy crap! I did the same thing and it worked. Can't believe I didn't try that before. I'm using Connectify-Lite on my laptop in Afghanistan and it was driving me nuts to not be able to connect my Tablet S.
hi all
i hit a wierd issue with adhoc p2p on my tablet S. my tablet is rooted and i have reference to all the available HC adhoc wpa_supplicant binary available out there..
scenario with adhoc connections setup on Win7 works fine(static IP setup). im able to ping the wifi ip of my Win7 from tablet S.
However, it failed to talk to talk to my adhoc device "OBDKey WLAN". It(tablet S) will see the adhoc ssid and connects to it(static ip setup). but it will goes into connect/disconnect loops. I ran a terminal to constantly ping my device adhoc IP but its always 'host unreachable'. Im constantly seeing errors :
I/wpa_supplicant( 2932): CTRL-EVENT-DRIVER-STATE HANGED
V/WifiMonitor( 155): Event [CTRL-EVENT-DRIVER-STATE HANGED]
ip route shows the correct network routing for network 192.168.0.0/16
netcfg shows my wlan0 is up and running with the static IP.
wpa logs that its able to connect to the adhoc ssid too.
(attached is the log of the occurance describe above.)
I did make sure its not the adhoc device faulty by testing with my HTC phoen. I was able to connect to my adhoc device using my HTC DHD (rooted with LeeDroid) and ping both ways.
Is there any kind souls who can point me to the right direction to solve this? am running out of ideas.
/etc/wifi/wpa_supplicant.conf contents:
$ cat /etc/wifi/wpa_supplicant.conf
cat /etc/wifi/wpa_supplicant.conf
update_config=1
ctrl_interface=DIR=/data/system/wpa_supplicant GROUP=wifi
eapol_version=1
ap_scan=1
fast_reauth=1
wpa_supplicant refs:
http://forum.xda-developers.com/showthread.php?t=1083182&page=2
http://forum.xda-developers.com/showthread.php?t=1069569&page=2
http://forum.xda-developers.com/showthread.php?t=1033314&page=14
http://androidtablethacks.com/android-tablet-hacks/how-to-enable-adhoc-wifi-on-android-tablets/
solved my issue with adhoc wifi keep d/c
zerod78 said:
hi all
i hit a wierd issue with adhoc p2p on my tablet S. my tablet is rooted and i have reference to all the available HC adhoc wpa_supplicant binary available out there..
scenario with adhoc connections setup on Win7 works fine(static IP setup). im able to ping the wifi ip of my Win7 from tablet S.
However, it failed to talk to talk to my adhoc device "OBDKey WLAN". It(tablet S) will see the adhoc ssid and connects to it(static ip setup). but it will goes into connect/disconnect loops. I ran a terminal to constantly ping my device adhoc IP but its always 'host unreachable'. Im constantly seeing errors :
I/wpa_supplicant( 2932): CTRL-EVENT-DRIVER-STATE HANGED
V/WifiMonitor( 155): Event [CTRL-EVENT-DRIVER-STATE HANGED]
ip route shows the correct network routing for network 192.168.0.0/16
netcfg shows my wlan0 is up and running with the static IP.
wpa logs that its able to connect to the adhoc ssid too.
(attached is the log of the occurance describe above.)
I did make sure its not the adhoc device faulty by testing with my HTC phoen. I was able to connect to my adhoc device using my HTC DHD (rooted with LeeDroid) and ping both ways.
Is there any kind souls who can point me to the right direction to solve this? am running out of ideas.
/etc/wifi/wpa_supplicant.conf contents:
$ cat /etc/wifi/wpa_supplicant.conf
cat /etc/wifi/wpa_supplicant.conf
update_config=1
ctrl_interface=DIR=/data/system/wpa_supplicant GROUP=wifi
eapol_version=1
ap_scan=1
fast_reauth=1
wpa_supplicant refs:
http://forum.xda-developers.com/showthread.php?t=1083182&page=2
http://forum.xda-developers.com/showthread.php?t=1069569&page=2
http://forum.xda-developers.com/showthread.php?t=1033314&page=14
http://androidtablethacks.com/android-tablet-hacks/how-to-enable-adhoc-wifi-on-android-tablets/
Click to expand...
Click to collapse
Ok, i have resolved my issue above. Even thou i was using a adhoc enabled wpa_supplicant, my adhoc wifi device is have constant disconnecting upon connecting and with Xoom adhoc HC built wpa_supplicant adhoc enabled, i get the above wifi errors (hung state) from wpa_supplicant.
After spending much time on it, i discover that my tablet S is doing wireless b,g,N. Looking further it seems my device only does a,b,g. Digged the whole /system for wifi related things and managed to find out some info in wmiconfig and wlan_tool.
So in wlan_tool, there is a commented line :
#WMODE="bg"
uncomment the above line will make your wifi to only communicate in b or g mode. And viola... problem solved. Connections remains strong and i do not face any d/c on my adhoc wifi connection to my device.
how to add ad hoc wifi capability to S
O.k., big newb here. I just read up on lots of threads on how to make the tablet S work with ad hoc wifi (I have a verizon thunderbolt). but, everything is way over my head.
Question, does the tablet S have to be rooted to enable it to work on ad hoc wifi?
I think all the forums and threads that I have read indicate that to be true. Obvious next question would be how...
Thanks in advance.
Yes, you have to have your tablet rooted to try any of the ad hoc solutions.
Hellomofo said:
I think all the forums and threads that I have read indicate that to be true. Obvious next question would be how...
Thanks in advance.
Click to expand...
Click to collapse
Here is where to begin...Tablet S root solution
Thanks. I'll start there.
No need to modify wpa_supplicant binary
I changed data/misc/wifi/wpa_supplicant.conf instead of wpa_supplicant.
Step1:First i scanned my adhoc network using Wifi Manager. It shows adhoc networks. I ignored it's warning and tried to connect. It'll fail.No problem! We now have the adhoc network listed in wpa_supplicant.conf.
Note: you can skip this step if you know how to edit wpa_supplicant.conf manually or if your device already lists adhoc networks on scanning.
Step2: You'll need to root your device if you're doing this through your device itself. If you use adb you may not need to root your device.(I had root access by default through adb. So rooting the device wasn't necessary for me). If you're using pc(windows or linux), i recommend Android Commander.
Pull and/or edit data/misc/wifi/wpa_supplicant.conf. Add the following line
ap_scan=2
Find line like
network={
ssid="your adhoc name"
bssid=*some value*
.
.
}
Delete bssid line.
Add/Change the following
scan_ssid=1
priority=1
mode=1
Push back/save the modified file.
chown ownership back to system.wifi. Type the following in adb
#chown system.wifi data/misc/wifi/wpa_supplicant.conf
Advantage: Safer than modifying system/etc/wifi/wpa_supplicant binary. Saves you the trouble of compiling modified wpa_supplicant or finding a compiled one for your platform.
Drawback: This is just a temporary solution.You'll have to repeat this process for every new adhoc network as it doesn't enable adhoc forever. It is good for connecting to your home network or other know networks, but if you want to connect to any adhoc network you scan,then this is not your method. Because, wpa_supplicant.conf will be overwritten every time you scan a new network.