Hi there, first i want to say thanks for the FAST Help of my last posting. But i can´t say that´s all. When i start the ftp-proxy i get the following error message : ftp-proxy [3437] <01/10-17:33:19> TECH-ERR can't get peername for socket 0 and the ftp-proxy is death. The DestinationAddress is an virtual Adress ( only in the intranet ), but i think that´s not the problem. With best regards Olaf Matthaei -- GfI Gesellschaft für Information und Datenverarbeitung matthaei@narz.de Tel. : 0421/5762 115 Fax : 0421/5762 299
On Mon, 10 Jan 2000, O. Matthaei wrote:
But i can´t say that´s all. When i start the ftp-proxy i get the following error message : ftp-proxy [3437] <01/10-17:33:19> TECH-ERR can't get peername for socket 0 and the ftp-proxy is death. The DestinationAddress is an virtual Adress ( only in the intranet ), but i think that´s not the problem.
Olaf, first of all, let me apologize for not answering earlier. I was on holidays, just returned, and will be on a business trip next week. After that I can offer more help. If you want to use FTP-Proxy for outbound traffic (internal user to internet servers, which I assume you want), it works but has some constraints. You have to include a "AllowMagicUser yes" in the config file and the users have to include the target FTP server in the USER name that they present to the Login prompt of the FTP-Proxy. [BTW: If anyone knows of a better way to do this, please let me know.]
With best regards
Olaf Matthaei
Volker -- Volker Wiegand Phone: +49 (0) 6196 / 50951-24 SuSE Rhein/Main AG Fax: +49 (0) 6196 / 40 96 07 Mergenthalerallee 45-47 Mobile: +49 (0) 179 / 292 66 76 D-65760 Eschborn E-Mail: Volker.Wiegand@suse.de ++ Only users lose drugs. Or was it the other way round? ++
Volker Wiegand wrote:
they present to the Login prompt of the FTP-Proxy. [BTW: If anyone knows of a better way to do this, please let me know.]
Wether this is possible as a quick hack, remains to be seen, but.... transparent proxying should route all outgoing requests to port 21 to the local ftp-proxy. Even though these requests end up on the firewall, the dest IP address is not the firewall's IP address. The proxy program should then ask the kernel waht the dest IP address acutally IS. Roger. -- ** R.E.Wolff@BitWizard.nl ** http://www.BitWizard.nl/ ** +31-15-2137555 ** *-- BitWizard writes Linux device drivers for any device you may have! --* "I didn't say it was your fault. I said I was going to blame it on you."
participants (3)
-
O. Matthaei
-
R.E.Wolff@BitWizard.nl
-
Volker Wiegand