Monday, January 19, 2009

IPv6 is *NOW* working from home

(funny what a single typo can do to a story. IPv6 is NOW working, and has been.)

I've had IPv6 working at the Outer Banks for some time now and now I'd like to announce I'm successfully running IPv6 at home using good, old IPv6 6to4. The difference between the two networks is at the beach I'm running IPv6 over a dedicated router (that will soon disappear) while at home I'm running IPv6 using everybody's favorite firewall: m0n0wall.

You didn't know m0n0 supported IPv6 using 6to4? Officially it does not, at least not yet. You have to run beta code to make it work but so far it seems stable. Having completed this little project the IPv6 Internet is wide open and waiting and believe me, it's mostly waiting. For who? YOU! Throw away that NAT mess young man or woman and get on the bandwagon.

Next up: my plans to host Time Machines and other dedicated IPv6 hosts at my undisclosed (and get unidentified) location in Wilson. Ah to build, perchance to dream. I've not yet figured out where the money is coming from but I've found the bandwidth and it's ripe, plentiful and inexpensive. What more is a kid to want? You want your own 10/10 meg server with bi-directional 100 meg burst window running IPv6, don't you? Heck, why not?

***

traceroute6 to ipv6.l.google.com (2001:4860:b002::68) from 2002:4bbd:e906:1:216:cbff:febc:6a62, 30 hops max, 12 byte packets
1 2002:4bbd:e906:1::1 2.526 ms 1.991 ms 1.95 ms
2 2002:82f4:21::1 102.334 ms * *
3 2a00:800:0:1::2:2 125.428 ms 124.444 ms 124.737 ms
4 pr61.ams04.net.google.com 127.144 ms 123.32 ms 121.244 ms
5 * * *
6 * * *
7 2001:4860:b002::68 225.418 ms * *

No comments: