Re: IPv6 T-Mobile US Beta Test
 

@scribbles you may want to try again. The T-Mobile IPv6 DNS64 server failed last night but seems to be fixed now.

Re: IPv6 T-Mobile US Beta Test
 

Looks like you are using the HE DNS which will by-pass the T-Mobile DSN64 service, and since 127.0.0.1 is first, i think you will just use the T-Mobile IPv4 DNS most of the time, which does not serve the Google IPv6 DNS records.

My suggestion is that your /etc/resolv.conf look like this to best use the local T-Mobile DNS64 as well as receive the native IPv6 content

namerserver 2607:FB90:BEEF:A::1

This name server should have the lowest latency since it is on the T-Mobile network and also serves the native google / youtube IPv6 content

Re: IPv6 T-Mobile US Beta Test
 

I think I figured out what my problem is. It seems I have followed two sets of instructions---->IPv4+IPv6 and the other is a pkg installed for IPv6 only

What is the command for removing the IPv6 only pkg (libicd-network-3g-ipv6_1.2_armel.deb) as I believe this is what's giving me problems?? I just need the dual-stack ipv4+ipv6.

Re: IPv6 T-Mobile US Beta Test
 

as root:

Re: IPv6 T-Mobile US Beta Test
 

Thank you sir...

Re: IPv6 T-Mobile US Beta Test
 

Thanks. I will try your suggestion. The way I have it set up now gives me as much speed as I want, though more is always welcome...I was suspicious that namerserver was correct, but it works just fine.

Re: IPv6 T-Mobile US Beta Test
 

I've setup IPv6-only on my N900 and it's working well enough that I've left it as the default. Web, email, and Google Talk work just fine. Dialcentral, The One Ring and Mail for Exchange do not work over IPv6, unfortunately.

IPv6 doesn't seem to work on my private network, however. I'm running radvd and my other PCs and laptops pick up a global IPv6 address automatically, but the N900 only sets up the local link one. Even if I manually add in an IP in my subnet using iproute, I'm not able to ping6 anything, local or outside.

Does anyone have their N900 working on the LAN?

Re: IPv6 T-Mobile US Beta Test
 

I am late to the party, but I also want to jot down something so that I can follow myself in case I have to redo this.

I went thru the nitdroid 0.0.7 installation, later upgraded to 0.0.8, http://talk.maemo.org/showthread.php?t=61338, and that is the status of my N900.

A) I started by following this, http://n900-ipv6.garage.maemo.org/, "enabling IPv6 thru linux kernel", and nothing happened. I proceeded to "Setting IPv6 Connectivity with builit-in web server", go about:config and flip the disabling ipv6 filter.

B) I then tried this, http://code.google.com/p/n900ipv6/wiki/README,
I followed the Steps to install
========================================
* grab the kernel-power package from extras
* put the 3g_ipv6 package on your n900: libicd-network-3g-ipv6_1.2_armel.deb
* install the package as root (dpkg -i libicd-network-3g-ipv6_1.2_armel.deb)
* run /usr/bin/register_3g_ipv6 install
* (Did not do) If you still have the "3G ipv6" connection from the non-packaged version, delete it with: /usr/bin/register_3g_ipv6 remove-old
* reboot
============================================

C) And followed this, http://groups.google.com/group/tmoip...-on-your-nokia

On N900, Settings>Internet Connections>Connect automatically> Always ask.
Connections>Edit>IPv6 (Red in color, wont miss it)
=======================
3 Enter the name ccinternet2.t-mobile.com and tap OK.
4 Select the new Internet access point you just made, ccinternet2.t-mobile.com
=======================
Done>Save>Save.

reboot N900

Now on your status bar, you should see a big big large, lovely sweet, red "v 6"
Use any editor, modify /etc/resolv.conf
===========================
nameserver 2607:FB90:BEEF:A::1
# nameserver 127.0.0.1
===========================

when using wifi, have to change back to 127.0.0.1

