Database Info

ATT Internet Connection Settings

Ok... I don't think I have found a definitive answer on this so I am going to open up another forum.
Personally I have ATT (old Cingular) with the unlimited data plan. Some people say to connect with isp.cingular and some people say to use wap.cingular. Which one is better and why? What DNS settings are better and why? What are the actual connection settings we should be using?
This only applies to US ATT users.
Thanks!

I know that media net wap.cingular is the ap that you are normally assigned when you get an unlimited data plan on the phone.
isp.cingular is supposed to be for tethering plans that cost more.
I have tested both using my Kaiser with internet sharing to a laptop and speedtest.net isp.cingular was just a little faster and it is said that it is supposed to be faster for data customers and supposedly has a higher traffic priority.
What was interesting was that from my location in California Speedtest.net reported isp.cingular as originating in Los Angeles and it reported wap.cingular as originating in Florida.
I've experienced recently myself, that MMS/SMS won't work thru isp.cingular and cingular video as well (I don't use it but read that). So I keep both ap's set up on my phone but have wap.cingular in use most of the time as it seems fine for most all streaming Slingbox video/email/MMS etc. I only use internet sharing occasionally on the road with a laptop and would possibly take the time to re-engage isp.cingular for more speed, but it wouldn't be a huge difference really.
AT&T tech support told me that they were going to really shut down isp.cingular on most phones very soon.
Settings;
Connects to: The Internet
Access point: wap.cingular
Username: [email protected]
Password: CINGULAR1
Primary DNS: 0.0.0.0
Secondary DNS: 0.0.0.0
IP address: (blank)
Connects to: The Internet
Access point: ISP.CINGULAR
User name: [email protected]
Password: CINGULAR1
Primary DNS: 0.0.0.0
Secondary DNS: 0.0.0.0
IP address: (blank)

Thanks! I appreciate the input.

ponch92 said:
Thanks! I appreciate the input.
Click to expand...
Click to collapse
One thing I would add is you should modify your DNS settings to use the OpenDNS.org servers. It really makes things snappier (doesn't help overall performance, but I've found the initial connection to websites is definetly faster than when you use the Cingular/AT&T DNS servers).
I personally use Kaiser Tweak to disable the isp.cingular entry, and only use the MEdiaNet access and have had no issues. As stated though, if you tether then be careful doing that on MEdiaNet as they may charge you (but I've tethered for short periods of time when I'm in a pinch with no issues). I also downgraded from the PDAConnect plan ($40 per month) to the unlimited MEdiaNet plan ($20 per month).

With the Wap.Cingular you cannot send recieve mail using imap service. You have to use isp.cingular. There are other services that are blocked through the wap.cingular but that arent used that often.

pkapadia,
I don't think that's true. I only have 1 connection enabled on my device and it's using wap.cingular and I can send/receive mail via IMAP. I haven't run into any services that's blocked as yet using wap.

so... what are the AT&T settings?
if AT&T is planning on ending the cingular settings, it would be good to have the new settings from AT&T

mfrazzz said:
One thing I would add is you should modify your DNS settings to use the OpenDNS.org servers. It really makes things snappier (doesn't help overall performance, but I've found the initial connection to websites is definetly faster than when you use the Cingular/AT&T DNS servers).
I personally use Kaiser Tweak to disable the isp.cingular entry, and only use the MEdiaNet access and have had no issues. As stated though, if you tether then be careful doing that on MEdiaNet as they may charge you (but I've tethered for short periods of time when I'm in a pinch with no issues). I also downgraded from the PDAConnect plan ($40 per month) to the unlimited MEdiaNet plan ($20 per month).
Click to expand...
Click to collapse
I am currently in my AT&T trial, likely switching over to this carrier from verizon because of the Kaiser. I currently have a 40$/mo phone plan and a 40$/mo data plan.
What is this 20$/mo plan you speak of with MEdiaNet, could you expand on this please, I'm new to AT&T's pricing plans, I think that 80$/mo is pretty ridiculous, so if you could fill me in on any tips or tricks you know about re: waps and networks, I'd really appreciate it.
I'm sorry if I'm coming across as noobish, I'm really not, but I know squat about pricing plans and such.

pkapadia said:
With the Wap.Cingular you cannot send recieve mail using imap service. You have to use isp.cingular. There are other services that are blocked through the wap.cingular but that arent used that often.
Click to expand...
Click to collapse
That's 100% false. I use imap mail over wap.cingular daily.

evolved303 said:
What is this 20$/mo plan you speak of with MEdiaNet, could you expand on this please, I'm new to AT&T's pricing plans, I think that 80$/mo is pretty ridiculous, so if you could fill me in on any tips or tricks you know about re: waps and networks, I'd really appreciate it.
Click to expand...
Click to collapse
Cingular / AT&T change the names of the plans all the time. But what I'm talking about is when you buy a Tilt, AT&T will tell you that you HAVE to have the PDA Connect plan if you want data. This plan is $40 per month (actually $39.95 or thats what it was a year ago and I've seen people still quote that price). What this does give you is access to isp.cingular which is supposed to be a better network connection (and not going through their proxy stuff).
But if you have a "simple" phone like a Razr or similar, you can get the Unlimited MEdiaNet package (At one time it was called MEdiaMax, but now I think that is something else) for $20 (ok, $19.95) per month. Its a full unlimited internet package, but its only wap.cingular (You can actually use isp.cingular, but I've heard some have gotten caught and they charge you for the usage). In my experience (almost a full year now) I've had NO (none, nada, zero, zilch) issues running on MEdiaNet alone. Now taht I'm on a Tilt, 3G works just fine (and with the reg tweak I'm getting the H icon now even and nice speeds from it). If connections settings runs where it sets up both MEdiaNet and ISP, then I go into Kaiser Tweak and I turn off the ISP side and only use MEdiaNet. I then also modify the DNS servers to use the OpenDNS ones and page lookups are noticeably faster.
There is an entire thread about Cingular settings and plans in the Wizard forum (Here's the link: http://forum.xda-developers.com/showthread.php?t=280993&highlight=MEdiaNet). I haven't looked at this thread in awhile, so some of the info may be dated (as it was when things were Cingular and not AT&T a year+ ago) but there are posts there from just a few months ago.
Good luck! Shopping for Cellular plans is like the old days of shopping for Long Distance plans with Long Distance companies. Very confusing and its all Apples to Pears in the comparisons (ie: they are similar but they aren't the same).

My xperia x1 still doesnt connect.....
i entered the settings from the previous post and it says 502 Bad Gateway when i try to visit a website. now what lol

in reponse to question
hello fellow member
The answer to your question is the WAP. Reason being the isp, Is more for faster downloading and not the best graphics in the world. att is doing an update to the wap nationwide pretty soon and let me tell you its going to make everything seem better. hope this helps
att world communications analyst.

jacksonite said:
i entered the settings from the previous post and it says 502 Bad Gateway when i try to visit a website. now what lol
Click to expand...
Click to collapse
In the last couple of weeks, I've had weird issues on MEdiaNet. I had upgraded to a couple of different roms but thought it might ahve been rom issues, but going back to an older rom that always worked before, I had the same 502 gateway issue. I played around with running the removehiddenproxy cab, and manually tweaking settings and seem to now have it working and stable again. I do think the HTC Connections settings in most of the roms will setup AT&T settings correctly now. I still go in and use Kaiser Tweak to disable the ISP one, and only use MEdiaNet. But I've wondered if AT&T is doing something with MEdiaNet in my area due to it working, then seems to stop for awhile, then starts working again. Still really not sure

mfrazzz said:
In the last couple of weeks, I've had weird issues on MEdiaNet. I had upgraded to a couple of different roms but thought it might ahve been rom issues, but going back to an older rom that always worked before, I had the same 502 gateway issue. I played around with running the removehiddenproxy cab, and manually tweaking settings and seem to now have it working and stable again. I do think the HTC Connections settings in most of the roms will setup AT&T settings correctly now. I still go in and use Kaiser Tweak to disable the ISP one, and only use MEdiaNet. But I've wondered if AT&T is doing something with MEdiaNet in my area due to it working, then seems to stop for awhile, then starts working again. Still really not sure
Click to expand...
Click to collapse
hmm no issues here. I strictly set all connections to medianet.
edit: and this is definitely in the wrong section

ive been tweeking with the settings for 2 weeks now lol. at&t said they dont nkow what to do to make it work either. i even tried sony ericsson tech support they couldnt do anythin about it either. so i dont know what the hell is wrong i think its the username password and domain thing not sure. i dont know if this will make a difference, but i have the regular phone data plan for 14.99 would that be the reason why its not connecting to my xperia? do i really need to have the pda plan?

OpenDNS blocking gmail while using wifi tether for root users?

What the hell? Never even heard of opendns...wtf is it?
How do I fix it?

KidJethro said:
What the hell? Never even heard of opendns...wtf is it?
How do I fix it?
Click to expand...
Click to collapse
Are you using Wifi or 3G/Edge? Looks like the problem is with the admin that setup your Wifi.

Well sounds like you are using their DNS servers and someone blocked gmail.
go to opendns.com while tethering to change your settings if you can. You should see a "dashboard" link at the top right of the page.

OpenDNS is an alternative DNS service (normally DNS is provided by the ISP). Wifi-Tether-For-Root by default has OpenDNS hardcoded in as the default DNS (instead of T-Mo's DNS servers). Since all traffic on T-Mo 3G is routed through their central server, regardless of where you are physically, your ip on the internet will appear as coming from a T-Mo data center in Missouri or Kansas or something. Perhaps someone has maliciously set up an OpenDNS account with this ip and locked out gmail.
Edit: I am having no problems getting to gmail using WT4R. My tmo ip was different from the usual though. Perhaps they are load-balancing their US network. Last time I checked, my tmo ip came out in Kansas. This time however, it came out of Rhode Island. Strange, considering I am physically in California.
Could you lookup your internet-side ip address while tethering and see which tmo datacenter you appear to be coming from when your gmail access is restricted?

This is the first time I've ever used wifi tether. Was kinda wierd to see gmail was blocked. Working on setting up an opendns acct now.

Ok....I'm totally lost now. I've got an opendns acct setup. I'm lookin at the dashboard thing, and have no idea what to change to fix this issue?

You are going to want to go here https://www.opendns.com/dashboard/settings/
It should show your current IP in the drop down.
Turn off the filtering and make sure nothing down below is added.

jashsu said:
OpenDNS is an alternative DNS service (normally DNS is provided by the ISP). Wifi-Tether-For-Root by default has OpenDNS hardcoded in as the default DNS (instead of T-Mo's DNS servers). Since all traffic on T-Mo 3G is routed through their central server, regardless of where you are physically, your ip on the internet will appear as coming from a T-Mo data center in Missouri or Kansas or something. Perhaps someone has maliciously set up an OpenDNS account with this ip and locked out gmail.
Edit: I am having no problems getting to gmail using WT4R. My tmo ip was different from the usual though. Perhaps they are load-balancing their US network. Last time I checked, my tmo ip came out in Kansas. This time however, it came out of Rhode Island. Strange, considering I am physically in California.
Could you lookup your internet-side ip address while tethering and see which tmo datacenter you appear to be coming from when your gmail access is restricted?
Click to expand...
Click to collapse
Easy enough to figure out my ip addy....but no idea how to do the rest.
Weird thing though...I signed up fro an opendns acct, browsed around a bit in the dashboard and now gmail works? ~edit~ nvermind, spoke too soon...gmail is blocked again.
For some reason I have a problem wrapping my brain around this kinda stuff.

your ip could have changed

neoobs said:
You are going to want to go here https://www.opendns.com/dashboard/settings/
It should show your current IP in the drop down.
Turn off the filtering and make sure nothing down below is added.
Click to expand...
Click to collapse
I see my IP under the network tab. Under the settings tab it says "to control your settings, you need to add a network to your account." If I click "add a network" it takes me back to the network tab where my ip is displayed. If I click add network, it says network already exists?
Bleh....

Like i said, T-Mo is likely load balancing across their many gateways. My guess is whoever locked gmail out only did it to one of the gateways. Your best bet is to change the DNS servers away from opendns.

KidJethro said:
I see my IP under the network tab. Under the settings tab it says "to control your settings, you need to add a network to your account." If I click "add a network" it takes me back to the network tab where my ip is displayed. If I click add network, it says network already exists?
Bleh....
Click to expand...
Click to collapse
The reason is because only one openvpn account can control a network. Whoever has messed up that tmo gateway has full control of it until that person or openvpn changes the situation.

jashsu said:
Like i said, T-Mo is likely load balancing across their many gateways. My guess is whoever locked gmail out only did it to one of the gateways. Your best bet is to change the DNS servers away from opendns.
Click to expand...
Click to collapse
Ok, need this in baby talk, barney style. I have no idea how to change dns servers?

KidJethro said:
Easy enough to figure out my ip addy....but no idea how to do the rest.
Click to expand...
Click to collapse
http://www.ip2location.com/

jashsu said:
http://www.ip2location.com/
Click to expand...
Click to collapse
IP Address : 208.54.94.59 Location :
UNITED STATES, WEST VIRGINIA, CHARLESTON Latitude / Longitude : 38.3515 LATITUDE, -81.632 LONGITUDE Connecting through : T-MOBILE USA Time Zone : UTC -05:00
IDD Code : 1 Area Code : 304 Weather Station : USWV0138 - CHARLESTON

KidJethro said:
Ok, need this in baby talk, barney style. I have no idea how to change dns servers?
Click to expand...
Click to collapse
It might be enough to edit /data/data/android.tether/conf/dnsmasq.conf with a text editor and substitute out the DNS values in there with your own DNS. I'll try it out later.

jashsu said:
It might be enough to edit /data/data/android.tether/conf/dnsmasq.conf with a text editor and substitute out the DNS values in there with your own DNS. I'll try it out later.
Click to expand...
Click to collapse
"wifi tether" should update the dnsmasq.conf-file automatically (will take the dns from your 2G/3G-connection) - this was introduced in version 0.95.
Type ... "getprop net.dns1" into terminal ... that should exactly be the nameserver in dnsmasq.conf (after you have started tethering).

Bleh....I need a break from phone tweaking for a bit. Buuurn ouuuut

Works for me
I just got home, tethered just to see if it would affect me too. Not problems at all.

harry_m said:
"wifi tether" should update the dnsmasq.conf-file automatically (will take the dns from your 2G/3G-connection) - this was introduced in version 0.95.
Type ... "getprop net.dns1" into terminal ... that should exactly be the nameserver in dnsmasq.conf (after you have started tethering).
Click to expand...
Click to collapse
harry_m is right. When I tethered to my G1 via WT4R (ver 0.9.6) and visited opendns.com, it showed the "Start using OpenDNS" button, indicating my currently used DNS was not OpenDNS. I verified that WT4R had fetched the G1's internal DNS setting by checking the dnsmasq.conf:
Code:
$ su
# cat /data/data/android.tether/conf/dnsmasq.conf
no-resolv
no-poll
server=10.177.0.34
server=10.176.80.242
I suggest you reinstall WT4R and choose no when it gives you the option to import old settings. This way, it will build your configuration files from scratch (and not use OpenDNS).

Tethering: Horrible Speeds and Ping. Any idea how to fix?

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.

[Q] T-Mobile IPv6 Beta for Nexus S

Anyone try the IPv6 Beta for ICS Nexus S? They have IPv6 enabled on 3G now.
https://sites.google.com/site/tmoipv6/lg-mytouch

Didn't work for me. Lost data.

I set up the apn for it, still waiting on the confirmation from t-mobile saying they've provisioned my number for use of ipv6.

dls5375 said:
Didn't work for me. Lost data.
Click to expand...
Click to collapse
What did not work for you?
I read this review that it worked well. http://www.prolixium.com/mynews?id=963
Highlights were that users get public IPv6 addresses and inbound connections to the phone work

its not working for me either. ive been exchanging emails with a person from that tmobile beta program, and he has a theory why its not working for me, custom rom. im on cm9. cm9 might not include the correct RIL files. i will try with a stock rom later on.

elgato99 said:
What did not work for you?
I read this review that it worked well. http://www.prolixium.com/mynews?id=963
Highlights were that users get public IPv6 addresses and inbound connections to the phone work
Click to expand...
Click to collapse
I set it up the way the instructions said to, rebooted and lost my data connection. It came back when I restored default.

IPv6 works fine for me with the stock Nexus S IML74K firmware, both with the special beta APN and the standard epc.tmobile.com APN (which is IPv6-enabled in the Bay Area). I did some reading on the topic last night for a friend, and it does look like you need support from the cellular radio for IPv6 to work correctly (for Android, I assume that means both baseband and RIL).

Apart from just doing it, what are the advantages of doing it?

mobilehavoc said:
Apart from just doing it, what are the advantages of doing it?
Click to expand...
Click to collapse
Fair question.
To people with mobile phones, the benefits are real public IPv6 addresses that allow for the bidirection flow of traffic. Read -- inbound connections... can have a web server or ssh server on your phone... A phone now becomes a real node on the real Internet, not a "mobile web" experience. Actually, each mobile phone is assigned 2^64 IPv6 addresses... that is a codified standard (yes, there are a lot of IPv6 addresses, no i dont think this a bright, but it is not actually a problem). There is no NAT from IPv6 to IPv6 addresses. But, other than that, not a whole lot is different from a user perspective. One can wax poetic about re-establishment of the internet's end to end principle, or how IPv6 is going to help battery life... but it gets kinda hand wavy. This is why IPv6 has been around for 10+ years without much traction.
The real benefit i see is to the mobile network providers, or Internet in general. Mobile devices are growing at a very high rate and there is just not enough IPv4 addresses to go around. Internet wide, IPv4 is pretty much exhausted.
I thought this article had some interesting pointers http://tech.slashdot.org/story/12/01/13/2348206/ipv6-only-is-becoming-viable
And, Facebook, Google, Bing, Yahoo ... are all turning on IPv6 for good in June. On the Internet, IPv6 is a pretty big deal in terms of how data flows through the tubes.... But, ideally, plane old joes dont have to care about IPv6. It should just work.
Here is some info on the World IPv6 launch day http://www.worldipv6launch.org/

Thanks. I noticed on the site they say P2P services like Skype won't work with IPv6 and there's obviously going to be some compatibility issues. I'm excited to try it out but at the same time I don't want to break apps or functionality. Guessing by this fall people will adopting it more and there'll be less breaks.

Right, some technologies are going to evolve quicker than others. The slashdot article had a link to a list of apps that work and dont work, i think it said 85% work fine... but a few fail. In any event, for this beta, switching between the IPv4 APN and the IPv6 APN is pretty easy (3 taps). I think one of the goals is to create an early adopter critical mass to find the broken things, complain, and get them fixed.
Here is another interesting link about getting the apps cleaned up http://www.gossamer-threads.com/lists/nsp/ipv6/32908
And, if you really want to go deep, there is this code which fixes the broken apps by doing translation on the phone from IPv4 to IPv6
http://code.google.com/p/android-clat/

Works fine for me....CM9 Euroskank kang and the Trinity t132 kernel. The lack of mms support makes it a non daily use apn for me..(kids, grandparents, etc...lots o' pictures)...but otherwise...good to go here...

working here now too. cm9 kang and trinity t144. i did have to flash the newest radio then let it sit there for a bit before it connected to data for the first time. now it connects quick every time. ive found one problem though, it wont let my laptop get data while its tethered, even though the phone has a good data connection. as soon as i change my apn back to the original and let it connect, data starts flowing to my laptop again. will someone else try to tether. it connects fine, just no data flow.

I got it working with the browser but my signal bars never turn blue and Sync doesn't work at all along with most background sync apps. Seems odd. I'm on 4.0.2 stock. I switched back to iPV4 and everything works perfectly. At least I have it configured to try later on in the summer.

mobilehavoc said:
I got it working with the browser but my signal bars never turn blue and Sync doesn't work at all along with most background sync apps. Seems odd. I'm on 4.0.2 stock. I switched back to iPV4 and everything works perfectly. At least I have it configured to try later on in the summer.
Click to expand...
Click to collapse
syncs here just fine with blue bars.

simms22 said:
syncs here just fine with blue bars.
Click to expand...
Click to collapse
Which APN are you using? The website lists one and the email I got from T-Mobile listed a slightly different one?
I tried it again and it worked this time with the blue bars and sync using the scpcf000 APN. Wonder why it didn't work before? Wonder if different towers/regions have issues because I was travelling when it wasn't working. Who knows.
I would keep it but no MMS is a bummer - if there were some practical advantage to using IPV6 right now I'd stick with it but there doesn't seem to be. Yet.

mobilehavoc said:
Which APN are you using? The website lists one and the email I got from T-Mobile listed a slightly different one?
Click to expand...
Click to collapse
epc-scpcf000.t-mobile.com

simms22 said:
ive found one problem though, it wont let my laptop get data while its tethered, even though the phone has a good data connection. as soon as i change my apn back to the original and let it connect, data starts flowing to my laptop again. will someone else try to tether. it connects fine, just no data flow.
Click to expand...
Click to collapse
Yeah, no Internet connection on my laptop when I try to tether either. It looks like Android's tethering infrastructure isn't IPv6-aware yet -- the laptop isn't picking up an IPv6 address, and the phone doesn't have an IPv4 address, so it's not capable of routing IPv4 traffic to the Internet.
That said, even if Android were to grow IPv6-aware tethering, providing Internet access is going to be a problem. I can see four possible approaches:
(1) The phone assigns IPv4 addresses to tethered devices (as it does now), and implements NAT46 to translate that traffic into IPv6 traffic to send upstream. I don't know of any NAT46 implementations, though, never mind any ones suitable for a phone.
(2) The phone assigns IPv6 unique local addresses to tethered devices, and implements NAT66 to push that traffic upstream. (Basically, this is like the current tethering setup, except with IPv6 everywhere instead of IPv4.) Highly experimental NAT66 standards and implementations exist, but their very existence seems to be controversial (one of the original ideas behind IPv6 was to have enough address space to not have to use NAT in the first place).
(3) The cell provider assigns a /64 or larger block of globally-routable IPv6 addresses to the phone, and the phone assigns those addresses to tethered devices. (This is the approach fixed-line broadband providers are taking.) As far as I know, though, there isn't a standardized way to hand out prefixes (other than DHCPv6, which people don't seem to like either), and of course, this requires carrier involvement, with implications for everyone who wants to tether without a carrier-approved tethering plan.
(4) The cell provider assigns an IPv4 address (public or private) to the phone, and tethered clients use the existing IPv4 tethering infrastructure. This requires no changes on our end (it'd work right now on carriers that provide dual-stack access), but T-Mobile has apparently decided to assign IPv6 addresses only and use NAT64/DNS64 to provide access to the IPv4 Internet, so this won't work for us.

I found this article to be well written and informative for IPv6 on ICS http://www.androidpolice.com/2012/0...ere-is-what-it-all-means-and-yes-no-more-nat/

http://dan.drown.org/android/clat/
I tried this code out. It is pretty cool since it allows some additional functionality by doing a NAT from IPv4 to IPv6 locally on the phone. Skype and a few other apps that require IPv4 now work while they did not work before.

Lost IPv6 on AT&T

I've got a Moto G Stylus 2021 on Consumer Cellular in the US. My ISP uses carrier grade NAT so I have no public IPv4 but I *can* ssh from my phone to a machine on my LAN using IPv6. Or at least I could until CC sent me a new SIM card last week as part of their switchover from T-Mobile to AT&T. Now when I try to ssh via IPv6 (using the Termius app) I get an error "Connection failed. Disconnected with the message: network is unreachable. Error type: 1, error code: -101". Ordinary 4G data, like email and web browsing works fine.
When I go to test-ipv6.com it tells me "No IPv6 address detected. You appear to be able to browse the IPv4 internet only. You will not be able to reach IPv6-only sites" (Yeah, no kidding).
I wasted 45 minutes on the phone to CC talking to people who had no clue as to what IPv6 even was, and tried to tell me that the problem was because CC stopped supporting 3G two years ago. I said, "No, IPv6 has been around for 15 years." They said "Oh that's old technology then. We don't support anything 15 yeares old". Duh. I checked my APN and found that my APN type and APN protocol fields were now set to IPv4. I changed them to IPv4/IPv6 and rebooted with wifi turned off. Didn't help. I tried setting them to just IPv6. That didn't work either. I tried the suggestions here: https://www.att.com/support/article/wireless/KM1062162/ and here: https://www.4gapn.com/us/en/consumer-cellular and they didn't work either.
Anyone else with this problem? Does anyone know if CC even still supports IPv6 on AT&T? Is there anyway to get my IPv6 ssh back?

I don't know if I'm answering my own question but the Hurricane Electric list of ASN's (https://bgp.he.net/country/US) seems to suggest that Consumer Cellular does *not* support IPv6 now. :-(
However, I found a workaround. route48.org offers free IPv4 to IPv6 tunneling. Very easy to setup and works fine.