QuFirewall Doesn't Block myQNAPcloud access???

[Ponderous]

Thought that a simple test for the effectiveness of the QuFirewall profile rule would be blocking a logon via https://www.myqnapcloud.com /.../ device management /.../ Shared Folder / Login

I was able to thus get external access even though the profile disallowed all but my local network connect IP space (see screenshot; the blacked out is my local address space: W.X.Y.Z/24) .

The QuLog Center / Access Log confirms access granted to external (not W.X.Y.Z/24) IP address, which address is me??? (address range assigned to my router my ISP; can't even see a IPv4 address assigned to the NAS on the Control Panel / System Status / Network Status) Is this my Router with real, QNAP IPv6 address remapped? What?

Does this mean that myqnapcloud utilizes a backdoor to my NAS that circumvents QuFirewall??? Can any SW running on NAS can reach out and similarly circumvent the QuFirewall?

Or is this a simple case of operator error; what am I missing? If not, does QNAP believe that can't be exploited?

(Yes, dosborne, it is looking less and less useful if I can't trust that I can simply configure and expect protection :- ).

[dolbyman]

Are we talking QNAPcloud DDNS (dangerous) or Cloudlink (tunnel)?

[Ponderous]

Tool on NAS desktop shows DDNS along with this text:

You can connect to different network services using the following internet address by changing the protocols. If the FTP server is running, you can access the FTP service using the FTP protocol. The same theory applies to other services such as POP3, SSH, and DNS.

Don't see options....

Don't know exactly what I expected, but I thought it would be something like an external IP address with VPN logging into the NAS. Is the NAS publishing an IP address for QNAP to use and bypassing the firewall entirely?