Static IPv6 problems
-
Good writeup on the subject:
http://etherealmind.com/allocating-64-wasteful-ipv6-not/Subnetting deeper than /64 breaks a number of automatic mechanisms in IPv6 and it's not really needed :p
-
I agree that we will probably regret handing out all the /64 bit subnets at some point.
However, some network administrators have used prefixes longer than /64 for links connecting routers, usually just two routers on a point-to-point link. On links where all the addresses are assigned by manual configuration, and all nodes on the link are routers (not end hosts) that are known by the network administrators do not need
I agree with this also, that we should probably be using longer prefixes for inter-router communication as in between an ISP and customer router (pfsense in my case) :). There is no need for automatic configuration or alot of the other feature as this is manually setup. But for home use, /64 does make sense as that will be mostly autoconfigs. Then, how do you setup FW services, as a bridge because a routed solution doesn't make much sense (where you are wasting 2 /64 to get access to at most 100 devices (and I am being generous for home users), neither does a NATed solution. You could even use 2 /112 in a routed solution (if it didn't break anything). That would be more than enough for any home user. IPv6 has been around long enough to have already fixed autoconfig without the /64. Hopefully that will be fixed soon enough. Enough of the soap box.
What are ISPs like comcast doing for IPv6 customers in the residential market?
-
What are ISPs like comcast doing for IPv6 customers in the residential market?
They use DHCPv6 with a /128 on the WAN side and a /64 for the LAN.
[1] http://forum.pfsense.org/index.php?topic=49575.0
[2] http://ipvsix.me/?p=220