25 Sep
2024
25 Sep
'24
10:17 a.m.
On 23/09/2024 02:08, Andy Smith via BitFolk Users wrote:
Past experience has shown that the majority of people won't be
interested in the upgrade and would rather not have to do anything, so
this communication is going to have to say something like, "if we don't
hear back from you to schedule this within 15 days, we will schedule it
ourselves for a date no sooner than 30 days from now".
This sort-of-implies that upgrading the VM spec requires that the
customer needs to upgrade their VM installation too, or stick to the old
spec. Or have I got the wrong end of the stick?
I do not expect to take away the legacy assignments from out of the
2001:ba8:1f1::/48 provided by Jump from existing VMs, but after we begin
rolling this out new VPS orders and new self-installs will not have the
legacy IPv6 space. At some point in the fairly distant future a retirement
date will be announce for that range.
When the distant future arrives (it's always sooner than you think) will
it be possible to route old and new subnets in parallel for a while? I
have a /48 for a VPN and the Jump addresses are hard-coded into all the
usual configuration. Being able to add the subnets into all of that
before the old one go away and break existing stuff would be a big
advantage, and IPv6 for all its faults at least makes giving interfaces
multiple addresses easy and functional.
Cheers,
Simon.