On 31/12/20 8:47 pm, Roland Schwarz via 44Net wrote:
Tony,
On 30.12.20 at 22:28 wrote Tony Langdon via 44Net:
...
Still have to find the /32 somehow. And I still see a lot of suboptimal routing happening here, unless there's some other protocol in the core doing clever routing.
I absolutely agree! What I wanted to point out is that there might be basically two expectations about 44 addresses. Topological routing as you have pointed out is one of it.
Yes, I'm usually on the wrong end of global RTT delays when using online services, unless it's a Google or Facebook with a distributed CDN that has POPs all over the world, so topological routing is an issue of high importance to me.
Let me elaborate on the second idea: lots of isolated /32 hosts or /28 subnets: Sure, if I need to load the entire routing table to every node, this will not scale. But a single node will not need the full routing table typically. Only a few entries are interesting at a single time. So if you have a dynamic lookup facility of the gateway address, you could populate your routing tables on demand. This facility could be realized by means of a distributed hash table, so there is no single point of failure. And yes the optimal routing is done by the core internet in such a use case.
That assumes the case of a single device wanting to access the network. That would also lead to suboptimal routing locally here, because I have multiple devices on the network (4 or 5 currently on 44.x). There is one way that could work, using something like ZeroTier to do the "last mile". That wouldn't give you a /32 address, but instead an address on a virtual LAN, of a size specified by the network admin. But while ZeroTier does have a lot of desirable qualities, like working transparently through NAT (and that can be tweaked), and using the best route it can find (two ZT hosts on the same physical LAN will quickly find the direct path between them, and route over that), it doesn't meet the criteria of running on routers, AFAIK. ZeroTier may be available on OpenWRT (I don't know if that's the case), but I highly doubt you'd find it on Cisco. It is available for Linux, Windows, Android and iOS, and is open source.
I use ZT myself. It allows me to be on the same virtual LAN as my VPSs, which makes moving data between all sites much easier. And when I travel, I can connect back here both securely and without worrying what NAT timeouts will do to idle sessions.