Re: IPv6 T-Mobile US Beta Test
 

That is correct. If both http://ipv6.whatismyv6.com and http://66.117.47.214 work, then you have both ipv4 and ipv6

Re: IPv6 T-Mobile US Beta Test
 

Thanks its working great. :)

Re: IPv6 T-Mobile US Beta Test
 

I got geePS worked only once. After rebooted, it wont open again. Currently everything works, except GeePS and Skype. Any suggestions where to look? Or should I redo ddown's 1.3 (http://code.google.com/p/n900ipv6/wiki/LDPreloadNat64) version again? Well, I am NOT as techie as other guys :( , I hope I am teachable :)

I can connect to IPv6 and switch back and forth to wifi without problems. Thank you ddown for your hardwork.

N900, OS1.3, power kernel 45, OC, using ddown 1.3 script.

TIA,

bun

Re: IPv6 T-Mobile US Beta Test
 

bun-

skype probably isn't going to work according to what ddown has posted. I haven't had any problems with GeePS not working.

However, yesterday afternoon, I was getting a very slow data connection (v4 & v6). It was causing RadioTimeToGo to crash. Later that evening in a different room, my connection was better, and RTTG was working just fine.

I'm guessing if RTTG doesn't get a response back from the internet, it times out and crashes. I'll bet GeePS is the same.

Maybe give it a couple of hours, or try a different location?

Re: IPv6 T-Mobile US Beta Test
 

Just wanted to confirm that pretty much that I tried works, including ssh and gtalk voice. The only not working thing is Skype, which is a shame, because with Skype working there is no need to use cellphone minutes.

Re: IPv6 T-Mobile US Beta Test
 

Tks.

I did the whatismyipv6address.com test, I was able to connect to ipv4 only test and ipv6 only test. I think that means I can connect to both.

My GeePS still wont connect. It loads for a second, then quit by itself. I know I was able to connect to GeePS right after ddown's script, and in fact I used it for half an hour, and now it cannot connect any more. Oh sure, it connects when switch to wifi.

I am using Modrana on ipv6 and has no problem.

App manager runs without any problem

Ovi Maps runs, no problem

so does The One Ring/GVoice, no problem

I am OC limits to 950,500, switched to 600,250, still cannot load GeePS

bun

Re: IPv6 T-Mobile US Beta Test
 

Just curious what is the tentative date for the beta test to end?

Thanks

Re: IPv6 T-Mobile US Beta Test
 

I hope never :-)

Re: IPv6 T-Mobile US Beta Test
 

I also hope that it will never end, but realistically it will probably end in the summer or earlier, as the new Android devices will support IPv6.

Re: IPv6 T-Mobile US Beta Test
 

The plan is that the beta will continue until after the production IPv6 service is launched towards the end of 2011.

Re: IPv6 T-Mobile US Beta Test
 

has anyone had issues with fmms with IPv6? i get the notification but can't download image, running in havoc mode. i see fmms uses IPv4 addresses in its settings.

Re: IPv6 T-Mobile US Beta Test
 

Oh I see. fmms brings up a second interface on the phone network. It then tries to connect to the mms server over that interface. That won't work when libnat64 is active. fmms should work in polite mode (have to disconnect from ipv6 connection), or havoc mode when you're on wifi. I'm not sure how to make libnat64 compatible with what fmms needs.

Re: IPv6 T-Mobile US Beta Test
 

When I tried to share my ipv6 connection using Mobile HotSpot with my N810, I got the message from TMobile that I don't have a data plan. True (for the N810) but I thought I would be able to share the N900 ipv6 connection without buying a new data plan. Is this the way it's expected to work?

Re: IPv6 T-Mobile US Beta Test
 

You would only get that response from the IPv4 APN, not the IPv6 APN. So, my guess is that you were sharing the IPv4 network not the IPv6 network.

Re: IPv6 T-Mobile US Beta Test
 

I assume you're talking about the app "Mobile HotSpot" for the n900. That app is only going to work with an ipv4 connection, because it requires an ipv4 address on the GPRS side.

Since the gprs ipv6 connection is a /64, you can route that to your wifi and give everyone a public address. I've been meaning to setup a script to do this (along the lines of what Mobile HotSpot does, but for ipv6). I even have radvd compiled for the n900, so automatic address configuration works.

