Hi! Thanks for your report! This is a known and fixed bug - I'll find the patched one on: http://www.suse.de/~mt/proxy-suite/fwproxy-1.7tp4-0.src.rpm (it is the ftp-daemon.c.dif patch inside of the src.rpm) I mean, there will be a new version tommorrow - I'm doing some autoconfig cleanup today, so it catches some problems with Freebsd, Solaris7 and perhaps HP-UX... On Tue, Nov 07, 2000 at 04:03:03PM -0500, rcotrone@weebotech.com wrote:
Hello all, First of all I should thank you for doing a great job on the ftp proxy. It was a good idea and it helped me out of a huge jam.
The story...
Our company is moving our data center and some of our customers did not have their T1 lines to the new data center in time for our move.
Through the use of your program I was able to fake the customers out and allow them to access our new hosts without any changes to their network configuration. When dealing with huge customers like Fidelity and Citibank, who can not get things done in a rapid time frame, tools like these help. So Kudos.. Your application has been put through the paces in many ways.
The strange sitatuation... I think I may have run across a bug with the FW-PROXY Suite program.
I have a new configuration I'm building where I will have 8 network adapters in one machine to front end another set of customers. (Same situation above, but caused by the telephone company strike in the summer). Each customer as a completely different network so I'm going to set 1 NIC per customer with one set of addressing per customer and proxy them into our FTP server.
During my testing I configured the FTP proxy to run in daemon mode and bind to a specific address. The situation I'm having is interference from multiple ftp's.
Example. FTP through proxy to one location sending a 17MB file. FTP through proxy to another location sending a 1 MB file.
When the small transmission (or connection ends "quits"). It terminates what ever other connections are present through the proxy's IP that is binded. I have not tested to another bound address yet.
Note this does not happen in inetd mode.
I'm not sure if anyone is even interested in reviewing this situation, I figured I would try anyway. I've attached a config and a startup script I use to fire off the daemon.
If you need my assistance in any way, such as debug dumps, let me know.
For now I'm considering using xinetd to capture incoming connections and spawning the fw proxy server that way.
Any assistance is greatly appreciated. Thanks.
--
Gruesse,
Marius Tomaschewski