check: go webserver, www.whatismyv6.com

What is the advantage of this exercise, FAST, as fast as wifi!

Useful links:
http://www.maemonokian900.com/maemo-...-and-facebook/
http://myn900.wordpress.com/2010/09/...-beta-service/

website support ipv6 so far:
google chrome, firefox, ipv6.google.com

No pic, no story, here are the pics, see the big (white) 6 on top of the green dot, and notice, I am online, but the homeip was read (no IP found) :-)

Enjoy,

bun

Re: IPv6 T-Mobile US Beta Test
 

FYI, anyone: Installing the firmware PR1.3 disabled my ipv6 connection, but I just reinstalled and all is well again.

Re: IPv6 T-Mobile US Beta Test
 

I found bunanson's comment above to be true:

Use any editor, modify /etc/resolv.conf
===========================
nameserver 2607:FB90:BEEF:A::1
# nameserver 127.0.0.1
===========================

when using wifi, have to change back to 127.0.0.1


Does anyone know how to make this change in resolv.conf automatically when switching from wireless to an ipv6 connection? I don't know anything about Linux scripting.

Re: IPv6 T-Mobile US Beta Test
 

You should not need to edit /etc/resolv.conf. Using 127.0.0.1 means use the local program "dnsmasq". dnsmasq gets the nameserver to query from /var/run/resolv.conf.gprs (among other files named resolv.conf* in /var/run). My libicd-network-3g-ipv6 package creates this file when you connect.

Are you using libicd-network-3g-ipv6? What happens when you use 127.0.0.1 in /etc/resolv.conf and you're on ipv6?

edit: it just occured to me that you could be using meego instead of maemo. If that's the case, then disregard this message.

Re: IPv6 T-Mobile US Beta Test
 

I'm not using Meego.

127.0.0.1 works fine in /etc/resolv.conf when I'm using ipv6.

Yes, I'm using libicd-network-3g-ipv6.

If I shouldn't edit resolv.conf that's fine.

What exactly should I do with the suggestion that

"My suggestion is that your /etc/resolv.conf look like this to best use the local T-Mobile DNS64 as well as receive the native IPv6 content

namerserver 2607:FB90:BEEF:A::1

This name server should have the lowest latency since it is on the T-Mobile network and also serves the native google / youtube IPv6 content"

as is posted above?

Re: IPv6 T-Mobile US Beta Test
 

Long answer: That's automatically done for you by libicd-network-3g-ipv6. It just puts the dns server in /var/run/resolv.conf.gprs (where dnsmasq looks for it) instead of /etc/resolv.conf (which disables dnsmasq's cache)

Short answer: you don't have to do anything

Re: IPv6 T-Mobile US Beta Test
 

manually editting /etc/resolv.conf is more for this method, http://n900-ipv6.garage.maemo.org/

It is not needed for the y libicd-network-3g-ipv6 method.

Re: IPv6 T-Mobile US Beta Test
 

Is ipv6 access using the libicd method currently working? Used to work for me way back in September but now I get an "Internet Connection Failed" popup when trying it.

Re: IPv6 T-Mobile US Beta Test
 

I had to reinstall the power kernel after updating to PR1.3. I'll have to make the error message clearer for my next update to libicd-network-3g-ipv6.

You can check to see if this is the problem by running "uname -r". If it says something like "2.6.28.10power40", that's the power kernel. If it says something like "2.6.28-omap1", that's the nokia kernel and you have to reinstall the power kernel.

If that's not the problem, let me know.

Re: IPv6 T-Mobile US Beta Test
 

The problem was simpler... the authorization to use ipv6 on my T-mobile account had dropped out... I was re-authorized and all is well now. I am still on PR1.2... thanks for your report on PR1.3.

Re: IPv6 T-Mobile US Beta Test
 

Wow, t-mobile dropped you? That made members number dropped from 77 to 76! Does anybody know how precious you are? The total number of betatesters is only 77... freightening small for such utmost important beta!

