"Force active mode to use local IP" has no effect

I tick "Force active mode to use local IP" on a LAN host (my NAS) and when I ftp to it I still see in the log:

[R] Connecting to qnap ftp -> DNS=qnap IP=192.168.0.106 PORT=21
[R] Connected to qnap ftp
[R] 220 NASFTPD Turbo station 2.x 1.3.2e Server (ProFTPD) [192.168.0.106]
[R] USER admin
[R] 331 Password required for admin
[R] PASS (hidden)
[R] 230 User admin logged in
[R] SYST
[R] 215 UNIX Type: L8
[R] FEAT
[R] 211-Features:
[R] MDTM
[R] MFMT
[R] MFF modify;UNIX.group;UNIX.mode;
[R] MLST modify*;perm*;size*;type*;unique*;UNIX.group*;UNIX .mode*;UNIX.owner*;
[R] LANG en-US*
[R] REST STREAM
[R] SIZE
[R] 211 End
[R] PWD
[R] 257 "/" is the current directory
[R] CWD Qrecordings
[R] 250 CWD command successful
[R] PWD
[R] 257 "/Qrecordings" is the current directory
[R] Listening on PORT: 4802, Waiting for connection.
[R] Requesting IP Lookup from http://iplookup.flashfxp.com
[R] Returned: 220.253.52.24
[R] PORT 220,253,52,24,18,194
[R] 200 PORT command successful
[R] MLSD
[R] 150 Opening ASCII mode data connection for MLSD
[R] 226 Transfer complete
[R] List Complete: 106 bytes in 0.60 seconds (0.2 KB/s)

Would be great if you could fix this, would increase throughput when transferring many small files as they wouldn't be hammering my router and instead would directly connect to the NAS.

Also, this should probably be enabled by default if the host is in a LAN subnet (10.0.0.0 - 10.255.255.255, 172.16.0.0 - 172.31.255.255 or 192.168.0.0 - 192.168.255.255)

In your setup you have "Force active mode to use local IP" checked and you're using
http://iplookup.flashfxp.com

In this context FlashFXP is treating your WAN IP as your local IP.

Since you're connecting to a lan based server the solution would be to uncheck the per-site option Force active mode to use local IP instead of check it.

I can see how this might be confusing and the documentation isn't clear on this.

Hmm you are right, you should probably change that to "external ip" instead of "local ip" as I think most people would assume local ip is the ip reported by the local system rather than an external site, it's like reverse terminology! But yeah force unticking it on site manager has fixed my problem, thanks

Yes I agree, a correction is planned for the next release.

This has been reworded in build 1535