Related
I'm having trouble getting wifi tether to work with 4G. It was working fine yesterday, and nothing has changed between when I last used it and now. The weird part is, when connected to 4G and tethered I can go to any Google site, but nothing else will load. When I'm connected to 3G everything works. I thought maybe it was that wifi tether is set to use Google's DNS and perhaps Google was having issues, but why would they work for 3G and not 4G. Do you think Sprint/Clearwire is blocking Google's DNS in an effort to curb unpayed tethering on 4G? Any other ideas?
Edit: I've tried a few different free DNS services and the same thing happens with all of them. No connection issues on 3G, but ONLY Google pages will load via 4G, regardless of which DNS service I'm using. This is a very strange problem....The only two things I can think of is Spring/Clearwire blocking DNS services or there's some sort of bug on the 4G network at the moment.
I'm seeing the same issue, and I did the same troubleshooting steps. It's almost as if they are inspecting http headers and checking the MAC against some database. Hopefully something is just broke on Sprint's side, though.
Co-signing. 3G wireless tether works while 4G doesn't.
Same Problem in NYC
Hey Guys, glad I found this post. Thought I was going crazy. Everything is fine on 3G but only google sites and certain non picture portions of other websites will load on 4G.
Strange thing is that all websites are fine on the phone itself while on 4G.
Heard someone that's using the paid sprint hotspot is having the same issue, so I'll keep my fingers crossed that this is a temporary issue.
rpav2004 said:
I'm seeing the same issue, and I did the same troubleshooting steps. It's almost as if they are inspecting http headers and checking the MAC against some database. Hopefully something is just broke on Sprint's side, though.
Click to expand...
Click to collapse
What? You do realize that the only MAC Sprint ever sees is that of the phone, right? As for inspecting headers, not only would that be trivial to get around, but it would also be likely to cause breakage in third-party browsers as the whitelist would likely not be complete. Reliable browser detection via HTTP is near impossible. That also would have no effect on non-HTTP traffic, IMAP e-mail or an XMPP instant message connection for example.
wolrah said:
What? You do realize that the only MAC Sprint ever sees is that of the phone, right? As for inspecting headers, not only would that be trivial to get around, but it would also be likely to cause breakage in third-party browsers as the whitelist would likely not be complete. Reliable browser detection via HTTP is near impossible. That also would have no effect on non-HTTP traffic, IMAP e-mail or an XMPP instant message connection for example.
Click to expand...
Click to collapse
I believe there is an individual MAC for every radio in the phone, so you would have a unique MAC for your cell radio, wimax radio, bluetooth radio, etc. Also, I don't believe he's referring to the browser's identity info, but the packet headers that contain DNS/tcp/etc. info that all network services use. That would have an effect on ALL traffic, and it clearly does as nothing works expcept most google services.
I have been usb tethering with CM7 since GB6 and it would switch back and forth between 3G and 4G without any problems. Pre GB roms would require google tether which would only work on 4G.
I am now experiencing the same dead 4G tether and am not droping back to 3G since the 4G signal is good. Yep like everybody else the phone by itself is connecting and browsing.
All tether traceroutes and pings seemed reasonable. Flashed back to an earlier working release and it also failed. I have not tried any port other than 80 at this time.
marcog42 said:
Heard someone that's using the paid sprint hotspot is having the same issue, so I'll keep my fingers crossed that this is a temporary issue.
Click to expand...
Click to collapse
I just added the Sprint HotSpot to my account and I can confirm that it's working flawlessly with 4G. Even with the HotSpot feature on the account, wireless tether will not work.
Imap works, SMTP works, ftp works, ftp via browser (port??) or any other browser activities do not work while tethering on 4G.
Port 80 and/or tethering via browser is hosed.
What wifitether version is everyone using? I'm using 2.0.5
Well, I got home connected to 4G and tethered to my laptop. Everything worked. Might be dependant on what tower you're connected to. I'm using wifi tether 3.0 pre11, but had the issue with 2.0.7.
marcog42 said:
Well, I got home connected to 4G and tethered to my laptop. Everything worked. Might be dependant on what tower you're connected to. I'm using wifi tether 3.0 pre11, but had the issue with 2.0.7.
Click to expand...
Click to collapse
I believe you're correct. I downloaded 3.0 pre11 and still nothing. Strangely enough it would allow streaming of an Amazon video on the browser but it worked on 2.0.5 as well. I wonder what clearwire is doing on their end. Does anybody have any ideas on circumventing it?
wolrah said:
What? You do realize that the only MAC Sprint ever sees is that of the phone, right? As for inspecting headers, not only would that be trivial to get around, but it would also be likely to cause breakage in third-party browsers as the whitelist would likely not be complete. Reliable browser detection via HTTP is near impossible. That also would have no effect on non-HTTP traffic, IMAP e-mail or an XMPP instant message connection for example.
Click to expand...
Click to collapse
I didn't go into much detail since I was posting from my phone, but allow me to expound now. Wifi-tether does nothing more than NAT your internal network to it's live IP address, whether that be on 4G or 3G. Both of these radios have the physical addresses that would not be hard to trace on a cellular network. When the packets are transmitted, as is the case with any packet transmission, the only information that gets changed as the packet passes through the NAT is the IP address. All of the other information stays the same. Now, in terms of most traffic, this isn't a big deal, but with HTTP and HTTPS traffic, the stream of data sent contains the header of the browser sending the request. Since the NAT doesn't mask this data, it's sent out into the wild blue yonder (Sprint's Clearwire WAN) where the capability of inspecting the packet header is very easy to do with most enterprise grade equipment. Now, while any blacklist of headers will inevitably be incomplete, a very simple whitelist of 'known' headers - such as mobile browsers on the market and the included browser on the phone - can be implemented with a few short lines of code. Now, while it might seem trivial, how many users are going to attempt to obfuscate or change their packet header identifiers just to get online? They'll give up, use another connection, or just view the pages on the phone.
I tested this for awhile today, using multiple different browsers on my PC and got nothing. I opened up a VPN connection to my workplace, and routed all my traffic through that (that is, encrypted in an IPSEC tunnel) and the internet worked fine. The most brilliant part, from Sprints point of view, is that the HTTP session is never actually 'closed', just kept in a perpetual waiting state where no data is transmitted. If this is all a fluke, it's the best bandwidth saving fluke Sprint could ever dream up.
All in all, I'm really really hoping this is a snafu, but all signs are pointing to sprint catching onto our usage, which is a huge uh-oh.
edit: I was still able to ssh and telnet via my tether, and open up the VPN and receive email, which points to this being a targeted attack on HTTP. Double uh-oh.
Firefox, IE, Opera, Epithany, Chromium, Midori and Konqueror all fail.
Port 80 traceroute is good.
Does anybody knnow of an agent switcher that can be used?
What about downloading Adfree and installing the host files. That fixed my data issues on my Evo.
Sent from my PC36100 using XDA App
This appears to be a new sprint development. Are you saying that you can tether with 4G?
Aha... finally found some people who are having the same issues, 4g just stopped working with wireless tether about 3 days ago. 3g works just fine, and 4g connects and is pushing data to the phone, but no webpages are loading on my laptop when 4g is on... I'm out of 4g range right now, but will check back in when I'm back in range tomorrow.
It's working for me again. I'm replying to this thread using my wifitether uder 4G.
Working again here too.
I'm experiencing a very odd issue with my Galaxy S3 on the Virgin Network. For some reason I can't go on any SSL enabled site no matter what browser I use and which website I go to. The most descriptive error message comes from firefox which says SSL received a record which exceeded the maximum permissible length. Oddly if I enable wifi or otherwise bypass the regular network (VPN etc.) everything works properly. SSL enabled apps like banking sites work with no issue.
I'm currently on the latest nightly of the Carbon Rom, though I've experienced it when I was on Cyanogenmod as well so I don't believe that it has anything to do with the rom itself. Any idea on what might be going on?
Ensure your APN settings are correct.
valunthar said:
I'm experiencing a very odd issue with my Galaxy S3 on the Virgin Network. For some reason I can't go on any SSL enabled site no matter what browser I use and which website I go to. The most descriptive error message comes from firefox which says SSL received a record which exceeded the maximum permissible length. Oddly if I enable wifi or otherwise bypass the regular network (VPN etc.) everything works properly. SSL enabled apps like banking sites work with no issue.
I'm currently on the latest nightly of the Carbon Rom, though I've experienced it when I was on Cyanogenmod as well so I don't believe that it has anything to do with the rom itself. Any idea on what might be going on?
Click to expand...
Click to collapse
Is your time and date set to automatic?
My APN settings are correct and my time and date are set to automatic.
After doing some more testing only certain SSL sites don't work which makes the whole situation even more murky. startpage.com doesn't work, but the login of tdcanadatrust does. This is really weird.
Are you in a public WiFi network or in an area with a lot of WiFi networks?
If in public WiFi: Someone may be trying to hack you by SSL strip or redirect you.( Which can be why a VPN works)
If there are many WiFi networks in range : Download WiFi Analyzer from Google play to check WiFi channels, and switch your WiFi router to a cleaner channel if needed.
(If there are a lot of WiFi networks all on the same "channel", it can cause common data loss,lag and congestion. )
Sometimes a VPN can fix the problems with congested wifi channels, but I'm not sure.
If none of these ideas apply, clear cookies and cache.
If that still doesn't work:
Settings > Security > Clear Stored Credentials.
This will clear your SLL certificates and VPN info saved on your device. It might help with your browser.
While the SSL strip idea is a valid point that I hadn't considered initially I don't think that's the issue because I rarely connect to unknown wifi networks when traveling, and I think that all certificates would come back invalid if somoene was pulling that instead of the hit and miss situation I'm currently experiencing.
The Wifi bit is what really gets me though since the sites that don't work on the cell network work perfectly when I'm on wifi with no other changes needed other than the change in the way the phone connects. I have tried clearing the browser's cache with no luck and I'm not able to clear the stored credentials as described as the option is greyed out for me.
I thought that it might have something to do with the cerficates themselves, something about the way the browser/phone accepts certs depending on connection method but I can't see any difference between working sites and non working sites other than a difference in certifying authority (GoDaddy vs Verisign for example)
Problem Solved
I'm bumping up this thread to bring attention to the fact that I've found the solution to the problem. The issue is not with the rom itself, but the proxy that Bell/Virgin insists on its users using. Clearing the proxy and port settings for the Bell APN found under mobile device settings fixes the issue nicely. Special thanks to Dream_Team over at this thread for finding the solution.
Makes me wonder why there's an HTTP only (port 80) proxy set by default in the APN settings when it's not needed to access the network..
I recently moved and got new internet service and ever since I've been having issues with the Wi-Fi on my phone. I have 300 mpbs internet service and so I expect my phone to scream through updates in seconds... But ever since the move apps like play store and google drive are slow as hell. So after trying everything I could find online I figure I'll ask for help.
I've narrowed the problem to IPv6 issues. At my old place I had Ipv6 working so I never had any issues. But now when I go to test my Ipv6 It's not working. I'm renting a modem/router from my isp. I know buying my equipment would probably be the easiest fix but that's not an option right now.
There is an option in the router configuration to disable dhcpv6 but that's not solving the issue. The test says I have an Ipv6 address but the dns does not resolve. I found an app on playstore called Ipv6 tool that disables it and my phones works after doing that but I'd love to figure out how to just get my Ipv6 to work. I'm going to exchange the router today to see if it's just the equipment. If anyone knows how to remedy my issue I'm all ears. If anyone is having issues like mine Ipv6 tool is a great temporary fix.
EDIT- SOLVED---- It was a network issue. In my router configuration I had to disable dhcpv6 and then after that renew WAN lease.
I noticed WiFi issues the other day and then noticed my sky box had updated and had lots of ipv6 settings. So I assumed it was to do with that.
I think it can be disabled but haven't looked into yet. But my device sometimes flies through some tasks but then grinds to a halt on others.
Glad I'm not the only one
The Ipv6 tool pro works pretty good after you do some configuring. But I'm leaning towards its a network configuration issue not necessarily an issue with our phones..
You can just disable Ipv6 by entering “echo 1 > /proc/sys/net/ipv6/conf/wlan0/disable_ipv6" according to these guys. But I saw the app before I learned of the command.
I'm back to updating 30+ apps in less than 10 minutes. I was getting mad because it was taking about two hours to do this. And being a flashaholic that seriously cuts into my flashing..lol
EDIT- SOLVED---- It was a network issue. In my router configuration I had to disable dhcpv6 and then after that renew WAN lease.
Any of you guys having the same issue? Mine started acting up earlier today, LTE works completely fine but can't seem to get WiFi to work at home. WiFi connects just fine, does not show there's no internet or anything. Works for the first 15 seconds I toggle on and off but then nothing afterwards. I have tinkered around with my router settings, including switching to IPv4 as well as activating the option to randomize MAC address on my phone under developer options but to no avail.
Please advise, thanks in advance!
If you are doing that much tinkering then I bet you have done way more tinkering than you have explained.
More than its worth actually unwinding.
If your phone works on all other wifi but yours it is probably your router
If your router works for all devices but your phone your router is fine.
Factory reset your phone.
Dont install try to use it fresh from install if it works then your fine.
Just watch what you tinker with.
If it works it is something you did after the fact.
I've had exactly the same thing start happening to me today. No problems with data over wifi before today, and I haven't made any changes on the router.
All other devices seem to be unaffected when connected to that router, and the phone has the issue whether it's connected to that router or a separate access point (connected back to the same router, so it doesn't completely rule out a router problem.
Edit: It seems that when the problem starts it's only internet traffic that's not getting through - I can still access servers on the local network.
kevinwilson said:
.
Edit: It seems that when the problem starts it's only internet traffic that's not getting through - I can still access servers on the local network.
Click to expand...
Click to collapse
That sounds like a DNS problem, are you using anything that changes dns servers?
Nergal di Cuthah said:
That sounds like a DNS problem, are you using anything that changes dns servers?
Click to expand...
Click to collapse
It does seem to suggest a DNS problem. I just have Pie's "Private DNS" setting set to Automatic, but I would assume that applies to LTE networks as well as wifi, whereas LTE data is unaffected for me.
As a test, I've set Private DNS to Off now, and I'll see if that solves it.
kevinwilson said:
It does seem to suggest a DNS problem. I just have Pie's "Private DNS" setting set to Automatic, but I would assume that applies to LTE networks as well as wifi, whereas LTE data is unaffected for me.
As a test, I've set Private DNS to Off now, and I'll see if that solves it.
Click to expand...
Click to collapse
"Android then sends all DNS queries over a secure channel to this server or marks the network as "No internet access" if it can't reach the server" sounds a bit like what you're experiencing
Source: https://android-developers.googleblog.com/2018/04/dns-over-tls-support-in-android-p.html?m=1
Nergal di Cuthah said:
"Android then sends all DNS queries over a secure channel to this server or marks the network as "No internet access" if it can't reach the server" sounds a bit like what you're experiencing
Source: https://android-developers.googleblog.com/2018/04/dns-over-tls-support-in-android-p.html?m=1
Click to expand...
Click to collapse
That's interesting. Setting Private DNS to Off has so far fixed the problem for me. I'm guessing that my mobile network's DNS servers don't support DNS over TLS, which is why LTE wasn't affected with it set to Automatic, and my wifi's DNS provider does support it but is currently broken.
Nergal di Cuthah said:
"Android then sends all DNS queries over a secure channel to this server or marks the network as "No internet access" if it can't reach the server" sounds a bit like what you're experiencing
Source: https://android-developers.googleblog.com/2018/04/dns-over-tls-support-in-android-p.html?m=1
Click to expand...
Click to collapse
I believe that's the case, I turned off Private DNS and it seems to be working fine now.
Thanks a lot guys! Very interesting.
I'm here with this issue now, I'll turn off private DNS and give it a try, this is driving me mad. thanks everyone!
Edit: been using the device for 30 minutes now with no problems, thanks for the solution!
I'm using a local DNS server (Pi-hole) to block ads and I had to turn off Private DNS, otherwise my phone was also reporting that it had no Internet access.
Private DNS seems to cause issues to many people
Never mind i'm foolish.
Holy crap, thank you guys. This just started happening to me and my wife a few days ago and thought my router was going bad since it was multiple devices. Then I noticed today that my laptop and a few other wireless devices were having absolutely no problems.
On mine it's being caused by the Snapchat update from a few days ago. Avoid Snapchat and WiFi is flawless again, as soon as I open it the WiFi stops working and I have to turn WiFi on and off before it springs to life again. Exactly the same on my eldest's 2xl and youngest's P10 lite.
Anybody noticed the servers being down in Europe? Cannot check for Android updates on any Samsung device.
It seemingly works, checks and says software up to date
What country you in?
Yes. It happened today. Now it's good.
My Samsung devices are still not able to reach update servers.
Try with wifi off, just data on.
lol. it works on 4g. What is going on?
big_ipaq said:
lol. it works on 4g. What is going on?
Click to expand...
Click to collapse
thats normally down to a network node being down, basically every ISP links to sites through a bunch of servers and all of them use different routes, if your home broadband provider is trying to route through a failing/overloaded/faulty server it will show errors on a bunch of sites that connect via that server. EE had it a while back with an Amazon server centre it took out loads of sites but using a Proxy or different provider you could access the sites as your routed round the problem server EE was using.
it's the same reason some ISP's will see a site as down while others will see it as fine, best way to check is if you can try with a different service provider normally achieved by swapping from mobile to wifi data unless your phone and wifi are from the same provider then chances are both will have the same problem.
Got it, makes sense. I don't get any other errors tho but through my ISP is still not working. This is the reason I did not even think about that. I was expecting that a network node down would bring lots more errors, but in fact just Samsung Android does not update. Everything else (and I am a very intensive internet user with lots of services active and lots of devices around) works.
Re Samsung update server down
Same issue in Australia..
Same problem in Croatia