Hi @Pink_Waters 

Pink_Waters wrote

  @Clive_A 

To be frank I am not sure if there is a language barrier or what but most of what you say make less sense the more you elaborate.

Are you saying the fix will come in firmware 5.15ish for the router? If the router firmware right now is on v1 that means the fix will be here in 2 years give or take? What are we talking about here?

 

Also I did some digging on this issue and seems like when I go to my local synology https url. While it's showing me referer check failed  , the ssl cert is tplink. So I am not sure, is the gateway intercepting the ssl connection?

V5.15.X.Y refers to a period of time. The firmware is not guaranteed in a specific date. We are aware of the issue and will provide a fix in the firmware update during this period. That's what it means.

If you are new, see the request page. We do not provide any specific date or version anymore due to some of you complained about the delay of the firmware release. Since then, we no longer guarantee a timeline.

The dev team is not only on a single case. They handle several at the same time. Debug, remote, and work with the firmware development. And we also have national holidays from time to time.

Dev also works with different teams as well. Marketing, contract users, customized firmware from the contract, and local sub-companies.

No.
Referer field verification is performed in the standalone backend uhttpd: Referer verification checks whether the referer field in the http request is consistent with the dst ip of the message. If they are inconsistent, the verification fails.

Suppose you understand what it means. That's the reason we have been diagnosed.

Hi @Pink_Waters 

Pink_Waters wrote

  @Clive_A Oh I completely get how it is like for the dev team and all. I am not trying to get a date out of you. I am more surprised that a bug of that magnitude and impact can still be not patched so far. I know it has been reported before for a different router model of the omada gateway line up. It only make sense that the patch should have been tested for and implemented against other models since basically they share the same firmware logic. Right at this moment i cannot at all use any synology remote apps to connect back to my nas from wan due to this issue, since i can only connect to my nas by ip and not FQDN anymore.

Referer check was due to a security fix in early firmware which leads to the problem you have now.

But I recall this security requirement was not forced on all models. That's why there is only a little feedback on this issue. Just two models have experienced this issue.