bun

Re: IPv6 T-Mobile US Beta Test
 

A friend of mine who is not a member of this forum tried to join the beta and her application was ignored. I guess they check whether you are a member here.

Re: IPv6 T-Mobile US Beta Test
 

How do you know you were dropped?? I'm having a problem getting iPv6 access after PR 1.3 and I've even email Cameron about it. I have been running the iPv4/iPv6 setup (http://n900-ipv6.garage.maemo.org/) for a couple of months and everything was fine until the upgrade. I've gone so far as to delete the scripts and download them again and configure them and I still can't get access. It made me wonder if they dropped me for some reason. I think I will email Cameron again...

Re: IPv6 T-Mobile US Beta Test
 

Did you reinstall the power kernel after updating to PR 1.3?

Re: IPv6 T-Mobile US Beta Test
 

No, I didn't have to. I did however had to re-install the kernel for power user settings (v0.11). After PR 1.3 I checked in xterm and the kernel was there, just not enabled.

Re: IPv6 T-Mobile US Beta Test
 

A guess, you might say... I had read elsewhere that the ipv6 authorization settings on the account are prone to drop out when the account is modified -- this being a beta program after all. Before, I had tried re-installing and configuring the libicd package and still I was getting apn connection failures. Sure enough, soon as Cameron re-authorized the account I was able to connect successfully!

Re: IPv6 T-Mobile US Beta Test
 

Being dropped is a result of the beta status. It is most often triggered by the user doing an account update (calling customer care, upgrading ...), which then triggers the account to be overwritten without the flags for the IPv6 beta program.

Re: IPv6 T-Mobile US Beta Test
 

You should ask your friend to try again. The beta is open, but the beta status means there are some manual processes and mistakes can be made. The only people that get rejected are iphone and android users, since their devices do not support IPv6 on the mobile network .... maybe someday.

Re: IPv6 T-Mobile US Beta Test
 

Ok, to get more info on what's going on, you can put libicd-network-3g-ipv6 into debug mode:

[run these commands as root, it'll disconnect you]
initctl stop icd2
/usr/sbin/icd2

This will print out the connection messages to your terminal.

If it's a matter of not having ipv6 support, it'll say:
ifconfig: socket: Address family not supported by protocol

If it's something else, it should say something like:
[X] failed (com.nokia.[Y]): [Z]

That error message should hint to what's going wrong.

After you're done with debugging mode, you can turn it back off with:

[this will disconnect you again]
hit control-c and you'll get a prompt back
initctl start icd2

Re: IPv6 T-Mobile US Beta Test
 

Thanks for your help gentlemen.... After Cameron verified that my account was still good, I decided to do some deeper file checking and in a slew of sloppy script writing *facepalm*, I found the problem and all is good. After visiting www.whatismyv6.com to verify my connectivity, www.v6.facebook.com and ipv6.google.com were also done swiftly. And of course the swimming turtle...

Re: IPv6 T-Mobile US Beta Test
 

I got accepted in the Beta today, and I followed the instructions here: https://code.google.com/p/n900ipv6/wiki/README
Everything was OK, the IPV6 connection was created, I changed the APN to ccinternet2.t-mobile.com, but still can't connect. I only have 2.5g here, could this be a problem?

When I try:
initctl stop icd2
/usr/sbin/icd2
icd2 will seg fault each time I try the ipv6 connection (but works fine with wifi).

Any ideas?

Re: IPv6 T-Mobile US Beta Test
 

2.5G is fine. I'm able to connect if I force it to only use 2G

Does it print any messages before it segfaults?

such as:

using non-default apn: ccinternet2.t-mobile.com
Attached: GPRSAttach
Available

Does it crash after you select the v6 connection, or when it presents you with a list of connections, or right after starting icd2?

Re: IPv6 T-Mobile US Beta Test
 

When I start icd2, it will stay there and do nothing indefinitely. However, as soon as I tell it to connect using the 3G ipv6 connection, it will say:
using default apn
seg fault

Re: IPv6 T-Mobile US Beta Test
 

I build a new version (1.3) and put it up on google code:
http://n900ipv6.googlecode.com/files..._1.3_armel.deb

This version will print out three additional messages:

before attach
before QuickConnect
after QuickConnect

Please install this version (just requires a dpkg -i and then restart icd2) and let me know what messages it generates.

Re: IPv6 T-Mobile US Beta Test
 

Wow, I tried your new version and now it actually works!! I can go to websites and stuff (a bit slow since it's only 2.5G and I have a bad signal, but it works!). You are the best :)

P.S. Is Skype supposed to work? Because it seems that my Skype won't connect over the cellular network.

Re: IPv6 T-Mobile US Beta Test
 

Nice! Glad it works.

It looks like Skype is trying to connect to IPv4 address directly. It probably won't work on v6 only connections.

Re: IPv6 T-Mobile US Beta Test
 

hi, i think i am not ready for ipv6. due to i have trouble connecting it. so i would like to roll back to ipv4. how do i uninstalled it. i did removed using xterm n reboot. i still cant connect to internet. can anyone show me how to get back to connect to ipv4?

thanks.

Re: IPv6 T-Mobile US Beta Test
 

Is the v6 connection still listed in your choices of networks to connect to? What happens when you try to connect manually to the v4 network?

Re: IPv6 T-Mobile US Beta Test
 

Is there any IPv6 voice chat option? It seems that Gtalk can only send/get text messages over IPv6, and it will not work if I try to talk to someone with an IPv4 connection.

Re: IPv6 T-Mobile US Beta Test
 

@ ddrown

HI thank for help. i think eerything was fine, just becuase i didnt got confirmed message from TMO about my v6. i got it today and installed again right away. at first installed, it worked great, faster down n upload speed. i can login with only google but not yahoo and skype (i knew cos its not support v6) its okay, but i found out my google can only chat but cannot make a call. i always video and voice call through google talk, but not anymore, i called her, the status stayed connecting forever..... she called me i picked up....it coneecting forever. so i assumed its not work. when i get home from work today. i have tried install script using dualstack, without remove IPV6 only deb package out of my n900. i've experience my ipv6 only connection not connect to any gtalk cutetube yahoo skype and also cannot go to youtube.com. that even put me in bad situation.

i've done the speed test, and chekc ip v6, i am everything right, but my speed isnt different from ipv4 before.
my speed test at work place using only ipv6 is UP: 1mb DW: 1.98mb
my speed test at home using dual stack is UP: 0.53mb DW: 0.48mb
i was wonder what a problem, so i test with only ipv6 i got the same number as dual stack. so i assumed that because its was different tower different location.

i really need skype n google talk to work. cos that the reason i buy n900

i am i saying it clear: i think its kinda complicate.
thanks

Re: IPv6 T-Mobile US Beta Test
 

ok yeah, I'm sure skype won't work on v6 only currently. I expect that google talk voice/video is in a similar situation. To work around that, you will have to either connect with v4 only, or use the dual stack setup.

I can only hope that someone will update skype/google talk to support v6. Theoretically, it would be easier than dealing with nat on v4.

Re: IPv6 T-Mobile US Beta Test
 

I have something I've been experimenting with that fixes some of the problem applications. With it, I was able to get The One Ring (Google Voice) working on my v6 connection. Unfortunately, skype still doesn't work.

I have more details at: http://code.google.com/p/n900ipv6/wiki/LDPreloadNat64

Re: IPv6 T-Mobile US Beta Test
 

Installed, rebooted, The One Ring works. Tested GeePS, fails to load, gives a segfault. GeePS works with the IPv4/IPv6 connection, but not on IPv6 only (w/o fix).

Temporarily uninstalled due to wifi bug (disconnect/reconnect wifi and it works). Is this just the first time after reboot, or the first time after the IPv6 connection?