@virgiliomi said in Configuration IPV6:
Easier until you start assigning IP ..........
I don't see any case where DHCPv6-PD would be desirable over a static IPv6 block. But maybe that's just me.
Noop, you got a point.
I have to add that I'm using a static IPv6 setup myself, as my ISP
doesn't know what IPv6 is.
and if they do, they come up with a single /64
or a /56 but only the first /64 is routable
or ..... (whatever, their BOX has just one LAN so they don't understand the fuzz - not even that some clients are actually companies and they could have more then 1 LAN ....)
with he.net, the one I'm using, the price is : not worlds fastest ISP, but free and rock solid. And very static.
@virgiliomi said in Configuration IPV6:
My prefix was rock solid on my last ISP (Comcast). .....
unplugging the interface or rebooting.
A pretty solid proof that '$$$€€€' and 'Mbits/sec' is just a part of the equation.
Good 'protocol' support is as important. And this one doesn't need the reading of their promises on paper. It will always be "Hands on testing for 6 months" ;)
@virgiliomi said in Configuration IPV6:
But they don't. Because my DUID hasn't changed...
They probably cleared out their DHCPv6 server cache and settings.
As you said : they are probably in the implementing phase.