IPv6 T-Mobile US Beta Test

[bunanson]

Well, ddown's program worked very well. Unfortunately, because of job, I moved to North Dakota now, say goodbye to North Carolina.

the IPv6 does NOT work here in North Dakota. Not quite sure why. I am now on a $1.49 day pass and kind of work. I saw geneven subscribed to a $15 monthly thing wondering what is the advantage? Still moving my house, ..., a human being is so small and insignificant if one has to move his house, :( a formidable task for me.

bun

[tmojoe]

In ND, you are probably on a roaming partner and not native T-Mobile USA coverage, so IPv6 will not work.

[bunanson]

Yes, You are totally correct. It asked for "OK to roaming data?" I guess it is with a tmob partner. I bought the daypass and it worked very well in a big city, like Fargo. When I go to a small city, even daypass wont work :( . Interestly, 2G is connected and phone is working, but no streaming data, even with the daypass. I guess I will have to switch to something. But thanks for ddrown effort. I did enjoy several month of working skype on the road while in NC.

bun

[hello from NC]

hey guys, need some help here, i got my ipv6 beta access yesterday. i did the ipv6 method from ddrown and it worked last night without a flaw. GV, skype everything, but it stopped working when i woke up. i reinstalled everything but no hope. i then used the debug and it came out to be:

QuickConnect failed (com.nokia.csd.GPRS.Error.ConnectFailed)
Cause: Unknown. Probably no ipv6 support on your account

i did got the access yesterday, is there a solution for it? thanks

[ioan]

but it stopped working when i woke up.

Same problem here. Maybe the beta period it's over? I hope not.

[tmojoe]

hardware error in the network last night. fixed now.

[ioan]

hardware error in the network last night. fixed now.

Thank you! I can confirm that works fine now.

[hello from NC]

yes!! thank you tmobjoe

[hello from NC]

strangest thing happened, as i reinstall the ddrown's files to restore the connection. i reinstalled the libicd file, iproute, and nat64d file. i am able to connect ipv6 but the GV, skype, stopped working on GPRS and wifi. (phone said Availability must be online to perform this action), the only things work are the web, and the apt-get.

[hello from NC]

quick update, i feel like a jackass now lol. forgot to turn the status back on. entirely my fault. thanks to ddrown and tmojoe. keep up the good work!:D

[Radu]

I am going over to Europe in a few months, and I would like to be able to use my N900 with some 3G prepaid data package. Unfortunately, they all use IPv4. Is there any elegant way to get IPv4 working as well over the 3G modem, without uninstalling the IPV6 'hack'? I have a 3G modem for my netbook, so this is not extremely important, but would be nice.

[ddrown]

Is there any elegant way to get IPv4 working as well over the 3G modem, without uninstalling the IPV6 'hack'? I have a 3G modem for my netbook, so this is not extremely important, but would be nice.

I assume you mean the dual connections documented at: http://n900-ipv6.garage.maemo.org/

You can just move the files in /etc/network to a temporary location.

[Radu]

I read that page a while ago, before the nat64 thing.
So do I just have to move the files in /etc/network to a temporary location, and I magically get IPv4 connectivity again? Then I just move them back when I need IPv6? Anything else? Do I move ALL the files in /etc/network ?

[Radu]

Nvm, I looked at the files there and I guess only the nat64 up and down must be moved, not all the files. But is moving them enough?

[ddrown]

Nvm, I looked at the files there and I guess only the nat64 up and down must be moved, not all the files. But is moving them enough?

Oh, if you have the files /etc/network/if-up.d/nat64-up and /etc/network/if-down.d/nat64-down, you're using the libnat64 library.

You shouldn't need to do anything with files in that case. You should have two cell phone connections listed in your list of internet connections. The one with the red "v6" text in the icon is the IPv6 connection, the one with the blue lines in the icon is the regular v4 connection. The libnat64 library only takes effect when using the IPv6 connection.

Does this make sense to you? I don't have my n900 on me, so I feel like my explanation might be a little off.

[Radu]

It makes sense, but I never seen the blue connection since I installed the IPv6. I see it in the connections list in Settings/Connections, but it never appears when I want to connect to 3G.

[ddrown]

It makes sense, but I never seen the blue connection since I installed the IPv6. I see it in the connections list in Settings/Connections, but it never appears when I want to connect to 3G.

That's odd, it should show up in the list of connections whenever you have a cell signal. You can try removing your v6 connection by running: "/usr/bin/register_3g_ipv6 deinstall"

If you want to re-add the v6 connection after you deinstall, you just need to run "/usr/bin/register_3g_ipv6 install"

[tmojoe]

FYI, T-Mobile is having a hardware issue in the lab where the beta is hosted... working to resolve it

[tmojoe]

FYI, the IPv6 Beta is fixed now

[ioan]

FYI, the IPv6 Beta is fixed now

Just curious, are the N900 owners the main testers for the IPv6 beta?

[tmojoe]

Just curious, are the N900 owners the main testers for the IPv6 beta?

Yes, the majority of handsets in the beta are N900s. It is the only place where power users who know what IPv6 is and IPv6 supported hardware converge.

Nearly all S60 phones support IPv6, but S60 users generally don't know or care about IPv6. And, people who know what IPv6 is do not want to use S60.

Android 2.3.4 has some new IPv6 code added that helps with IPv6, but we are still waiting on the OEMs to produce the required solution (including devices specific RIL) to make Android phones work with IPv6.

I am crossing my fingers that Meego will provide IPv6 support.

[Radu]

That's odd, it should show up in the list of connections whenever you have a cell signal. You can try removing your v6 connection by running: "/usr/bin/register_3g_ipv6 deinstall"

If you want to re-add the v6 connection after you deinstall, you just need to run "/usr/bin/register_3g_ipv6 install"

Well, I didn't do that, but I have a desktop widdget called ConnectNow, where you can spawn multiple instances on it on your desktop and select a connection for each one of them. So I designated one for IPv4 and it worked just fine, without removing the IPv6 NAT.
The standard thing that lets you switch connections is really broken for me, it's one of the things that I hate the most at the N900.

[tmojoe]

here comes the big day http://worldipv6day.org/

[stlpaul]

Happy ipv6 day :) So far everything seems to be working for me.

[martycollinsesq]

Question: if you get hspa+ speeds with a even more plus dumbphone plan you still test ipv6? I was approved for beta, I installed per ddrone. thanks

[stlpaul]

Question: if you get hspa+ speeds with a even more plus dumbphone plan you still test ipv6? I was approved for beta, I installed per ddrone. thanks

Yep, if you have any kind of working internet on your n900 it should work with the IPv6 beta, too.

[bunanson]

You ALL IPv6 netizen pay attentions: the new android gingergreat 2.3.4 has IPv6 built-in!!!

Unannouned Easter bunny from android!

Somebody now in tmobile zone see whether nitdroid works. I will be in pittsburgh next week. Cant wait to try it out.

bun

[bunanson]

Hey, would some of you ipv6 netizens wake up, please? anybody test it yet or I am the only with ipv6 and nitdroid 2.3.4? I am not in a tmobile zone, cannot test it. I would be in a couple of week. Very anxious to see whether nitdroid 2.3.4 can get online.

bun

[Radu]

What phone are you using?

[bunanson]

n900

how about yours, n901 :) ?

