Related
For some reason when I enable my location and my phone is connected to my Airave, it locates me in a city about an hour away. When I turn my airave off, it is able to tell the actually city I am in. Is there anyway to correct this?
I am using the stock ROM with WM6.5 which was recently released. The only modifications I have done is added the Taskbar and Co0kie home screen mod.
Thanks,
Same issue. Soon as the phone enters the building with the Airave it jumps 200 miles.
I can answer this one! I'm a Sprint employee and am extremely familiar with the Airave.
The Airave broadcasts signal allowing your phone to have signal in an area where Sprint signal is not normally available. It does this by receiving a request from your phone, connecting to the Airave, and then then sending the request via your broadband internet connection rather than through a Sprint tower.
The problem you are experiencing is because of settings with your Internet Service Provider (ISP). Your location, often refered to geolocation, is set by your IP address (provided to you automatically by your ISP). ISPs often base IP addresses in a city where the company is basing operations. For example, I live in Indianapolis, Indiana, and use Comcast as my ISP. My IP address however is based out of Rockford, Illinois.
If you go to http://whatismyipaddress.com, you will see the city to which your IP address is set. The city listed at this site, I would assume, is the city you see on your phone as your current location.
As far as a fix, I don't have much in the way of an answer. If the weather application is the issue, you could always set a city, rather than using the automatic location setting.
I hope this gives you some insight as to why the problem exists.
I had this same problem with my Touch Pro 2 using one of the Mighty Roms. I can't believe I didn't even think of the AirRave as the culprit. I figured the weather location came from my GPS coordinates, not which cell tower I'm connected to. This makes sense now. However, once I updated to Mighty Roms latest Rom, I no longer have this problem and my location is correct. Maybe Time Warner NY is doing something differently now and my AirRave is reporting the correct area. Before my phone was saying my location was "Jackson"...now it says "New York".
MrMaNz said:
Before my phone was saying my location was "Jackson"...now it says "New York".
Click to expand...
Click to collapse
Precisely the same has happened with me. On cooked ROM's my location is "Jackson" (NJ, I think) and on the Sprint 6.5 ROM it's New York. I'm on Comcast cable, not Time Warner. I doubt this is an issue of the ISP one uses to access the internet from the Airave's location but rather of Sprint as the ISP for the phone via the Airave - Sprint is supplying the IP address for the phone, not your personal ISP.
The likely explanation for the apparent location change, of course, is that between ROM flashes Sprint changed something that provides different geolocation data and that this has nothing to do with the ROM itself.
More interesting is the comment above about a recent cooked ROM providing correct location information. It seems as if it should be possible to hack the location feature to use GPS rather than IP geolocation.
It is not rom related you are wrong. It is all about the ip address location.
same thing for me, but dont think it has anything to do with airave, dont even know wat that is or if i even have it on, but my fone shows my current location as a small town about 20 miles away with a population of about 200 (not thousand, just 200) so dont think it has anything to do with towers, any ideas?
It is all about the ip address. If I plug in the phone to activesync I get one ip and one location. If I use the verizon data connection I get another ip and another location
It does not appear to be IP related as the website posted to check the ip shows me in Kansas... but my location on the TP2 shows Canton, OH while connected to the airave. I know that I put in a zipcode in the settings for the airave on sprint's website and even that zipcode is different than the city I get.
jobobusa said:
It does not appear to be IP related as the website posted to check the ip shows me in Kansas... but my location on the TP2 shows Canton, OH while connected to the airave. I know that I put in a zipcode in the settings for the airave on sprint's website and even that zipcode is different than the city I get.
Click to expand...
Click to collapse
When you go to the same website ON YOUR PHONE does it show you as being in KS or OH?
Your phone and your computer don't have the same IP, even if your phone is connecting through your computer.
jhworley said:
I'm a Sprint employee and am extremely familiar with the Airave.
...
The problem you are experiencing is because of settings with your Internet Service Provider (ISP). Your location, often refered to geolocation, is set by your IP address (provided to you automatically by your ISP).
Click to expand...
Click to collapse
You're quite wrong about this.
The IP for my phone is supplied by Sprint's DHCP servers when it connects via the Airave. It's not supplied by Comcast's DHCP servers at all.
At the moment, both my notebook and my phone are online. Both the wireless router to which my notebook is connected and the Airave go through the same Comcast cable modem. There is no cellular service available near my house except via my Airave.
At the moment, my notebook's public IP is 24.147.35.xxx and my phone's is 174.146.248.xxx. As you can see, they're quite different. If I switch off my cellular radio and connect the phone to my WiFi, it uses the same IP of 24.147.35.xxx as my notebook. The 24.147.35.xxx address gives a geolocation of Monson, MA even though I'm in NH. The 174.146.248.xxx gives a geolocation of Cedar Grove, NJ.
Thus, your answer is wrong on several fronts. The ISP that supplies internet connectivity to the Airave has nothing at all to do with geolocation on a phone connected through that Airave. Further, the location shown on the phone still does not match the actual geolocation that corresponds with the phone's IP address. In the real-life example before me right now, the location on the phone is 21 miles from the geolocation of the phone's IP address.
Finally, the location service on the phone does not depend entirely upon geolocation based on IP address. If I turn off my cellular radio and connect via WiFi, my phone decides that it's in Hancock, NH which is correct even though the phone's IP geolocates to a different state.
That last bit suggests that the location service on the phone is perfectly capable of using GPS if it can't use IP geolocation.
mstevens said:
You're quite wrong about this.
The IP for my phone is supplied by Sprint's DHCP servers when it connects via the Airave. It's not supplied by Comcast's DHCP servers at all.
At the moment, both my notebook and my phone are online. Both the wireless router to which my notebook is connected and the Airave go through the same Comcast cable modem. There is no cellular service available near my house except via my Airave.
At the moment, my notebook's public IP is 24.147.35.xxx and my phone's is 174.146.248.xxx. As you can see, they're quite different. If I switch off my cellular radio and connect the phone to my WiFi, it uses the same IP of 24.147.35.xxx as my notebook. The 24.147.35.xxx address gives a geolocation of Monson, MA even though I'm in NH. The 174.146.248.xxx gives a geolocation of Cedar Grove, NJ.
Thus, your answer is wrong on several fronts. The ISP that supplies internet connectivity to the Airave has nothing at all to do with geolocation on a phone connected through that Airave. Further, the location shown on the phone still does not match the actual geolocation that corresponds with the phone's IP address. In the real-life example before me right now, the location on the phone is 21 miles from the geolocation of the phone's IP address.
Finally, the location service on the phone does not depend entirely upon geolocation based on IP address. If I turn off my cellular radio and connect via WiFi, my phone decides that it's in Hancock, NH which is correct even though the phone's IP geolocates to a different state.
That last bit suggests that the location service on the phone is perfectly capable of using GPS if it can't use IP geolocation.
Click to expand...
Click to collapse
Well said. BTW, Sprint has still not been able to fix this. All of my phones show Galena, IL instead of Cedar Rapids, IA (where I really am). The latest reason I got from Airave Technical Support is:
The Airave unit gets GPS data from a satellite. The location you see, is the location of the specific satellite that the Airave is connecting to.
Oh... My... God... I couldn't think of how to politely disagree; so I just flat out said that makes no sense whatsoever. The floor manager tried to tell me the same thing. :| This was after she tried to tell me the GPS was only used to facilitate connection to the network; which I agreed was possible, but pressed her to why it showed me about 100mi off if it was to be used for network connection? I also asked if this would affect my 911 use as the Airave is suppose to provide E911 data in case of emergencies; she said it doesn't use the GPS location for 911. I pointed her to the Sprint website which claimed it did; after which she started me a 'Network' ticket. ::sigh::
I'm having this same issue. I originally got my airave for my office which was out in the middle of nowhere with no sprint service. I have since moved and changed jobs. Even though I live in an area with strong coverage due to the buildings (I think) I get signal fluctuations from full to nothing and dropped calls. I set my airave back up which solved that problem but when I am home my weather still shows the location of my previous office which is 200 miles from where I am now. I have made 4 calls to airave "support" and they have been unable to fix the problem. The last 2 calls I finally hung up after they left me on hold for about 45 minutes (I guess that's their current solution). Sad that after over a year since this thread was started sprint still hasn't figured out how to change the registered location of the airave. Not only is it annoying but it worries me that should I ever have to call 911 I may have issues. IF the registered location affects E911, and I have no idea if it does or doesn't, aren't they required by law to provide reliable E911 service?
I've recently upgraded to WM 6.5 on my Sprint TP2 and I really liked the home screen with the weather. The fact that it automagically updated the weather city as I drove to work is very cool.
Did you notice the past tense in the above paragraph? Now it tells me the weather Beverly Hills and I can't get it to report on my home location.
From the weather application I've deleted all but my home location and turned off location services. Although I've deleted all locations except my home location, it still shows 2 weather locations from the forecast screen, one of them being Beverly Hills.
Do you have sense 2.1? I had the same problem, didn't know what town I was it kept telling me that I was in Espoo Finland lol. When I upgraded to 2.5 it solved my problem.
Hope it helps
How do I check what 'sense' I have?
I'll search the site for an update.
I'm sure this is my problem, I have a Sprint Airave at my house. This is from another forum.
I can answer this one! I'm a Sprint employee and am extremely familiar with the Airave.
The Airave broadcasts signal allowing your phone to have signal in an area where Sprint signal is not normally available. It does this by receiving a request from your phone, connecting to the Airave, and then then sending the request via your broadband internet connection rather than through a Sprint tower.
The problem you are experiencing is because of settings with your Internet Service Provider (ISP). Your location, often refered to geolocation, is set by your IP address (provided to you automatically by your ISP). ISPs often base IP addresses in a city where the company is basing operations. For example, I live in Indianapolis, Indiana, and use Comcast as my ISP. My IP address however is based out of Rockford, Illinois.
If you go to http://whatismyipaddress.com, you will see the city to which your IP address is set. The city listed at this site, I would assume, is the city you see on your phone as your current location.
As far as a fix, I don't have much in the way of an answer. If the weather application is the issue, you could always set a city, rather than using the automatic location setting.
I hope this gives you some insight as to why the problem exists.
For someone that works for Sprint, you are giving out a lot of bad information on their products. The Airave Geolocation is obviously NOT ISP based! The geolocation on my computers are all correct, well the location on my phone is not correct. That shows that it is not an ISP issue.
FYI, that Airave descriptions wasn't mine it was from an entry "Sense 2.5 My Location and Airave Issue" by jhworley under another topic.
In running some tests on my phone I'm getting more confused.
First of all WhatIsMYIPAddress shows my home computer being in Lansing, Michigan. Im on DLS and live in Okemos, a suburb of Lansing.
I went through all the combinations of Airave on and off, and the TP2 WiFi on and off, and WhatIsMYIPAddress on the phone always showed Wichita, KS. I did reload the page every time but maybe I should have done a hard reset to make sure it cleared everything.
Also, now the weather location the home screen of the phone is showing Okemos, not the previous display of Beverly Hills. I think what's going on here is that my phone is actually connecting through the local cell tower (which is usually marginal, hence the Airave) and Geolocating "Okemos".
It would be interesting to know when the phone (Sprint TP2) connects through the cell tower, Airave, or home WiFi. Can anyone tell me if the phone only does data connections thru the home WiFi, or will it do VoIP over the WiFi if available?
Thnx
crites said:
FYI, that Airave descriptions wasn't mine it was from an entry "Sense 2.5 My Location and Airave Issue" by jhworley under another topic.
Click to expand...
Click to collapse
I knew that, but only because I was familiar with that (incorrect) post from another forum. They way you post it, without quoting or attribution, makes it look as if you're saying you wrote it. It's best to avoid that, because either other people's blunders are going to make you look dumb, or you'll be stealing other people's work.
crites said:
Can anyone tell me if the phone only does data connections thru the home WiFi, or will it do VoIP over the WiFi if available?
Click to expand...
Click to collapse
VOIP uses a data connection. It doesn't care whether that's cellular data or WiFi. The phone does not come set up with VOIP, though. You have to install a VOIP application such as Skype.
Airave & Wrong Weather Time/Location
Maybe just coincedental, but when I started using my Airave this morning, my Homescreen on my TP2 now has the wrong city, about 10 miles away, and is frozen at US 8:07CST.
Maybe a coincedence.
mine does it randomly too, i just havce to input the location manually
Yeah, I called Airave and they said that in some cases it is a known bug and they are going to do an update at some point to correct it.
The moment I unplug my Airave I instantly get my updated local weather. Oddly, all the other major cities I keep on my Airave, such as Chicago, IL, don't have any update issues.
But, since I've got more bars on my phone than the Hershey Chocolate factory cranks out, I'll gladly put up with it. Sure beats 1 bar and dropped calls.
I have a Captivate running Cognition V2.2.Beta1. Using either usb tether or wireless tether, I get pings of 600+ and slow upload/download speeds.
http://www.speedtest.net/result/1064395617.png
http://www.speedtest.net/result/1064400255.png
Anyone else getting better results? Anyone know how to optimize/fix the issue?
it's because you're pinging and speed testing on a server 400 miles away from where your phone accesses the internet. where you personally are located is not necessarily where your phone connects to the internet. that speedtest app using your location to suggest "nearby" servers to test on instead of using your ip address. testing on servers closest to where your ip address routes to/from will get you much better results.
edit: for instance, I'm currently in central new jersey, but the speedtest app suggests a server 220 miles away in virginia because I disabled the location services (gps and wireless networks) and it is now using my ip address to suggest the closest servers.
slifer315 said:
it's because you're pinging and speed testing on a server 400 miles away from where your phone accesses the internet. where you personally are located is not necessarily where your phone connects to the internet. that speedtest app using your location to suggest "nearby" servers to test on instead of using your ip address. testing on servers closest to where your ip address routes to/from will get you much better results.
edit: for instance, I'm currently in central new jersey, but the speedtest app suggests a server 220 miles away in virginia because I disabled the location services (gps and wireless networks) and it is now using my ip address to suggest the closest servers.
Click to expand...
Click to collapse
Actually I manually selected the server in San Diego as that is where I connecting from.
What I am really trying to do is get this to work with a good enough ping to play Aion an MMORPG when traveling and in a hotel room.
what are your results when you pick the recommended server?
San Fran:
http://www.speedtest.net/result/1064446975.png
http://www.speedtest.net/result/1064447880.png
http://www.speedtest.net/result/1064448553.png
you should try a rom with HSUPA support such as assonance, perception, axura, or even the latest cognition now has HSUPA support. you'll get higher upload speeds and therefore a lower ping. then maybe you'll be able to play in very low populated areas because too many other players or monsters would flood your bandwidth with data and therefore cause you to lag out.
Im thinking about it. You said the voice quality goes down with one of those roms however?
I also thinking the upgrade process from 2.2b1 is going to be ugly/hard to do since with this rom it doesn't support clockwork.
call quality used to be bad, but the jk3 modem included in most of them is crystal clear. just find an update.zip from somewhere on this forum that contains clockworkmod recovery, put it on your sd card, odin one click back to stock, do not master clear, reboot to recovery, reinstall packages twice to install clockwordmod recovery, data wipe / factory reset in recovery, and finally flash your rom of choice. as long as you don't change that update.zip, which you shouldn't ever need to, you can use this method to flash any rom in the future.
slifer315 said:
it's because you're pinging and speed testing on a server 400 miles away from where your phone accesses the internet. where you personally are located is not necessarily where your phone connects to the internet. that speedtest app using your location to suggest "nearby" servers to test on instead of using your ip address. testing on servers closest to where your ip address routes to/from will get you much better results.
edit: for instance, I'm currently in central new jersey, but the speedtest app suggests a server 220 miles away in virginia because I disabled the location services (gps and wireless networks) and it is now using my ip address to suggest the closest servers.
Click to expand...
Click to collapse
Where you are physically located has nothing to do with it (or not much in picking a server). Your phone gets on the cellular network near your house. Its data transits AT&Ts servers and hits the Internet wherever it exits the AT&T data centers - usually Dallas, TX. Best results are when SpeedTest tells you as that server is closest to the AT&T Proxy server that is putting you online.
Cell Phone networks were not built with Latency or ping times in mind, so tethering will give mediocre performance. Aircards tend to do better as carriers and prioritize traffic for PCs over phones - also depending on how you are tethered, there may even be one less hop.
alphadog00 said:
Where you are physically located has nothing to do with it (or not much in picking a server). Your phone gets on the cellular network near your house. Its data transits AT&Ts servers and hits the Internet wherever it exits the AT&T data centers - usually Dallas, TX. Best results are when SpeedTest tells you as that server is closest to the AT&T Proxy server that is putting you online.
Cell Phone networks were not built with Latency or ping times in mind, so tethering will give mediocre performance. Aircards tend to do better as carriers and prioritize traffic for PCs over phones - also depending on how you are tethered, there may even be one less hop.
Click to expand...
Click to collapse
that was exactly my point.
slifer315 said:
that was exactly my point.
Click to expand...
Click to collapse
Yes, but picking your IP address should give you the same physical location as the speedtest.net servers - that is how they locate you - IP geo-location. Your IP address is the last hop Speedtest sees - they are trying to ping you. If you pick your physical location then the speedtest has to cross the internet to your IP address then ride the carrier network back to your physical location.
Picking your physical address should make ping times and speedtest times longer.
I second using a HSUPA rom. I've been on perception for the last 2 weeks using it to tether my pc for some Black Ops Multiplayer. On the cognition rom i would regularly ping about 300+ with 1.5mb down/1up. Now with perception 7 i am pinging under <100 with 3.5mb down/ 1.5up. Its all in the modem the rom is using.
Hey now-
Im not sure what is happening with my mobile irc.
Instant DC and one client reports back a "SASL error: must authenticate using SASL on this server"
Googling the problem found one helpful post HERE.
This seems to be a result of the IPbackhaul for 4g.(?) I'm not sure if ive just got a funky modcell near me im locked onto or what but when i do a speedtest from the browser on 4g it always pings me back to Kansas City (im in california lol).
So my question: Wouldn't it be faster and easier to just switch to 3g (or edge for that matter) when i want to use the irc?
I'm going to search for something to do just that- (does it exsist without rooting?)
Curious what the bigbrains thought of this situation. (and my pinging KC?)
thanks for the flames and help in advance
"Look at the Big Brain on Brad"
You can do this without rooting...
*#*#4636#*#* from your dialer will take you to your hidden menu.
Choose Phone information
Set Preferred Network type
Currently this will be WCDMA preferred, if you change it to GSM only, it will only connect to Edge
As far as your speed tests are concerned, a couple things might be happening. If you're using speedtest.net app, wait for the GPS to find you. When you open the app it will start a GPS search and should be able to find you and redirect you to the closest speed test server. If you don't wait, it's going to use the closest spot to which the IP address your phone is using comes from (and from the sounds of other users, it looks like ATTs IP addresses come from the Kansas City area)
Thnx alot i will check it out!
Sent from my Desire HD using XDA App
Okay, I'm here in Houston and as of yesterday, I have noticed that it takes FOREVER for certain web pages to load. Specifically, Google.com(along with google search), and Yahoo (m.yahoo.com)
When I switch to 3g and Wifi, they resolve normally. On 4g, it's as if the dns server is having a tough time getting there. The weird thing is when I ping the sites by domain, I'm getting responses on my phone so I'm not even sure if it's DNS. Since if it was DNS I'd get slow responses, or I would only be able to ping it by I.P address.
So, I got an app on the market called SETDNS, and it seems to change my DNS server (I have it set to OpenDNS) and it still doesn't load up these sites fast.
Anyone in Houston having an issues with slow sites?
I've verified that it's not my rom (CUBEDROM) as my Co-worker here is on BAMF and is currently experiencing the same thing. I thought it was just the tower we both happened to be on, but we went somewhere outside of work on the other side of town, and still the same thing
Any ideas?
Samsuck said:
Okay, I'm here in Houston and as of yesterday, I have noticed that it takes FOREVER for certain web pages to load. Specifically, Google.com(along with google search), and Yahoo (m.yahoo.com)
Click to expand...
Click to collapse
FWIW, I'm in Denver and experiencing the same issues on those sites. While on the LTE network, some sites are ridiculously slow to load compared to 3G. I don't believe it's strictly a DNS issue; you'd never get the page to load at all if you couldn't resolve the domain name, you'd just get a 404 or the like.
Same thing with me in Pittsburgh. Even happens when trying to load the XDA app. Just takes forever on 4G but then 3G works fine.
NickWarner said:
FWIW, I'm in Denver and experiencing the same issues on those sites. While on the LTE network, some sites are ridiculously slow to load compared to 3G. I don't believe it's strictly a DNS issue; you'd never get the page to load at all if you couldn't resolve the domain name, you'd just get a 404 or the like.
Click to expand...
Click to collapse
Yeah, you know what you're right. If it was strictly DNS then I would only be able to ping by I.P
So is 4g being routed through a proxy or something?
It's getting annoying because I use google search alot on my phone, and it will only load up properly on 3g.
Hrm, so apparently it's not just a Houston thing.
If anyone could continue to confirm this that would be great.
Purely just a theory, but with the big sites like google.com and yahoo.com, they are testing IPv6 (Global IPv6 test day, started yesterday at like 4pm West time i believe). Possible that your wifi and 3g can handle IPv6, but the 4g switches were struggling? Just a theory.
Same issues here in Detroit, was better 20 mins ago but back to the same problem again.
I agree that World IPv6 Day could be a cause, but that's only if you have trouble routing to the IPv6 address. I'm testing using purely IPv4 addresses for m.google.com (First response I get is 74.14.213.193).
On LTE, I'm averaging 300ms for the first hop (69.83.157.73), and ~75ms for the other hops.
On 3G, I average 130ms for the first hop (69.83.157.73), and ~115ms for the other hops.
If that's on each packet, I'm experiencing about double the load time for any traffic to m.google.com on LTE vs. 3G. Of course, that's not taking into account actual transfer speeds, so some of that might be recouped on larger packets, but still, it's significant.
Same in Columbus, Ohio except that 3g was doing the same thing. I was trying to stream Tunewiki on the way to work around 8am and nothing would load. I tried rebooting but it didn't help. At that point I chalked it up to network problems. I jumped on wifi when I got to work and have been waiting for the threads to pop up here to confirm.
Same thing in socal so its a national thing
good thing we have options to change to 3g
and not 1x
Hrm, that's interesting.
Yooooo, i think you're right
check this article out
http://www.metro.co.uk/tech/865705-google-facebook-and-bing-test-ipv6-as-net-runs-out-of-space
I can't resolve google,yahoo, facebook,and bing is occasional.
They all will failover to IPv4, and I was testing using the IPv4 addresses. I still think there's something wrong here, and the World IPv6 Day stuff is masking it.
I can resolve all of the major sites in DNS and get both an IPv6 and IPv4 address for them. I chose to test with only IPv4 to ensure that my results would be comparable to each other.
Nick, i agree that there is an error here. I'm just outside of my 4g at work, but can you check what your IP is if you are on 4G? I have a sneaky suspicion that there is a correlation here. If we are on v6 and pinging to v4, could possibly see higher load times if there is software glitches on verizons end. Awfully suspicious if they are not related! And i do know the t-bolt is v6 ready, as all LTE on verizon are required to be v6 ready.
Hrm. When on 4g my IP is 166.249.220.38, for 3g my IP is 166.249.197.80
Samsuck said:
Hrm. When on 4g my IP is 166.249.220.38, for 3g my IP is 166.249.197.80
Click to expand...
Click to collapse
Well there goes my theory. Thanks for checking Samsuck.
I too see addresses in the same IPv4 Class A (10.0.0.0) when on either LTE or 3G. I'm seeing non-routables, of course, which then get NAT'd through to a pool of external IPv4 addresses.
Running netcfg on the phone shows that I only get IPv4 addresses. I don't believe that these phones are receiving IPv6 addresses from Verizon, which makes sense if they're non-routable addresses, since they'll have to be NAT'd at some point.
Ok, so netcfg on Android only supports IPv4, which is my bad.
I may have spoke too soon. This guy says his VZ LTE always assigns him a IPv6
www(dot)anandtech(dot)com/show/4289/verizon-4g-lte-two-datacards-wifi-hotspot-massively-reviewed/3
I can't seem to find any sites discussing for definite what IP's VZ deals out on LTE.
Samsuck, was the checker you used IPv6 capable?
cmhfdisker said:
Same in Columbus, Ohio except that 3g was doing the same thing. I was trying to stream Tunewiki on the way to work around 8am and nothing would load. I tried rebooting but it didn't help. At that point I chalked it up to network problems. I jumped on wifi when I got to work and have been waiting for the threads to pop up here to confirm.
Click to expand...
Click to collapse
Same here in Reynoldsburg man. Went down forbme last night around 1am n spotty ever since...
4Geezy ON DopeDiculous's ROOTED TBeezy!
NickWarner said:
I too see addresses in the same IPv4 Class A (10.0.0.0) when on either LTE or 3G. I'm seeing non-routables, of course, which then get NAT'd through to a pool of external IPv4 addresses.
Running netcfg on the phone shows that I only get IPv4 addresses. I don't believe that these phones are receiving IPv6 addresses from Verizon, which makes sense if they're non-routable addresses, since they'll have to be NAT'd at some point.
Ok, so netcfg on Android only supports IPv4, which is my bad.
Click to expand...
Click to collapse
Man it sucks not being on 4g to try myself, but if someone could try usb tethering, and also wifi tethering, then IP checking on a IPv6 capable checker. Might find out if it is the culprit.
When you say checker what do you mean? How did I check my IP?
I just browsed to http://whatismyip.com
I pinged the different sites via the terminal emulator.
nbdysreal said:
Man it sucks not being on 4g to try myself, but if someone could try usb tethering, and also wifi tethering, then IP checking on a IPv6 capable checker. Might find out if it is the culprit.
Click to expand...
Click to collapse
Ok, when I'm on LTE, I do indeed get a public, routable IPv6 address. Using http://whatismyipv6.net on the phone, I can both see the address and traceroute back to it. Awesome.
On 3G, going back to the same site shows me that I only have an IPv4 address. It's a non-routable 10.0.0.0 address that gets NAT'd to a 166.250.0.0 address on the outside.