WordPress and FTPing to and from it.

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.