bun

[Radu]

I thought you actually had an Android 2.3.4 phone

[bunanson]

Hi, everybody, its me :)

Just wondering if anybody has tried mobile hotspot or jakui hotspot? would install this hotspot program causing any problems with the IPv6 problem? Thanks


bunanson

[bunanson]

Hi, anybody has problem getting the IPv6 work? I was away from the use for 3 month, and it worked beautiful for 24 hr yesterday, and now it is dead. Not quite sure whether it is the account? or the program. Any suggestions where to look?

TIA,

bun

[bunanson]

I used the debug to look at it, it turned out to be:

Attach failed (try disconnecting),,,,using default apn

acccording to this, the solution is re-install the latest lib...

Would re-install the whole ipv6 help? I hate to lose the skype upon doing that

TIA,

bun

[geneven]

I didn't realize the ipv6 beta test was still going.

[tmojoe]

Yep, it's still going. In fact, SF Bay area now has native IPv6 on the default epc.tmobile.com APN and the first Android T-mobile IPv6 capable (but still IPv4 default) phone has launched. Some info here https://sites.google.com/site/tmoipv6/lg-mytouch

[Radu]

tmojoe, thanks for that link. You guys seem to move fast :)
Any idea when the beta will end? Last time I've seen one of your posts on this matter you said by the end of the year. Do you still plan to end it by the end of the year, or are you extending it a bit?

