I used to run my ftp on a non-standard port, sitting behind a d-link internet gateway. It worked without any problems. The procedure was also clearly outlined in the manual. The NAT function demands that the gateway knows of where to send incoming requests.
This was done in the setup where I told the gateway to link everything incoming (to the real world IP) on port (f eks) 7654 to go to internal IP 192.168.0.2 port 21. That computer then run the server on port 21. I also told the gateway to translate real world IP port 7653 to go to 192.168.0.2 port 20.
Isnīt this possible to do with your gateway? I hardly had anyone that complained about troubles with logging in. There were a few that logged in and then never succeeded to get any dir-listings. After I asked them to toggle between PASV and PORT mode my impression is that they overcame the trouble. (Or maybe they gave in?)
Are there other experiences?
The (few) problems was not at the NAT/gateway (D-Link) nor at the server (RaidenFTPD) but rather with some ftp-clients. At least this is what I think. Or maybe I wish that this was the situation, I donīt know for sure as I didnīt log in myself from the outside more than at one single occassion.
The problem is interestening as running your own server sometimes is the only solution to actually get stuff. I wish everyone run a small private server...
And maybe I should install one myself again just for the feeling if not for something else.
.unicorn
Threaded Mode
