10.20.*.* really shouldn’t be on your wan, that’s not routable. Also, 214*256+167=54951, outside the range you say you dictated in the conf (49500-52500)
I don’t think PFSense is going to provide you an ftp proxy, both because you’re not using port 21, and this document: https://doc.pfsense.org/index.php/FTP_without_a_Proxy I’m not convinced that ProFTPd is actually using your conf. I think you’re now fighting with ProFTPd, not PFSense. wireshark (or Microsoft Network Monitor) is your friend. ED > On 2015, Jul 7, at 10:49 PM, Ryan Coleman <ryan.cole...@cwis.biz> wrote: > > Yes. > > ProFTPd reports the masquerading address properly when starting the service. > > — > Ryan > > >> On Jul 7, 2015, at 5:14 PM, Steve Yates <st...@teamits.com> wrote: >> >> Ryan Coleman wrote on Tue, Jul 7 2015 at 4:48 pm: >> >>>> http://www.proftpd.org/docs/directives/linked/config_ref_MasqueradeAddress.html >> >>> Yep - I’m using that. >> >>> Command: PORT 10,20,1,49,214,167 >> >> Pretty sure this would be IP 10.20.1.49, not the public one...is >> 10.20.1.x on your WAN? >> >> -- >> >> Steve Yates >> ITS, Inc. >> >> >> _______________________________________________ >> pfSense mailing list >> https://lists.pfsense.org/mailman/listinfo/list >> Support the project with Gold! https://pfsense.org/gold > > _______________________________________________ > pfSense mailing list > https://lists.pfsense.org/mailman/listinfo/list > Support the project with Gold! https://pfsense.org/gold _______________________________________________ pfSense mailing list https://lists.pfsense.org/mailman/listinfo/list Support the project with Gold! https://pfsense.org/gold
