On Mon, 12 Feb 2007, Jochen Hayek wrote:

> DS> Yes, you tell the server to connect to a private IP address:
>
> DS> PORT 10,0,4,119,180,254
>
> Yes, it looks like that -- but when the socks server goes through the NAT
> router, everything is fine.

The fact that this works with "socksify" is then only because that translates
this address to before it reaches the FTP server. curl doesn't magically
translate for you, but expects you to set the address it should use if the
default isn't good enough.

This isn't strictly a SOCKS issue.

> Today's NAT routers are wonderful little (Linux) machines :-)

Perhaps, but this problem has nothing to do with the actual NAT or what OS it
runs... The problem is related to you using NAT and passing a private address
to an outside server that can't reach you back on that address.

> So that private IP address should not be a problem.

Yes it should. Unless you introduce a middle-man that translates it for you.

BTW, protocol-wise, when you use SOCKS for an outgoing connection to a FTP
server, is SOCKS involved in any way on the incoming "active" connection then?

> Alright, alright "NLST" is not the same as "LIST",

No, but the difference is not what causes this problem.

> but actually if "LIST -1" (for "ls -1") does the right thing for me in this
> case, I would be fine using that instead, if I knew how to tell curl resp.
> libcurl.

-X is your friend

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