I'm on a rooted RC33. I have no problems with my network connection (3g or wifi), but I noticed recently that when I go to the "phone info" activity (via anycut) and hit the "run ping test" button, the "ping ip address" and "ping hostname" tests always fail (but the "http client" test passes, and, as I mentioned, everything else network-wise seems to work fine).
I know I tried this when I was on an unrooted RC30 and it worked.
Any ideas? Any reason to be concerned?
EDIT: command line ping from terminal shell works fine...
Same here. On latest JF build (non ADP)
Related
Guys, apologies if this has been posted before but couldn't find it.
I've rooted my phone with JF RC9, but for some reason I can't use the wifi tether (one of my main reasons for rooting in the first place). So far as I can tell, I have root (in that I can su in a terminal) and my pc can see the ssid of the phone and connects quite happily but I don't get internet access for some reason - am I missing something really obvious or have others encountered this before?
Hi!
I assume you are using "Wifi Tether for Root Users" ...
If yes please make sure that you are using the lastest Version (0.97.1) which is available here:
http://code.google.com/p/android-wifi-tether/downloads/list
(0.97.1 fixes some cupcake-related issues)
You say that you see that your client is able to connect ... right?
Please check the following:
1) What ip-address do you got from the phone?
(For Windows): Open command-prompt and type "ipconfig"
You should got an ip-address like: 192.168.2.100 (maybe 101, 102, ... at the end).
2) Are you abel to ping the standard-gateway?
type: ping 192.168.2.254
You client must support ad-hoc mode - otherwise it won't work.
Please check and report back.
Man, have I been dense. After spending a couple of weeks, scouring forums, taking the classic I.T. approach of 'turn off, wait, turn on again', I've figured it out...
I'd set up a static i.p. on my pc a long time ago so was still trying to make it through the router...
doh!
Thanks for your reply though harry_m, it was your comment around pinging the i.p. address tat jogged my memory! works like a charm now
Hi all, this is my first post and sorry for my english
I have a big problem with my galaxy sl, i can't use wifi connection (eduroam) in my uni (http://venus.unive.it/wifi/index.php?cmd=eduroam_android Venice)
I have followed the istruction of my uni, but wifi don't work
I have read http://forum.xda-developers.com/showthread.php?t=1477743, i have tryed all versions but the connection don't work
I use miui rom v2.3.23 (http://forum.xda-developers.com/showthread.php?t=1538234) with default kernel.
Do u have a solutions???
thanks to all
Hey there!! I also have eduroam in my University and I have never been able to connect it. Sorry then!!
Same problem here (with eduroam and another similar wifi network in my university).
Actually I was able to connect, but it worked few times. Usually after a full wipe my phone connects flawlessly to wifi, but after that connection, another full wipe is needed.
In my case, it seems that the phone is unable to get a valid IP, because using a fake IP, gateway etc (in wifi settings press the menu button and then go in advanced) it will immediately enstablish a connection (no internet connection of course). I tried to put valid infos once (I had with me my laptop connected and I copied all the infos from it, I only changed the last number in the IP) and it worked. That's why I think is an IP problem, but maybe it was luck .
Maybe doing a sort of "wifi config reset" solves the problem (at least in my case), but it means that everytime I should reconfigure it... I simply gave up and I use my 3G connection .
I found this weird workaround time ago, but I never tried it. I think it worths a try.
===
EDIT:
Strange, you use a different config. I thought all Eduroam networks would have used the same config. Here mine's:
SSID: eduroam
Security: 802.1x Enterprise
EAP method: TLS
CA certificate: "Not specified"
Client certicate: the downloaded certificate
i will try ur config next week but, my friend can use edoroam with a acer liquid (2.2 foryo) with config written in university site.
IMO there are a bugs in the kernel of galaxy sl because a lot of android phone can connected to eduroam
Up
I tried again after I saw this thread and I now I'm quite sure that my problem is an IP problem. I played a little with airplane mode/static IP in a random way (as suggested in the link I posted) and finally I enstablished a connection.
Usually, right before the connection, my phone asks the credential password. And that's weird.
Anyway I discovered something interesting. In our /system/build.prop we have:
Code:
...
wifi.interface=eth0
...
wifi.interface=tiwlan0
but
Code:
getprop wifi.interface
gives as result tiwlan0 and that's ok, this is our wifi interface.
But after that I went to see some other config files and I found that in our /system/etc/dhcpcd we have
Code:
interface eth0
I think this should be
Code:
interface tiwlan0
(I found reference to eth0 in /system/etc/wifi/wifi.conf too, but I don't what this file is used for).
I wanted to see if changing eth0 with tiwlan0 in /system/etc/dhcpcd/dhcpcd.conf and removing wifi.interface=eth0 from build.prop would have helped, but I had no time and now I'm on holiday.
If your problem is similar to mine, try to do that change, it won't break anything, I already did that and wifi works (at home of course, where I've never had a problem).
I have also eduroam in my university and i am using eduroam fixer and it is working perfectly. İt is in google play and free you can use it
Sent from my GT-I9003 using Tapatalk
Try this app: Transparent Proxy. Input your wifi proxy and port.
It may work...
I also have eduroam in my university and I've managed to make it work.
You just need to enter eduroam config and set it like this (I have my phone in spanish, so the names could be a little messed up ):
Code:
EAP method: TTLS
Phase 2 authentication: PAP
Identity: [I]"your university mail"[/I]
Password: [I]"your university mail password"[/I]
And leave everything else blank. Hope it works for you guys!!
I have a rooted Skyrocket. About a year ago I used a QuickSSHd to ssh into my phone from my local wifi network. I haven't used the application in a while and somewhere in that time ATT did some sort of software update that made the windows less Apple-like but not much else. That may or may not have something to do with the fact that if I try to ssh in now the request just times out. I can get a shell through the usb cable using adb (or a terminal program), confirm that I still have root, and see the sshd process with ps | grep dropbear. I also know that something is trying to connect because if I don't launch the sshd and try to ssh in I just get "connection refused" and nmap -p 22 doesn't show anything open but after sshd is running the port shows as "22/tcp filtered SSH" but the ssh request just sits there until it times out. I've tried running dropbear manually through adb, an updated QuickSSHd, and another very nice looking Android application called "DropBear SSH Server" with the same results. I've also tried changing ports. I even make an /etc/shells file because that showed up on some really old how-to document.
When trying to ssh to the Skyrocket from a laptop Wireshark shows the requests going out repeatedly but no replies from the Skyrocket. Shark running on the Skyrocket shows nothing (although other wifi traffic does show up). As a diagnostic I tried sshing from the Skyrocket to my laptop over wifi and wireshark on the laptop shows traffic both ways but they never close the deal. It's as if something is intercepting any incoming ssh traffic on the Skyrocket.
For what it's worth I can ssh from the skyrocket to localhost or its own wifi IP address in an adb shell. It seems like some sort of firewall issue. Any ideas? Do I need a new busybox (whatever that is)? I really don't want to flash any major OS modifications, I just want to be able to ssh in and then start on the real project (trying to talk to an rtl-sdr dongle...)
Thanks!
Dave
c'mon guys, 169 reads and no ideas? Is this something weird with just my phone or are they all this way and everyone's given up?
Is it safe to use Orbot while getting the "error starting transparent proxy"? It says that I am connected to Tor, but when bootstrapping I get an error that says "error starting transparent proxy". Am I revealing anything about myself when I'm browsing if I continue to use Tor (connected & green) in this manner?
manboob said:
Is it safe to use Orbot while getting the "error starting transparent proxy"? It says that I am connected to Tor, but when bootstrapping I get an error that says "error starting transparent proxy". Am I revealing anything about myself when I'm browsing if I continue to use Tor (connected & green) in this manner?
Click to expand...
Click to collapse
It is possible that you may be fine in using the orweb browser since it is made for scenario that the transparent proxy cannot be set due to lack of root, but any other app will most likely not be going through tor. An simple (though not all encompassing) way to check this is to browse to google and type "ip address" with orbot running and with it not running and see if it shows a different address (it should be different when working properly).
sparkym3 said:
It is possible that you may be fine in using the orweb browser since it is made for scenario that the transparent proxy cannot be set due to lack of root, but any other app will most likely not be going through tor. An simple (though not all encompassing) way to check this is to browse to google and type "ip address" with orbot running and with it not running and see if it shows a different address (it should be different when working properly).
Click to expand...
Click to collapse
Perfect. Yea, I used Orweb to connect to Tor. I just wanted to make sure that I didn't leave anything out there. I did the IP check, and all was fine in that regard. As for use of apps, this is only if I open one up and use while on Tor, right? (As opposed to an app running in the background.)
I also recall reading something that indicated that Tor on Android was less secure than Tor on a PC, so that was a concern as well.
when I connect to a captive wifi, I want to use the connection as is (maybe I want to login without telling google - since the builtin authenticator uses their gstatic domain, or maybe I want to probe the network as it is being redirected, or maybe I just want firefox to manage my password to the portal, etc)
but after I select "use wifi as is" on the android webview builtin auth screen, android starts to route all and every traffic to my 3g/4g data connection instead, until I disable and re-enable wifi.
it will only ever redirect traffic to wifi after it successfully got the correct 204 from gstatic.com
is there anyway to work around this?
I am on android6, but I think I has always been like that.
gcbxda said:
when I connect to a captive wifi, I want to use the connection as is (maybe I want to login without telling google - since the builtin authenticator uses their gstatic domain, or maybe I want to probe the network as it is being redirected, or maybe I just want firefox to manage my password to the portal, etc)
but after I select "use wifi as is" on the android webview builtin auth screen, android starts to route all and every traffic to my 3g/4g data connection instead, until I disable and re-enable wifi.
it will only ever redirect traffic to wifi after it successfully got the correct 204 from gstatic.com
is there anyway to work around this?
I am on android6, but I think I has always been like that.
Click to expand...
Click to collapse
Do you have any kind of Linux ide? Have you tried making a tunnel?
Or is that what your looking for. I'm not 100% sure what your looking for. If your trying to skip Hotspot authentication? Or anything like that Then a tunnel would work fine.
Sorry I can't be of much else help
If your phone is rooted or has a custom ROM (Which would obviously indicate that the phone is rooted), there is a solution that you can try using a terminal (Or ADB shell).
Issue the command: "settings put global captive_portal_detection_enabled 0" That should prevent captive portal detection and gstatic confirmation. This should work, I haven't tried it personally though.
Additionally, you can setup a captive server.
Issue the command: "settings put global captive_portal_server g.cn"
Restart your phone, and you should have access to the pages.
Basically, connecting as is, requires you to reach a site that does not require 204 confirmation and afterward other sites should be accessible. Let me know if this helps.
Josh Ross said:
If your phone is rooted or has a custom ROM (Which would obviously indicate that the phone is rooted), there is a solution that you can try using a terminal (Or ADB shell).
Issue the command: "settings put global captive_portal_detection_enabled 0" That should prevent captive portal detection and gstatic confirmation. This should work, I haven't tried it personally though.
Additionally, you can setup a captive server.
Issue the command: "settings put global captive_portal_server g.cn"
Restart your phone, and you should have access to the pages.
Basically, connecting as is, requires you to reach a site that does not require 204 confirmation and afterward other sites should be accessible. Let me know if this helps.
Click to expand...
Click to collapse
no root on the phone (damn blackberry priv) and no control of the portal.
this is so infuriating. This is trivial, banal even, on any device i control. Feel like a kid on training wheels every time i touch my phone.