Those 3 ips have different routes to world wide internet. So the
application program does not have to select anything in respect to
routes to destination servers. This is done by the hardware that route
those ip addresses.
Anyway, I am aware that I can start 3 different DeleGate with different
SRCIF, but that is waist of resources. What if I have 100 ips and I want
to do that...
All I need is a simple way of telling DeleGate to automatically use to
connect to final destination the ip that the original request came on. I
need to keep things apart, but with the minimum effort...
Yutaka Sato wrote:
> In message <_A4027@delegate-en.ML_> on 07/31/08(05:11:46)
> you Sorin Esanu <firstname.lastname@example.org> wrote:
> |I run delegate (http proxy)on a multihomed linux server. Although
> |delegate listens to all ips, the outgoing ip is always the main ip of
> |the computer. Is it possible for delegate to use as outgoing ip address
> |the address that request came on? So, if the server has ip1 ip2 ip3 and
> |the client is connecting to ip3, I want delegate to connect to the
> |requested URL using ip3, and not ip1 (the main ip of the machine).
> Why you need to do so? As long as I underdstand, an application
> program like DeleGate can't select the route to the destination
> server. You can select the source address of an outgoing connection
> by binding it with the SRCIF parameter but it will not be routed to
> the destination if your ip1, ip2 and ip3 have different routes.
> 9 9 Yutaka Sato <email@example.com> http://delegate.org/y.sato/
> ( ~ ) National Institute of Advanced Industrial Science and Technology
> _< >_ 1-1-4 Umezono, Tsukuba, Ibaraki, 305-8568 Japan
> Do the more with the less -- B. Fuller