NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
WordPress and FTPing to and from it.
Using Windows 10 and CoreFTP, having setup FTP on my ReadyNAS RN516. Running CoreFTP (as the ReadyNAS admin user) it seems to connect okay but does not show any files whatsoever at the other end....
If you only want FTP on the local LAN then there is no need to figure out what masquerading does. But I'll tell you anyway :smileysurprised:
With passive mode FTP, the server sends the client the IP address and port numbers for the data connections. If the NAS has a public internet address, then that is fine. But when your FTP server is behind a NAT, then your client can't use the local IP address over the internet. Instead it needs to use the public IP address of the NAS router.
There are two solutions - one in the client, and one in the server.
Some clients detect that the IP address isn't routable (e.g., is 192.168.xxx.xxx or one of the other private address spaces), and simply substitute the public address of the control connection. Basically they ignore the IP address they get from the server, and only use the port number. FileZilla does that (so I don't need masquerading in the server).
The server solution is simply to sent the router IP instead of the local LAN IP. That's what masquerading does. You enter a DNS name or IP address, and it uses that instead of the local LAN address.
BaJohn wrote:
My goal is to FTP to the WordPress folder /apps/wordpress/web/wp-content/ to easily upload and change items in WordPress on the NAS.
How do I arrange a share that covers that folder?
The best way is to create a wordpress share on the NAS, and copy the /apps/wordpress/web/wp-content/ contents to it. Then create a symlink in /apps/wordpress/web/ called wp-content that points to the new share (deleting the wp-content folder).
Then you have all the normal access controls on the folder.
Hi BaJohn,
Just tested this with the following settings (port forwarded 21 in my firewall) and it worked fine.
Hope this helps!
Kind regards,
BrianL
NETGEAR Community Team
If the goal is over-the-internet access, then I'd suggest a much smaller range of passive ports, within the range 49152-65535. 49152 is the lowest port number reserved for private use. I find that 4 passive ports are enough for a single user connection. If your client allows for multiple data connections, make sure that you have it configured as <= the number of ports you have forwarded.
Some clients don't need masquerading (Brian's didn't if his configuration worked through a NAT). If you don't need it, then leave the setting alone. If you do, then set masquerade to match your ddns address.
Hi BrainL and StephenB
I will have another go later today .....
Most of my FTP's are Internet use and this is the first time I have had a problem, over the LAN:)
Between the 2 of you I am confused over what the 'masqerading' does.
I have not used it so far, but will do so, BUT what do I put in there, as I have seen on other sites they seem to put any old rubbish in there as if it doesn't matter.
That is why I didn't use it (default not used anyway) before. If you can put rubbish in ther, why would it make a difference?
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