Re: IPv6 T-Mobile US Beta Test
 

That would be AWESOME. I think some of the other handset guys have looked at doing this an L2 bridge while proxying the ND

Re: IPv6 T-Mobile US Beta Test
 

Ok, I setup a simple shell script and uploaded my radvd package. This uses routing instead of bridging.

http://code.google.com/p/n900ipv6/wi...nectionSharing

I have it use an ipv4 subnet for DHCP (to hand out the DNS address), as well as local DNS traffic. Any device connected this way is going to have the same problems (IPv4 literals) as the handset.

Re: IPv6 T-Mobile US Beta Test
 

I was thinking about ways of handling nat64 on the handset that works with tethering. I came up with something else (incompatible with the libnat64 library):

http://code.google.com/p/n900ipv6/wiki/Nat64D

As a bonus, skype works now. Also, fmms in havoc mode should work with it.

I still need to update the ipv6-share script to work under this, but it'll be possible.

Re: IPv6 T-Mobile US Beta Test
 

Before I install it, can you please clarify a few things?
1. "The scripts /etc/network/if-up.d/nat64-up and /etc/network/if-down.d/nat64-down start and stop the nat64d process."
Does the script need to be started manually, or is it started automatically at reboot?

2. Is it necessary for the script to be started in order for Skype to work?

Thanks.

Re: IPv6 T-Mobile US Beta Test
 

Uninstalled libnat64 1.3, installed nat64d, reboot

Gtalk works, skype doesn't, geeps loads, but doesn't get gps info from internet.

When I start xterm, I see the following message repeated 6x :
ERROR: ld.so: object '/usr/lib/libnat64.s0' from /etc/ld.so.preload cannot be preloaded: ignored.

Let me know if more info is needed.

Re: IPv6 T-Mobile US Beta Test
 

The scripts in /etc/network are run automatically when your network connection comes up. So you don't have to run anything.

Re: IPv6 T-Mobile US Beta Test
 

Ah. For that error message, edit /etc/ld.so.preload and delete the line that says /usr/lib/libnat64.so

for skype, can you login? Does it just give you the "unable to connect to one or more accounts"

Can you check to see if you have a default route? (ip route list exact 0.0.0.0/0)

for the gps problem, I still need to research it.

Re: IPv6 T-Mobile US Beta Test
 

Ok. I uploaded nat64d version 1.1. That should fix the route problem, which is what probably caused your problems with skype and gps based on cell tower.

With this version, my phone gets a "coarse accuracy" location with the location-home-applet package, geeps package, and ovi maps.

Re: IPv6 T-Mobile US Beta Test
 

OK, installed new version, everything appears to work now (skype, sip, gtalk, TOR, GeePS).

Still had to fix ld.so.preload. No big deal.

Thanks for the hard work.

Re: IPv6 T-Mobile US Beta Test
 

The ld.so.preload file was supposed to be fixed with the command "/usr/bin/register_nat64 deinstall" (has to happen before removing the libnat64 package). This is documented on the wiki for ldpreload, but I should probably just add it to a deinstall script in the libnat64 package.

Glad to hear it's working!

Re: IPv6 T-Mobile US Beta Test
 

Ok, so how do I uninstall libnat64?

Re: IPv6 T-Mobile US Beta Test
 

Two commands (as root):

/usr/bin/register_nat64 deinstall
dpkg -r libnat64

Re: IPv6 T-Mobile US Beta Test
 

Ahh, my fault then, didn't run the deinstall, just removed it with dpkg. Too much plunging ahead, not enough reading. (Although in your favor, it was working well enough that I hadn't needed to remove it prior to the new version :) )

Re: IPv6 T-Mobile US Beta Test
 

Is it possible that the new Nat64D is eating battery more than LDPreloadNat64? Two days ago I installed the new Nat64D (nothing else changed on my phone) and now the battery is out in about one day.

Re: IPv6 T-Mobile US Beta Test
 

I'm not sure about this, but unscientifically, it seems to me that both were draining more power than the regular IPv6 connection. In other words the latest updates that do the nat portion so the IPv4 only stuff works, seems to draw more.

I can't say if the new nat64d is drawing more that the ldpreload version though.

