IPv6 - a noobs prespective

James Harr james.harr at gmail.com
Tue Jun 14 13:30:53 CDT 2011


Really -- just go play with it. I started by setting up a
tunnelbroker.net account at home.

A majority of the packet slapping functionality of routers work just
fine. It's when you get into things like applications, load balancing,
NAT64/DNS64 where things start to get a little buggy. And you'll never
get to those things unless there's some basic IPv6 on your network
already.

At work, we started by deploying it across the routers, but not to any
end hosts. This way we can turn IPv6 on/off to specific end-host VLANs
without much effort. Currently, our techs and one enthusiastic end
user group have IPv6 and it seems to be running well. After the
basics, it's going through one application/service at a time and
getting it on IPv6.

On Tue, Jun 14, 2011 at 11:44 AM, Octavio Alvarez
<alvarezp at alvarezp.ods.org> wrote:
>
> On Wed, 09 Feb 2011 03:00:27 -0800, Robert Lusby <nanogwp at gmail.com> wrote:
>
>> I am however *terrified* of making that move. There is so many new phrases, words, things to think about etc
>
> You fears will significantly lower after you set up a separate lab and
> play with it. With something as simple as a switch you can make a simple
> IPv6-only network. Try to replicate your current network in the lab as
> far as you can, using the "new" concepts and techniques and understand
> the current state of the art (read that as RA+DHCPv6, etc.) Get your
> pings right.
>
> This will automatically get you to dual-stacking, as in "how do I make
> both protocols work in the same physical network?". They just do. At
> this point the problem stops belonging to the network infrastructure
> and it passes on to the application servers and hosts.
>
> (And ask your ISP to support IPv6).
>
> Good luck.
>
> --
> Octavio.
>



--
^[:wq^M




More information about the NANOG mailing list