In message <20110627002625.4C85311371DC@drugs.dv.isc.org>, Mark Andrews writes :

In message <BANLkTikzmCsHAxFfwQ2pidFPKXCTQTRBNA@mail.gmail.com>, Deric Kwok wr ites:

...

Hi all

I am trying to configure website for testing ipv6

Just wander how internet users eg: DSL users can visit this website and any people can access this website over the world

Thank you

About 10-6% of the net is dual stack capable, there is a working IPv6 path from the brower to the server. About 0.4% of the net prefers IPv6 over IPv4. It was higher but changes to depreference using 2002::/16 (6to4) as a source address have been pushed in various OS updates.

http://www.potaroo.net/stats/1x1/sitec/v6hosts.png

I meant to post the aggregate graph. http://www.potaroo.net/stats/1x1/v6hosts.png

This is updated daily.

APNIC/Geoff could use more test data sources. http://labs.apnic.net/index.shtml

Mark -- Mark Andrews, ISC 1 Seymour St., Dundas Valley, NSW 2117, Australia PHONE: +61 2 9871 4742 INTERNET: marka@isc.org

-- Mark Andrews, ISC 1 Seymour St., Dundas Valley, NSW 2117, Australia PHONE: +61 2 9871 4742 INTERNET: marka@isc.org

In message <4E08AF25.4090902@network-services.uoregon.edu>, John Kemp writes:

The more optimistic number was that something like 20% - 30% of clients could retrieve an IPV6-Only Literal URL. So yeah, still sad, but there is some potential there.

Given most of that traffic is going through automatic tunnels from behind firewalls that generally havn't been configured to support the tunnels I don't think it is that bad. -- Mark Andrews, ISC 1 Seymour St., Dundas Valley, NSW 2117, Australia PHONE: +61 2 9871 4742 INTERNET: marka@isc.org

In message <BANLkTimyBLbf_W2EjKwnsL-zqBQsucqr_Q@mail.gmail.com>, Kenny Sallee w rites:

On Sun, Jun 26, 2011 at 5:02 PM, Deric Kwok <deric.kwok2000@gmail.com>wrote:

...

Hi all

I am trying to configure website for testing ipv6

Just wander how internet users eg: DSL users can visit this website and any people can access this website over the world

I did this by creating a 6to4 tunnel to a relay provided by

6in4, not 6to4. While HE do operate 6to4 relays, the brokered tunnel service is 6in4.

www.tunnelbroker.net provided by Hurricane Electric - a great service they provide BTW. They provide sample configuration templates for various routers and OS's. I created the 'tunnel' from a Cisco 871w router (don't forget to configure a firewall here since you'll get IPv6 public IP's assigned to you). I used their block of v6 addresses they assigned to me, along with IPv4 addresses I already had - ie dual-stack, on my various windows and linux boxes behind my firewall. I then used their IPv6 DNS server, which returns IPV6 addressing if there's an AAAA record for the website you are going to. Some sites - like google search are reachable via different DNS names, like ipv6.google.com or ipv6.cnn.com...and www.v6.facebook.com.

You can also build / use Teredo tunnels - which I tested and worked as well - tho not as good as from the routers. This works well for hosts behind IPv4 NAT

Finally, you can test your personal IPv6 connectivity here:

http://test-ipv6.com/

And you can test if your site, or any site, is reachable via IPv6 here: http://ipv6-test.com/validate.php if you do not have IPv6 configured.

Good luck, Kenny -- Mark Andrews, ISC 1 Seymour St., Dundas Valley, NSW 2117, Australia PHONE: +61 2 9871 4742 INTERNET: marka@isc.org

Thank you all Two questions: If I get the HE as upstream to advertsie our ipv6, 1/ Do we still have www.tunnelbroker.net as tunneling connection? 2/ All the internet users can access our ipv6 website? Thank you On Tue, Jun 28, 2011 at 2:09 PM, Kenny Sallee <kenny.sallee@gmail.com> wrote:

