To clarify what cholzhauer said, the Tunnelbroker service does not use AICCU/TSP, so you will not need an AICCU client. To set up a tunnel through Tunnelbroker, you will use 6in4 (IPv6-in-IPv4/protocol 41).

Old accounts also can't use PPTP.

Old tunnels that currently have PPTP enabled will be able to continue using it for the moment. No new tunnels will have PPTP enabled. If you delete a tunnel that has PPTP, you won't be able to get it back.

I understand, but, why is it that some ping responses are not in IP/IPv6 numerical format??  This is kinda something new to me.  I always
in the past saw numerical responses and not fqdn as a response.

Thanks for th -n option (didn't see this in the --help under Linux. )

Is this something of an IP/IPv6 mask??  I did some digging and noticed this is a router option to mask the routers IP address.

No, ping is just doing a reverse DNS lookup on the IP address you are pinging. Using ping -n will cause ping not to do those lookups.

Actually, we do not peer directly with Comcast. If you look at the original traceroute, you can see we are connected to Comcast through Global Crossing (glbx.net). And of course, GLBX is now owned by Level3.

So the obvious solution is for GLBX/Level3 to peer with us in Chicago. Of course, that doesn't mean that Comcast will get a more efficient route. They might still have to go through NY. The internet is weird like that.

i got it working.

now if i could only get something similar for tunnelbroker...

Check out the link that ratcheer posted, it should provide you with some helpful directions for setting up ddwrt to automatically update your endpoint in TunnelBroker. Specifically, this script: http://fcartegnie.free.fr/articles/Hurricane's%20IPv6%20TunnelBroker%20Endpoint%20ipv4%20address%20updater.html

/ns1.mydomain.ch/ does not appear to be a substring of syno1.ipv6.mydomain.ch
syno1.ipv6.mydomain.ch
mydomain.ch

What is the full domain name you initially used when starting the tests? If it was syno1.ipv6.mydomain.ch, then your nameservers need to be a subdomain of syno1.ipv6.mydomain.ch, not mydomain.ch.

What you are currently doing, which is actually not such a bad idea, is sending everything destined for HE address space (2001:470::/32) through tunnelbroker, and everything else out default through native.

The problem is that you are routing EVERYTHING destined for HE space through tunnelbroker. You probably want to put a static route for your allocations before the less specific /32 route. I'm not familiar with how OpenVPN is handling IPv6, but if you are assigning a /64 to the vpn tunnel, you would want to insure that the /64 is routed down the vpn interface instead of out the tunnelbroker interface.

So in the future I should ask ipv6@he.net and let them (you) know I'm having problems?

Yes, that's usually the quickest way to get a response and to let us know of an issue.

I know of no one who routes anything over firewire.  It's for devices, not host-host communication.

I've seen a couple of devices that do IP over firewire, but granted, it isn't very common. See http://tools.ietf.org/html/rfc2734 and http://tools.ietf.org/html/rfc3146

If that doesn't convince you, then think about the fact that one day MAC addressing might have to be expanded to 64bits, or replaced with something longer. (MACv6 anyone?)

Not good, IPv6 is running out of address space!

I'm sure you meant that as a joke and its funny and all   But on a serious note -- I personally do not understand the need of giving out even /64 to anyone..  come on..  This is what is planned to be handed out to users -- 18,446,744,073,709,551,616 addresses, come on.. Did we learn nothing from how IPv4 was handled.  with a /48 your talking 64,000 x 18,446,744,073,709,551,616 for possible addresses..

Yes I understand the address space for IPv6 "seems" infinitely large, but improperly managed and you can run out of anything..  What possible reason could there be that a lan would need a /64??

I just don't understand their logic with /64 being the breaking spot for addresses.  Its pure insanity if you ask me.

The main idea behind /64 for SLAAC is that it uses EUI-64 for choosing interface addresses. Remember, it is based on the 48bit MAC address.

Also, don't think of IPv6 prefixes in terms of address space. You should think of it in terms of subnet space. If you are using SLAAC, then a /64 only gives you a single LAN segment. With a /48 (or /56), you can subnet out into a more complicated network layout.

You can get the score for any user from the scoresheet page: http://ipv6.he.net/certification/scoresheet.php?pass_name=jrocha

Currently you'll have to parse the page yourself, and it will only provide you with the raw score. I'll look into seeing if we can provide the level as well.

What I normally end up doing is using a hop along the way that returns ptr, and whois can be a pain sometime - many sites are on he tunnels hehehe

The best way I have found to deal with 100 different daily whois tests is to understand the concept of sparse allocation.

Already run a whois on 2001:470::/32? Run one on 2001:440::/32!

I got my Sage certification in November 2010 but haven't received a shirt yet.  I'd buy one from the new merch store that you guys opened up but they're not for sale.   

I haven't received my shirt yet either. I completed the Sage certification level in January

You should email ipv6@he.net, and we can track down that tshirt for you. It can sometimes take quite a while for the tshirts to work their way through the mail system.

I am trying to configure things to do the Enthusiast certification. I am a bit confused about the domain registration that I apparently performed, successfully.

I am managing zone 2001:470:8:b57::/64. I requested 2001:470:8:b57:230::1 to be added as hostname ratcheer.com. This was successful.

On my client host, I started apache2. It states that it is "using 2001:470:8:b57:230:1bff:feb5:9a1d for ServerName".

It also sounds like your apache configuration is incorrect, and is using your IP address as ServerName, which isn't usually what you want to do.

Have not gotten mine??  I saw some email that said batch was going out in end of Jan, but maybe they  compiled the list on 17th of jan?

I completed my sage level and validated address for tshirt on
26 January 2011

is there anywhere to check where if on the next shipment list, etc.

If you haven't received your t-shirt yet, send an email in to ipv6@he.net and we'll have the person in charge of the tshirt shipments check it out for you. I don't remember if you validated your address before or after the last shipment date.