Re: IPv6 T-Mobile US Beta Test
 

I don't think nat64d should be using a significant amount of CPU time. You can check this by running:

cut -d" " -f14-17 /proc/`pgrep nat64d`/stat

This will show four numbers: User CPU, System CPU, Child Process User CPU, and Child Process System CPU. They are in units of 1/100th of a second.

You can also check to see how much traffic has gone through the nat64 process with:

/sbin/ifconfig nat64

I haven't personally noticed any difference in battery usage, but I'll have to compare a day's usage on ipv6 vs ipv4 in battery-eye.

Re: IPv6 T-Mobile US Beta Test
 

This one returns: 33 214 3 0

RX: 3.6 MiB, TX: 3.6 MiB

I suppose it's something else eating the battery not the nat64.

Re: IPv6 T-Mobile US Beta Test
 

I tested the new version, and it works great, I think Skype works well too, but no one on Skype when I tried to test it. However, I did hear the ringing stuff, so I am assuming everything works well.

Re: IPv6 T-Mobile US Beta Test
 

Just came to say thanks for continuing to develop and maintain these packages. It works great and it's very easy.

Re: IPv6 T-Mobile US Beta Test
 

Would you or someone please drop a few lines about the installation? I am still with the original version. Thanks.

bun

Re: IPv6 T-Mobile US Beta Test
 

If you installed the ld_preload package, use the uninstall instructions at: http://code.google.com/p/n900ipv6/wiki/LDPreloadNat64

After that, the install instructions are at: http://code.google.com/p/n900ipv6/wiki/Nat64D

Re: IPv6 T-Mobile US Beta Test
 

Some not so new news? http://www.eweek.com/c/a/IT-Infrastr...-Wings-287643/

bun

Re: IPv6 T-Mobile US Beta Test
 

I've had my N900 working great with IPv6 on T-Mobile for quite awhile, and have just recently been trying to tether my laptop to it, but haven't had any luck. I run "ipv6-share start" on the N900, and then "dhcpcd usb0" on the laptop, and this is what I get:

dhcpcd: version 5.2.2 starting
dhcpcd: usb0: checking for 169.254.208.219
dhcpcd: usb0: using IPv4LL address 169.254.208.219
dhcpcd: forking to background

Why is it giving me that address? I also have a valid IPv6 address, but no name servers in /etc/resolv.conf, so nothing gets resolved. I can ssh into the N900 using it's IPv6 address, but I can't connect to anything on the Internet by name, IPv4 address, or IPv6 address. Trying to ssh to an IPv6 address results in "Name or service not known" and trying to ssh to an IPv4 address results in "Network is unreachable".

According to whois.arin.net (using the whois command), the IPv4 address I'm getting is a link local address, and "Hosts obtain these addresses by auto-configuration, such as when a DHCP server cannot be found", but it's obviously finding the N900's DHCP server or it wouldn't be getting the correct IPv6 address (from T-Mobile's 2607:fb90:: block).

Looking at the ipv6-share script, it looks like I should be getting an address between 10.255.255.10 and 10.255.255.100, so why am I getting that link local address instead?

Re: IPv6 T-Mobile US Beta Test
 

Are you using the libnat64 library? If you are, I recommend you switch to the nat64d package. libnat64 breaks dnsmasq's dhcp server. Additionally, using the nat64d package means that regular ipv4 traffic will work on your laptop.

You are getting a link-local address because dhcp clients will configure that first to request the address from the dhcp server. For my scripts, DNS settings come from DHCP. IPv6 addresses come from radvd. So it sounds like you're not getting any DHCP responses at all, only radvd announcements.

I also cleaned up the scripts for connection sharing:
http://code.google.com/p/n900ipv6/source/browse/share

Following the README in the usb directory will set the n900 up to automatically share when you're connected via 3g/2g and plug it into a usb device.

Re: IPv6 T-Mobile US Beta Test
 

No, I'm not using libnat64. I'm using nat64d. I just installed your new scripts, which at first seemed to give me the same results (same output from the dhcpcd command), but running ifconfig shows that, in spite of what dhcpcd said, it didn't actually use that link local address, and actually gave me 10.255.255.157 instead, and I'm now able to use the 3G connection from my laptop. Thanks.