2.2.3 and FTP Client Proxy Package 0.2 - Microsoft FTP and FTP Client Issues
I don't believe this has been explicitly answered yet on this forum. My apologies if it has. I'm not super familiar with the pfSense setup and interface, so my apologies if I've overlooked something stupid.
I upgraded to 2.2.3 this past weekend. Everything worked fine except a piece of software that uses the Microsoft FTP program to grab files. After digging into it I found out how the FTP proxy was removed and proceeded to install the FTP Client Proxy Package 0.2. Attached the service to the LAN interface and the Microsoft FTP client started working again. Awesome!
Later on in the day I hopped on an FTP connection via Filezilla and it won't connect. It stops and starts and spits out:
Status: Connection established, waiting for welcome message…
Response: 220---------- Welcome to Pure-FTPd [privsep] [TLS] –--------
Response: 220-You are user number 3 of 500 allowed.
Response: 220-Local time is now 13:19. Server port: 21.
Response: 220-This is a private system - No anonymous login
Response: 220 You will be disconnected after 3 minutes of inactivity.
Command: AUTH TLS
Response: 234 AUTH TLS OK.
Status: Initializing TLS...
Error: GnuTLS error -110: The TLS connection was non-properly terminated.
Status: Server did not properly shut down TLS connection
Error: Could not connect to server
If I shut off the FTP Proxy package, everything works fine on the Filezilla end, but the Microsoft FTP portion stops working.
Is there some option to allow both to work freely? Can I direct the FTP Proxy Package to only work on one IP (the one running the batch files running through Microsoft FTP) and just let everything else run without it?
The Microsoft FTP stuff is by some third party software we run and I've already complained to them about this, but they don't seem to really care since I'm the one who "broke" it in the first place.
This isn't a huge issue and one I can work around, but was just curious if there's something simple I can do to make the Microsoft FTP and Filezilla client (or even switching FTP clients is fine, I'm not picky) play nice together.
1/ Every idiot who writes any software around the ftp.exe hyperjunk should be shot.
2/ The proxy CANNOT be used for encrypted FTP.
KOM last edited by
Speaking of Filezilla, I stopped using it ever since the author starting letting SourceForge wrap his installers in shit.