QUOTE(xxboxx @ Jan 8 2021, 09:57 PM)
Hey, thanks for the white paper. Now I understand more how QuickConnect works.
If there's DDNS and DSM port is open, QuickConnect will redirect to DDNS domain.
If there's no DDNS but DSM port is open, QuickConnect will redirect to my public ip.
The problem is even when there's no DDNS, my public ip is still exposed due to QuickConnect will redirect to it.
1 solution I found is port forward unused port such as 5003. When I need direct connection I change DSM port to 5003 and change back to default port when finish use.
If use QuickConnect relay server max speed about 15 Mb/s, good enough for tens of MB files transfer.
That's why is worthwhile to get a domain. set up your cname to point to your ddns. setup reverse proxy with the certificates. you are golden. quickconnect can't allow you to access your docker apps only synology ones which is a major downside. quickconnect file transfers are way too slow, another downside.If there's DDNS and DSM port is open, QuickConnect will redirect to DDNS domain.
If there's no DDNS but DSM port is open, QuickConnect will redirect to my public ip.
The problem is even when there's no DDNS, my public ip is still exposed due to QuickConnect will redirect to it.
1 solution I found is port forward unused port such as 5003. When I need direct connection I change DSM port to 5003 and change back to default port when finish use.
If use QuickConnect relay server max speed about 15 Mb/s, good enough for tens of MB files transfer.
This post has been edited by mintgadget: Jan 9 2021, 07:05 AM
Jan 9 2021, 07:02 AM
Quote
0.2863sec
0.59
6 queries
GZIP Disabled