Re: IPv6 T-Mobile US Beta Test
 

I thought you actually had an Android 2.3.4 phone

Re: IPv6 T-Mobile US Beta Test
 

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

Re: IPv6 T-Mobile US Beta Test
 

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

Re: IPv6 T-Mobile US Beta Test
 

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

Re: IPv6 T-Mobile US Beta Test
 

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

Re: IPv6 T-Mobile US Beta Test
 

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

Re: IPv6 T-Mobile US Beta Test
 

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?

Re: IPv6 T-Mobile US Beta Test
 

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

Re: IPv6 T-Mobile US Beta Test
 

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.

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.

Re: IPv6 T-Mobile US Beta Test
 

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.

Re: IPv6 T-Mobile US Beta Test
 

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

Re: IPv6 T-Mobile US Beta Test
 

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

Re: IPv6 T-Mobile US Beta Test
 

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:
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.

Re: IPv6 T-Mobile US Beta Test
 

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.

Re: IPv6 T-Mobile US Beta Test
 

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.

Re: IPv6 T-Mobile US Beta Test
 

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?

Re: IPv6 T-Mobile US Beta Test
 

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?

Re: IPv6 T-Mobile US Beta Test
 

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

Re: IPv6 T-Mobile US Beta Test
 

Tried that too, also didn't work :/

Re: IPv6 T-Mobile US Beta Test
 

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.

Re: IPv6 T-Mobile US Beta Test
 

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

Re: IPv6 T-Mobile US Beta Test
 

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.

Re: IPv6 T-Mobile US Beta Test
 

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

Re: IPv6 T-Mobile US Beta Test
 

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.

Re: IPv6 T-Mobile US Beta Test
 

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.

Re: IPv6 T-Mobile US Beta Test
 

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/ )