Hello,
I am currently running codefireX SR14. My provider is Petro-Canada Mobility. I am having issues when tethering through their "unlimited browsing service" Basically this service only allows http/SSL TCP traffic on ports 80/443.
Anyhow, I've been using autoproxy and this has allowed me greater functionality of most apps. Here lies the problem. When I attempt to tether (wifi hotspot or USB) Traffic is not being forwarded at all from the hotspot gateway. As a result, connected hosts cannot access the internet. After doing some initial troubleshooting, I have concluded the issue appears to be the OS itself.
Regardless of the situation, the hotspot gateway will not forward traffic with autoproxy connected, disconnected, or if I use my Junos VPN.
As a result I have 2 questions:
1)How does the Android tether operate?
2)Are there any "Backend" options I can access someone to force the gateway to forward traffic through autoproxy or my Junos VPN?
I have included the trouble shooting results below:
When tethered:
My PC IP = 192.168.43.83
gateway = 192.168.43.1
Ping to gateway is ok:
>ping 192.168.43.1
Pinging 192.168.43.1 with 32 bytes of data:
Reply from 192.168.43.1: bytes=32 time=23ms TTL=64
Reply from 192.168.43.1: bytes=32 time=2ms TTL=64
Reply from 192.168.43.1: bytes=32 time=1ms TTL=64
Reply from 192.168.43.1: bytes=32 time=1ms TTL=64
Ping statistics for 192.168.43.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
This means my PC can reach the gateway fine (with autoproxy on and off) With that in mind, I try to ping the Petro-Canada proxy server:
Proxy server IP = 10.128.1.69
Ping to Proxy server fails
>ping 10.128.1.69
Pinging 10.128.1.69 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 10.128.1.69:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
This happens regardless if autoproxy is connected or disconnected. What this means is that the gateway traffic on my phone is not being properly forwarded.
When I usb tether it's the same issue:
PC IP:192.168.42.142
Gateway:192.168.42.129
Ping to gateway is ok:
>ping 192.168.42.129
Pinging 192.168.42.129 with 32 bytes of data:
Reply from 192.168.42.129: bytes=32 time<1ms TTL=64
Reply from 192.168.42.129: bytes=32 time<1ms TTL=64
Reply from 192.168.42.129: bytes=32 time<1ms TTL=64
Reply from 192.168.42.129: bytes=32 time<1ms TTL=64
Ping statistics for 192.168.42.129:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
Ping to Proxy server fails
>ping 10.128.1.69
Pinging 10.128.1.69 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 10.128.1.69:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
This happens regardless if autoproxy is connected or disconnected. What this means is that the gateway traffic on my phone is not being properly forwarded.
At this point I believe the issue to be Android OS. I am running Jellybean 4.2.2, I also have Junos VPN installed, and I have full internet from my phone when connected (all ports tcp/udp) through Petro-Canada unlimited browsing. I still run into the same issue where trying to ping any outside IP results in a timeout. (i.e Google DNS 8.8.8.8)
I fixed the issue. I'm not sure if it's the ROM or my provider.
Related
Hi guys, wonder if someone can help.
My Orbit is having problems connecting to my home internet over wifi... it will connect ok, and sometimes load pages, but then will stop and not find any pages....
My home PC setup is I am sharing my internet connection over a wireless card in my home pc. I am able to connect to this with my laptop no problems at all and as I said, have managed to connect with the Orbit and load a couple of pages in the past but not for long....
After advice, I have used task manager to ping google and got the following:
"Pinging 64.233.183.104 with 32 bytes of data
Reply [1] from: 64.233.183.104 bytes=32 time=84 ms TTL=240
Request Timed Out
Reply [3] from: 64.233.183.104 bytes=32 time=107 ms TTL=240
Reply [4] from: 64.233.183.104 bytes=32 time=32 ms TTL=240
Reply [5] from: 64.233.183.104 bytes=32 time=29 ms TTL=240"
Did it again and got:
""Pinging 64.233.183.104 with 32 bytes of data
Reply [1] from: 64.233.183.104 bytes=32 time=84 ms TTL=240
Request Timed Out
Request Timed Out
Request Timed Out
Request Timed Out
Request Timed Out"
Does anyone know what the problem could be and what I could do to fix?
Cheers
I have the same problem, just looking at alternate roms now as mines starting to get a bit slow recently, as far as i know this has been an issue the entire time using the offical o2 wm6 rom, only had wm5 for a few days and can't remember if it did it there for me it drives me nuts the wifi thing!
You could try to set your routers speed to 11 Mbit/s instead to 54 Mbit/s or auto. I had a problem with a laptop's backup software that crashed because the router was set to auto and changed the speed all the time as routers usually do when the connectivity changes. I think when the router changes the speed from 54 Mbit/s to anything slower the wireless connection gets disconnected for a very short time. It could cause that problem.
Go to comm manager->settings->wireless lan-> Power Mode-> make best performance.
It helped for me.
and the same for me..... I've used several WM5 and WM6 ROMS and on every one, I have had to change the power settings for the WLAN from "middle of the road" to "best performance" for the internet to keep working.
It would always connect and get the first page, but would then "time out" if I didn't keey using it and then wouldn't load anything else.
Hi!
First: I do not know wether General discussion - Networking would be a better place, so if an admin thinks so, please move this thread.
my problem: after some hours, offen after night, my wlan does not work properly:
my config:
2 WLAN-routers Syslink WRT54G with DD-WRT v24-sp2 with identical config (SSID and so on - but of course different channels):
two virtual WLANs on each
1) WPA(2) Enterprise with username/pass or user certificate
radius server
for individual users
2) WPA(2) PSK for wlan radios and so on
my Desire uses 1) (tried both: username and certificate, same result)
my Desire:
various radios, now 5.10.05.23
LeeDroid V2.0a Froyo
my problem:
after some hours in the Wi-Fi config I got:
Wi-Fi: Authenticating with MY_SSID...
and this messages does not change.
This has interesting effects to my Desire:
there is still the wlan symbol in status bar, no G3 (mobile network setting is on) so my Desire seems to know, that wlan is working
htc weather app - refresh - "Unable to connect You need a network connection to use this application. Please turn on mobile network or Wi-Fi"
standard internet browser - internet works fine
http://mobil.tagesschau.de Streaming of Tagesschau in 100 Sekunden
popup "Movies or Streaming Media Player" - Movies = all works, Streaming = "Connection failes This application requieres network access ..."
Astrid snyc - works
maps - works
K-9 - new mails are received after manual "check mail" but not pushed via IMAP idle
via *#*#4636#*#*
Wifi Config
* ID 5 SSID: "MY_SSID" BSSID: null
PRIO: 67
KeyMgmt: WPA_EAP IEEE8021X Protocols: WPA RSN
AuthAlgorithms:
PairwaiseCiphers: TKIP CCMP
GroupCiphers: WEP40 WEP104 TKIP CCMP
PSK:
eapEAP
phase2: auth=MSCHAPV2
identity: My User Name
anonymous_identity:
password: xxxxxx
client_cert:
private_key:
ca_cert:
Wifi Status
Wifi State: enabled
Network State: Authenticating with MY_SSID
Supplicant State: COMPLETED
RSSI: -61
BSSID: 00:14:xxxx
SSID: MY_SSID
Hidden SSID: false
IPaddr: 192.168.1.15
MAC addr: 38:xxxx
Network ID: 5
Link Speed: 54 Mbps
Scan results:
run ping test:
ping IpAddr: pass
ping Hostname (www.google.com): pass
HTTP Client test: pass
even if there is an "authentication ..." message
my radius server log shows me no authentication process, no working and no failing one.
so, now I have to options:
wifi off/on or
going to the second wlan ap, so my Desire switches to it because this is then the stronger wifi
signal
in wifi setting now: Connecting MY_SSID, scan, Connecting, Connected with MY_SSID
after this K-9 get immediately new mails pushed via imap idle, weather updating works, streaming is fine ... and my radius server log shows me an authentication process
(I swaped both routers but no effect for my problem.)
changes in *#*#4636#*#*
Wifi State: enabled
Network State: Connected to MY_SSID
RSSI: -64
Any idea for this strange phenomenon? It is very annoying!
nobody here who uses WPA enterprise / wpa with radius?
Hi
were you able to ever fix this problem. I am currently having the same issue
thanks
there is an issue in google's android bugtracker, with many concerned users, but no help by google.
http://code.google.com/p/android/issues/detail?id=12125
Hi Folks
Does anyone know if there is a ROM that fixes this issue, or if there is a fix anywhere. We have a number of Desires in the office which all suffer this issue when connected to our Cisco based WiFi network (WPA Enterprise). We have managed to get IT to extend the re-auth period to 1hr, but they will go no further. Current work around is to take a walk to the other side of the office and force a re-associate to a new AP (or dis/enable wifi on the phone). Not ideal.
Thanks
there is still no fix to this, but I found a working solution:
Fix My Wifi
https://market.android.com/details?...wsMSwxLDEsImNvLnVrLnN5c2x5bnguZml4bXl3aWZpIl0.
https://market.android.com/details?...xLDEsImNvLnVrLnN5c2x5bnguZml4bXl3aWZpZGVtbyJd
HTH
Not much more I can add... Is anyone aware of this issue? When I connect the phone, all connections to the router time out completely. Here's a sample ping to my ISP:
Code:
Pinging netvigator.com [218.102.48.43] with 32 bytes of data:
Reply from 218.102.48.43: bytes=32 time=20ms TTL=250
Reply from 218.102.48.43: bytes=32 time=23ms TTL=250
Reply from 218.102.48.43: bytes=32 time=31ms TTL=250
Reply from 218.102.48.43: bytes=32 time=53ms TTL=250
Now with the N4 connected to Wifi:
Code:
Pinging netvigator.com [218.102.48.43] with 32 bytes of data:
Reply from 218.102.48.43: bytes=32 time=1537ms TTL=250
Reply from 218.102.48.43: bytes=32 time=396ms TTL=250
Request timed out.
Reply from 218.102.48.43: bytes=32 time=481ms TTL=250
If this is a known issue, please let me know if there's a solution. This is bone stock, straight out of the box, with 4.2.2 installed.
I had a dlink dir-615 that didn't like android phones or tablets for some reason it would lock up whenever the device would go to sleep. Running netgear right now and few problems at the moment. The netgear does have some software glitches though.
Sent from my Galaxy Nexus using xda app-developers app
My father's wireless router would always die (no more internet for anyone) when I connected to it. He since bought a new one and it no longer dies when I visit. I have a D-link DIR601 and it works just fine with any device I've ever connected to it.
I have read articles about other smartphones and tablets killing wireless routers too.
Question for the forum: why am I seeing a bunch of DNS requests sent by the AFTV to various DNS services which are NOT the ones served by my router?
I have it set up with a staically assigned DHCP address, the DNS served is my router, therefore the concern about DNS queries sent to OTHER servers?
UDP 192.168.x.y 36814 208.78.70.16 53 Service 1 374 718
UDP 192.168.x.y 36814 208.78.70.4 53 Service 1 201 498
where 192.168.x.y is the IP of AFTV and there is bi-directional traffic (ie it gets a reply).
I also found other servers (don't have the snapshot but they were amazon.com, ultradns, etc). WTH is going on?
Is this related to me forcing the DNSmasq config to resolve the amazon update addresses to 127.0.0.1? Is the device now trying to resolve it bypassing the local DNS????
EDIT: I got pi$$ed and activated "DNS intercept" in DNSmasq config...let's see what doesn't work now that all those packets are captured.
OK ...and the plot thickens:
Proto Source S Port Destination D Port Class Rule Bytes Out Bytes In
UDP 192.168.x.y 36814 205.251.193.249 53 Unclassified 131 549
UDP 192.168.x.y 36814 204.13.250.16 53 Unclassified 423 1438
UDP 192.168.x.y 36814 208.78.70.16 53 Unclassified 509 1866
UDP 192.168.x.y 36814 208.78.71.16 53 Unclassified 382 1364
UDP 192.168.x.y 36814 204.74.108.1 53 Unclassified 309 1190
UDP 192.168.x.y 36814 195.154.191.225 53 Unclassified 189 424
UDP 192.168.x.y 36814 156.154.103.3 53 Unclassified 138 516
UDP 192.168.x.y 36814 204.74.115.1 53 Unclassified 186 768
Holly smokes...looks like I'm the only one that cares. Good - don't be surprised if one day you wake up with your AFTV updated to a non-rootable ROM.
Ipse_Tase said:
Holly smokes...looks like I'm the only one that cares. Good - don't be surprised if one day you wake up with your AFTV updated to a non-rootable ROM.
Click to expand...
Click to collapse
That is not going to happen with CWM custom recovery installed & with OTA updates disabled after root.
I just discovered that my lineageOS (starlte) is doing a connection to amazonaws every time I'm using GPS (doesn't matter which app). The used port indicates that its a SUPL connect for assisted GPS (which I deactivated) . But I didn't found a configuration file like gps.conf to change that. Probem is: Those SUPL requests are known to reveal IMEI and location.
Code:
starlte:/ # tcpdump -i any -s0 port 7275
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on any, link-type LINUX_SLL (Linux cooked), capture size 262144 bytes
12:01:27.77129 IP 192.168.179.29.33724 > ec2-52-34-211-161.us-west-2.compute.amazonaws.com.7275: Flags [S], seq 2728158607, win 65535, options [mss 1460,sackOK,TS val 4294942063 ecr 0,nop,wscale 6], length 0
15:06:27.777399 IP ec2-52-34-211-161.us-west-2.compute.amazonaws.com.7275 > 192.168.179.29.33724: Flags [R.], seq 0, ack 2728158608, win 0, length 0
Hi,
You should sniff the packet that are sent/received through these connections, both to know what information is leaking and to know of who are these servers.
you could setup a bridge connection on a PC , Fiddler should be the software for you. Or wireshark if you are more advanced.
I've also seen this on multiple of my past devices