Score:0

Configure "forward proxy" or DNAT in the docker with multiple public IP

cn flag

I'm trying to find answers and a possible solution on the questions regarding forward proxy, docker and multiple network interfaces/public ip. I hope that I will get answers on them here.

I have an application which sends https requests on public API on 2 independent sites (API1, API2). This application runs on the hosted server (Linux) with 3 public ip (ip1, ip2, ip3). Required to configure network for the following requirements: the application for each request should use as source ip the next public ip from the pool of ips(ip1, ip2, ip3) "Robin Round Load Balancing"

Questions:

  1. For a solution should I used a "forward proxy" or DNAT ?
  2. If required to use a forward proxy than which one from the list haproxy, nginx, squid is better for this solution? and how to bind public ip and configure "Robin Round Load Balancing" for that?
  3. If required to use DNAT than could you share a sample of a configuration?
  4. The application works as a service in the docker. Is it possible to configure network: "forward proxy" or DNAT in the same docker-composer file?
mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.