NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Help with RAX20 and port forwarding FTP
I just got this router today and have it setup through a Xfinity Gateway in bridged mode. Previous to this on the Gateway, I was able to port forward my Raspberry PI FTP server (port 21) and access i...
There is only one port 21/TCP ... if the router is configured on ReadyShare to FTP, port 21/TCP is obviously already occupied. Disable the FTP service on the advanced ReadyShare settings.
I would expect that this does free up port 21/TCP on the WAN interface to become available for the port forwarding. Netgear has an old flaw on port 443 (the default https one) - even with the https remote access service and https ReadyShare disabled or relocated to an alternate port, the port 443/TCP isn't becoming available for port forwarding.
Something general ref. ftp: These routers (including your previous one) have an application layer gateway (ALG) listening on the standard ports, e.g. 21/TCP for FTP on the handshake communication for the passive connection, dynamically adding a port forward to that port. If using FTPS (encryption) the ALG can't work so you need to configure the passive port range configured on the ftp server in a port forward range.
This is just an update on trying to get it working. I'm still unable to get it to port forward but if I have the ReadyShare setup (To a USB drive plugged into the Router) I have no problem with logging into that with FTP and port 21. My only guess is that Port forwarding Port 21 Is only optional when ReadyShare is on and has no option to assign it to any other device. I've tried literally everthing I can think of to try and get this working.
There is only one port 21/TCP ... if the router is configured on ReadyShare to FTP, port 21/TCP is obviously already occupied. Disable the FTP service on the advanced ReadyShare settings.
I would expect that this does free up port 21/TCP on the WAN interface to become available for the port forwarding. Netgear has an old flaw on port 443 (the default https one) - even with the https remote access service and https ReadyShare disabled or relocated to an alternate port, the port 443/TCP isn't becoming available for port forwarding.
Something general ref. ftp: These routers (including your previous one) have an application layer gateway (ALG) listening on the standard ports, e.g. 21/TCP for FTP on the handshake communication for the passive connection, dynamically adding a port forward to that port. If using FTPS (encryption) the ALG can't work so you need to configure the passive port range configured on the ftp server in a port forward range.
Thank you.I was able to get it sorted out with what you mentionted.
kawivukan wrote:Thank you.I was able to get it sorted out with what you mentionted.
Disabled the FTP on the ReadyShare was sufficient?
Time permitting, if you have the ability to set-up a test e.g. a https on the RasPi (or any other service operating on 443/TCP like telnet for a test), I would like to learn if if the RAX, e.g. your RAX20 does still reserve 443/TCP internally, or of 443/TCP is freely available (if removed from ReadyShare and the remote access). Following the test, do't forget to disable the test service or it's port forward again.
TIA,
-Kurt
I posted a reply but it didn't show up for some reason. I'll try again later because it was limiting my message replys for 60 minutes or something.