FTP broken again after update to 2.2-RC
-
Well…in my case, for now i've returned to 2.1.5. Ftp connectvity is importante here, our legacy ERP uses standard ftp to update itself...if you're thinking about +- 50 workstations...
-
from https://redmine.pfsense.org/issues/4210
"…not something we're looking into for 2.2 at this point.."Does it means that 2.2 will be released with ftp proxy broken? :o
Can somebody test jftpgw or frox port via pkg add to see if it's an workaround until native ftp proxy get fixed?
-
2.2 has no FTP proxy and will be released without one. It only helped with active mode clients behind NAT anyway, and only with a simple single public IP setup. Passive mode clients, what essentially everything does by default in recent years (minus the Windows command line FTP client) doesn't need a proxy. Servers can be configured easily in a means that doesn't require a proxy. You have to do so with FTPS anyway, which is the only FTP anything you should be using at this point.
Time to move on from FTP, folks.
-
-
Thanks Chris. I do not recomend ftp also, but you know that many sites still use it. :)
-
To the sites that still use it – you would hope atleast it was ftps, which breaks the helper anyway. The helper is need it 2 setups.. Where your wanting your client behind pfsense to use a active connection to public server. Or your running server behind pfsense and you want to allow passive clients.
If client use passive no helper needed, if your running server you would hope you were running ftps anyway which would of required the manual firewall rules anyway because helper could not see the traffic to fix up. So I don't really see this as loss of anything of real function.. And you really shouldn't be using ftp anyway ;)
