On 10/13/2012 17:05, Robert Elz wrote:
In that case I'm back to suspecting a EPSV/NET clask between you and the server - that would affect ftp, that atempts to use EPSV for IPv4 - since the server supports it& replies, the client assumes all is OK, but some intervening NAT has no idea what has happened, and doesn't know what to do with the data connection. fetch doesn't use EPSV for IPv4, just PASV (which even the dumbest NAT supports).
So is there anything to be done with this package?It seems that I'm the only one that suffered this, but why? Is the ftp from platform base system or pkgsrc? If the former, maybe that's the difference.
It's hard to say the package is broken if I'm the only one that sees a problem, but I'm wondering if this package should always use fetch the only server that has the source is misconfigured (or is being a misconfigured NAT).
I'm okay with whatever is decided. The problem is documented and the solution is documented so maybe that's enough.
John