IPv6?

[Jason T. Nelson]

In our last exciting episode, Joshua Judson Rosen (rozzin at hackerposse.com) said:
> Hm. That prompts a few follow-up questions:
> 
> 	- Does "native Comcast IPv6" mean that Comcast is actually putting
> 	  their residential customers on IPv6 addresses now?
> 
> 	  (I haven't been a Comcast residential customer in years, so I 
> 	  don't know)
> 
> 	  Is that something that you need to (or can) request, or do they 
> 	  just
> 	  do it as a matter of course?

They appear to have pretty good coverage now, they started on the west
coast sometime in 2011. I think I received a native (by this I mean
non-tunneled, not translated) IPv6 address earlier last year in Manchester.
Assuming you have a supported cable modem and your hardware connected to
it supports it, you will be provided an IPv6 address via DHCPv6; there's no
opt-in or even opt-out. In addition, you can ask for additional prefixes
beyond the default /128 address given if your DHCPv6 client supports Prefix
Delegation. I'll leave that configuration as an exercise to the reader as
it depends on OS and client implementation :)
 
> 	- How are you going about determining your IPv4/IPv6 traffic split?

My edge device/router is a small FreeBSD box where I'm using the netflow
Netgraph node to export netflow data for analysis. I did it originally as
a testbed for $dayjob.

-- 
Jason T. Nelson <jtn at jtn.cx>
GPG key 0xFF676C9E
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 196 bytes
Desc: not available
Url : http://mail.gnhlug.org/mailman/private/gnhlug-discuss/attachments/20150113/f14a8638/attachment.bin