On Sun, Mar 09, 2025 at 09:10:36AM +0100, Gert Doering wrote:
"Multiple address per node" + a decent API so *users* can easily control what they want applications to do ("web surfing via DSL, bittorrent on the cable Internet") + proper source address failover would be bliss...
Especially "proper source address failover" would be much more robust against remote failures than "BGP" - think "packets going out via ISP A, and there being a blackhole [think broken MPLS tunnel] between ISP A and ISP X, so packets disappear" - with BGP you basically need to fumble on your route policies then. With "mmh, ISP A source does not work, let's try ISP B source" things can be fixed from the application/client OS level.
Actually, I implemented something related once: https://codeberg.org/jonas-l/socksbalance This is a socks proxy server (can be configured in applications like Browsers) that selects source IPs for the connections. It's implementation with round robin is quite simple. However, just retrying to connect results in a certain chance that the application picks the other source IP. There is of course the possibility to make it more advanced. This proxy server can run at the end user machine itself.