I wish to forward a persistent HTTP request through a different public IP. It connects to the server and stays connected as the server continuously streams data.
This needs to be transparent to the application; the routing logic needs to be limited to just making the HTTP connection to a target port number (or host:port).
I'm considering having a Squid service listening on a LAN IP but on several ports; if the application connects to port A, forward the request through nic A; for port B connections, forward through nic B; and so on.
Is this a suitable task for Squid? And where I could find some hints about the configuration? I got lost reading the Squid documentation finding for anything related to this (specifically how to map local ports->different output NICs).