Re:Pentagon retakes control of IP addresses it moved in last...
by CameronNemo on Saturday September 11, 2021 @10:07PM
(#28497998)
It is rarely an issue in practice. There are workarounds to minimize connection resets. Using ECMP hashing on routers and a tiered load balancing topology are important.
https://vincent.bernat.ch/en/blog/2018-multi-tier-loadbalanc...
https://blog.cloudflare.com/high-availability-load-balancers...
https://engineering.linkedin.com/network-performance/tcp-ove...
Re:Pentagon retakes control of IP addresses it moved in last...
by sterlind on Sunday September 12, 2021 @01:17AM
(#28498787)
Seems like LinkedIn had to do some finessing and still couldn't go with global anycast.
How do CDNs work without controlling DNS resolution by source subnet?
Re:Pentagon retakes control of IP addresses it moved in last...
by diroussel on Sunday September 12, 2021 @04:51AM
(#28499563)
Cloudflare uses any cast, and they deal with it by making every external node able to handle every public IP that they have.
If packets in a TCP stream end up going to different nodes, then they deal with that in their infrastructure.
Re:Pentagon retakes control of IP addresses it moved in last...
by CameronNemo on Sunday September 12, 2021 @02:12AM
(#28498980)
Presumably a CDN has better and more direct peerings with ISPs than LinkedIn, or admittedly archive.is.
You can serve UDP services (eg DNS) by anycast, but if you hosted a tcp service, there's no guarantee the same server would receive consecutive packets from the tcp stream