[tmojoe]

tmojoe, thanks for that link. You guys seem to move fast :)
Any idea when the beta will end? Last time I've seen one of your posts on this matter you said by the end of the year. Do you still plan to end it by the end of the year, or are you extending it a bit?

There is no planned end of the beta for now. We'll continue working to make it so that a beta is not needed.

[Joe Cool]

I recently had ipv6 turned on for me and managed to get it running using the instructions found here:
http://n900-ipv6.garage.maemo.org/
I live in an 2.5G area but frequent a city which is 4G. Twice this week I have had the ipv6 working where I live but when I visit the 4G city I have a ipv6 address (disconnecting then reconnecting shows gprs1 with what appears to be a valid address) but am unable to use ipv6 DNS.


N900:~# ping6 -c 4 www.google.com
ping6: bad address 'www.google.com'


This website http://test-ipv6.com/ says "IPv6 connections work, but connections using DNS names do not use IPv6. For some reason, your browser or your OS is not doing IPv6 DNS 'AAAA' lookups."
Has anyone experienced something similar?
FYI - When I went back to 2.5G, kame.net did work and test-ipv6.com was fully successful. Also, I am currently running the bfs9 kernel.

Thank you for your time.

[addisjon]

Hey Guys,

Thanks for the great work! I managed to get my ipv6 connection working using the instructions here: http://code.google.com/p/n900ipv6/wiki/README

After installing the libicd-network-3g-ipv6_1.4_armel.deb package, setting the apn to the one provided by the beta test (epc-xxxxx000.t-mobile.com), and configuring the browser to use ipv6, I now see the swimming turtles at http://www.kame.net. Also http://test-ipv6.com/ returns 10/10 for ipv6 performance.

After this I installed the nat64d_1.1-1_armel.deb package as I need to have TOR working. Unfortunately it never connects. Skype also doesn't work.

And I'm also only seeing EDGE speeds from the various speed tests (with a solid 5 bars of 3G/3.5G). Is the speed limited by the data plan? I have an unlimited 2G data plan but was under the impression from this thread that using the ipv6 beta test would provide 3G speeds.

Thanks for any feedback.

[geneven]

Someone posted an updated nat64 package very recently. You might search for the message and try it. It wasn't in this thread, unfortunately.

[Radu]

Do you happen to have a link for that?
Edit: Nvm, found it: http://talk.maemo.org/showthread.php?t=80958&highlight=nat64

[Mentalist Traceur]

I finally got myself internet data on my plan, and signed up for the beta shortly after (within 24 hours). Today I spent all day working on it.

I noticed, for starters, that the ccinternet2.t-mobile.com APN didn't work for me, and that my e-mail confirming my T-Mobile IPv6 beta activation contained a different APN address that did work.

Is T-Mobile just giving different APNs out to customers on the beta in different regions or something?

At any rate, I found that following this: http://n900-ipv6.garage.maemo.org/

...worked fine for me, although everything worked for me with this as my /etc/resolv.conf file:
nameserver ::1
nameserver 127.0.0.1

I do not have an IPv6 only WiFi network to see if not having a specific address in resolv.conf for IPv6 instead of ::1 (which is localhost, like 127.0.0.1) breaks anything, but I think it won't.

I did however notice that having the IPv4 entry first in resolv.conf broke my ability to get IPv6 DNS resolution, whereas both IPv4/6 work if I have the IPv6 locahost entry first.

*Shrug* The whole resolv.conf thing is rather confusing to me, but I just thought I should point out that you don't have to use "nameserver 2001:470:b:c8::1" as suggested by the link about, or "nameserver [T-Mobile's nameserver]" in your /etc/resolv.conf file itself (especially since T-Mobile's DNS nameserver address can be added by the script that adds the gprs1 interface from the above link anyway - I'm also not sure it'd be ideal to be using the T-Mobile DNS server for, say, WiFi browsing on non-T-Mobile IPv6 networks). Since the default in that file is "nameserver 127.0.0.1", it seems to me that the 'proper' way is to use localhost address in IPv6 in that file as well for the /etc/resolv.conf nameserver entry, and leave the actual DNS resolution to 'upper' settings/services. I presume localhost addresses for nameservers lead to resolution using dnsmasq (spelling?) on first try, so it seems if you need special provisions on the N900 for IPv6-only networks, there's better ways to do it then set an external nameserver in the /etc/resolv.conf.

