I assume you wanted to talk of you LAN, not the WAN. Theefore, the general valid proposal is- beyond the pure ftp(-control) port - to forard the Passive FTP Port Range (for TCP) as configured in the NAS ftp Admin Web UI, to the NAS LAN IP-address, too. Tis is somewhat limiting the value of na FTP-ALG again. ftpes = FTP with SSL/TLS (Explicit)) session. FileZilla Server List of ports betaeen 5. Port Forwarding Remote Web Access LAN port 5003 5000 Traffic Monitor Destination IP 192.168.0.185 192.168.0.33. However - the FTP-ALG can only listen on a plain text ftp control session - not on an encrypted (ie. Router P: 19216801 Hostname: mygateway FW version: 17.20320 USB DE-CT LAN 1920B. Some more sophisticated routers allow to define additional ports, where the FTP-ALG does listen. Tis ALG is listening on the ftp-control channel (on port 21/TCP), and does open/close the negotiated ftp-data ports. Some sophisticated NAT routers are coming with an FTP-ALG - an ftp application layer gateway. When using passive, the NAS ftp server configured passive data port range is used.
As the cleint does not know about the configuration and the environment, passive is almost mandatory. First please be aware ftp is using more than just the one ftp (ftp-control) port - there are ftp-data port(s) - these are either deined by the client (active mode) or by the server (passive mode). The most misunderstand protocol is ftp - especially when it comes to NAT.
0 kommentar(er)
