Search squid archive

Re: Native FTP relay: connection closes (?) after 'cannot assign requested address' error

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Actually, a PASV-handling logic looks a bit strange to me. In
Ftp::Server::handlePasvReply() there is a comment:

"In interception setups, we combine remote server address with a local port
number and hope that traffic will be redirected to us."

How is it supposed to work? A client receives server's IP and squid's port
and tries to make a connection, which obviously ends with ECONNREFUSED. I do
not have any idea on how a traffic could be redirected to squid (redirecting
everything from A to B is not an option). Also, why squid needs to intercept
a data connection?

If I hardcode one of squid's IP in handlePasvReply(), everything works fine.
However I am not sure if it is a correct way because a client opens a data
connection not to an FTP server...




--
View this message in context: http://squid-web-proxy-cache.1019090.n4.nabble.com/Native-FTP-relay-connection-closes-after-cannot-assign-requested-address-error-tp4681208p4681258.html
Sent from the Squid - Users mailing list archive at Nabble.com.
_______________________________________________
squid-users mailing list
squid-users@xxxxxxxxxxxxxxxxxxxxx
http://lists.squid-cache.org/listinfo/squid-users




[Index of Archives]     [Linux Audio Users]     [Samba]     [Big List of Linux Books]     [Linux USB]     [Yosemite News]

  Powered by Linux