Fibre with LTE HA is an extremely common scenario in the physical retail world. And retail is notorious for tight margins. With IPv4 this is dead simple for a router to do using NAT. With IPv6 it’s a nightmare because everyone is against NAT in IPv6. It took ages to get some form of NAT, and it’s poorly supported.
> multiple internet feeds .. assigned IPv6 block ... paying through the teeth to the ISPs for the privilege.
People like having their own network blocks, but typical route-my-subnet-here arrangement require all core routers to store the path to it. IMO assignments of globally re-routable addresses should be actively discouraged and you shouldn't get one unless you're an ISP. Not defending current payment arrangements.
Roaming should be done at or close to the endpoints - imagine if all internet routers had to keep and synchronize ~12G entries, usually in special CAM memory (currently at ~800K) - that does not scale, at all.
Gosh I wish IPv4 -> IPv6 was just 10.x.x.x -> 10.x.x.x.x.x
Instead we went to some hex-colon-double-colon BS. Like instead of "ssh 10.0.0.1" I have to now do "ssh -6 :://::2001:db8:ffff:abcd::34ff:2e6f::49af:fdef::"? Fuck that.
The simple fact that I can't memorize IPv6 addresses makes me lazy to use it. Whenever I want to SSH into a machine in 5 seconds flat I just rattle off its IPv4 address and I'm in.
It's called "The Domain Name System". I know it sounds alien and weird, but I assure you that you'll find that it greatly eases the burden of having to memorise network addresses!
Maybe your distribution has it included, just download it and give it a go.
>10.x.x.x.x.x
Looks a little short. It's more like... 10.x.x.x.x.x.x.x.x.x.x.x.x.x.x.x