[guylhem]

Hello

(repost from [Development] kernel-power following a suggestion)

I have a working ipv6 wifi network at home (fritzbox, ipv6 tunnels, etc)

The n900 gets an ipv6, which I can ping6 from the lan and which can ping6 to the lan as well, but that's all - it can not ping6 external machines, or wget -6 from them, while they are properly resolved.

ip -6 route shows the proper route - identical to other machines on the lan. /proc/sys/net/ipv6/conf/all/disable_ipv6 is not set

I haven't found similar reports of this problem. I'd like to keep ipv6 but it also causes problem with my google talk account, which works only if I disable ipv6 :-/

Any idea is welcome.

[guylhem]

My fault here.

Somehow my ISP changed my static IPv4 (duh!)

The problem was with all the machines on the wifi lan - it just started showing on the n900. A quick change to the ipv6 tunnel and it works fine now.

[unicorn]

Is the beta test over? I haven't been able to use T-Mobile's IPv6 in a couple of days. It appears to connect, but it's not useable. The host command at the command line always results in a "Nameserver not responding" error. The nameserver should be fd01:353:e973:99ac::7, correct? If I ping that address, I get 100% packet loss. The Linux Kernel for power user was updated to version 2.6.28.10 just prior to this problem but it continued to work for the duration of the session. I don't remember it I rebooted in between that session and the next one that didn't work. Could this be related, or is the beta test over?

[stlpaul]

Is the beta test over? I haven't been able to use T-Mobile's IPv6 in a couple of days. It appears to connect, but it's not useable. The host command at the command line always results in a "Nameserver not responding" error. The nameserver should be fd01:353:e973:99ac::7, correct? If I ping that address, I get 100% packet loss. The Linux Kernel for power user was updated to version 2.6.28.10 just prior to this problem but it continued to work for the duration of the session. I don't remember it I rebooted in between that session and the next one that didn't work. Could this be related, or is the beta test over?

ccinternet2.t-mobile.com has been decommissioned. They are rolling out official IPv6 support on the standard APN on a city-by-city basis. Until then we are supposed to use epc-scpcf000.t-mobile.com for IPv6 -- however, it doesn't work for me. Anyone else have better luck?

[unicorn]

Thanks for that information. Unfortunately, it doesn't work for me, either. Anybody else have any ideas?

[Radu]

Tried that too, also didn't work :/

[geneven]

Is there a list of cities where ipv6 has been rolled out? I wonder if that affects me as a Simple Mobile customer. Simple Mobile uses the t-mobile network.

[stlpaul]

epc.tmobile.com works for ipv6 for me now, using the package from https://code.google.com/p/n900ipv6/ and setting custom apn using the instructions on the wiki

[tmojoe]

ccinternet2.t-mobile.com has been decommissioned. They are rolling out official IPv6 support on the standard APN on a city-by-city basis. Until then we are supposed to use epc-scpcf000.t-mobile.com for IPv6 -- however, it doesn't work for me. Anyone else have better luck?

to get access to epc-scpcf000 you must sign up at https://sites.google.com/site/tmoipv6/lg-mytouch , but you should check to see if epc.tmobile.com works for you first.

[stlpaul]

Updated nat64d for epc.tmobile.com APN is available here:
http://talk.maemo.org/showpost.php?p=1185461&postcount=5

[Radu]

I got a Samsung Galaxy Nexus, and it didn't work with epc-scpcf000.t-mobile.com Maybe the IPv6 flag from my account was deleted? I filled the form again, hope it will work.

[tmojoe]

FYI, the network deployment is now complete. So, no more whitelist. Any one with an IPv6 capable phone such as the n900 can now connect to epc.tmobile.com without any special network side setup.

[Mentalist Traceur]

I thought people should know, in case, like me, it took them over a month to finally stumble upon this info:
The current production IPv6 DNS address on T-Mobile is fd00:976a::9

Because, since around the time the production epc.tmobile.com IPv6 APN started rolling out, until I managed to stumble upon someone mentioning that nameserver address in one of the posts on the Google Group for this beta, I've been stuck unable to get DNS lookups working, (using method described here for dual-stack IPv4/IPv6: http://n900-ipv6.garage.maemo.org/ )