On Mon, 12 Feb 2007, Daniel Beardsmore wrote:

> Sorry, I was trying to say that they don't all rewrite private IPs within
> packets themselves. i.e. the string "PORT 10.1.2.3" won't necessarily be
> converted to a public IP by the router itself. Some NAT routers take on this
> role and "fix" all your packets for you.

And if the NAT/router fixes this, it certainly fixes it for curl as well and
thus it should work the same...

Hence my question about SOCKS on the incoming connection.

-- 
  Commercial curl and libcurl Technical Support: http://haxx.se/curl.html