However, I got an error message when I tried to use explicit FTP over TLS: I connected to the FTP site using CuteFTP Pro 8.3.3, and it worked fine using plain FTP (no encryption). However, I’m now abandoning that in favour of FileZilla. I’ve been using CuteFTP for several years: I registered for version 1.0 back in 2001, and I’ve been using version 8 since 2007. However, I ran into a few problems when I tested it, which turned out to be partly due to the client software I was using. Destination NAT incoming connections on ports 51000 - 52000 to your FTP server.I’ve recently been setting up a new FTP server, and I wanted it to support FTPS.For the sake of example, let's pick TCP ports 51000 - 52000. You'll also need to set a range of ports for forwarding. You'll need to set the public IP either manually or use an IP discovery mechanism, I think FileZilla has one built-in. The FTP server has to tell the client what public IP to connect back to and on what port. I believe FileZilla has a lot of 'knobs' that you can turn to make this work. Enable the FTP server to establish new connections outbound on ports > 1024įor passive mode, you'll need to handle NAT traversal.Destination NAT the control traffic on port 21 to your FTP server.Here is a list of requirements for active mode: Depending on the client being used that may or may not work. This requires the client to manage traversing NAT. In active mode, FTP requires the client to open a port and the server connects back to the client. If you insist on using FTP and you require it to work over IPv4. All of which can be handled easily by the IPv6 firewall filter. This greatly eases the firewall configuration by only requiring ports to be opened for both passive and active modes.

If you insist on using FTP, you can run it over IPv6. If you insist on sticking with FTP, be prepared for a battle with NAT while learning about FTP.You could save yourself a lot of trouble switching to a more modern protocol like SSH.

Filezilla server sftp ipv6