And finally I take offense to the l33t hackers statement. I already spend over 50+ hours a week on this project and hold a full time job. I have a feeling most of the "l33t hackers" are in this same predicament.
If you need quality answers and are not satisfied with the status quo around here then you need to look into commercial support.
But do me a favor and stop targeting folks that spend all of their free time helping this project. It's not productive and just makes folks want to stop helping that much more....
I apologize. It was a generalization that obviously doesn't apply to all. I was frustrated that the first response to a request was met with rudeness and I know that I shouldn't respond right away when upset. I really do appreciate all of the hard work that goes into this product. It is the best open source firewall I've ever found and I'm thoroughly impressed with the functionality.
I am actually quite experienced in networking and understand how FTP works and why it is such an issue to setup through NAT, etc. I DID search quite a bit for an answer, but perhaps I was not searching for the correct terms.
I have a perfectly working FTP server. Everything's setup just fine. What I was originally wondering was if there is any way, without locking my external IP to a single machine (ie. 1:1 NAT), to have the originating IP address flow through to the FTP server. I understand that this isn't something that is possible using pfSense and port forwarding and the ftphelper, but I thought there may be a feature that I wasn't aware of that would provide this functionality in conjunction with port forwarding.
As is stands, my FTP server works just fine, and I can live with the fact that I don't see the actual IP connecting to the FTP server.
Thank you all for your comments.