No, the idea is not to choose the ouput interface on the curl system.

But to specify the ip address of the TARGET system.

Just think about the following architecture:

Internet
    |
    |
www.test.com is directed by DNS to a virtual IP load balanced among a
    | farm of web server
    |
 +-----+----+--... Official Network
W1 W2 W3 ....

Now suppose you can reach each Web server individually because you know each IP address.

When you use curl in the normal way:

curl http://wwww.test.com/

You get the response from one server in the pool.

And for security reason the web server refuse:

curl http://1.2.3.W1/

So I add the support of:

curl --remote-ip 1.2.3.W1 http://www.test.com/

Which works fine here, I can test each web server in the pool.

In fact I do that for the integration of individual test in Nagios (Network monitoring).

Regards

Pascal

> Message du 27/09/04 19:50
> De : "Daniel Stenberg" <daniel-curl_at_haxx.se>
> A : pascal.trouvin_at_wanadoo.fr, "libcurl development" <curl-library_at_cool.haxx.se>
> Copie &agrave; : murf_at_e-tools.com
> Objet : Re: [patch] Changing the originating IP of outgoing posts
>
> On Mon, 27 Sep 2004, Pascal TROUVIN wrote:
>
> > I do not know if this is really your problem, but I patched curl to add a
> > new option '--remote-ip', this new option let you specify a URL and assign
> > the request to the specified host IP address.
>
> You mean like --interface already works?
>
> --
> Daniel Stenberg -- http://curl.haxx.se -- http://daniel.haxx.se
> Dedicated custom curl help for hire: http://haxx.se/curl.html
>
Received on 2004-09-28