I've got an unlocked AT&T Nexus 6 running on Verizon. My plan includes tethering. The phone is running stock, so I can get OTAs.
I can enable tethering, and it starts after the provisioning check. I can connect my computer via wifi successfully, however DNS doesn't work, so nothing loads. If I manually change the dns settings on my computer to 8.8.8.8 or some other public DNS everything works fine.
I've googled a bit, and found some bug reports here and there for other lollipop devices having the same issue, but I've been unable to find a resolution other than manual DNS settings on every device.
Is anyone aware of a fix for this? I'd expect google to jump on this before too long.
Nevermind, it seems to be working fine now. I'm not sure what caused the problem for me.
Related
since updateing to FRF83, wifi tether seems to have been slowed down.
has this been done to keep american networks happy?
Can anyone else verify this? I'll check when I get home... but that would suck.
I just tested it. I can not confirm this issue. My tether speeds are as fast as they always are.
No issues at all here, worked great!
Same here, my WiFi tether speeds are right in line with my N1's 3G speed tests.
well my tether is working but my hotspot is not... >: l
Everything is happy happy joy joy on my end
WiFi Tethering not Changed
No changes have been made to the WiFi tether however your speeds can be hindered by network traffic and a number of other issues. Even a microwave oven near by will interfere with speeds or something as simple as an application checking for updates in the background on your computer.
Best thing, try again at another time or location. It helps to test often to get an idea of the fastest speeds you may see, when and where you got the best results.
I had this problem as well. Here's what I did that fixed it:
Change the security to Open. After that, try to connect to your phone. If you're able to connect, change back to WPA and it should work.
I noticed that the password I set before the update had quotes around it, so I wonder if that was the problem...
I've got an AT&T n1 and I am using it with Vodacom in Tanzania. I'm now running frf83 and internet on my phone works but I am unable to tether. The computer can see the hotspot and connect, but there are DNS problems. My tech friend helped me but he was unable to make it work and concluded that he could ping the internet fine but DNS wouldn't work, not even open DNS. I dunno, anyone have this problem or know a fix? I would be grateful.
crazedwowo said:
I had this problem as well. Here's what I did that fixed it:
Change the security to Open. After that, try to connect to your phone. If you're able to connect, change back to WPA and it should work.
I noticed that the password I set before the update had quotes around it, so I wonder if that was the problem...
Click to expand...
Click to collapse
I'm using open and it still doesn't work but thanks for your help.
Im stock and on tmobile and its working great for me, hooked my buddy's iphone just now to test it
It does not work with me . i tried on FRF50 work fine but on FRF83 no wifi at all
Does not work for me ether
I even factory reset my phone but wifi tether doesn't work, something to do with DNS.
Hello, I'm new here on XDA, even though I've been browsing the forums ever since whenever.
Anyway, I have a T-Mobile Note 4 running CM12 and I also must say that I do have unlimited data.
The problem that's been bugging me is this: when I was tethering on stock ROM, I could not ping any host from any of my tethered clients. However, pinging used to work on CM12 (indicating of course that stock ROM has restrictions imposed) until two days ago. I know this because when I tether to my PS3/XBox One, I can access the Internet but cannot login to PSN (Playstation Network). I can only log on to it when ping is working.
I do have an HTTP user agent spoofer for HTTP traffic but this problem seems to be more related with routing on the Note 4 I guess. I have tried many tethering apps (with or without root) in hopes that they would fix this problem but I still cannot ping.
I have seen on the Internet people mentioning native tethering and I was wondering if you guys can recommend any tethering apps that can fix this. Also, I'm not really familiar with the linux iptables and the routing utility and have been trying all these scripts I found on here but they are not working.
So, correct me if what I'm asking for is already done (which would then mean T-Mobile is blocking my outbound traffic on their routers), but what I was thinking was to route the wlan0 traffic straight through rmnet_data0 without any tethering flagging or something like that. Again, I do have internet I just can't access other services like ping which is needed by some programs that I have for MTU path discovery etc.
FoxFi/PdaNet - Not working
Wi-Fi Tether Router - Not working
Other generic tethering apps on PlayStore - Not Working
Thanks in advance.
SM-N910T3. Maximum OvrDriVE MM v1.2 (Android 6.0.1, N910TUVU2EP3)
Since this ROM was flashed on my phone, I've always used the "built in" T-Mobile hotspot app. I'm on the 10GB family share. I am not over my data cap. No unlimited tether mods, or anything like that. Just rooted with OvrDriVE rom. Nothing has changed since it was flashed in August 2016.
I use tether maybe once or twice a month in emergency situations.
Tried to connect to my work laptop, and the PC (Win 10 Dell Tablet) does see the hotspot, connects just fine, gets a DHCP assigned IP address but "no internet." If I try to ping google.com I get an immediate error. So did the normal windows stuff, restart the computer, flush DNS cache, etc. IPV6 disabled and re-enabled. No change. "Forgot" the network in WIndows, thinking something about the encryption has changed, or something. No dice. So I tried my personal laptop. Same thing. Connects, gets IP, no internet what so ever. I thought maybe it's an issue with T-Mobile's DNS servers, so I leave the device IP DHCP, but change DNS server to google's 8.8.8.8 & 8.8.4.4. Still nothing. Tried a computer that has never connected to the hotspot before. Same thing. Gets an internal IP address, but cannot connect to the internet.
Only thing I've done is wipe dalvik/cache but that did nothing. I don't have a recent backup to restore to. I haven't found the hotspot app in Application Manager, as I want to wipe data/cache for that specific app and see if that helps.
Anybody have any ideas? Or what I can do to get more information about where it is failing?
EDIT: Thought maybe i was a T-Mobile network error. When starting the hotspot, I get the popup saying "verifying you account information" and do not get any errors. It has not been working for about 4 days now so I'd think it it was an internal T-Mobile issue it'd be resolved by now, or I'd see posts from others saying it wasn't working.
So this evening I downloaded the ol' tried and true "WiFi Tether Router" and configured it per the apps' recommendations for the Note 4. That doesn't work at all, can never see the SSID of the hotspot on any computer.
try to switch your frequency of your hotspot from 4 or 5. something to 2.4 im pretty sure under hotspot settings that is my only guess.
No effect. This is just the AP mode, whether 2.4GHz or 5GHZ. As I stated the PC connects to the phone fine, gets an IP address. Something with the routing or DNS is failing. I think it goes beyond DNS as typing in a URL's IP address also doesn't work.
Nokia 7plus India version. Not rooted. Have been encountering issues with certain apps over WiFi as the app doesn't load data on wifi just keeps attempting to load content. Twitter, Amazon, Instagram, yahoomail, all have issues. All of these apps work perfect on mobile data. But apps like whatsapp, kaspersk,flipkart, you tube, all browsers work well with WiFi as well as mobile data. So nothing wrong with WiFi as such. MAY month update from Nokia had this corrected, but June update brought the issue back. Currently on August security patch, continue to have the same problem . Anyone else facing same issue? Any fixes? Saw some comments in net from users encountering same problem
Unfortunately i'm tired of this problem as well
I am also facing the said issue in twitter and plx app when connected to wi-fi
Looks like it's common issue across Nokia devices. Shocking.
'Search WiFi issues with Nokia' on Google. So many people facing the issue and Nokia hasn't fixed it yet.
I am having the same issue on Android Pie beta. I tried the following to resolve the issue but it still persists!
1. Hard Reset my phone through recovery.
2. Hard and Soft Reset my Wifi Router.
3. Updated Wifi router firmware.
4. Reinstalled all the apps which were not working on Wifi.
5. Cleared Cache and Storage of these apps.
6. Changed Wifi router settings to IPV4 instead of IPV6.
7. Reverted back to Oreo 8.1 (updated upto July Security Patch)
8. Checked if these apps work on other phones on the same Wifi settings and found that it works perfectly!
None of these helped. In the end I have to shift to mobile data to check out these apps and its annoying!
Any other suggestions other than the ones i have tried above?
Learn going back to April security patch solves it. By the way how did u go back to June security patch?
xanderzonereloaded said:
Learn going back to April security patch solves it. By the way how did u go back to June security patch?
Click to expand...
Click to collapse
I did when I reverted back to Oreo 8.1. After that I got 2 OTAs consecutively before I could even setup the phone upto June Security Patch. And then updated to July the next day. But the issue persists after the various updates.
xanderzonereloaded said:
Nokia 7plus India version. Not rooted. Have been encountering issues with certain apps over WiFi as the app doesn't load data on wifi just keeps attempting to load content. Twitter, Amazon, Instagram, yahoomail, all have issues. All of these apps work perfect on mobile data. But apps like whatsapp, kaspersk,flipkart, you tube, all browsers work well with WiFi as well as mobile data. So nothing wrong with WiFi as such. MAY month update from Nokia had this corrected, but June update brought the issue back. Currently on August security patch, continue to have the same problem . Anyone else facing same issue? Any fixes? Saw some comments in net from users encountering same problem
Click to expand...
Click to collapse
After a lot of research into trying to understand the issues that I was seeing, I finally figured out that this was a IPv6 related issue. As it happens, in my case, it turned out that my router was causing the issue and not the phone itself. Please note that you may be seeing either the same issue or you may have completely different issue, but I hope the description below will give you some clues and directions that you may want to investigate.
The primary issue was that my router was returning a bad IPv6 address whenever a device connected over WiFi. I figured this out by running network diagnostics using the Netalyzr app from the Play store. When connected thru WiFi, this app reported a bad IPv6 address, but when connected thru a 4G LTE connection, it didn't report that as a problem. As a secondary check, I also used the IPv6 status widget to verify the network status when connect thru either of the connections. Again, this clearly showed that my phone was only on IPv4 when connected via WiFi, but was on IPv6 when connected vi 4G LTE.
Net, Net (no pun intended), some apps on the phone refused to work via the IPv4 address and required a working IPv6 address to work. Others were probably more tolerant and would fall back to work via IPv4 when they found a bad IPv6 address on the phone. Not sure if the apps should be made tolerant or the phone networking should be tolerant enough to do the IPv4 fallback for all apps. This is something that Nokia could investigate as a possible issue in the firmware.
Anyway, subsequently I checked many IPv6 related settings on my VDSL router (DLINK-224), but couldn't resolve the issue myself. I ended up calling my ISP (Airtel) and asking them about their support for IPv6. Initially, they claimed to support it, but later confirmed that for now, they don't support IPv6 for broadband connections. However, they sent over a technician who was extremely helpful and for no obvious reason, replaced my DLINK router with Huawei HG630. Again, for reasons not clear to me, this router started giving valid IPv6 addresses whenever a device connected over WiFi. My guess is that internally, its doing some IPv6 to IPv4 translation or tunneling, but at least the IPv6 address it was giving out were valid and working. Of course, as soon as my phone got a working IPv6 address, all those misbehaving apps started working and I have no issues any more. Interestingly, after the router change, ipv6-test.com tests now shows DNS6+IPV4 as reachable, even though it clearly shows IPv6 connectivity as 'NOT SUPPORTED'. In any case, as long as all my apps work well over both WiFi and 4G, I am a happy camper !
If you folks are still seeing these issues, please try the apps and sites I have linked above and see if you have the same issues. If so, you may be able to find a resolution thru your CSP or may be able to resolve the IPv6 address issue another way. All the best !
vmx560001 said:
After a lot of research into trying to understand the issues that I was seeing, I finally figured out that this was a IPv6 related issue. As it happens, in my case, it turned out that my router was causing the issue and not the phone itself. Please note that you may be seeing either the same issue or you may have completely different issue, but I hope the description below will give you some clues and directions that you may want to investigate.
The primary issue was that my router was returning a bad IPv6 address whenever a device connected over WiFi. I figured this out by running network diagnostics using the Netalyzr app from the Play store. When connected thru WiFi, this app reported a bad IPv6 address, but when connected thru a 4G LTE connection, it didn't report that as a problem. As a secondary check, I also used the IPv6 status widget to verify the network status when connect thru either of the connections. Again, this clearly showed that my phone was only on IPv4 when connected via WiFi, but was on IPv6 when connected vi 4G LTE.
Net, Net (no pun intended), some apps on the phone refused to work via the IPv4 address and required a working IPv6 address to work. Others were probably more tolerant and would fall back to work via IPv4 when they found a bad IPv6 address on the phone. Not sure if the apps should be made tolerant or the phone networking should be tolerant enough to do the IPv4 fallback for all apps. This is something that Nokia could investigate as a possible issue in the firmware.
Anyway, subsequently I checked many IPv6 related settings on my VDSL router (DLINK-224), but couldn't resolve the issue myself. I ended up calling my ISP (Airtel) and asking them about their support for IPv6. Initially, they claimed to support it, but later confirmed that for now, they don't support IPv6 for broadband connections. However, they sent over a technician who was extremely helpful and for no obvious reason, replaced my DLINK router with Huawei HG630. Again, for reasons not clear to me, this router started giving valid IPv6 addresses whenever a device connected over WiFi. My guess is that internally, its doing some IPv6 to IPv4 translation or tunneling, but at least the IPv6 address it was giving out were valid and working. Of course, as soon as my phone got a working IPv6 address, all those misbehaving apps started working and I have no issues any more. Interestingly, after the router change, ipv6-test.com tests now shows DNS6+IPV4 as reachable, even though it clearly shows IPv6 connectivity as 'NOT SUPPORTED'. In any case, as long as all my apps work well over both WiFi and 4G, I am a happy camper !
If you folks are still seeing these issues, please try the apps and sites I have linked above and see if you have the same issues. If so, you may be able to find a resolution thru your CSP or may be able to resolve the IPv6 address issue another way. All the best !
Click to expand...
Click to collapse
Thank you for the detailed analysis and your work around! I tried to change the required settings on my Dlink DSL 2750u router. I even tried to disable IPV6. But somehow it gets turned on automatically. I think its a problem with the router as you mentioned perfectly. I have contacted my ISP (BSNL) for some support, but I doubt they could help. Now only Instagram wont work. Even I reverted back to stable 8.1 with August Security Patch but still it wont work.
Hi,
I have had a quick look and found no answer to this issue.
I have an XZ2, which has worked faultlessly until a few weeks ago. The result is that when at work my connects to the network but shows 'connected, no internet'. It used to work on the network no bother. I have checked without IT dept and they can see no reason why it shouldn't work (ie it's not blocked on the network)
This appears to coincide with us getting a new router at home, We binned BT and moved to 4g Broadband from 3. Now when I connect at home it says connected no internet, then after a few minutes it gets internet connection. Sometimes I need to restart the phone. At work restarting makes no difference. I have tried:-
a)Forgetting the network and re-joining
b)reset network settings
I have read that the only fix is a factory reset of the phone. But I am hoping there may be a better solution to this.
Thanks
I am still having issues with this. I have tried starting the phone in 'Safe Mode' but still will not connect to the internet through my work network.
Does anyone have any suggestions?
Thanks
bit the bullet and did a full reset on the phone. Still getting 'connected, no internet'.
I am assuming that there must be an issue with the network/router at work if this is still happening after a reset. Although our IT has checked my mac address, DNS and IP address and say all are correct.
Well, looks like I may have resolved the issue. just as a last-ditch attempt I did the following.
1.Settings
2.Network & Internet
3.Advanced
4.Private DNS
In here you have three options. OFF, Automatic and Private DNS Provider.
Mine was set to Private so I changed it to Automatic.
It seems to have fixed the issue. Not sure why as this is not a setting I have ever changed.
Calcifur said:
Well, looks like I may have resolved the issue. just as a last-ditch attempt I did the following.
1.Settings
2.Network & Internet
3.Advanced
4.Private DNS
In here you have three options. OFF, Automatic and Private DNS Provider.
Mine was set to Private so I changed it to Automatic.
It seems to have fixed the issue. Not sure why as this is not a setting I have ever changed.
Click to expand...
Click to collapse
Weird, it is automatic by default at my side.