...

...

...

I did this by creating a 6to4 tunnel to a relay provided by

6in4, not 6to4.  While HE do operate 6to4 relays, the brokered tunnel service is 6in4.

A very important distinction I didn't have clear in my head.  To regurgitate some reading I just completed: both methods use v6 in v4 tunneling using ip proto 41 in the IPv4 protocol field.  However, 6to4 derives the IPv4 tunnel destination of an IPv6 packet based on bits 17-48 of the IPv6 packet - which when converted, equals the 32 bit IPv4 destination.  While 6in4 is statically configured IPv4 source and destination IP addresses on the Tunnel (gre) interface.  In Cisco world the config comes down to 'tunnel mode ipv6ip' vs 'tunnel mode ipv6ip 6to4' and a few other lines of config. Of course there are a lot more details then that searchable via google.  Thanks for pointing out my mistake - it helped me learn some more!  Later, Kenny

Derik, 1. Yes, you still use tunnelbroker.net if you wish you your own IPv6 PI space tunneled. HE does require you to have an ASN as well. With this you can multihome up to 5 of their PoPs. Find more info at their site: http://tunnelbroker.net/ However, they will give you up to 5 tunnels, each with a /64 and optional /48 allocated from their address space. However as this is allocated from their address space, you cannot multihome with it. They also do have a premium service you can purchase for IPv6 transit as well: http://www.reuters.com/article/2011/06/06/idUS130127+06-Jun-2011+BW20110606 Also they will sell you native IPv6 with IPv4 service as well. You provide the circuit to them. http://he.net/ip_transit.html 2. If you have transit only with HE, all IPv6-connected Internet users can access you with the except of those single-homed to Cogent or Level 3. Both Cogent and Level 3 refuse to route any IPv6 traffic destined to HE. Having said that, Hurricane Electric has the most IPv6 peers at present (more than 3 times the amount of Cogent and Level 3): http://bgp.he.net/AS6939 I'm using HE for multihomed transit using my PI /44 and ASN (AS19621). I'm waiting while AT&T and Verizon try to upgrade their PoPs (AT&T in San Jose, Verizon in Sacramento) to provide me transit on my existing enterprise IPv4 circuits. I'll continue to use HE as backup transit even once I get IPv6 connectivity to either or both of the telcos. The nice thing is that you can get your feet wet with HE for free and no commitment and get started now while the giants still sleep. Plus, who knows, HE may remain an IPv6 giant as others grow up, and perhaps this will raise their IPv4 status to that of coveted Tier 1. Maybe IPv4 transmit won't matter in 10 years, and they'll just stay the top IPv6 dog. Jason Roysdon On 06/28/2011 06:15 PM, Deric Kwok wrote:

Thank you all Two questions:

If I get the HE as upstream to advertsie our ipv6,

1/ Do we still have www.tunnelbroker.net as tunneling connection?

2/ All the internet users can access our ipv6 website?

Thank you

On Tue, Jun 28, 2011 at 2:09 PM, Kenny Sallee <kenny.sallee@gmail.com> wrote:

...

...

...

...

I did this by creating a 6to4 tunnel to a relay provided by

6in4, not 6to4. While HE do operate 6to4 relays, the brokered tunnel service is 6in4.

A very important distinction I didn't have clear in my head. To regurgitate some reading I just completed: both methods use v6 in v4 tunneling using ip proto 41 in the IPv4 protocol field. However, 6to4 derives the IPv4 tunnel destination of an IPv6 packet based on bits 17-48 of the IPv6 packet - which when converted, equals the 32 bit IPv4 destination. While 6in4 is statically configured IPv4 source and destination IP addresses on the Tunnel (gre) interface. In Cisco world the config comes down to 'tunnel mode ipv6ip' vs 'tunnel mode ipv6ip 6to4' and a few other lines of config. Of course there are a lot more details then that searchable via google. Thanks for pointing out my mistake - it helped me learn some more! Later, Kenny