[MyQnapCloud]force Port mapping by itself:ExtPort/ExtSSLPort

[father_mande]

Hi,
EDIT corrected after a big error about the "suspect" ... thanks to schumaku

I am fall in trouble accessing my QNAP from external after CloudLink have been installed ... (even if not directly linked to this fonction ...)
After analyse :

QNAP have a good functionality BEFORE MyQnapCloud + CloudLink (hidden) BUT not used for now ... except manually
... it's additional parameters in uLinux.conf named :
ExtPort, ExtSSLPort for Web Admin, and Web server
HOW : this Port are use to replace (by Upnpn IGD mapping) the port defined (for ex. default) if they are already used ...
... so for ex. if 443 is define for Admin SSL and 443 is already use (by another server, QNAP, etc.) and ExtSSLPort = 4443
so unpnc client send a request to
MAP port 4443 (external view) to QNAP 443 internal port

... if MyQnapCloud after cloudlink install (I don't know before) identify the conflict (Port already forwarded in the router/box ... myQnapCloudGENERATE ITSELF a ExtSSLPort starting with 8082

BUT seem than MyQnapCloud can do sometimes a false analyse ... and force the MAPPING and replace by itself the forwarding ...

ALSO MyQnapCloud display in router the mapping and inform myqnapcloud server ... so IF YOU USE MyQnapCloud only to access your QNAP ... it's O.K. BUT if you try to use by yourself ... and don't identify the auto-mapping of MyQnapCloud... you fall in error

On my system ...
Web SSL port is 7443 (unique in my network) and Web SSL is 8743 (unique in my network) BUT auto mapped (without information) to 8082 and 8083
myqnapcloud access work ... but direct access (before I understand) NOT ...

So take attention ... I think it's possible to clear the Ext[SSL]Port ... but don't know if MyQnapCloudforce again news Ports ... and due to the fact I am in travel ... I can do lot of tests ...

I think better if MyQnapCloud can add a checkbox to said : Admin authorize MyQnapCloud to auto-map Port if they are used ...
because for my case ... it's a FALSE analyse ... so mapping is not needed ... forwarding is enough ...

Philippe.
NB I will open a ticket about this ... BUT inform the forum about ...

[father_mande]

Hi,

For your information ...

Changing original Port, apply, redo to return to previous value, apply ... then go to router auto configuration, uncheck all, apply reselect (new value (correct) are displayed) ... then apply ...

OK now all ports are correct ... and forwarding is used v.s. mapping ...

Philippe.

[schumaku]

Philippe,

CloudLink does not make use of any port forwarding, so no UPnP IGD controls at all.

Regards,
-Kurt

[father_mande]

Hi,

OUPSS! typo ... it's myqnapcloud agent or what name you want ...

Just change become after cloudink installation (I have my trace before and after ... ) ... ... I will make change in my message ...

Apologize for stupid error due to direct write without enough reread ...

hilippe.

[schumaku]

The"feature" i's the Automatic Router Configuration, a dedicated (sub-)control of myQNAPcloud.com