Build your own IPv6 lab on the cheap, part 2

You're so close to creating your own IPv6-ready lab -- now InfoWorld's Matt Prigge takes you through the final steps

Note: This is part two of two; the first part was posted last week.

Last week, we took a look at how to make the transition from IPv4 to IPv6 using nothing but standard equipment you probably already own. This week, you can wrap up your project with the details below.

Building an IPv6 tunnel

Since your ISP almost definitely doesn't deliver IPv6 yet, you'll need to build a tunnel across the IPv4 Internet to someone who can gateway you onto the IPv6 Internet. In this case, I used Hurricane Electric's free IPv6 tunnel broker service. You'll need to sign up for an account (a fairly painless process) before you can create a new tunnel.

To do that, you'll need to know the outside interface IP of the router. If you create the tunnel from behind the firewall, the Create Tunnel dialog will tell you the originating IP. If not, you can run show interfaces ethernet to see what IP your ISP has doled out.

If you want, you can choose a specific POP to which to route your tunnel, but Hurricane Electric's service does a pretty good job of telling you where you're coming from and which of its POP options might be the fastest for you. Once you hit submit, Hurricane Electric will ping your IPv4 tunnel endpoint to ensure it's available (which is why you allowed ICMP echo requests in the "out-local" rule earlier), then it will dump out all of the information you'll need to configure your end of the tunnel.

The Tunnel Details dialog even goes so far as to provide you with a personalized example configuration. Choose Vyatta from the drop-down box and hit Show Config. You should get a ready-made chunk of configuration that looks like this:


edit interfaces tunnel tun0

set encapsulation sit

set local-ip X.X.X.X

set remote-ip

set address 2001:470: XXXX:XXXX::2/64

set description "HE.NET IPv6 Tunnel"


set protocols static interface-route6 ::/0 next-hop-interface tun0


That block uses slightly different modal notation from what I've shown in my examples so far. It is effectively a version that's easier to hand-type (along with the necessary configure and commit statements):

set interfaces tunnel tun0 encapsulation 'sit'

set interfaces tunnel tun0 local-ip 'X.X.X.X'

set interfaces tunnel tun0 remote-ip ''

set interfaces tunnel tun0 address '2001:470: XXXX:XXXX::2/64'

set interfaces tunnel tun0 description 'HE.NET IPv6 Tunnel'

set protocols static interface-route6 ::/0 next-hop-interface 'tun0'

1 2 3 4 Page 1
Page 1 of 4