On 16/09/10 01:28, Henrik Nordström wrote:
tis 2010-09-14 klockan 01:23 +0000 skrev Amos Jeffries:
* Squid should be starting with EPSV not EPRT anyway. Check that your
ftp_pasv directive is set to "on" (default), or remove it from the config
altogether.
Shouldn't we start with PASV if it's a IPv4 connection?
There is no big need for EPSV/EPRT in IPv4, and many NATs and Firewalls
have issues tracking the E* requests/responses.
Sure, they are designed to actually be easier for NATs and Firewalls,
and they are, but things do fail if the directives are not understood.
The old PASV/PORT commands are well known for ages, and supported by
virtually every device out there.
This problem is seen on both client and server sides, for both EPSV and
EPRT.
Yes, it's somewhat depressing to still frequently see these issues when
the EPSV and EPRT directives have been official standards track changes
to the FTP protocol for over a decade (1998), but that's the reality of
Internet.
This is the first issue with them in some months (last ones were me
buggering up the v4/v6 connection types used).
This was caused by configuration of ftp_passive to "yes" instead of
"on". Which turned passive off entirely.
Amos
--
Please be using
Current Stable Squid 2.7.STABLE9 or 3.1.8
Beta testers wanted for 3.2.0.2
