« Posts tagged IPv6

IPv6 over an IPv4 Tunnel on a Dlink DIR-825 Rev. B

June 27, 2011 / posted in howto, Microsoft, Networking / 1 Comment

Although I missed World IPv6 Day, I was bored the other night and decided to finally setup an IPv6 tunnel. To do this, I registered a free account with Hurricane Electric’s Tunnel Broker. The process was a breeze and in no time I had a regular tunnel created. From there, it was all up to the Dlink router.

A few notes:

  1. Make sure you have the latest firmware for your DIR-825 Rev. B. At the time of writing, it’s version 2.05(NA).
  2. You will need to enable “WAN Ping Respond” – this can be found under Advanced -> Advanced Network. You can safely disable this after you finish complete the process and your tunnel is working. This is needed so that Tunnel Broker (TB, from here on out) can confirm your public-facing IP address and link it to your tunnel.

So, that out of the way, once Tunnel Broker has confirmed your tunnel is available, login to your router and do the following:

  1. Under the main Setup tab, click IPv6.
  2. Click the Manual IPv6 Internet Connection Setup button. Do not use the wizard.
  3. For the IPv6 CONNECTION TYPE, choose IPv6 in IPv4 Tunnel.
  4. In the Remote IPv4 Address box, enter the Server IPv4 Address provided by TB.
  5. In the Remote IPv6 Address box, enter the Server IPv6 Address provided by TB.
  6. The Local IPv6 Address is the Client IPv6 Address from TB.
  7. Under the IPv6 DNS SETTINGS heading, choose Use the following IPv6 DNS servers and enter the Anycasted IPv6 Caching Nameserver provided by TB in the Primary IPv6 DNS Server box (TB did not provide me with a secondary DNS address).
  8. Finally, uncheck Enable DHCP-PD under the LAN IPv6 ADDRESS SETTINGS heading.
  9. Leave the settings under the ADDRESS AUTOCONFIGURATION SETTINGS heading as their defaults.
  10. Click the Save Settings button at the top of the page and let the router do it’s thing. It will take some time to ‘measure the internet connection’ – this is normal.

You’re almost done. At this point, if you go to the Status tab and choose IPv6 from the options down the left side of the page, you should see the TB information you entered, and Network Status should say Connected.

The rest of the work depends on your operating system. I use Windows 7 on my main PC, which natively supports IPv6 (as does OS X and most *nix distros). As IPv6 is enabled by default, I simply had to open an Elevated Command Prompt and type:

ipconfig /release

ipconfig /renew

After it finished thinking, ipconfig spat out the new network configuration which included the correct IPv4 and IPv6 addresses. I opened Firefox and browsed to http://ipv6.google.com – success! Everything works! You can also confirm that IPv6 is working by using the nslookup tool from a command prompt like so:

C:\Users\Laslow>nslookup
Default Server:  ordns.he.net
Address:  2001:470:20::2

> xbox.com
Server:  ordns.he.net
Address:  2001:470:20::2

Non-authoritative answer:
Name:    xbox.com
Addresses:  2a01:111:f009::3b03
65.55.42.140

>

As you can see, the IPv6 nameserver came back with an IPv6 AAAA record (2a01:111:f009::3b03) and an IPv4 A record (65.55.42.140) for xbox.com.

Updated x4: The Non-Existent State of IPv6 in Canada

July 25, 2010 / posted in Networking, Rants, Support, Twitter / 12 Comments

Further Update (06/27/2011): If you have a Dlink DIR-825 router, I just published an article on getting a free Tunnel Broker IPv6 tunnel account working. Check it out! If you have a router that is cable of an IPv6 over IPv4 tunnel, or just want to use a single computer, check out Tunnel Broker from Hurricane Electric.

Over the last few days I’ve been attempting to gather information on IPv6 in Canada, and so far the news is grim. Why am I looking in to it? Well, there have been a number of articles posted lately about the impending end of available IPv4 addresses and the sorry state of IPv6 addoption, and I wanted to check in on my local ISPs and see if any of them are preparing for this. The short answer? No.

My region has two primary ISPs – Telus and Shaw Cable. I did a quick Google search to see if either had made any announcements about IPv6 readiness, and I ended up with no relevant results. In fact, a search of “IPv6″ on the domain shaw.ca only returns results on user hosted pages. Searching Google for “IPv6 Telus” only comes up with one close match – this PDF document that’s basically a beginners guide to IPv6.

So, I opened a ticket with my ISP (Shaw), and tweeted at their customer care guys. I also tweeted at Telus’ customer care. Here’s what I got back.

Telus tweeted back pretty quickly:

@laslow We don’t have any news on implementation of IPv6. It would make sense that everyone will switch eventually. -Trevor @TELUSSupport

I replied, and they came back with this:

@laslow We’ll try and help where we can but no real info on this. Hope your day goes well!

Well, that was rather uninformative.

Sean from Shaw Customer Care also replied rather quickly on Twitter:

@laslow hey man, no word on IPv6 yet, hopefully sometime in the near future though.

Shortly after, I received the following reply to the ticket that I opened with Shaw:

Hello [Laslow],

This is [Agent], thank you for your e-mail.

At this time there is no set date that IPv6 will start to be used. As soon as address’s have ran out with IPv4 then everything would be switched over to the IPv6. Kind of like how in B.C. not including the lower mainland we have been using the area code 250 for years. There are no longer numbers available with the 250 area code so they moved to 778 area codes. It will be similar to this when IPv6 is released, sorry we have no further information for you at this time on this.

So in short, Shaw’s plans are to wait until they’ve run out addresses, and then worry about what to do next. I don’t know about you, but I’m definitely feeling more confident that Shaw will be able to connect me to IPv6-only services in the next, you know, ten years or so.

Honestly, though, there are a number of ISPs in the states that already have public IPv6 tests available (Comcast, for example) – why is Canada so far behind?

If anyone reading this works for Telus or Shaw and has more information on their progress towards IPv6, please leave a comment or send me a tweet – It would be nice to know if there are at least plans in place rather than just a sense of “we’ll cross that bridge when we get there”.

Updated (11/29/2010):

I contacted Shaw, Telus, and Rogers via twitter again and received the following responses (still waiting to hear from Shaw):

@laslow At this time we do not have any information/news – Ryan with @TELUSSupport (Direct link to tweet)

And:

@laslow Hi Laslow. I have no info – but can ask around tomorrow. I’ll get back to you if I get an update. (via @RogersElise - Direct link to tweet)

I’ll post any additional information I receive as I get it.

Updated (11/30/2010):

Shaw responded this morning with the following (still no additional information back from Rogers):

@laslow yes, it’s in the pipeline, however, no confirmed release dates yet. (via @Shaw_Sean – Direct link to tweet)

So we have at least one ISP that will willing to publicly state that they have plans to deploy IPv6. Still, solid details would be welcome.

Updated (02/01/2011):

You can check to see if your ISP has IPv6 Prefixes using this site. If they do (I can confirm Shaw and Telus do, haven’t checked others yet), it shows that they have IPv6 connectivity with the rest of the world. If not…well, it might be time to panic. I bugged Shaw again via Twitter about IPv6, and got this response:

@laslow I honestly have no idea, but I’ll make sure you’re the first to know should I hear something.

So, I’ll update again when I hear more.