4 ms·
I'm with you. It'd be nice if they handed out a proper IPv6 prefix to their droplets too. The 16 addresses or whatever it is doesn't count. Bonus points for
by 2bluesc 11y ago
I'm with you. It'd be nice if they handed out a proper IPv6 prefix to their droplets too. The 16 addresses or whatever it is doesn't count.
Bonus points for optionally handing out a /48 as recommended so that docker containers can be allocated /64's.
We can dream.
- IgorPartola 11y agoYou know what? I just realized that Vultr.com has /64's everywhere. Time to switch. [edit: I am not affiliated in any way with Vultr, was not even a customer until about 30 seconds ago].
- 2bluesc 11y agoShoot, should have included my referral code. In case anyone else is interested: http://www.vultr.com/?ref=6818844 http://www.vultr.com/?ref=6818844 Vultr also has larger HDD droplets for storage/back-up/archive whatever people want it for (my case bitcoin nodes). DO has been "working on this" for quite some time and it's the most requested feature: https://digitalocean.uservoice.com/forums/136585-digitalocean/filters/top https://digitalocean.uservoice.com/forums/136585-digitalocea...
- stock_toaster 11y ago> Bonus points for optionally handing out a /48 as > recommended so that docker containers can be allocated /64's. A believe that currently a /48 is recommended for "larger" end networks (65K subnets), not for end systems or "home networks"[1] where a /56 is recommended. Would docker instances each need unique subnets? I think a /56 would be sufficient (256 subnets, 4.7×10^21 addresses), maybe even "just" a /64, if docker instances could share the same subnet. [1]: https://tools.ietf.org/html/rfc6177 https://tools.ietf.org/html/rfc6177